From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"David Hildenbrand (Red Hat)" <david@kernel.org>,
"Michal Hocko" <mhocko@kernel.org>,
"Qi Zheng" <qi.zheng@linux.dev>,
"Shakeel Butt" <shakeel.butt@linux.dev>,
"Lorenzo Stoakes" <ljs@kernel.org>,
"Kairui Song" <kasong@tencent.com>,
"Barry Song" <baohua@kernel.org>,
"Axel Rasmussen" <axelrasmussen@google.com>,
"Yuanchu Xie" <yuanchu@google.com>, "Wei Xu" <weixugc@google.com>,
"Baoquan He" <baoquan.he@linux.dev>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Ridong Chen" <chenridong@xiaomi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmscan: avoid false-positive -Wuninitialized warning, again
Date: Thu, 17 Sep 2026 15:44:05 +0200 [thread overview]
Message-ID: <be7213e7-db2a-44e2-ae36-7735b17c20d5@app.fastmail.com> (raw)
In-Reply-To: <d832c2d1-d691-4583-852a-f05d4335e9ce@app.fastmail.com>
On Thu, Sep 17, 2026, at 12:15, Arnd Bergmann wrote:
> On Thu, Sep 17, 2026, at 08:03, Andrew Morton wrote:
> I also managed to create a reduced test case, see
> https://godbolt.org/z/xofecssz4 but this still doesn't make sense
> to me. I do see that gcc creates a both an out-of-line version
> of read_ctrl_pos() and also inlines it. Marking it either
> __always_inline or noinline avoids the warning.
I now reported this as a gcc bug at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127454
Let's see what they think.
Arnd
next prev parent reply other threads:[~2026-09-17 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 8:34 Arnd Bergmann
2026-09-16 23:08 ` Andrew Morton
2026-09-16 23:28 ` Andrew Morton
2026-09-16 23:30 ` Andrew Morton
2026-09-17 2:56 ` Baoquan He
2026-09-17 5:50 ` Arnd Bergmann
2026-09-17 6:03 ` Andrew Morton
2026-09-17 10:15 ` Arnd Bergmann
2026-09-17 13:44 ` Arnd Bergmann [this message]
2026-09-17 10:19 ` David Laight
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=be7213e7-db2a-44e2-ae36-7735b17c20d5@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@kernel.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baoquan.he@linux.dev \
--cc=chenridong@xiaomi.com \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=qi.zheng@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=weixugc@google.com \
--cc=yuanchu@google.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 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®