From: Laurence Oberman <loberman@redhat.com>
To: Bart Van Assche <bvanassche@acm.org>,
Yi Zhang <yi.zhang@redhat.com>,
linux-block <linux-block@vger.kernel.org>
Cc: CKI Project <cki-project@redhat.com>
Subject: Re: [bug report] blktests srp/013 lead kernel panic with latest block/for-next and 5.13.15
Date: Sun, 12 Sep 2021 17:28:24 -0400 [thread overview]
Message-ID: <c5db85b3ecb9730d848b2c37c975b72acd8a2413.camel@redhat.com> (raw)
In-Reply-To: <059007be-03fa-5948-d86d-d1750587e894@acm.org>
On Sun, 2021-09-12 at 14:25 -0700, Bart Van Assche wrote:
> On 9/12/21 09:26, Yi Zhang wrote:
> > [ 130.851918] Failing address: 000003ff80815000 TEID:
> > 000003ff80815803
> > [ 130.852068] CPU: 1 PID: 950 Comm: multipathd Not tainted 5.14.0
> > #1
> > [ 130.852071] Hardware name: IBM 8561 LT1 400 (KVM/Linux)
> > [ 130.852073] Krnl PSW : 0704e00180000000 000000002e37e7cc
> > (scsi_mq_exit_request+0x2c/0x58)
> > [ 130.852113] Call Trace:
> > [ 130.852115] [<000000002e37e7cc>] scsi_mq_exit_request+0x2c/0x58
> > [ 130.852120] [<000000002e1c2608>] blk_mq_free_rqs+0x80/0x218
> > [ 130.852125] [<000000002e1c2f0a>] blk_mq_free_tag_set+0x5a/0x128
> > [ 130.852128] [<000000002e3774d0>]
> > scsi_host_dev_release+0xb0/0x118
> > [ 130.852130] [<000000002e33fe10>] device_release+0x48/0xb0
> > [ 130.852136] [<000000002e28bf12>] kobject_put+0xca/0x1f0
> > [ 130.852140] [<000000002e33fe10>] device_release+0x48/0xb0
> > [ 130.852142] [<000000002e28bf12>] kobject_put+0xca/0x1f0
> > [ 130.852145] [<000000002dc1324a>]
> > execute_in_process_context+0x4a/0xf0
> > [ 130.852149] [<000000002e33fe10>] device_release+0x48/0xb0
> > [ 130.852151] [<000000002e28bf12>] kobject_put+0xca/0x1f0
> > [ 130.852153] [<000000002e38e49e>] sd_release+0x6e/0xf8
> > [ 130.852158] [<000000002e1a86d0>] blkdev_put+0xe0/0x278
> > [ 130.852162] [<000000002e1a9946>] blkdev_close+0x3e/0x50
> > [ 130.852164] [<000000002de94728>] __fput+0xa0/0x280
> > [ 130.852168] [<000000002dc19190>] task_work_run+0x88/0xd0
> > [ 130.852170] [<000000002dc89b9e>]
> > exit_to_user_mode_loop+0x1ce/0x1d8
> > [ 130.852175] [<000000002dc89c22>]
> > exit_to_user_mode_prepare+0x7a/0x80
> > [ 130.852178] [<000000002e6e70be>] __do_syscall+0x106/0x1e8
> > [ 130.852181] [<000000002e6f5518>] system_call+0x78/0xa0
>
> I haven't seen this yet. Is this crash reproducible? If so, please
> bisect this crash.
>
> Thanks,
>
> Bart.
>
I am looking to reproduce and bisect as well.
Regards
Laurence
next prev parent reply other threads:[~2021-09-12 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 16:26 [bug report] blktests srp/013 lead kernel panic with latest block/for-next and 5.13.15 Yi Zhang
2021-09-12 21:25 ` Bart Van Assche
2021-09-12 21:28 ` Laurence Oberman [this message]
[not found] ` <CAHj4cs_8KbMJ+HU22E4-e_zYuPj8TfGOzxNtzQqxqKig9S=gQg@mail.gmail.com>
2021-09-28 18:07 ` Bart Van Assche
2021-10-05 3:21 ` Yi Zhang
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=c5db85b3ecb9730d848b2c37c975b72acd8a2413.camel@redhat.com \
--to=loberman@redhat.com \
--cc=bvanassche@acm.org \
--cc=cki-project@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=yi.zhang@redhat.com \
/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).