linux-kernel - Reminder: 5 open syzbot bugs in lockdep subsystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 9 Jul 2019 22:58:38 -0700
From:   Eric Biggers <ebiggers@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>,
        Bart Van Assche <bvanassche@....org>
Cc:     syzkaller-bugs@...glegroups.com
Subject: Reminder: 5 open syzbot bugs in lockdep subsystem

[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 lockdep 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, 3 were seen in mainline in the last week.

Of these 5 bugs, 1 was bisected to a commit from the following person:

	Bart Van Assche <bvanassche@....org>

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 lockdep subsystem, please let me
know, and if possible forward the report to the correct people or mailing list.

Here are the bugs:

--------------------------------------------------------------------------------
Title:              BUG: MAX_STACK_TRACE_ENTRIES too low! (2)
Last occurred:      0 days ago
Reported:           102 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=55fb46b50c9b08dfe294667f184db5840f9cdecc
Original thread:    https://lkml.kernel.org/lkml/0000000000005ff8b20585395280@google.com/T/#u

This bug has a C reproducer.

This bug was bisected to:

	commit 669de8bda87b92ab9a2fc663b3f5743c2ad1ae9f
	Author: Bart Van Assche <bvanassche@....org>
	Date:   Thu Feb 14 23:00:54 2019 +0000

	  kernel/workqueue: Use dynamic lockdep keys for workqueues

The original thread for this bug received 2 replies; the last was 0 hours ago.

If you fix this bug, please add the following tag to the commit:
    Reported-by: syzbot+6f39a9deb697359fe520@...kaller.appspotmail.com

If you send any email or patch for this bug, please reply to the original
thread, which had activity only 0 hours ago.  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/0000000000005ff8b20585395280@google.com

--------------------------------------------------------------------------------
Title:              BUG: MAX_LOCKDEP_CHAIN_HLOCKS too low!
Last occurred:      0 days ago
Reported:           125 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=381cb436fe60dc03d7fd2a092b46d7f09542a72a
Original thread:    https://lkml.kernel.org/lkml/000000000000b7fd51058370d0d9@google.com/T/#u

This bug has a C reproducer.

syzbot has bisected this bug, but I think the bisection result is incorrect.

The original thread for this bug received 1 reply, 89 days ago.

If you fix this bug, please add the following tag to the commit:
    Reported-by: syzbot+91fd909b6e62ebe06131@...kaller.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/000000000000b7fd51058370d0d9@google.com

--------------------------------------------------------------------------------
Title:              BUG: MAX_LOCKDEP_CHAINS too low!
Last occurred:      5 days ago
Reported:           284 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=bf037f4725d40a8d350b2b1b3b3e0947c6efae85
Original thread:    https://lkml.kernel.org/lkml/0000000000007523a60576e80a47@google.com/T/#u

Unfortunately, this bug does not have a reproducer.

The original thread for this bug received 3 replies; the last was 284 days ago.

If you fix this bug, please add the following tag to the commit:
    Reported-by: syzbot+aaa6fa4949cc5d9b7b25@...kaller.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/0000000000007523a60576e80a47@google.com

--------------------------------------------------------------------------------
Title:              BUG: MAX_LOCK_DEPTH too low! (2)
Last occurred:      362 days ago
Reported:           392 days ago
Branches:           Mainline and others
Dashboard link:     https://syzkaller.appspot.com/bug?id=e4feb2f88affd6242e3153d5c14ebb8569b499b8
Original thread:    https://lkml.kernel.org/lkml/000000000000798298056e76cbbb@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+802a5abb8abae86eb6de@...kaller.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/000000000000798298056e76cbbb@google.com

--------------------------------------------------------------------------------
Title:              BUG: MAX_LOCKDEP_ENTRIES too low!
Last occurred:      23 days ago
Reported:           22 days ago
Branches:           linux-next
Dashboard link:     https://syzkaller.appspot.com/bug?id=3d97ba93fb3566000c1c59691ea427370d33ea1b
Original thread:    https://lkml.kernel.org/lkml/000000000000ec7273058b877e1f@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+cd0ec5211ac07c18c049@...kaller.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/000000000000ec7273058b877e1f@google.com