From: Harry Yoo <harry.yoo@oracle.com>
To: Vlastimil Babka <vbabka@suse.com>
Cc: David Wang <00107082@163.com>,
surenb@google.com, vbabka@suse.cz, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [7.0-rc1] codetag: kernel warning "alloc_tag was not set" during boot
Date: Tue, 24 Feb 2026 11:15:13 +0900 [thread overview]
Message-ID: <aZ0JsUPSf6_GKSzA@hyeyoo> (raw)
In-Reply-To: <6ca5f70c-43c5-4ba3-bdc4-8c48607dbe7c@suse.com>
On Mon, Feb 23, 2026 at 06:18:32PM +0100, Vlastimil Babka wrote:
> On 2/23/26 16:51, David Wang wrote:
> > Hi,
> >
> > When upgrade to 7.0.0-rc1, caught a kernel WARN during boot:
>
> Would this possibly help? (it probably shouldn't but let's see)
> https://lore.kernel.org/all/20260223075809.19265-1-harry.yoo@oracle.com/
I think it could probably help.
While x86's TSO memory model does not reorder loads after loads and
stores after stores, the compiler is free to reorder
READ_ONCE(slab->obj_exts) after loading slab->stride.
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2026-02-24 2:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 15:51 [7.0-rc1] codetag: kernel warning "alloc_tag was not set" during boot David Wang
2026-02-23 17:18 ` Vlastimil Babka
2026-02-23 18:34 ` Suren Baghdasaryan
2026-02-24 1:56 ` David Wang
2026-02-24 2:15 ` Harry Yoo [this message]
2026-02-24 2:28 ` David Wang
2026-02-24 7:07 ` Suren Baghdasaryan
2026-02-24 11:15 ` David Wang
2026-02-24 14:16 ` Harry Yoo
2026-02-24 14:26 ` Harry Yoo
2026-02-24 16:15 ` Suren Baghdasaryan
2026-02-24 16:56 ` Suren Baghdasaryan
2026-02-24 22:18 ` Suren Baghdasaryan
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=aZ0JsUPSf6_GKSzA@hyeyoo \
--to=harry.yoo@oracle.com \
--cc=00107082@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=surenb@google.com \
--cc=vbabka@suse.com \
--cc=vbabka@suse.cz \
/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.