From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi_lib: add NULL check to scsi_setup_blk_pc_cmnd
Date: Tue, 24 Jul 2012 09:01:41 +0400 [thread overview]
Message-ID: <1343106101.3513.0.camel@dabdike> (raw)
In-Reply-To: <20120723192439.GB17767@logfs.org>
On Mon, 2012-07-23 at 15:24 -0400, Jörn Engel wrote:
> On Mon, 23 July 2012 23:45:55 +0400, James Bottomley wrote:
> > On Mon, 2012-07-23 at 13:32 -0400, Jörn Engel wrote:
> > > At least two slightly different paths can lead to a NULL pointer
> > > dereference in scsi_prep_state_check and have been hit in practice.
> >
> > Have you checked this with the patches in scsi-misc? There's a series
> > of patches in there that alters the way sdev handling is done.
>
> I would have liked to, but the tree referenced in MAINTAINERS does not
> appear to exist:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
> Cloning into 'scsi-misc-2.6'...
> fatal: The remote end hung up unexpectedly
git clone git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git
use the misc branch
James
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-24 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 17:32 [PATCH] scsi_lib: add NULL check to scsi_setup_blk_pc_cmnd Jörn Engel
2012-07-23 19:45 ` James Bottomley
2012-07-23 19:24 ` Jörn Engel
2012-07-24 5:01 ` James Bottomley [this message]
2012-07-25 19:13 ` Jörn Engel
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=1343106101.3513.0.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=joern@logfs.org \
--cc=linux-scsi@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.