All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl Mehltretter <kmehltretter@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
	 Rich Felker <dalias@libc.org>,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sh: intc: sort the prio and sense lists after filling them
Date: Fri, 2 Oct 2026 23:58:14 +0200	[thread overview]
Message-ID: <asAk-lpM0rBnQTT3@gmail.com> (raw)
In-Reply-To: <3bd32eaf159db61ed1d423e1d52a869b3689c682.camel@physik.fu-berlin.de>

On Fri, Oct 02, 2026 at 06:57:19AM +0100, John Paul Adrian Glaubitz wrote:
> I just booted the kernel with slub_debug=FZPU on my SH-7785LCR EVB and
> I'm getting the following "kmalloc Redzone overwritten" warning in both
> cases.
> 

Hi Adrian,

thanks for testing. A cold reboot is not needed. The reported object was
allocated by usb_get_configuration(), so this warning is unrelated to the
INTC patch.

I sent a fix for the USB R8A66597 bug and copied you:

https://lore.kernel.org/r/20261002213225.27834-1-kmehltretter@gmail.com/

> Are you sure your patch actually fixes this problem?
> 
> Or do I maybe need a cold reboot?

A cold reboot is not needed.

The INTC allocation remains live after boot, so SLUB does not necessarily
check its redzone automatically. To check it explicitly after boot, run:

  echo 1 > /sys/kernel/slab/kmalloc-32/validate

Could you please test once with only the USB patch and once with both
patches, using slub_debug=FZPU and running that command after each boot?

Thanks,
Karl

  reply	other threads:[~2026-10-02 21:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 19:13 [PATCH] sh: intc: sort the prio and sense lists after filling them Karl Mehltretter
2026-09-27 19:30 ` Karl Mehltretter
2026-09-28 15:01 ` John Paul Adrian Glaubitz
2026-09-28 16:03   ` Geert Uytterhoeven
2026-09-28 16:46     ` John Paul Adrian Glaubitz
2026-09-28 17:00       ` Geert Uytterhoeven
2026-09-28 17:21         ` John Paul Adrian Glaubitz
2026-09-28 18:34           ` Geert Uytterhoeven
2026-09-28 19:02             ` John Paul Adrian Glaubitz
2026-09-28 21:22               ` Karl Mehltretter
2026-09-28 21:29                 ` John Paul Adrian Glaubitz
2026-09-29  9:20                 ` John Paul Adrian Glaubitz
2026-09-29  9:39                   ` John Paul Adrian Glaubitz
2026-10-02  4:57 ` John Paul Adrian Glaubitz
2026-10-02 21:58   ` Karl Mehltretter [this message]
2026-10-03  6:53     ` John Paul Adrian Glaubitz
2026-10-03  7:51 ` John Paul Adrian Glaubitz
2026-10-13 16:47 ` John Paul Adrian Glaubitz
2026-10-13 17:24 ` John Paul Adrian Glaubitz

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=asAk-lpM0rBnQTT3@gmail.com \
    --to=kmehltretter@gmail.com \
    --cc=dalias@libc.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.