From: Byungchul Park <byungchul@sk.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Huang, Ying" <ying.huang@intel.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, vschneid@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel_team@skhynix.com
Subject: Re: [PATCH v4] sched/numa, mm: do not try to migrate memory to memoryless nodes
Date: Tue, 20 Feb 2024 12:20:08 +0900 [thread overview]
Message-ID: <20240220032008.GH65758@system.software.com> (raw)
In-Reply-To: <20240219190520.b5e373273ec743aacbad263b@linux-foundation.org>
On Mon, Feb 19, 2024 at 07:05:20PM -0800, Andrew Morton wrote:
> On Tue, 20 Feb 2024 10:53:43 +0900 Byungchul Park <byungchul@sk.com> wrote:
>
> > > > IIUC, you will use patch as fix to the issue in
> > > >
> > > > https://lore.kernel.org/lkml/20240216111502.79759-1-byungchul@sk.com/
> > > >
> > > > If so, we need the Fixes: tag to make it land in -stable properly.
> > >
> > > Yes, this changelog is missing rather a lot of important information.
> >
> > This is not the root cause fix any more but just optimization.
>
> It would have been helpful to have told us this in the changelog :(
Sorry for that and making you guys confused.
> > That's
> > why I didn't add Fixes: tag and cc stable@vger.kernel.org in here.
> >
> > Instead, I added Fixes: tag and cc'ed stable@vger.kernel.org in the real
> > fix patch. check the following link please:
> >
> > https://lore.kernel.org/lkml/20240216111502.79759-1-byungchul@sk.com/
>
> But doesn't this patch "sched/numa, mm: do not try to migrate memory to
> memoryless nodes" also fix the bug? Do we truly need both?
Yes. The oops is gone with "sched/numa, mm: do not try to migrate memory
to memoryless nodes". However, as you know, wrongly manipulating array
index is very dangerous - what hackers are looking for. Even with security
in mind, both are necessary. Plus, no one gurantees the problematic code
is gone through with a numa node that has no managed zones in the future.
Byungchul
next prev parent reply other threads:[~2024-02-20 3:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 4:19 Byungchul Park
2024-02-19 8:43 ` Huang, Ying
2024-02-20 1:45 ` Andrew Morton
2024-02-20 1:53 ` Byungchul Park
2024-02-20 3:05 ` Andrew Morton
2024-02-20 3:20 ` Byungchul Park [this message]
2024-02-20 2:07 ` Byungchul Park
2024-02-20 2:33 ` Byungchul Park
2024-02-20 3:28 ` Andrew Morton
2024-02-20 4:09 ` Byungchul Park
2024-02-19 15:06 ` Phil Auld
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=20240220032008.GH65758@system.software.com \
--to=byungchul@sk.com \
--cc=akpm@linux-foundation.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kernel_team@skhynix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=ying.huang@intel.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