mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Karl Mehltretter <kmehltretter@gmail.com>
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: Sat, 03 Oct 2026 08:53:18 +0200	[thread overview]
Message-ID: <f1e0019607971c4719f96f32af2b948a071501e7.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <asAk-lpM0rBnQTT3@gmail.com>

Hi,

On Fri, 2026-10-02 at 23:58 +0200, Karl Mehltretter wrote:
> 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.

OK, so how do I reproduce the INTC issue?

> I sent a fix for the USB R8A66597 bug and copied you:
> 
> https://lore.kernel.org/r/20261002213225.27834-1-kmehltretter@gmail.com/

Let me check.

> > 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

So, running the validation should trigger the INTC issue on an unpatched kernel?

> 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?

I'll test the USB patch first and see if that fixes the issue when booting
with slub_debug=FZPU. Then test the INTC issue with the command above.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2026-10-03  6:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-27 19:13 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
2026-10-03  6:53     ` John Paul Adrian Glaubitz [this message]
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
2026-10-14  7:03 ` Geert Uytterhoeven
2026-10-14  8:00   ` 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=f1e0019607971c4719f96f32af2b948a071501e7.camel@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=dalias@libc.org \
    --cc=kmehltretter@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®