From: Eric Biggers <ebiggers@kernel.org>
To: reiserfs-devel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Reminder: 5 open syzbot bugs in "fs/reiserfs" subsystem
Date: Tue, 9 Jul 2019 13:26:41 -0700 [thread overview]
Message-ID: <20190709202641.GK641@sol.localdomain> (raw)
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 5 of them as possibly being bugs in the "fs/reiserfs" subsystem. I've
listed these reports below, sorted by an algorithm that tries to list first the
reports most likely to be still valid, important, and actionable.
If you believe a bug is no longer valid, please close the syzbot report by
sending a '#syz fix', '#syz dup', or '#syz invalid' command in reply to the
original thread, as explained at https://goo.gl/tpsmEJ#status
If you believe I misattributed a bug to the "fs/reiserfs" subsystem, please let
me know, and if possible forward the report to the correct people or mailing
list.
Here are the bugs:
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in blkdev_get
Last occurred: 19 days ago
Reported: 391 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=00965426fe7ceec1fd2d8756770d4c7c3cacdc4b
Original thread: https://lkml.kernel.org/lkml/000000000000e59aab056e8873ae@google.com/T/#u
This bug has a C reproducer.
The original thread for this bug received 1 reply, 215 days ago.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+eaeb616d85c9a0afec7d@syzkaller.appspotmail.com
If you send any email or patch for this bug, please consider replying to the
original thread. For the git send-email command to use, or tips on how to reply
if the thread isn't in your mailbox, see the "Reply instructions" at
https://lkml.kernel.org/r/000000000000e59aab056e8873ae@google.com
--------------------------------------------------------------------------------
Title: BUG: unable to handle kernel paging request in cleanup_bitmap_list
Last occurred: 13 days ago
Reported: 464 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=f7a51e226194a72ab7364a64af1b8fb1e80e94bb
Original thread: https://lkml.kernel.org/lkml/001a1140e9201dd16b0568cc6beb@google.com/T/#u
This bug has a C reproducer.
No one replied to the original thread for this bug.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+008ac33be9dec51e0ca3@syzkaller.appspotmail.com
If you send any email or patch for this bug, please consider replying to the
original thread. For the git send-email command to use, or tips on how to reply
if the thread isn't in your mailbox, see the "Reply instructions" at
https://lkml.kernel.org/r/001a1140e9201dd16b0568cc6beb@google.com
--------------------------------------------------------------------------------
Title: WARNING in unlock_new_inode
Last occurred: 446 days ago
Reported: 446 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=ef79070d08a744686c4db202d9ba6817bba86ebb
Original thread: https://lkml.kernel.org/lkml/0000000000002ab8c5056a35b12b@google.com/T/#u
This bug has a C reproducer.
No one replied to the original thread for this bug.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+187510916eb6a14598f7@syzkaller.appspotmail.com
If you send any email or patch for this bug, please consider replying to the
original thread. For the git send-email command to use, or tips on how to reply
if the thread isn't in your mailbox, see the "Reply instructions" at
https://lkml.kernel.org/r/0000000000002ab8c5056a35b12b@google.com
--------------------------------------------------------------------------------
Title: kernel BUG at fs/reiserfs/journal.c:LINE!
Last occurred: 445 days ago
Reported: 465 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=4f66f3287ba3341410ff35b736339628173a5aaa
Original thread: https://lkml.kernel.org/lkml/001a113eba282f2ffc0568b76123@google.com/T/#u
This bug has a syzkaller reproducer only.
No one replied to the original thread for this bug.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+6820505ae5978f4f8f2f@syzkaller.appspotmail.com
If you send any email or patch for this bug, please consider replying to the
original thread. For the git send-email command to use, or tips on how to reply
if the thread isn't in your mailbox, see the "Reply instructions" at
https://lkml.kernel.org/r/001a113eba282f2ffc0568b76123@google.com
--------------------------------------------------------------------------------
Title: kernel BUG at fs/reiserfs/lock.c:LINE!
Last occurred: 78 days ago
Reported: 364 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=633d4e446a638abe31cc3054b5a69a42a4cd25d6
Original thread: https://lkml.kernel.org/lkml/0000000000002bd65e0570aa16f2@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
No one replied to the original thread for this bug.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+66d2c2155ece8b6d3fc0@syzkaller.appspotmail.com
If you send any email or patch for this bug, please consider replying to the
original thread. For the git send-email command to use, or tips on how to reply
if the thread isn't in your mailbox, see the "Reply instructions" at
https://lkml.kernel.org/r/0000000000002bd65e0570aa16f2@google.com
next reply other threads:[~2019-07-09 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 20:26 Eric Biggers [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-24 2:30 Reminder: 5 open syzbot bugs in "fs/reiserfs" subsystem Eric Biggers
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=20190709202641.GK641@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzkaller-bugs@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