From: Dan Carpenter <dan.carpenter@oracle.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzkaller <syzkaller@googlegroups.com>,
Hillf Danton <hdanton@sina.com>,
syzbot <syzbot+106b378813251e52fc5e@syzkaller.appspotmail.com>,
Andrey Konovalov <andreyknvl@google.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Jiri Kosina <jikos@kernel.org>,
"open list:HID CORE LAYER" <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: use-after-free Read in hiddev_disconnect
Date: Mon, 27 Jan 2020 18:11:35 +0300 [thread overview]
Message-ID: <20200127151135.GM1870@kadam> (raw)
In-Reply-To: <CACT4Y+ag59G4p=DO3Dg7jnFt3wQb=dtjzBujADtGHKn-97O8_g@mail.gmail.com>
One possible option would be to list the similar bugs at the start of
the bug report.
See also:
KASAN: use-after-free Write in hiddev_disconnect
https://syzkaller.appspot.com/bug?extid=784ccb935f9900cc7c9e
Then we could just copy and paste to the "#syz dup:" command. The
bitmap_port_list() stuff was reported something like 15 times so it was
really complicated to track. Hopefully if it were easier to mark things
as duplicate that would help.
regards,
dan carpenter
next prev parent reply other threads:[~2020-01-27 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 13:04 KASAN: use-after-free Read in hiddev_disconnect syzbot
2020-01-25 21:43 ` syzbot
[not found] ` <20200126024957.11392-1-hdanton@sina.com>
2020-01-27 9:28 ` Dan Carpenter
2020-01-27 12:28 ` Andrey Konovalov
2020-01-27 14:34 ` Dmitry Vyukov
2020-01-27 15:11 ` Dan Carpenter [this message]
2020-01-27 15:51 ` Dmitry Vyukov
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=20200127151135.GM1870@kadam \
--to=dan.carpenter@oracle.com \
--cc=andreyknvl@google.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dvyukov@google.com \
--cc=hdanton@sina.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+106b378813251e52fc5e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@googlegroups.com \
/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).