public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Tejun Heo <tj@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kay.sievers@vrfy.org" <kay.sievers@vrfy.org>,
	"hch@infradead.org" <hch@infradead.org>
Subject: Re: block: Fix oops caused by __blkdev_get() calling  disk_unblock_events() with invalid @disk
Date: Wed, 9 Mar 2011 20:16:02 +0100	[thread overview]
Message-ID: <4D77D1F2.2030104@fusionio.com> (raw)
In-Reply-To: <20110309185909.GA13729@mtj.dyndns.org>

On 2011-03-09 19:59, Tejun Heo wrote:
> On Wed, Mar 09, 2011 at 07:26:44PM +0100, Jens Axboe wrote:
>>>   This is fixed by moving reference putting after open success is
>>>   determined and not clearing @disk to %NULL.  On success, @disk is
>>>   valid because there is another opener holding reference to it.  On
>>>   failure, the references are put after disk_unblock_events() is
>>>   called.
>>
>> Thanks, applied. A bit unfortunate to have a 100% crasher in the tree,
>> though. Will suck for bisects.
> 
> Yeah, that does suck.  I folded in the fix to the offending commit and
> regenerated the tree in case you want to rebase the tree.
> 
>   ssh://master.kernel.org/pub/scm/linux/kernel/git/tj/misc.git disk-event-convert-fixed

Thanks, but it's pretty deep in at this point. I'll take a look at it.


-- 
Jens Axboe


      reply	other threads:[~2011-03-09 19:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09  9:13 [PATCHSET] block: Convert block drivers to ->check_events(), take#2 Tejun Heo
2011-03-09  9:13 ` [PATCH 01/16] block: Don't implicitly trigger event check on disk_unblock_events() Tejun Heo
2011-03-09  9:13 ` [PATCH 02/16] block: Don't check events on close unless it was blocked Tejun Heo
2011-03-09  9:13 ` [PATCH 03/16] block: Don't check events while open is in progress Tejun Heo
2011-03-09  9:13 ` [PATCH 04/16] ide: Convert to bdops->check_events() Tejun Heo
2011-03-09 22:17   ` David Miller
2011-03-09  9:13 ` [PATCH 05/16] floppy,{ami|ata}flop: " Tejun Heo
2011-03-09  9:13 ` [PATCH 06/16] gdrom,viocd: " Tejun Heo
2011-03-09  9:13 ` [PATCH 07/16] paride: " Tejun Heo
2011-03-09  9:13 ` [PATCH 08/16] dac960: " Tejun Heo
2011-03-09  9:13 ` [PATCH 09/16] swim[3]: " Tejun Heo
2011-03-10  0:10   ` Benjamin Herrenschmidt
2011-03-09  9:13 ` [PATCH 10/16] ub: " Tejun Heo
2011-03-09 16:46   ` Pete Zaitcev
2011-03-09 16:58     ` Tejun Heo
2011-03-09  9:13 ` [PATCH 11/16] xsysace: " Tejun Heo
2011-03-09  9:13 ` [PATCH 12/16] i2o_block: " Tejun Heo
2011-03-09  9:13 ` [PATCH 13/16] s390/tape_block: " Tejun Heo
2011-03-09  9:13 ` [PATCH 14/16] umem: Drop dummy ->media_changed() Tejun Heo
2011-03-09  9:13 ` [PATCH 15/16] pktcdvd: Convert to bdops->check_events() Tejun Heo
2011-03-09  9:13 ` [PATCH 16/16] staging: " Tejun Heo
2011-03-09  9:20 ` [PATCHSET] block: Convert block drivers to ->check_events(), take#2 Jens Axboe
2011-03-09 14:49   ` Jens Axboe
2011-03-09 15:38     ` block: Fix oops caused by __blkdev_get() calling disk_unblock_events() with invalid @disk Tejun Heo
2011-03-09 18:26       ` Jens Axboe
2011-03-09 18:59         ` Tejun Heo
2011-03-09 19:16           ` 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=4D77D1F2.2030104@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=hch@infradead.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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