From: Mike Snitzer <snitzer@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-raid@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [Bug 19642] New: 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113
Date: Sun, 3 Oct 2010 17:00:03 -0400 [thread overview]
Message-ID: <20101003210002.GA4050@redhat.com> (raw)
In-Reply-To: <1286132006.2984.32.camel@mulgrave.site>
On Sun, Oct 03 2010 at 2:53pm -0400,
James Bottomley <James.Bottomley@suse.de> wrote:
> On Sun, 2010-10-03 at 18:37 +0000, bugzilla-daemon@bugzilla.kernel.org
> wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=19642
> >
> > Summary: 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113
> > Product: IO/Storage
> > Version: 2.5
> > Kernel Version: 2.6.36-rc6
> > Platform: All
> > OS/Version: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: SCSI
> > AssignedTo: linux-scsi@vger.kernel.org
>
> I think this is wrong.
>
> > ReportedBy: maciej.rutecki@gmail.com
> > CC: rjw@sisk.pl, maciej.rutecki@gmail.com,
> > linux@horizon.com
> > Regression: Yes
> >
> >
> > Subject : 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113
> > Submitter : "George Spelvin" <linux@horizon.com>
> > Date : 2010-09-30 21:10
> > Message-ID : 20100930211006.27449.qmail@science.horizon.com
> > References : http://marc.info/?l=linux-kernel&m=128588102620299&w=2
>
> That looks like a zero length barrier send down to SCSI with the RW flag
> set (hence we try to map a buffer that has nothing to map). I cc'd
> dm-devel to see what their opinion is.
Given that the referenced LKML report is MD focused it seems linux-raid
should be cc'd instead (doing so now).
Mike
prev parent reply other threads:[~2010-10-03 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19642-11613@https.bugzilla.kernel.org/>
2010-10-03 18:53 ` [Bug 19642] New: 2.6.36-rc6 BUG at drivers/scsi/scsi_lib.c:1113 James Bottomley
2010-10-03 21:00 ` Mike Snitzer [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=20101003210002.GA4050@redhat.com \
--to=snitzer@redhat.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dm-devel@redhat.com \
--cc=linux-raid@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).