From: Christoph Hellwig <hch@infradead.org>
To: james.bottomley@steeleye.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: scsi-misc BK tree: Fix scsi_device_get to allow NULL devices
Date: Mon, 19 Apr 2004 10:38:22 +0100 [thread overview]
Message-ID: <20040419103822.A9502@infradead.org> (raw)
In-Reply-To: <20040405140552.GB8535@us.ibm.com>; from andmike@us.ibm.com on Mon, Apr 05, 2004 at 07:05:52AM -0700
On Mon, Apr 05, 2004 at 07:05:52AM -0700, Mike Anderson wrote:
> Christoph Hellwig [hch@infradead.org] wrote:
> > Can the SuSE guys please elaborate what this patch is supposed to solve?
> > We should never pass a NULL pointer to scsi_device_get..
>
> I agree. If this is happening then something is wrong in the scsi
> support of the device model.
As no one stands up to defend the patch could we please remove it again?
I saw it made it into 2.6.6-rc1 despite the critisism.
prev parent reply other threads:[~2004-04-19 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 11:55 scsi-misc BK tree: Fix scsi_device_get to allow NULL devices Christoph Hellwig
2004-04-05 14:05 ` Mike Anderson
2004-04-19 9:38 ` Christoph Hellwig [this message]
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=20040419103822.A9502@infradead.org \
--to=hch@infradead.org \
--cc=james.bottomley@steeleye.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox