From: James Bottomley <James.Bottomley@SteelEye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] SCSI core: fix leakage of scsi_cmnd's
Date: Tue, 13 Sep 2005 16:34:01 -0500 [thread overview]
Message-ID: <1126647241.4809.65.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0509131254250.4481-100000@iolanthe.rowland.org>
On Tue, 2005-09-13 at 13:00 -0400, Alan Stern wrote:
> On Fri, 9 Sep 2005, James Bottomley wrote:
>
> > On Thu, 2005-09-08 at 16:49 -0400, Alan Stern wrote:
> > > This hasn't been tested very thoroughly, so please look through it
> > > carefully.
> >
> > Actually, just one problem and one cosmetic fix:
> >
> > 1) We need to dequeue for the loop and kill case (it seems easiest
> > simply to dequeue in the scsi_kill_request() routine)
> > 2) There's no real need to drop the queue lock. __scsi_done() is lock
> > agnostic, so since there's no requirement, let's just leave it in to
> > avoid any locking issues.
>
> Have you applied this to any publicly-accessible tree yet? I looked at
> the git browsers on parisc-linux.org and kernel.org, but the patch doesn't
> seem to be there yet.
Yes, they should both be in 2.6.14-rc1
> For that matter, what about the other patches you agreed to take (as543 -
> as546)? They aren't in the git repositories either. It would be good if
> all these things could be ready in time for the next -mm release.
That I think was these [from the latest GIT PATCH email]:
> Alan Stern:
> o Fix module removal/device add race
> o fix callers of scsi_remove_device() who already hold the scan
> muted
> o add missing scan mutex to scsi_scan_target()
James
next prev parent reply other threads:[~2005-09-13 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 14:56 [PATCH] SCSI core: fix leakage of scsi_cmnd's Alan Stern
2005-09-08 15:56 ` James Bottomley
2005-09-08 16:44 ` Alan Stern
2005-09-08 17:13 ` James Bottomley
2005-09-08 20:49 ` Alan Stern
2005-09-09 18:40 ` James Bottomley
2005-09-13 17:00 ` Alan Stern
2005-09-13 21:34 ` James Bottomley [this message]
2005-09-14 13:59 ` Alan Stern
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=1126647241.4809.65.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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