[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250625141551.ca068f6bc901943559df6bdf@linux-foundation.org>
Date: Wed, 25 Jun 2025 14:15:51 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Christoph Berg <myon@...ian.org>
Cc: David Hildenbrand <david@...hat.com>, Zi Yan <ziy@...dia.com>, Matthew
Brost <matthew.brost@...el.com>, Joshua Hahn <joshua.hahnjy@...il.com>,
Rakie Kim <rakie.kim@...com>, Byungchul Park <byungchul@...com>, Gregory
Price <gourry@...rry.net>, Ying Huang <ying.huang@...ux.alibaba.com>,
Alistair Popple <apopple@...dia.com>,
"open list:MEMORY MANAGEMENT - MEMORY POLICY AND MIGRATION"
<linux-mm@...ck.org>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Fix do_pages_stat to use compat_uptr_t
On Wed, 25 Jun 2025 23:10:13 +0200 Christoph Berg <myon@...ian.org> wrote:
> Re: Andrew Morton
> > I'll update the Subject: as David suggests and I'll add a cc:stable,
> > thanks. I'll also add a note that David suggested an alternative, so
> > please let's advance that option.
>
> Sorry, I'm new here. Do I have to do anything now? The above sounds
> like the alternative coding by David would be preferred, but the other
> mails say the patches have already been pushed to a hotfix branch? Or
> are we doing both, i.e. stable gets the simple fix and next the pretty
> one?
Well I added the v1 patch for testing and so it doesn't get lost -
fixing the bug is the most important thing.
But if a nicer v2 patch is sent in the next few days, I can switch to
that version.
Powered by blists - more mailing lists