From: Pavel Begunkov <[email protected]>
To: syzbot <[email protected]>,
[email protected], [email protected],
[email protected], [email protected]
Subject: Re: [syzbot] [io-uring?] WARNING in io_pin_pages
Date: Fri, 22 Nov 2024 15:02:23 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/22/24 10:51, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: ae58226b89ac Add linux-next specific files for 20241118
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=14a67378580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=45719eec4c74e6ba
> dashboard link: https://syzkaller.appspot.com/bug?extid=2159cbb522b02847c053
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137beac0580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=177beac0580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/fd3d650cd6b6/disk-ae58226b.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/89a0fb674130/vmlinux-ae58226b.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/92120e1c6775/bzImage-ae58226b.xz
>
> The issue was bisected to:
>
> commit 68685fa20edc5307fc893a06473c19661c236f29
> Author: Pavel Begunkov <[email protected]>
> Date: Fri Nov 15 16:54:38 2024 +0000
>
> io_uring: fortify io_pin_pages with a warning
Seems I wasn't too paranoid. I'll send a fix
--
Pavel Begunkov
prev parent reply other threads:[~2024-11-22 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 10:51 [syzbot] [io-uring?] WARNING in io_pin_pages syzbot
2024-11-22 15:02 ` Pavel Begunkov [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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