From: Eric Biggers <ebiggers@kernel.org>
To: linux-ntfs-dev@lists.sourceforge.net,
Anton Altaparmakov <anton@tuxera.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Reminder: 5 open syzbot bugs in "fs/ntfs" subsystem
Date: Tue, 9 Jul 2019 13:27:06 -0700 [thread overview]
Message-ID: <20190709202706.GL641@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/ntfs" 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.
Of these 5 bugs, 2 were seen in mainline in the last week.
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/ntfs" subsystem, please let me
know, and if possible forward the report to the correct people or mailing list.
Here are the bugs:
--------------------------------------------------------------------------------
Title: WARNING: bad unlock balance in rcu_core
Last occurred: 1 day ago
Reported: 86 days ago
Branches: Mainline and others
Dashboard link: https://syzkaller.appspot.com/bug?id=0d5bdaf028e4283ad7404609d17e5077f48ff26d
Original thread: https://lkml.kernel.org/lkml/000000000000c0bffa0586795098@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
No one has replied to the original thread for this bug yet.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+36baa6c2180e959e19b1@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/000000000000c0bffa0586795098@google.com
--------------------------------------------------------------------------------
Title: KASAN: use-after-free Read in ntfs_read_locked_inode
Last occurred: 460 days ago
Reported: 460 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=5c5466347d4969ec80f5000c5e049056f48e3e2e
Original thread: https://lkml.kernel.org/lkml/001a11441b6c6cb96c0569120042@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+19b469021157c136116a@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/001a11441b6c6cb96c0569120042@google.com
--------------------------------------------------------------------------------
Title: WARNING: bad unlock balance in rcu_lock_release
Last occurred: 5 days ago
Reported: 16 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=a939746456c0350d6a368a9d30a4dcfcafa800be
Original thread: https://lkml.kernel.org/lkml/000000000000fdd3f3058bfcf369@google.com/T/#u
Unfortunately, this bug does not have a reproducer.
No one has replied to the original thread for this bug yet.
If you fix this bug, please add the following tag to the commit:
Reported-by: syzbot+f9545ab3e9f85cd43a3a@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/000000000000fdd3f3058bfcf369@google.com
--------------------------------------------------------------------------------
Title: KASAN: slab-out-of-bounds Read in ntfs_attr_find
Last occurred: 463 days ago
Reported: 463 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=731ba1daa85050266cef2836e917da1cc785f50a
Original thread: https://lkml.kernel.org/lkml/001a11447acae6b4560568e08829@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+aed06913f36eff9b544e@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/001a11447acae6b4560568e08829@google.com
--------------------------------------------------------------------------------
Title: kernel BUG at fs/ntfs/aops.c:LINE!
Last occurred: 446 days ago
Reported: 446 days ago
Branches: Mainline
Dashboard link: https://syzkaller.appspot.com/bug?id=86d590f642a6d325d2f9dc9571e6702bed1a77ee
Original thread: https://lkml.kernel.org/lkml/000000000000c4b45a056a36872f@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+6a5a7672f663cce8b156@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/000000000000c4b45a056a36872f@google.com
next reply other threads:[~2019-07-09 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 20:27 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/ntfs" 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=20190709202706.GL641@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=anton@tuxera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--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