From: Qingfang Deng <dqfext@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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>,
David Hildenbrand <david@redhat.com>
Subject: Re: Please apply d2155fe54ddb to 5.10 and 5.4
Date: Tue, 22 Apr 2025 14:34:13 +0800 [thread overview]
Message-ID: <CALW65jbEq250E1T=DpGWnP+_1QnPmfQ=q92NK8vo8n+jdqbDLg@mail.gmail.com> (raw)
In-Reply-To: <2025042237-express-coconut-592c@gregkh>
On Tue, Apr 22, 2025 at 2:27 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> On Tue, Apr 22, 2025 at 02:10:53PM +0800, Qingfang Deng wrote:
> > On Tue, Apr 22, 2025 at 2:06 PM Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > > All mm patches MUST get approval from the mm maintainers/developers
> > > before we can apply them to stable kernels.
> > >
> > > Can you please do that here?
> >
> > Sure. Added to Cc list.
>
> They have no context here at all :(
Let me post it again:
Please consider applying d2155fe54ddb ("mm: compaction: remove
duplicate !list_empty(&sublist) check") to 5.10 and 5.4, as it
resolves a -Wdangling-pointer warning in recent GCC versions:
In function '__list_cut_position',
inlined from 'list_cut_position' at ./include/linux/list.h:400:3,
inlined from 'move_freelist_tail' at mm/compaction.c:1241:3:
./include/linux/list.h:370:21: warning: storing the address of local
variable 'sublist' in '*&freepage_6(D)->D.15621.D.15566.lru.next'
[-Wdangling-pointer=]
next prev parent reply other threads:[~2025-04-22 6:34 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 [this message]
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
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='CALW65jbEq250E1T=DpGWnP+_1QnPmfQ=q92NK8vo8n+jdqbDLg@mail.gmail.com' \
--to=dqfext@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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