From: Tejun Heo <tj@kernel.org>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Mike Anderson <andmike@linux.vnet.ibm.com>,
Mike Christie <michaelc@cs.wisc.edu>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Andrew Morton <akpm@osdl.org>,
Alan Stern <stern@rowland.harvard.edu>,
Hannes Reinecke <hare@suse.de>,
Boaz Harrosh <bharrosh@panasas.com>,
Jens Axboe <jens.axboe@oracle.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Linux-iSCSI.org Target Dev"
<linux-iscsi-target-dev@googlegroups.com>
Subject: Re: Changes to Linux/SCSI target mode infrastructure for v2.6.28
Date: Tue, 02 Dec 2008 13:18:36 +0900 [thread overview]
Message-ID: <4934B71C.4030907@kernel.org> (raw)
In-Reply-To: <1228187439.13241.176.camel@haakon2.linux-iscsi.org>
Nicholas A. Bellinger wrote:
>>> So far during my initial testing, I am running into a two different
>>> exceptions. One NULL pointer deference OOPS after half dozen Open/iSCSI
>>> login/logouts in block/elevator.c:elv_dequeue_request(). Here is the
>>> trace from SCSI softirq context:
>>>
>>> http://linux-iscsi.org/builds/user/nab/2.6.28-rc6-oops-0.png
>>> http://linux-iscsi.org/builds/user/nab/2.6.28-rc6-oops-1.png
Can you build with debug info and find out which line is the offending
one?
>>> The other one is a BUG_ON in blk/blk-timeout.c:177 in blk_add_timeout()
>>> that happens after a few hundred MB of READ_10 traffic, which also
>>> appears to pass through elv_dequeue_request() at some point:
>>>
>>> http://linux-iscsi.org/builds/user/nab/2.6.28-rc6-oops-2.png
>>> http://linux-iscsi.org/builds/user/nab/2.6.28-rc6-oops-4.png
Hmmm... this means blk_add_timer() is being called after the request
is already completed. All the problem discovered till now have to do
with timeout going off without the low level driver knowing about the
request. I don't have much idea and it'll probably be best to trace
what's going on using blktrace or printks. Maybe this is caused by
list corruption as with the first issue or request completion races
with requeueing?
--
tejun
next prev parent reply other threads:[~2008-12-02 4:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 1:52 Changes to Linux/SCSI target mode infrastructure for v2.6.28 Nicholas A. Bellinger
2008-12-02 2:04 ` Nicholas A. Bellinger
2008-12-02 3:10 ` Nicholas A. Bellinger
2008-12-02 3:25 ` Nicholas A. Bellinger
2008-12-02 3:43 ` Tejun Heo
2008-12-02 4:18 ` Tejun Heo [this message]
2008-12-02 5:05 ` Nicholas A. Bellinger
2008-12-02 6:40 ` Mike Anderson
2008-12-02 7:49 ` Nicholas A. Bellinger
2008-12-02 8:30 ` Nicholas A. Bellinger
2008-12-02 8:35 ` Nicholas A. Bellinger
2008-12-02 9:13 ` Mike Anderson
2008-12-02 23:18 ` Nicholas A. Bellinger
2008-12-03 0:47 ` Nicholas A. Bellinger
2008-12-02 8:39 ` Boaz Harrosh
2008-12-02 10:34 ` Nicholas A. Bellinger
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=4934B71C.4030907@kernel.org \
--to=tj@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@osdl.org \
--cc=andmike@linux.vnet.ibm.com \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jens.axboe@oracle.com \
--cc=linux-iscsi-target-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=stern@rowland.harvard.edu \
/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