All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Dmitry Vyukov <dvyukov@google.com>,
	syzbot <syzbot+d958a65633ea70280b23@syzkaller.appspotmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: KASAN: null-ptr-deref Write in io_wq_cancel_all
Date: Fri, 25 Oct 2019 07:50:42 -0600	[thread overview]
Message-ID: <0e1b3410-95b0-f9d9-6838-486eae0bf5d7@kernel.dk> (raw)
In-Reply-To: <CACT4Y+Y946C-kyiBSZtyKY7PU4qxrysOfukd42--pXdyTRyjbw@mail.gmail.com>

On 10/25/19 5:58 AM, Dmitry Vyukov wrote:
> On Fri, Oct 25, 2019 at 1:51 PM syzbot
> <syzbot+d958a65633ea70280b23@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:    139c2d13 Add linux-next specific files for 20191025
>> git tree:       linux-next
>> console output: https://syzkaller.appspot.com/x/log.txt?x=17ab5a70e00000
>> kernel config:  https://syzkaller.appspot.com/x/.config?x=28fd7a693df38d29
>> dashboard link: https://syzkaller.appspot.com/bug?extid=d958a65633ea70280b23
>> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
>>
>> Unfortunately, I don't have any reproducer for this crash yet.
>>
>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>> Reported-by: syzbot+d958a65633ea70280b23@syzkaller.appspotmail.com
> 
> +Jens

Let me know if/when you have a reproducer for this one. I initially thought
this was a basic NULL pointer check, but it doesn't look like it. I wonder
if the thread handling the request got a signal, and since it had the
task file_table with the io_uring fd attached, it's triggering an exit.

I'll poke at it, but don't immediately see the issue.

-- 
Jens Axboe


  reply	other threads:[~2019-10-25 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 11:51 KASAN: null-ptr-deref Write in io_wq_cancel_all syzbot
2019-10-25 11:58 ` Dmitry Vyukov
2019-10-25 13:50   ` Jens Axboe [this message]
2019-10-25 14:35     ` Jens Axboe
2019-10-27  2:36 ` syzbot
2019-10-27  2:47   ` Jens Axboe
2019-10-27  6:33 ` 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 \
    --in-reply-to=0e1b3410-95b0-f9d9-6838-486eae0bf5d7@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=dvyukov@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+d958a65633ea70280b23@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.