linux-ext4 - Re: what happened with dccaf33fa37 "ext4: flush any pending end

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]

Date:	Mon, 19 Mar 2012 21:21:51 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Jiaying Zhang <jiayingz@...gle.com>
CC:	Theodore Tso <tytso@...gle.com>, gregkh@...uxfoundation.org,
	stable@...nel.org, linux-ext4@...r.kernel.org,
	Theodore Ts'o <tytso@....edu>, Jan Kara <jack@...e.cz>
Subject: Re: what happened with dccaf33fa37 "ext4: flush any pending end_io
 requests before DIO" for 3.0?

19.03.2012 21:10, Jiaying Zhang wrote:
> On Mon, Mar 19, 2012 at 9:42 AM, Jan Kara<jack@...e.cz>  wrote:
>> On Sat 17-03-12 13:31:30, Michael Tokarev wrote:
>>> Ping?
>>>
>>> Maybe just a one-line reply isn't THAT difficult?
> Sorry for the slow response. I am not sure what happened to this patch.
> Ted, do you know what we need to do to get this patch to the
> stable release?

For reference, attached is the version I use locally since last August.

...
>>>>> There was one more ext4 commit at that time, which made its way into
>>>>> stable but this one did not.
>>>>>
>>>>> I wonder if the reason for that was the fact that it needed a small
>>>>> "backport" for 3.0, since in 3.1+ the code has been moved into another
>>>>> file, and the context is slightly different.  In that case, attached
>>>>> is the "backport" which we use with 3.0.x since that time.

Thanks,

/mjt

View attachment "ext4-flush-any-pending-end_io-requests-before-DIO-reads-w-dioread_nolock-dccaf33fa3.diff" of type "text/x-diff" (2056 bytes)