From: Bart Van Assche <bvanassche@acm.org>
To: Amit Sahrawat <amit.sahrawat83@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <JBottomley@parallels.com>,
Mike Christie <michaelc@cs.wisc.edu>, Tejun Heo <tj@kernel.org>
Subject: Re: Deadlock observed in SCSI device removal
Date: Sat, 15 Dec 2012 10:04:23 +0100 [thread overview]
Message-ID: <50CC3D17.10902@acm.org> (raw)
In-Reply-To: <CADDb1s0wdZfHTZ8jyKdT4zpsYg4+hYXCSBN5=bY3Q=03wBJT4Q@mail.gmail.com>
On 12/15/12 05:22, Amit Sahrawat wrote:
> We are using kernel version 3.0.33, and the patch which is mentioned for
> the above problem - is already applied in the kernel.
If the kernel reports that io_schedule() hangs that usually means that
an I/O request was not finished properly. It would help if you could
verify whether or not you can reproduce this issue with kernel 3.6.10.
Bart.
parent reply other threads:[~2012-12-15 9:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CADDb1s0wdZfHTZ8jyKdT4zpsYg4+hYXCSBN5=bY3Q=03wBJT4Q@mail.gmail.com>]
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=50CC3D17.10902@acm.org \
--to=bvanassche@acm.org \
--cc=JBottomley@parallels.com \
--cc=amit.sahrawat83@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=tj@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).