From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Mike Anderson <andmike@linux.vnet.ibm.com>
Cc: bugme-daemon@bugzilla.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [Bug 12195] "dd" make kernel panic
Date: Fri, 12 Dec 2008 09:09:37 -0600 [thread overview]
Message-ID: <1229094577.3262.19.camel@localhost.localdomain> (raw)
In-Reply-To: <20081212102205.GA16034@linux.vnet.ibm.com>
On Fri, 2008-12-12 at 02:22 -0800, Mike Anderson wrote:
> bugme-daemon@bugzilla.kernel.org <bugme-daemon@bugzilla.kernel.org> wrote:
> > http://bugzilla.kernel.org/show_bug.cgi?id=12195
> >
> >
> >
> >
> >
> > ------- Comment #6 from ming.m.lin@intel.com 2008-12-11 18:27 -------
> > 2.6.28-rc8 also panic
>
> The blk_mark_rq_complete check should prevent completions from occurring on
> already timed out requests unless the interaction previous mentioned between
> mpt_fault_reset_work and the scsi eh thread requeue alows the REQ_ATOM_COMPLETE
> bit to get cleared prior to the scsi_done being called from
> mptscsih_flush_running_cmds. This did not look obvious to hit.
>
> mpt_fault_reset_work
> mpt_HardResetHandler
> mpt_signal_reset
> mptsas_ioc_reset
> mptscsih_flush_running_cmds
> mpt_do_ioc_recovery
Actually, this isn't quite true. Particularly in the eh case. It looks
like the block timeout isn't stopped until blk_complete_request() which
is pretty late. If the timeout fires after scsi_done is called but
before we complete the request, any timeout goes through the
BLK_EH_HANDLED path to __blk_complete_request(). This routine
unconditionally adds to the done routine without checking the mark, so
there is a window where we can get double dones.
James
next prev parent reply other threads:[~2008-12-12 15:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 2:07 [Bug 12195] New: "dd" make kernel panic bugme-daemon
2008-12-11 2:09 ` [Bug 12195] " bugme-daemon
2008-12-11 2:15 ` bugme-daemon
2008-12-11 3:12 ` bugme-daemon
2008-12-11 9:05 ` bugme-daemon
2008-12-11 15:17 ` James Bottomley
2008-12-11 9:26 ` bugme-daemon
2008-12-11 15:17 ` bugme-daemon
2008-12-11 19:45 ` bugme-daemon
2008-12-12 2:27 ` bugme-daemon
2008-12-12 10:22 ` Mike Anderson
2008-12-12 15:09 ` James Bottomley [this message]
2008-12-12 19:28 ` James Bottomley
2008-12-12 10:22 ` bugme-daemon
2008-12-12 15:09 ` bugme-daemon
2008-12-12 19:28 ` bugme-daemon
2008-12-13 17:58 ` bugme-daemon
2008-12-15 9:52 ` bugme-daemon
2008-12-15 10:39 ` bugme-daemon
2008-12-15 20:13 ` James Bottomley
2008-12-15 20:13 ` bugme-daemon
2008-12-16 5:12 ` bugme-daemon
2008-12-21 19:52 ` bugme-daemon
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=1229094577.3262.19.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=andmike@linux.vnet.ibm.com \
--cc=bugme-daemon@bugzilla.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