From: Sven Schnelle <svens@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: KASAN: slab-out-of-bounds in print_synth_event+0xa68/0xa78
Date: Tue, 08 Aug 2023 07:58:59 +0200 [thread overview]
Message-ID: <yt9dmsz2qdlo.fsf@linux.ibm.com> (raw)
In-Reply-To: <20230807215310.068fce2f@gandalf.local.home> (Steven Rostedt's message of "Mon, 7 Aug 2023 21:53:10 -0400")
Steven Rostedt <rostedt@goodmis.org> writes:
> On Fri, 04 Aug 2023 08:20:23 +0200
> Sven Schnelle <svens@linux.ibm.com> wrote:
>
>> Hi Steven,
>>
>> i noticed the following KASAN splat in CI (on s390):
>
> Could this actually be a bug in KASAN?
>
> The reason I ask, is because of the report.
I don't think so. I looked into the trace file when the problem occurred
yesterday, and it looked like this:
kworker/0:2-83 [000] d..4. 59.260107: wake_lat: pid=2654624 delta=55 stack=STACK:
=> 0x6b6b6b6b6b6b6b6b
=> 0x6b6b6b6b6b6b6b6b
=> 0x6b6b6b6b6b6b6b6b
=> 0x6b6b6b6b6b6b6b6b
=> 0x6b6b6b6b6b6b6b6b
[..]
Somtimes the number is 0xcc, which is POISON_FREE_INITMEM instead of POISON_FREE.
In other entries delta and pid are also wrong:
swapper/0-1 [002] ..... 5.864575: wake_lat: pid=5437496 delta=7880749591624456 stack=STACK:
Of course PID could have gone away, but that delta looks interesting. So
it looks like the whole entry is just random data not owned by tracing,
and not the data that was allocated in the ringbuffer code.
next prev parent reply other threads:[~2023-08-08 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 6:20 BUG: KASAN: slab-out-of-bounds in print_synth_event+0xa68/0xa78 Sven Schnelle
2023-08-04 15:50 ` Steven Rostedt
2023-08-04 16:32 ` Sven Schnelle
2023-08-04 17:36 ` Steven Rostedt
2023-08-07 6:08 ` Sven Schnelle
2023-08-08 1:53 ` Steven Rostedt
2023-08-08 5:58 ` Sven Schnelle [this message]
2023-08-08 9:44 ` Sven Schnelle
2023-08-08 10:14 ` Steven Rostedt
2023-08-08 14:28 ` Sven Schnelle
2023-08-08 17:20 ` Steven Rostedt
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=yt9dmsz2qdlo.fsf@linux.ibm.com \
--to=svens@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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