From: Steffen Maier <maier@linux.vnet.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>,
Bart Van Assche <bvanassche@acm.org>,
linux-scsi@vger.kernel.org
Subject: Re: WARNING: at drivers/scsi/scsi_lib.c:1704
Date: Thu, 10 Nov 2011 16:51:35 +0100 [thread overview]
Message-ID: <4EBBF307.4070000@linux.vnet.ibm.com> (raw)
In-Reply-To: <1320677484.1215.10.camel@dabdike.int.hansenpartnership.com>
On 11/07/2011 03:51 PM, James Bottomley wrote:
> On Mon, 2011-11-07 at 17:24 +1100, Stephen Rothwell wrote:
>> WARNING: at drivers/scsi/scsi_lib.c:1704
>> I get lots more of these. The obvious commit to point the finger at
>> is 3308511c93e6 ("[SCSI] Make scsi_free_queue() kill pending SCSI
>> commands") but the root cause may be something different.
>
> Actually, I don't think it's anything to do with this: it's Anton's
> fault
>
> commit f7c9c6bb14f3104608a3a83cadea10a6943d2804
> Author: Anton Blanchard<anton@samba.org>
> Date: Thu Nov 3 08:56:22 2011 +1100
>
> [SCSI] Fix block queue and elevator memory leak in scsi_alloc_sdev
>
> Doesn't completely do the teardown. The true fix is to do a proper
> teardown instead of hand rolling it. Does this fix it for you?
>
> James
>
> ---
> diff --git a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
> index 72273a0..b3c6d95 100644
> --- a/drivers/scsi/scsi_scan.c
> +++ b/drivers/scsi/scsi_scan.c
> @@ -319,11 +319,7 @@ static struct scsi_device *scsi_alloc_sdev(struct scsi_target *starget,
> return sdev;
>
> out_device_destroy:
> - scsi_device_set_state(sdev, SDEV_DEL);
> - transport_destroy_device(&sdev->sdev_gendev);
> - put_device(&sdev->sdev_dev);
> - scsi_free_queue(sdev->request_queue);
> - put_device(&sdev->sdev_gendev);
> + __scsi_remove_device(sdev);
> out:
> if (display_failure_msg)
> printk(ALLOC_FAILURE_MSG, __func__);
James, is it OK that __scsi_remove_device() now also calls
sdev->host->hostt->slave_destroy(sdev) which wasn't there before?
I cannot prove it yet, but with this patch and some asorted others on
top of 3.1 our zfcp LLD gets called with an sdev argument that was freed
before or at least before dereferencing (found with DEBUG_PAGEALLOC).
Steffen
Linux on System z Development
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2011-11-10 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 6:24 WARNING: at drivers/scsi/scsi_lib.c:1704 Stephen Rothwell
2011-11-07 7:33 ` Bart Van Assche
2011-11-08 1:36 ` [PATCH] [SCSI] scsi_alloc_sdev() trips WARN_ON in scsi_free_queue() Anton Blanchard
2011-11-07 14:51 ` WARNING: at drivers/scsi/scsi_lib.c:1704 James Bottomley
2011-11-08 0:03 ` Stephen Rothwell
2011-11-08 0:36 ` Stephen Rothwell
2011-11-08 7:07 ` Bart Van Assche
2011-11-08 8:49 ` Stephen Rothwell
2011-11-16 20:58 ` Luis Henriques
2011-11-08 15:30 ` Hannes Reinecke
2011-11-10 15:51 ` Steffen Maier [this message]
2011-11-10 16:06 ` 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=4EBBF307.4070000@linux.vnet.ibm.com \
--to=maier@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).