From: Jiri Slaby <jirislaby@gmail.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mm-commits@vger.kernel.org, linux-scsi@vger.kernel.org,
Jens Axboe <Jens.Axboe@oracle.com>,
neilb@suse.de
Subject: Re: BUG at scsi_lib.c:1108 [Was: mmotm 2009-11-24-16-47 uploaded]
Date: Wed, 25 Nov 2009 21:22:57 +0100 [thread overview]
Message-ID: <4B0D9221.2050103@gmail.com> (raw)
In-Reply-To: <1259162399.2535.8.camel@mulgrave.site>
On 11/25/2009 04:19 PM, James Bottomley wrote:
> On Wed, 2009-11-25 at 16:12 +0100, Jiri Slaby wrote:
>> On 11/25/2009 01:47 AM, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2009-11-24-16-47 has been uploaded to
>>
>> Hi, I'm hitting the BUG below in the past two -mmotm's
>> (2009-11-24-16-47, 2009-11-17-14-03):
>
> So this looks like some type of bug in the barrier code. What the BUG_ON
> is saying is that something sent us a REQ_TYPE_FS (which should be a
> filesystem read or write) with no attached data, so we can't process it.
>
> I've cc'd Jens to see what he thinks.
>
> Could you bisect this to find the offending commit?
Hmm. I bisected it twice to
commit 1bebedd653e1bb0440ebf40724c55791c21ad7cc
Merge: a8d5ddf 62fa36a
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed Nov 25 17:42:47 2009 +1100
Merge remote branch 'md/for-next'
It doesn't make sense at all. How can empty merge cause a regression?
And md/for-next doesn't produce the BUG.
After the 1st bisection I did
git checkout 1bebedd653e1bb0440ebf40724c55791c21ad7cc
and built it. It crashed. Then I did
git bisect start 1bebedd origin/stable
where origin is next. And got back to the 1bebedd by bisection.
--
js
Faculty of Informatics, Masaryk University
Suse Labs, Novell
next prev parent reply other threads:[~2009-11-25 20:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 0:47 mmotm 2009-11-24-16-47 uploaded akpm
2009-11-25 15:12 ` BUG at scsi_lib.c:1108 [Was: mmotm 2009-11-24-16-47 uploaded] Jiri Slaby
2009-11-25 15:19 ` James Bottomley
2009-11-25 20:22 ` Jiri Slaby [this message]
2009-11-25 21:13 ` Neil Brown
2009-11-26 10:17 ` Boaz Harrosh
2009-11-27 4:17 ` Neil Brown
2009-11-27 10:20 ` Jiri Slaby
2009-11-26 1:46 ` mmotm 2009-11-24-16-47 uploaded (gpio_max7301) Randy Dunlap
2009-11-28 16:21 ` Wolfram Sang
2009-12-15 22:43 ` Andrew Morton
2009-12-15 22:46 ` Randy Dunlap
2009-12-15 23:10 ` Andrew Morton
2009-12-16 11:30 ` Wolfram Sang
2009-11-27 10:33 ` ugly sound output (intel-hda) [was: mmotm 2009-11-24-16-47 uploaded] Jiri Slaby
2009-11-27 10:33 ` Jiri Slaby
2009-11-27 10:45 ` Takashi Iwai
2009-11-27 10:45 ` Takashi Iwai
2009-11-27 11:07 ` Jiri Slaby
2009-11-27 11:07 ` Jiri Slaby
2009-11-27 11:18 ` Takashi Iwai
2009-11-27 11:18 ` Takashi Iwai
2009-11-27 12:22 ` Jiri Slaby
2009-11-27 12:22 ` Jiri Slaby
2009-11-27 12:26 ` Takashi Iwai
2009-11-27 12:26 ` Takashi Iwai
2009-11-27 15:03 ` WARNING: kernel/smp.c:292 smp_call_function_single [Was: " Jiri Slaby
2009-11-27 15:17 ` Peter Zijlstra
2009-11-27 16:37 ` Thomas Gleixner
2009-11-27 16:44 ` Thomas Gleixner
2009-11-28 12:12 ` Avi Kivity
2009-11-30 8:58 ` Tejun Heo
2009-11-30 9:41 ` Avi Kivity
2009-11-30 10:02 ` Thomas Gleixner
2009-11-30 10:45 ` Tejun Heo
2009-11-30 11:02 ` [PATCH tip/sched/urgent] sched: revert 498657a478c60be092208422fefa9c7b248729c2 Tejun Heo
2009-11-30 11:13 ` Avi Kivity
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=4B0D9221.2050103@gmail.com \
--to=jirislaby@gmail.com \
--cc=James.Bottomley@suse.de \
--cc=Jens.Axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=neilb@suse.de \
/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.