From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
stern@rowland.harvard.edu, mdharm-usb@one-eyed-alien.net,
svens@stackframe.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH ver3] isd200: Allocate sense_buffer for hacked up scsi_cmnd
Date: Thu, 13 Mar 2008 15:16:53 -0500 [thread overview]
Message-ID: <1205439413.2893.49.camel@localhost.localdomain> (raw)
In-Reply-To: <20080313130112.22c0776f.akpm@linux-foundation.org>
On Thu, 2008-03-13 at 13:01 -0700, Andrew Morton wrote:
> On Wed, 12 Mar 2008 19:20:09 +0200
> Boaz Harrosh <bharrosh@panasas.com> wrote:
>
> >
> > Since the separation of sense_buffer from scsi_cmnd, Drivers that hack their
> > own struct scsi_cmnd like here isd200, must also take care of their own
> > sense_buffer.
> >
> > Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
> > ---
> > drivers/usb/storage/isd200.c | 5 ++++-
> > 1 files changed, 4 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/usb/storage/isd200.c b/drivers/usb/storage/isd200.c
> > index 4f2d143..971d13d 100644
> > --- a/drivers/usb/storage/isd200.c
> > +++ b/drivers/usb/storage/isd200.c
> > @@ -1470,6 +1470,7 @@ static void isd200_free_info_ptrs(void *info_)
> > if (info) {
> > kfree(info->id);
> > kfree(info->RegsBuf);
> > + kfree(info->srb.sense_buffer);
> > }
> > }
> >
> > @@ -1495,7 +1496,9 @@ static int isd200_init_info(struct us_data *us)
> > kzalloc(sizeof(struct hd_driveid), GFP_KERNEL);
> > info->RegsBuf = (unsigned char *)
> > kmalloc(sizeof(info->ATARegs), GFP_KERNEL);
> > - if (!info->id || !info->RegsBuf) {
> > + info->srb.sense_buffer =
> > + kmalloc(SCSI_SENSE_BUFFERSIZE, GFP_KERNEL);
> > + if (!info->id || !info->RegsBuf || !info->srb.sense_buffer) {
> > isd200_free_info_ptrs(info);
> > kfree(info);
> > retStatus = ISD200_ERROR;
>
> I've thoroughly lost the plot here.
Don't worry ... that's why life gave us SCSI maintainers ...
> Is this needed in 2.6.25? If so, why?
Yes. Because the changes that separate the sense buffer from the
commmand allocation which cause this bug went in in the merge window for
2.6.25
James
next prev parent reply other threads:[~2008-03-13 20:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <867igc3w8r.fsf@deprecated.bitebene.org>
2008-03-10 15:20 ` [PATCH] [SCSI] gdth: Allocate sense_buffer to prevent NULL pointer dereference Boaz Harrosh
2008-03-10 21:12 ` James Bottomley
2008-03-10 21:50 ` Sven Schnelle
2008-03-11 15:47 ` Boaz Harrosh
2008-03-11 16:16 ` Boaz Harrosh
2008-03-11 17:39 ` Matthew Dharm
2008-03-11 18:07 ` Alan Stern
2008-03-11 18:36 ` Boaz Harrosh
2008-03-11 19:18 ` Alan Stern
2008-03-12 13:07 ` Boaz Harrosh
2008-03-12 13:11 ` [PATCH] isd200: Allocate sense_buffer for hacked up scsi_cmnd Boaz Harrosh
2008-03-12 15:10 ` Alan Stern
2008-03-12 15:24 ` [PATCH resend] " Boaz Harrosh
2008-03-12 16:54 ` James Bottomley
2008-03-12 17:05 ` Boaz Harrosh
2008-03-12 17:20 ` [PATCH ver3] " Boaz Harrosh
2008-03-13 20:01 ` Andrew Morton
2008-03-13 20:16 ` James Bottomley [this message]
2008-03-12 13:55 ` [PATCH] isd200: Fix memory leak in isd200_get_inquiry_data Boaz Harrosh
2008-03-12 15:11 ` Alan Stern
2008-03-12 15:08 ` [PATCH] [SCSI] gdth: Allocate sense_buffer to prevent NULL pointer dereference 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=1205439413.2893.49.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=stern@rowland.harvard.edu \
--cc=svens@stackframe.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