From: Jens Axboe <jaxboe@fusionio.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Parag Warudkar <parag.lkml@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] SCSI IOCTL: Check for device deletion [was Re: __elv_add_request OOPS]
Date: Fri, 27 May 2011 07:43:35 +0200 [thread overview]
Message-ID: <4DDF3A07.7040106@fusionio.com> (raw)
In-Reply-To: <1306468385.4048.73.camel@mulgrave.site>
On 2011-05-27 05:53, James Bottomley wrote:
> On Wed, 2011-05-25 at 15:52 -0500, James Bottomley wrote:
>> On Wed, 2011-05-25 at 16:42 -0400, Parag Warudkar wrote:
>>> Yeah - that makes sense. By that logic, looks like we can only disallow
>>> for SDEV_DEL (if we decide to do that check here).
>>
>> I don't think this is the root cause. I think q is non-NULL but has
>> already been released, so we're just getting a NULL deref on the actual
>> list head.
>>
>> Does this fix it? It adds the refcounting at approximately the correct
>> places. Of course, we'll now be trying elevator operations on an extant
>> queue but one whose elevator functions have been destroyed, so there are
>> probably additional state guards to place.
>>
>> James
>>
>> ---
>>
>> diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
>> index 58584dc..44e8ca3 100644
>> --- a/drivers/scsi/scsi_scan.c
>> +++ b/drivers/scsi/scsi_scan.c
>> @@ -297,7 +297,7 @@ static struct scsi_device *scsi_alloc_sdev(struct scsi_target *starget,
>> kfree(sdev);
>> goto out;
>> }
>> -
>> + blk_get_queue(sdev->request_queue);
>
> Apparently we can't do this because blk_[put|get]_queue aren't exported
> for use in modules (and SCSI can be modular), so this caused a build
> failure in linux-next.
I'll just export them.
--
Jens Axboe
next prev parent reply other threads:[~2011-05-27 5:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.02.1105232329040.1910@natty-nar>
2011-05-24 10:44 ` __elv_add_request OOPS Jens Axboe
2011-05-25 1:41 ` [PATCH] SCSI IOCTL: Check for device deletion [was Re: __elv_add_request OOPS] Parag Warudkar
2011-05-25 7:37 ` Jens Axboe
2011-05-25 18:44 ` Parag Warudkar
2011-05-25 18:55 ` Linus Torvalds
2011-05-25 19:02 ` Jens Axboe
2011-05-25 19:13 ` Linus Torvalds
2011-05-25 19:17 ` Jens Axboe
2011-05-25 19:52 ` Parag Warudkar
2011-05-25 20:03 ` Linus Torvalds
2011-05-25 20:18 ` Parag Warudkar
2011-05-25 20:26 ` Linus Torvalds
2011-05-25 20:42 ` Parag Warudkar
2011-05-25 20:52 ` James Bottomley
2011-05-25 23:00 ` Parag Warudkar
2011-05-25 23:14 ` Linus Torvalds
2011-05-25 23:45 ` Parag Warudkar
2011-05-25 23:52 ` Linus Torvalds
[not found] ` <1306370123.1641.76.camel@mulgrave.site>
2011-05-26 1:01 ` Linus Torvalds
2011-05-26 1:06 ` James Bottomley
2011-05-26 1:43 ` Parag Warudkar
2011-05-27 3:53 ` James Bottomley
2011-05-27 5:43 ` Jens Axboe [this message]
2011-05-27 20:21 ` James Bottomley
2011-05-28 12:42 ` Jens Axboe
2011-06-08 6:50 ` Torsten Hilbrich
2011-05-25 20:20 ` James Bottomley
2011-05-25 20:22 ` Parag Warudkar
2011-05-25 20:29 ` James Bottomley
2011-05-25 20:26 ` __elv_add_request OOPS James Bottomley
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=4DDF3A07.7040106@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=parag.lkml@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).