From: Joe <joego@mcn.org>
To: linux-hams@vger.kernel.org, netdev@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: Reminder: 3 open syzbot bugs in "net/ax25" subsystem
Date: Tue, 23 Jul 2019 20:42:11 -0700 [thread overview]
Message-ID: <623ff230-5883-560c-22d0-3e6b0eeaba39@mcn.org> (raw)
In-Reply-To: <20190724024049.GC643@sol.localdomain>
Hi Eric, How do I get off of this thread? When I try to unsubscribe it
tells me I'm not a member of the group.
Thanks in advance,
Joe G.
On 7/23/19 7:40 PM, Eric Biggers wrote:
> [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 3 of them as possibly being bugs in the "net/ax25" 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 "net/ax25" subsystem, please let me
> know, and if possible forward the report to the correct people or mailing list.
>
> Here are the bugs:
>
> --------------------------------------------------------------------------------
> Title: general protection fault in ax25_send_frame
> Last occurred: 0 days ago
> Reported: 204 days ago
> Branches: Mainline and others
> Dashboard link: https://syzkaller.appspot.com/bug?id=1cdd5b120f129364fc8e9b2b027826cf99fa696e
> Original thread: https://lkml.kernel.org/lkml/0000000000009ea37c057e58d787@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+e0b81535a27b8be39502@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/0000000000009ea37c057e58d787@google.com
>
> --------------------------------------------------------------------------------
> Title: KASAN: stack-out-of-bounds Write in ax25_getname
> Last occurred: 90 days ago
> Reported: 206 days ago
> Branches: Mainline and others
> Dashboard link: https://syzkaller.appspot.com/bug?id=fb195f91dc044978c1b186f1288b1eff61edcc20
> Original thread: https://lkml.kernel.org/lkml/000000000000ed4120057e2df0c6@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+6a29097222b4d3b8617c@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/000000000000ed4120057e2df0c6@google.com
>
> --------------------------------------------------------------------------------
> Title: inconsistent lock state in ax25_std_heartbeat_expiry
> Last occurred: 122 days ago
> Reported: 120 days ago
> Branches: net
> Dashboard link: https://syzkaller.appspot.com/bug?id=9086a8eac930890b2730d6441093bd478e32913f
> Original thread: https://lkml.kernel.org/lkml/0000000000001b07250584efbee3@google.com/T/#u
>
> Unfortunately, this bug does not have a reproducer.
>
> The original thread for this bug received 2 replies; the last was 119 days ago.
>
> If you fix this bug, please add the following tag to the commit:
> Reported-by: syzbot+e350b81e95a6a214da8a@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/0000000000001b07250584efbee3@google.com
>
next prev parent reply other threads:[~2019-07-24 3:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 2:40 Eric Biggers
2019-07-24 3:42 ` Joe [this message]
2019-07-24 8:01 ` 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=623ff230-5883-560c-22d0-3e6b0eeaba39@mcn.org \
--to=joego@mcn.org \
--cc=davem@davemloft.net \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.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
all inboxes | Powered by JetHome®