From: Jens Axboe <jaxboe@fusionio.com>
To: Shaun Ruffell <sruffell@digium.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Christoph Hellwig <hch@lst.de>,
Neil Brown <neilb@suse.de>,
"David S. Miller" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"kay.sievers@vrfy.org" <kay.sievers@vrfy.org>
Subject: Re: [PATCH 1/2] block: don't propagate unlisted DISK_EVENTs to userland
Date: Thu, 21 Apr 2011 20:10:30 +0200 [thread overview]
Message-ID: <4DB07316.5000405@fusionio.com> (raw)
In-Reply-To: <4DB0714B.90701@digium.com>
On 2011-04-21 20:02, Shaun Ruffell wrote:
> On 04/21/2011 12:31 PM, Jens Axboe wrote:
>> On 2011-04-21 19:25, Linus Torvalds wrote:
>>> Should I take these as patches, or through Jens/David/Who?
>>>
>>> I'll happily take them as patches, but I'd also like to hear
>>> confirmation from the people who saw the lock-up that it's gone now..
>>
>> I'm pulling them in now, with the elevator patch referenced in the IO
>> scheduler switch email. I've verified that it fixes the ide-cd bug for
>> me.
>
> Jens, Tejun,
>
> I was never seeing a lockup, just the stream of events, but I applied the
> two patches on top of mainline (584f790467 from yesterday) and do not see
> any issues on the system where I first noticed the constant events [1].
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=33342
Great, thanks for testing!
--
Jens Axboe
prev parent reply other threads:[~2011-04-21 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 17:08 [PATCH 1/2] block: don't propagate unlisted DISK_EVENTs to userland Tejun Heo
2011-04-21 17:09 ` [PATCH 2/2] ide: unexport DISK_EVENT_MEDIA_CHANGE for ide-gd and ide-cd Tejun Heo
2011-04-21 17:14 ` David Miller
2011-04-21 17:25 ` [PATCH 1/2] block: don't propagate unlisted DISK_EVENTs to userland Linus Torvalds
2011-04-21 17:27 ` David Miller
2011-04-21 17:31 ` Jens Axboe
2011-04-21 17:46 ` Jens Axboe
2011-04-21 18:02 ` Shaun Ruffell
2011-04-21 18:10 ` Jens Axboe [this message]
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=4DB07316.5000405@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=sruffell@digium.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.