From: syzbot <syzbot+1c85a21f1c6bc88eb388@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, will@kernel.org
Subject: Re: WARNING: refcount bug in chrdev_open
Date: Mon, 13 Jan 2020 12:02:01 -0800 [thread overview]
Message-ID: <000000000000d80d1a059c0af28a@google.com> (raw)
In-Reply-To: <0000000000008dcde00590922713@google.com>
syzbot suspects this bug was fixed by commit:
commit 68faa679b8be1a74e6663c21c3a9d25d32f1c079
Author: Will Deacon <will@kernel.org>
Date: Thu Dec 19 12:02:03 2019 +0000
chardev: Avoid potential use-after-free in 'chrdev_open()'
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14412659e00000
start commit: 81b6b964 Merge branch 'master' of git://git.kernel.org/pub..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d98e4bd76baeb821
dashboard link: https://syzkaller.appspot.com/bug?extid=1c85a21f1c6bc88eb388
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=147ad0a6e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15483312e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: chardev: Avoid potential use-after-free in 'chrdev_open()'
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-13 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 20:18 WARNING: refcount bug in chrdev_open syzbot
2020-01-13 20:02 ` syzbot [this message]
2020-01-14 12:47 ` Andrey Konovalov
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=000000000000d80d1a059c0af28a@google.com \
--to=syzbot+1c85a21f1c6bc88eb388@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).