From: syzbot <syzbot+e9be5674af5e3a0b9ecc@syzkaller.appspotmail.com>
To: andreyknvl@gmail.com, hdanton@sina.com,
linux-kernel@vger.kernel.org,
penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] KASAN: stack-out-of-bounds Read in __show_regs (2)
Date: Fri, 02 Aug 2024 20:14:02 -0700 [thread overview]
Message-ID: <000000000000f3ff7b061ebed57f@google.com> (raw)
In-Reply-To: <20240803024329.2596-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+e9be5674af5e3a0b9ecc@syzkaller.appspotmail.com
Tested-by: syzbot+e9be5674af5e3a0b9ecc@syzkaller.appspotmail.com
Tested on:
commit: 931a3b3b Add linux-next specific files for 20240729
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14e78d11980000
kernel config: https://syzkaller.appspot.com/x/.config?x=91dc4a647da4c251
dashboard link: https://syzkaller.appspot.com/bug?extid=e9be5674af5e3a0b9ecc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=10936c7d980000
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2024-08-03 3:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 7:06 [syzbot] [kernel?] KASAN: stack-out-of-bounds Read in __show_regs (2) syzbot
2024-06-23 11:38 ` syzbot
2024-06-25 1:22 ` Tetsuo Handa
2024-07-01 12:43 ` Tetsuo Handa
2024-07-01 15:10 ` Andrey Konovalov
2024-07-02 6:11 ` Tetsuo Handa
2024-07-02 7:05 ` Tetsuo Handa
2024-07-02 14:29 ` Andrey Konovalov
2024-07-02 15:21 ` Tetsuo Handa
2024-07-07 10:32 ` Tetsuo Handa
2024-08-01 23:39 ` syzbot
2024-08-03 2:43 ` Hillf Danton
2024-08-03 3:14 ` syzbot [this message]
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=000000000000f3ff7b061ebed57f@google.com \
--to=syzbot+e9be5674af5e3a0b9ecc@syzkaller.appspotmail.com \
--cc=andreyknvl@gmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--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