From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Greg KH <greg@kroah.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
stable@kernel.org, rjw@sisk.pl, hias@horus.com,
linux-scsi@vger.kernel.org, dgilbert@interlog.com
Subject: Re: [stable] [PATCH -stable 2.6.28.x] sg: avoid blk_put_request/blk_rq_unmap_user in interrupt
Date: Wed, 11 Feb 2009 10:24:56 -0500 [thread overview]
Message-ID: <1234365896.3295.20.camel@localhost.localdomain> (raw)
In-Reply-To: <20090211060558.GB31483@kroah.com>
On Tue, 2009-02-10 at 22:05 -0800, Greg KH wrote:
> On Wed, Feb 11, 2009 at 02:50:18PM +0900, FUJITA Tomonori wrote:
> > This patch is against 2.6.28.x, fixes a regression from 2.6.27.
> >
> > This is the modified version of the following patch that is planed to
> > merged into 2.6.30-rc1 in scsi-misc tree:
> >
> > http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=b35fe25ae156830f85a305afaba837b084458e7a
> >
> > scsi-misc tree has other patches to fix sg oops so the above patch
> > can't be cleanly applied to 2.6.28.x. These patches are too large for
> > 2.6.28.x (needs more testings) so sg in 2.6.28.x still has the oops
> > bugs for now even with this patch. I expect that these patches will go
> > into stable trees too after 2.6.30-rc1 (that is, after more people
> > test them).
>
> What about 2.6.29? If it still has this problem as well, why not get
> this patch into that tree now? Then it can go into the -stable trees.
> As it is, I can't take a patch in the .28.y or .27.y trees that is not
> in Linus's tree.
>
> confused,
Sorry my fault ... this is a risky change, so we're going to incubate in
misc first, then place in the merge window, then backport to stable. If
nothing turns up in linux-next, I could move across to rc-fixes and send
upstream earlier ... I was just wary of the depth of testing in
linux-next.
James
next prev parent reply other threads:[~2009-02-11 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 5:50 [PATCH -stable 2.6.28.x] sg: avoid blk_put_request/blk_rq_unmap_user in interrupt FUJITA Tomonori
2009-02-11 6:05 ` [stable] " Greg KH
2009-02-11 15:24 ` James Bottomley [this message]
2009-02-11 17:15 ` Greg KH
2009-02-11 13:42 ` Douglas Gilbert
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=1234365896.3295.20.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=dgilbert@interlog.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=greg@kroah.com \
--cc=hias@horus.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stable@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