From: Jiri Slaby <jslaby@suse.cz>
To: lists+linux-kernel@corpit.ru
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
James.Bottomley@HansenPartnership.com,
Jens Axboe <axboe@kernel.dk>,
greg@kroah.com, stable@kernel.org, jejb@parisc-linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [stable] apparent regression (crash) - 2.6.38.6
Date: Fri, 03 Jun 2011 09:15:49 +0200 [thread overview]
Message-ID: <4DE88A25.2040300@suse.cz> (raw)
In-Reply-To: <4DE888BB.8000008@msgid.corpit.ru>
On 06/03/2011 09:09 AM, lists+linux-kernel@corpit.ru wrote:
> 03.06.2011 11:01, Michael Tokarev wrote:
>> commit 2e8532e0a9ee1d25b279ac78ee8ce31701e2aa15
>> Author: Michael Tokarev <mjt@tls.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
next prev parent reply other threads:[~2011-06-03 7:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 19:55 apparent regression (crash) - 2.6.38.6 Michael Tokarev
2011-05-11 6:30 ` Jiri Slaby
2011-05-11 19:19 ` James Bottomley
2011-05-11 19:31 ` Michael Tokarev
2011-05-11 20:22 ` Michael Tokarev
2011-05-19 0:25 ` [stable] " Greg KH
2011-05-11 19:34 ` Greg KH
2011-05-19 0:25 ` Greg KH
2011-05-19 3:39 ` James Bottomley
2011-05-19 8:20 ` Arkadiusz Miskiewicz
2011-06-01 12:34 ` Atsushi Nemoto
2011-06-03 7:01 ` Michael Tokarev
2011-06-03 7:09 ` lists+linux-kernel
2011-06-03 7:15 ` Jiri Slaby [this message]
2011-06-04 11:38 ` Atsushi Nemoto
2011-05-11 7:58 ` Wolfgang Walter
-- strict thread matches above, loose matches on Subject: below --
2011-05-24 13:06 [stable] " Paul Slootman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DE88A25.2040300@suse.cz \
--to=jslaby@suse.cz \
--cc=James.Bottomley@HansenPartnership.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=axboe@kernel.dk \
--cc=greg@kroah.com \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists+linux-kernel@corpit.ru \
--cc=stable@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox