From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+e9be5674af5e3a0b9ecc@syzkaller.appspotmail.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Andrey Konovalov <andreyknvl@gmail.com>,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] KASAN: stack-out-of-bounds Read in __show_regs (2)
Date: Sat, 3 Aug 2024 10:43:29 +0800 [thread overview]
Message-ID: <20240803024329.2596-1-hdanton@sina.com> (raw)
In-Reply-To: <0000000000007fca5d061ea7b850@google.com>
On Thu, 01 Aug 2024 16:39:23 -0700
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 931a3b3bccc9 Add linux-next specific files for 20240729
> git tree: linux-next
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f437f1980000
Test Tetsuo's idea [1].
[1] https://lore.kernel.org/lkml/5136bcc7-3db7-4fc2-abde-a3aceeaf17c2@I-love.SAKURA.ne.jp/
#syz test linux-next 931a3b3bccc9
--- x/arch/x86/kernel/dumpstack.c
+++ y/arch/x86/kernel/dumpstack.c
@@ -192,6 +192,7 @@ static void show_trace_log_lvl(struct ta
int graph_idx = 0;
bool partial = false;
+ kasan_disable_current();
printk("%sCall Trace:\n", log_lvl);
unwind_start(&state, task, regs, stack);
@@ -304,6 +305,7 @@ next:
if (stack_name)
printk("%s </%s>\n", log_lvl, stack_name);
}
+ kasan_enable_current();
}
void show_stack(struct task_struct *task, unsigned long *sp,
--
next prev parent reply other threads:[~2024-08-03 2:43 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 [this message]
2024-08-03 3:14 ` 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=20240803024329.2596-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=andreyknvl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=syzbot+e9be5674af5e3a0b9ecc@syzkaller.appspotmail.com \
--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