From: Bob Pearson <rpearsonhpe@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Daisuke Matsuda (Fujitsu)" <matsuda-daisuke@fujitsu.com>,
'Rain River' <rain.1986.08.12@gmail.com>,
Zhu Yanjun <yanjun.zhu@linux.dev>,
"leon@kernel.org" <leon@kernel.org>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [bug report] blktests srp/002 hang
Date: Tue, 17 Oct 2023 16:39:38 -0500 [thread overview]
Message-ID: <bf2705ff-716a-45b5-bcc4-8710ea0fb98e@gmail.com> (raw)
In-Reply-To: <cad2fee4-9359-4614-b36b-c2599dc12358@acm.org>
On 10/17/23 16:30, Bart Van Assche wrote:
>
> On 10/17/23 14:23, Bob Pearson wrote:
>> Not really, but stuck could mean it died (no threads active) or it is
>> in a loop or waiting to be scheduled. It looks dead. The lower layers are
>> waiting to get kicked into action by some event but it hasn't happened.
>> This is conjecture on my part though.
>
> This call stack means that I/O has been submitted by the block layer and
> that it did not get completed. Which I/O request got stuck can be
> verified by e.g. running the list-pending-block-requests script that I
> posted some time ago. See also
> https://lore.kernel.org/all/55c0fe61-a091-b351-11b4-fa7f668e49d7@acm.org/.
>
> Thanks,
>
> Bart.
Thanks. Would this run on the side of a hung blktests or would I need to
setup an srp-srpt file system?
Bob
next prev parent reply other threads:[~2023-10-17 21:39 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 6:46 [bug report] blktests srp/002 hang Shinichiro Kawasaki
2023-08-22 1:46 ` Bob Pearson
2023-08-22 10:18 ` Shinichiro Kawasaki
2023-08-22 15:20 ` Bart Van Assche
2023-08-23 16:19 ` Bob Pearson
2023-08-23 19:46 ` Bart Van Assche
2023-08-24 16:24 ` Bob Pearson
2023-08-24 8:55 ` Bernard Metzler
2023-08-24 15:35 ` Bernard Metzler
2023-08-24 16:05 ` Bart Van Assche
2023-08-24 16:27 ` Bob Pearson
2023-08-25 1:11 ` Shinichiro Kawasaki
2023-08-25 1:36 ` Bob Pearson
2023-08-25 10:16 ` Shinichiro Kawasaki
2023-08-25 13:49 ` Bart Van Assche
2023-08-25 13:52 ` Bart Van Assche
2023-09-13 17:36 ` Bob Pearson
2023-09-13 23:38 ` Zhu Yanjun
2023-09-16 5:59 ` Zhu Yanjun
2023-09-19 4:14 ` Shinichiro Kawasaki
2023-09-19 8:07 ` Zhu Yanjun
2023-09-19 16:30 ` Pearson, Robert B
2023-09-19 18:11 ` Bob Pearson
2023-09-20 4:22 ` Zhu Yanjun
2023-09-20 16:24 ` Bob Pearson
2023-09-20 16:36 ` Bart Van Assche
2023-09-20 17:18 ` Bob Pearson
2023-09-20 17:22 ` Bart Van Assche
2023-09-20 17:29 ` Bob Pearson
2023-09-21 5:46 ` Zhu Yanjun
2023-09-21 10:06 ` Zhu Yanjun
2023-09-21 14:23 ` Rain River
2023-09-21 14:39 ` Bob Pearson
2023-09-21 15:08 ` Zhu Yanjun
2023-09-21 15:10 ` Zhu Yanjun
2023-09-22 18:14 ` Bob Pearson
2023-09-22 22:06 ` Bart Van Assche
2023-09-24 1:17 ` Rain River
2023-09-25 4:47 ` Daisuke Matsuda (Fujitsu)
2023-09-25 14:31 ` Zhu Yanjun
2023-09-26 1:09 ` Daisuke Matsuda (Fujitsu)
2023-09-26 6:09 ` Zhu Yanjun
2023-09-25 15:00 ` Bart Van Assche
2023-09-25 15:25 ` Bob Pearson
2023-09-25 15:52 ` Jason Gunthorpe
2023-09-25 15:54 ` Bob Pearson
2023-09-25 19:57 ` Bob Pearson
2023-09-25 20:33 ` Bart Van Assche
2023-09-25 20:40 ` Bob Pearson
2023-09-26 15:36 ` Rain River
2023-09-26 1:17 ` Daisuke Matsuda (Fujitsu)
2023-10-17 17:09 ` Bob Pearson
2023-10-17 17:13 ` Bart Van Assche
2023-10-17 17:15 ` Bob Pearson
2023-10-17 17:19 ` Bob Pearson
2023-10-17 17:34 ` Bart Van Assche
2023-10-17 17:58 ` Jason Gunthorpe
2023-10-17 18:44 ` Bob Pearson
2023-10-17 18:51 ` Jason Gunthorpe
2023-10-17 19:55 ` Bob Pearson
2023-10-17 20:06 ` Bart Van Assche
2023-10-17 20:13 ` Bob Pearson
2023-10-17 21:14 ` Bob Pearson
2023-10-17 21:18 ` Bart Van Assche
2023-10-17 21:23 ` Bob Pearson
2023-10-17 21:30 ` Bart Van Assche
2023-10-17 21:39 ` Bob Pearson [this message]
2023-10-17 22:42 ` Bart Van Assche
2023-10-18 18:29 ` Bob Pearson
2023-10-18 19:17 ` Jason Gunthorpe
2023-10-18 19:48 ` Bart Van Assche
2023-10-18 20:03 ` Bob Pearson
2023-10-18 20:04 ` Bob Pearson
2023-10-18 20:14 ` Bob Pearson
2023-10-18 20:29 ` Bob Pearson
2023-10-18 20:49 ` Bart Van Assche
2023-10-18 21:17 ` Pearson, Robert B
2023-10-18 21:27 ` Bart Van Assche
2023-10-18 21:52 ` Bob Pearson
2023-10-19 19:17 ` Bart Van Assche
2023-10-20 17:12 ` Bob Pearson
2023-10-20 17:41 ` Bart Van Assche
2023-10-18 19:38 ` Bart Van Assche
2023-10-17 19:18 ` Bart Van Assche
2023-10-18 8:16 ` Zhu Yanjun
2023-09-22 11:06 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-10-13 12:51 ` Linux regression tracking #update (Thorsten Leemhuis)
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=bf2705ff-716a-45b5-bcc4-8710ea0fb98e@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matsuda-daisuke@fujitsu.com \
--cc=rain.1986.08.12@gmail.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=yanjun.zhu@linux.dev \
/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.