linux-kernel - Re: [GIT PULL] ext4 bug fixes for 4.6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFzfmHptveL=y1C5VidQjjiSekcCq=-fg1Z-W6Szog-VRA@mail.gmail.com>
Date:	Sun, 10 Apr 2016 13:48:39 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg Thelen <gthelen@...gle.com>
Cc:	"Theodore Ts'o" <tytso@....edu>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [GIT PULL] ext4 bug fixes for 4.6

On Sun, Apr 10, 2016 at 1:29 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> I think the right choice might be to
>
>  (a) revert that patch (or just change the signal_pending() into
> fatal_signal_pending())
>
>  (b) to get the latency advantage, do something like this:

The attached patch is actually tested and seems to fix the issue.

I do not have a good way to check the latency of signal delivery and I
didn't check if the signal_pending() actually ever triggers, but your
test-case that showed the problem before seems to be fine with it.

                     Linus