From: Dave Hansen <dave.hansen@intel.com>
To: reveliofuzzing <reveliofuzzing@gmail.com>,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, kirill.shutemov@linux.intel.com
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: reproducible GPF error in native_tss_update_io_bitmap
Date: Tue, 7 Jan 2025 13:28:12 -0800 [thread overview]
Message-ID: <57af7a02-c765-409d-a04c-bf74e747f8b6@intel.com> (raw)
In-Reply-To: <CA+-ZZ_igYSw1=563skeb-e5+YiN81KHtjmYGZ7bvBK4h3piZ9g@mail.gmail.com>
On 1/6/25 18:32, reveliofuzzing wrote:
> Hello,
>
> We found the following general protection fault bug in Linux kernel 6.12, and
> it can be reproduced stably in a QEMU VM. To our knowledge, this problem has not
> been observed by SyzBot so we would like to report it for your reference.
>
> - dmesg
> syzkaller login: [ 90.849309] Oops: general protection fault,
> probably for non-canonical address 0xdffffc0000000000: 0000 [#1]
> PREEMPTI
> [ 90.853735] KASAN: null-ptr-deref in range
> [0x0000000000000000-0x0000000000000007]
> [ 90.856772] CPU: 0 PID: 3265 Comm: iou-sqp-3264 Not tainted 6.10.0 #2
> [ 90.859386] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),
> BIOS 1.13.0-1ubuntu1.1 04/01/2014
> [ 90.862774] RIP: 0010:native_tss_update_io_bitmap+0x143/0x510
The whole thing looks like an issue in the failure path when trying to
create an io_uring io worker thread. It's probably some confusion in
treating the worker thread like a userspace thread with an io bitmap
when the worker thread doesn't have one.
It's _probably_ only reproducible with io_uring. It's arguable whether
it's likely an x86 issue or an io_uring issue.
In any case, running:
scripts/decode_stacktrace.sh
and providing a full vmlinux might be helpful if folks want to dig into
this more.
next prev parent reply other threads:[~2025-01-07 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 2:32 reproducible GPF error in native_tss_update_io_bitmap reveliofuzzing
2025-01-07 21:28 ` Dave Hansen [this message]
2025-01-08 0:24 ` reveliofuzzing
2025-01-15 14:22 ` Thomas Gleixner
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=57af7a02-c765-409d-a04c-bf74e747f8b6@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reveliofuzzing@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@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