From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Qingfang Deng <dqfext@gmail.com>
Cc: David Hildenbrand <david@redhat.com>,
Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, linux-mm@kvack.org,
Zi Yan <ziy@nvidia.com>, Johannes Weiner <hannes@cmpxchg.org>,
Brendan Jackman <jackmanb@google.com>,
Michal Hocko <mhocko@suse.com>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Liu Xiang <liu.xiang@zlingsmart.com>
Subject: Re: Please apply d2155fe54ddb to 5.10 and 5.4
Date: Wed, 23 Apr 2025 09:39:12 +0200 [thread overview]
Message-ID: <2025042306-perfected-retake-80d3@gregkh> (raw)
In-Reply-To: <CALW65jaXh=0+MkkNWHG9PpcDA88zBR5-S3j=pYbMZVcQ19hvag@mail.gmail.com>
On Wed, Apr 23, 2025 at 03:37:39PM +0800, Qingfang Deng wrote:
> On Tue, Apr 22, 2025 at 8:41 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > The commit looks harmless. But I don't see how it could fix any warning?
> > > >
> > > > I mean, we replace two !list_empty() checks by a single one ... and the
> > > > warning is about list_cut_position() ?
> > >
> > > I have no idea, actually. Maybe the double !list_empty() confuses the
> > > compiler, making it think `sublist` can be referenced out of the
> > > scope?
> >
> > That is odd, are you sure this isn't a compiler bug?
>
> I think it is a compiler bug. If so, what should we do to fix the warning?
Fix the compiler :)
prev parent reply other threads:[~2025-04-23 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALW65jbBY3EyRD-5vXz6w87Q+trxaod-QVy2NhVxLNcQHVw0hg@mail.gmail.com>
[not found] ` <2025042251-energize-preorder-31cd@gregkh>
2025-04-22 6:10 ` Qingfang Deng
2025-04-22 6:27 ` Greg Kroah-Hartman
2025-04-22 6:34 ` Qingfang Deng
2025-04-22 7:04 ` David Hildenbrand
2025-04-22 9:58 ` Qingfang Deng
2025-04-22 12:41 ` Greg Kroah-Hartman
2025-04-23 7:37 ` Qingfang Deng
2025-04-23 7:39 ` Greg Kroah-Hartman [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=2025042306-perfected-retake-80d3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dqfext@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=linux-mm@kvack.org \
--cc=liu.xiang@zlingsmart.com \
--cc=mhocko@suse.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.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