From: Ming Lei <ming.lei@redhat.com>
To: Guangwu Zhang <guazhang@redhat.com>
Cc: linux-block@vger.kernel.org, Jeff Moyer <jmoyer@redhat.com>
Subject: Re: [bug report] kernel panic at _find_next_zero_bit in io_uring testing
Date: Sat, 25 Mar 2023 18:06:45 +0800 [thread overview]
Message-ID: <ZB7HtcDOwmsKbQtj@ovpn-8-21.pek2.redhat.com> (raw)
In-Reply-To: <CAGS2=YohS-+HDNaTfd_0xP249ewTc5ffgY+XB+kQnDQ+c_BwMg@mail.gmail.com>
Hi Guang Wu,
On Sat, Mar 25, 2023 at 03:25:34PM +0800, Guangwu Zhang wrote:
> Hello,
>
> We found this kernel panic issue with upstream kernel 6.3.0-rc3 and
> it's 100% reproduced, let me know if you need more info/testing,
> thanks
>
> kernel repo : https://github.com/torvalds/linux.git
> reproducer : run the testing from git://git.kernel.dk/liburing
>
> [ 1089.762678] Running test recv-msgall-stream.t:
> [ 1089.922127] Running test recv-multishot.t:
> [ 1090.231772] Running test reg-hint.t:
> [ 1090.282612] general protection fault, probably for non-canonical
> address 0xdffffc0000000000: 0000 [#1] PREEMPT SMP KASAN NOPTI
> [ 1090.294014] KASAN: null-ptr-deref in range
The issue is fixed by:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/commit/?h=io_uring-6.3&id=02a4d923e4400a36d340ea12d8058f69ebf3a383
since liburing merges test case quicker than kernel fix, :-)
BTW, please report io_uring issue on io-uring@vger.kernel.org next time.
thanks,
Ming
next prev parent reply other threads:[~2023-03-25 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 7:25 [bug report] kernel panic at _find_next_zero_bit in io_uring testing Guangwu Zhang
2023-03-25 10:06 ` Ming Lei [this message]
2023-03-25 13:51 ` Jens Axboe
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=ZB7HtcDOwmsKbQtj@ovpn-8-21.pek2.redhat.com \
--to=ming.lei@redhat.com \
--cc=guazhang@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).