public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: syzbot <[email protected]>,
	[email protected], [email protected],
	[email protected], [email protected]
Subject: Re: [syzbot] [io-uring?] general protection fault in __io_remove_buffers
Date: Thu, 18 Jul 2024 19:03:21 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 7/18/24 02:20, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    d67978318827 Merge tag 'x86_cpu_for_v6.11_rc1' of git://gi..
> git tree:       upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=1178e9e9980000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=e206d588252bd3ff
> dashboard link: https://syzkaller.appspot.com/bug?extid=2074b1a3d447915c6f1c
> 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=10e07d9e980000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16adf045980000
> 
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/f34b31760156/disk-d6797831.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/a92e51d8d32e/vmlinux-d6797831.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/000a6a162550/bzImage-d6797831.xz
> 
> The issue was bisected to:
> 
> commit 87585b05757dc70545efb434669708d276125559
> Author: Jens Axboe <[email protected]>
> Date:   Wed Mar 13 02:24:21 2024 +0000
> 
>      io_uring/kbuf: use vm_insert_pages() for mmap'ed pbuf ring
Easily reproducible, the diff helps

#syz test:


diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
index d2945c9c812b..c95dc1736dd9 100644
--- a/io_uring/kbuf.c
+++ b/io_uring/kbuf.c
@@ -657,8 +657,10 @@ static int io_alloc_pbuf_ring(struct io_ring_ctx *ctx,
  	ring_size = reg->ring_entries * sizeof(struct io_uring_buf_ring);
  
  	bl->buf_ring = io_pages_map(&bl->buf_pages, &bl->buf_nr_pages, ring_size);
-	if (!bl->buf_ring)
+	if (IS_ERR(bl->buf_ring)) {
+		bl->buf_ring = NULL;
  		return -ENOMEM;
+	}
  
  	bl->is_buf_ring = 1;
  	bl->is_mmap = 1;


  reply	other threads:[~2024-07-18 18:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18  1:20 [syzbot] [io-uring?] general protection fault in __io_remove_buffers syzbot
2024-07-18 18:03 ` Pavel Begunkov [this message]
2024-07-18 18:03   ` syzbot

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