All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Oliver Sang <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com
Subject: Re: [willy-pagecache:slab-future] [slab]  d7a6fafee0: RIP:__ksize
Date: Tue, 9 Sep 2025 19:25:40 +0100	[thread overview]
Message-ID: <aMBxJL8hCfeKvyPS@casper.infradead.org> (raw)
In-Reply-To: <aLhFYcQtJYSWzxKw@xsang-OptiPlex-9020>

On Wed, Sep 03, 2025 at 09:40:49PM +0800, Oliver Sang wrote:
> > Hi.  Do you have a log for this configuration without this patchset?
> > I believe it should hit this warning:
> 
> do you mean the dmesg from parent commit?
> (attach one as dmesg-c5bbf49e67ff44.xz which seems quite clean)
> 
> or a dmesg from below commit
> 
> 3cace99d63192a (tag: next-20250829,
> 
> which seems the base of this branch?
> 
> 6259b37f692a4f (willy-pagecache/slab-future) mm: Remove redundant test in validate_page_before_insert()
> 20f8e938ae667d slab: Remove references to folios from virt_to_slab()
> ...
> ab89f51ec71be2 slab: Remove unnecessary test from alloc_debug_processing()
> 3cace99d63192a (tag: next-20250829,
> 
> 
> but we didn't capure WARNING from 3cace99d63192a, but a random issue as below
> (dmesg is attached as dmesg-3cace99d63192a.xz)

Ah, the bug was not what I thought it was.  Thank you for providing the
reproducer; it was very useful.

      reply	other threads:[~2025-09-09 18:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 14:35 [willy-pagecache:slab-future] [slab] d7a6fafee0: RIP:__ksize kernel test robot
2025-09-03 11:43 ` Matthew Wilcox
2025-09-03 13:40   ` Oliver Sang
2025-09-09 18:25     ` Matthew Wilcox [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=aMBxJL8hCfeKvyPS@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.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 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.