public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>,
	syzbot <[email protected]>,
	[email protected], [email protected],
	[email protected]
Subject: Re: [syzbot] general protection fault in __io_queue_sqe
Date: Mon, 16 Aug 2021 23:50:42 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 8/16/21 10:57 PM, Jens Axboe wrote:
> On 8/16/21 3:49 PM, Jens Axboe wrote:
>> On 8/16/21 3:41 PM, syzbot wrote:
>>> syzbot has found a reproducer for the following issue on:
>>>
>>> HEAD commit:    b9011c7e671d Add linux-next specific files for 20210816
>>> git tree:       linux-next
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=1784d5e9300000
>>> kernel config:  https://syzkaller.appspot.com/x/.config?x=a245d1aa4f055cc1
>>> dashboard link: https://syzkaller.appspot.com/bug?extid=2b85e9379c34945fe38f
>>> compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
>>> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17479216300000
>>> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=147f0111300000
>>
>> #syz test: git://git.kernel.dk/linux-block for-next
> 
> Forgot to push out the update...
> 
> #syz test: git://git.kernel.dk/linux-block 16a390b4109c6eaa65f84e31c2c1d19bcbeb666f

fwiw, tested locally, solves the problem

-- 
Pavel Begunkov

  reply	other threads:[~2021-08-16 22:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 13:29 [syzbot] general protection fault in __io_queue_sqe syzbot
2021-08-16 21:41 ` syzbot
2021-08-16 21:49   ` Jens Axboe
2021-08-16 21:57     ` Jens Axboe
2021-08-16 22:50       ` Pavel Begunkov [this message]
2021-08-17  3:50       ` syzbot
2021-08-17  3:33     ` syzbot
2021-08-17  8:19 ` 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