linux-kernel - Re: [stable] apparent regression (crash)

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: <4DE88A25.2040300@suse.cz>
Date:	Fri, 03 Jun 2011 09:15:49 +0200
From:	Jiri Slaby <jslaby@...e.cz>
To:	lists+linux-kernel@...pit.ru
CC:	Atsushi Nemoto <anemo@....ocn.ne.jp>,
	James.Bottomley@...senPartnership.com,
	Jens Axboe <axboe@...nel.dk>, greg@...ah.com,
	stable@...nel.org, jejb@...isc-linux.org,
	linux-kernel@...r.kernel.org
Subject: Re: [stable] apparent regression (crash) - 2.6.38.6

On 06/03/2011 09:09 AM, lists+linux-kernel@...pit.ru wrote:
> 03.06.2011 11:01, Michael Tokarev wrote:
>> commit 2e8532e0a9ee1d25b279ac78ee8ce31701e2aa15
>> Author: Michael Tokarev <mjt@....msk.ru>
>> Date:   Fri Jun 3 10:50:49 2011 +0400
>>
>>     block: add proper state guards to elv_queue_empty()
>>
>>     Like in 0a58e077eb600d1efd7e54ad9926a75a39d7f8ae (backported to
>>     stable 2.6.38 as 0a58e077eb600d1efd7e54ad9926a75a39d7f8ae) which
>>     fixes this for __elv_next_request(), as reported by Atsushi Nemoto,
>>     elv_queue_empty() also needs to check for dead queue condition
>>     before touchin elevator.
>>
>>     elv_queue_empty() has been removed upstream so this is only applicable
>>     for versions prior to 2.6.39, including 2.6.32-longterm.
> 
> Um, i'm not sure about this one -- 2.6.32 does not have
> other pieces of this puzzle (and 2.6.38.8 was the last
> in the 2.6.38.y series).

And what about .33 and .34 which are longterm too? Does this apply to them?

thanks,
-- 
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/