From: Hannes Reinecke <hare@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
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: Tue, 08 Nov 2011 16:30:45 +0100 [thread overview]
Message-ID: <4EB94B25.3030108@suse.de> (raw)
In-Reply-To: <20111108110300.e8494242e6c404142b1fe4c0@canb.auug.org.au>
On 11/08/2011 01:03 AM, Stephen Rothwell wrote:
> Hi James,
>
> On Mon, 07 Nov 2011 08:51:24 -0600 James Bottomley<James.Bottomley@HansenPartnership.com> wrote:
>>
>> 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?
>
> I don't get the WARNING any more, but now get lots of:
>
> scsi: killing requests for dead queue
>
Yeah, that is really annoying.
And what's more the printk is wrong, as it doesn't indicate
that we've actually killed requests. It's just announcing that we
might start killing requests, provided the request_queue isn't empty.
I'll be sending a patch.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2011-11-08 15:30 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 [this message]
2011-11-10 15:51 ` Steffen Maier
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=4EB94B25.3030108@suse.de \
--to=hare@suse.de \
--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