All of lore.kernel.org
 help / color / mirror / Atom feed
From: FUJITA Tomonori <tomof@acm.org>
To: James.Bottomley@HansenPartnership.com
Cc: tomof@acm.org, lnxninja@linux.vnet.ibm.com,
	fujita.tomonori@lab.ntt.co.jp, linux-scsi@vger.kernel.org,
	Mark_Salyzyn@adaptec.com, jeff@garzik.org
Subject: Re: ips.c broken since 2.6.23 on x86_64?
Date: Wed, 20 Feb 2008 05:29:14 +0900	[thread overview]
Message-ID: <20080220052915V.tomof@acm.org> (raw)
In-Reply-To: <1203437199.3103.15.camel@localhost.localdomain>

On Tue, 19 Feb 2008 10:06:39 -0600
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:

> On Tue, 2008-02-19 at 17:02 +0900, FUJITA Tomonori wrote:
> > ips did scsi_add_host(sh, NULL) so scsi_dma_map uses
> > shost_gendev.parent that isn't initialized properly, then the kernel
> > crashes. 2.6.23 and 2.6.24 have this bug.
> > 
> > We can fix this by calling scsi_add_host with pdev->dev, in the
> > standard way (like the following way) but this bug was fixed in the
> > current Linus tree by:
> > 
> > commit 2551a13e61d3c3df6c2da6de5a3ece78e6d67111
> > Author: Jeff Garzik <jeff@garzik.org>
> > Date:   Thu Dec 13 16:14:10 2007 -0800
> > 
> > [SCSI] ips: handle scsi_add_host() failure, and other err cleanups
> > 
> > 
> > James, the legitimate way to fix stable trees is sending this commit
> > (not sending a patch that was not committed upstream)?
> 
> Well, the upstream patch doesn't look so bad as a stable candidate to my
> eye.  Just because it's an unintended bugfix doesn't automatically
> invalidate it.
> 
> The reason stable likes backports of existing upstream patches is
> because they've supposedly been well tested in upstream.  Although that
> doesn't apply in this case because the other bug rather prevented
> testing, the principle is still sound.
> 
> So, would there be any problems simply backporting this?

Thanks, I see. There is no problem. Please backport this.

      reply	other threads:[~2008-02-19 20:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 21:43 ips.c broken since 2.6.23 on x86_64? Tim Pepper
     [not found] ` <532ABFBDAAC3A34EB12EBA6CEC2838F439964688@ADPE2K703.adaptec.com>
2008-02-14  0:04   ` Tim Pepper
2008-02-18 14:57     ` Salyzyn, Mark
2008-02-18 23:34       ` Tim Pepper
2008-02-14 11:48 ` FUJITA Tomonori
2008-02-14 23:55   ` Tim Pepper
2008-02-15  0:13     ` FUJITA Tomonori
2008-02-15  1:16       ` Tim Pepper
2008-02-15 16:09         ` FUJITA Tomonori
2008-02-15 22:50           ` Tim Pepper
2008-02-16  0:41             ` FUJITA Tomonori
2008-02-17 12:52               ` Boaz Harrosh
2008-02-17 13:09                 ` Boaz Harrosh
2008-02-17 21:16                   ` Tim Pepper
2008-02-17 21:15               ` Tim Pepper
2008-02-17 22:31                 ` FUJITA Tomonori
2008-02-17 23:29                   ` Tim Pepper
2008-02-17 23:37                   ` Tim Pepper
2008-02-18 13:32                     ` FUJITA Tomonori
2008-02-18 23:30                       ` Tim Pepper
2008-02-19  0:11                         ` FUJITA Tomonori
2008-02-19  3:48                           ` Tim Pepper
2008-02-19  8:22                             ` FUJITA Tomonori
2008-02-19  8:02                       ` FUJITA Tomonori
2008-02-19 16:06                         ` James Bottomley
2008-02-19 20:29                           ` FUJITA Tomonori [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=20080220052915V.tomof@acm.org \
    --to=tomof@acm.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Mark_Salyzyn@adaptec.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jeff@garzik.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lnxninja@linux.vnet.ibm.com \
    /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.