From: syzbot <syzbot+155274e882dcbf9885df@syzkaller.appspotmail.com>
To: andriy.shevchenko@linux.intel.com, keescook@chromium.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
sel4@disroot.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] kernel BUG in hfs_show_options
Date: Sat, 26 Aug 2023 10:33:41 -0700 [thread overview]
Message-ID: <000000000000ba5da70603d6dc04@google.com> (raw)
In-Reply-To: <000000000000de4c2c0600c02b28@google.com>
syzbot has bisected this issue to:
commit c30417b20f4993e49406f3f6d986355c6e943aa2
Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: Mon Jul 17 09:33:32 2023 +0000
seq_file: Replace strncpy()+nul by strscpy()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1009eda7a80000
start commit: aeba456828b4 Add linux-next specific files for 20230718
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1209eda7a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1409eda7a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e7ec534f91cfce6c
dashboard link: https://syzkaller.appspot.com/bug?extid=155274e882dcbf9885df
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=136fa2aaa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16629fe4a80000
Reported-by: syzbot+155274e882dcbf9885df@syzkaller.appspotmail.com
Fixes: c30417b20f49 ("seq_file: Replace strncpy()+nul by strscpy()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-26 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 10:13 [syzbot] [hfs?] kernel BUG in hfs_show_options syzbot
2023-08-26 17:33 ` syzbot [this message]
[not found] <c0c7247d6a133b188c8e9780f243ae29@disroot.org>
2023-07-22 3:43 ` syzbot
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=000000000000ba5da70603d6dc04@google.com \
--to=syzbot+155274e882dcbf9885df@syzkaller.appspotmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sel4@disroot.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;
as well as URLs for NNTP newsgroup(s).