All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bing Jiao <bingjiao@google.com>
To: SeongJae Park <sj@kernel.org>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] mm/vmscan: fix uninitialized variable in demote_folio_list()
Date: Sat, 10 Jan 2026 03:03:30 +0000	[thread overview]
Message-ID: <aWHBgmOxt5_40Ues@google.com> (raw)
In-Reply-To: <20260110012812.81501-1-sj@kernel.org>

On Fri, Jan 09, 2026 at 05:28:11PM -0800, SeongJae Park wrote:
> On Fri,  9 Jan 2026 05:59:37 +0000 Bing Jiao <bingjiao@google.com> wrote:
>
> > Commit d92027a5f30a6c ("mm/vmscan: select the closest preferred node in
> > demote_folio_list()") refactored the selection logic for demotion target
> > nodes. However, it removed the initial assignment of 'target_nid' while
> > leaving a premature check for 'NUMA_NO_NODE' in place.
> >
> > Since 'target_nid' is now assigned further down in the function based on
> > preferred and allowed node masks, the initial check at line 1046 is
> > redundant.
> >
> > Remove the redundant check to resolve the compiler warning.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202601091037.vUSHeJCH-lkp@intel.com/
> > Fixes: d92027a5f30a6c ("mm/vmscan: select the closest preferred node in demote_folio_list()")
>
> Seems the broken commit is on mm-new, and therefore no need to Cc stable@.  I
> think explicitly clarifying that would be nice.  Also, as this fixup may need
> to be squashed into the broken commit before it is pulled into the mainline,
> sending this kind of fixup as a reply to the patch mail [1] of the commit would
> also be nice, and usual in mm.
>
> [1] https://lkml.kernel.org/r/20260108033248.2791579-3-bingjiao@google.com
>
> > Signed-off-by: Bing Jiao <bingjiao@google.com>
>
> Reviewed-by: SeongJae Park <sj@kernel.org>
>
>
> Thanks,
> SJ
>
> [...]

Hi SeongJae,

Thank you for the review and suggestions! The patch has sent to the patch
mail you mentioned.

Have a great weekend!

Best regards,
Bing


  reply	other threads:[~2026-01-10  3:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  5:59 [PATCH] mm/vmscan: fix uninitialized variable in demote_folio_list() Bing Jiao
2026-01-09  6:06 ` [PATCH v1] " Bing Jiao
2026-01-09  6:13   ` Bing Jiao
2026-01-10  1:28 ` [PATCH] " SeongJae Park
2026-01-10  3:03   ` Bing Jiao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-08  3:32 [PATCH v7 2/2] mm/vmscan: select the closest preferred node " Bing Jiao
2026-01-10  3:00 ` [PATCH] mm/vmscan: fix uninitialized variable " Bing Jiao
2026-01-10  3:38 ` Bing Jiao

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=aWHBgmOxt5_40Ues@google.com \
    --to=bingjiao@google.com \
    --cc=linux-mm@kvack.org \
    --cc=sj@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.