From: Mel Gorman <mgorman@techsingularity.net>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Vlastimil Babka <vbabka@suse.cz>,
Michal Hocko <mhocko@suse.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com,
kernel-janitors@vger.kernel.org, linux-safety@lists.elisa.tech
Subject: Re: [PATCH] mm/vmscan: drop unneeded assignment in kswapd()
Date: Mon, 5 Oct 2020 08:59:03 +0100 [thread overview]
Message-ID: <20201005075903.GH3227@techsingularity.net> (raw)
In-Reply-To: <alpine.DEB.2.21.2010050831010.6202@felia>
On Mon, Oct 05, 2020 at 08:58:53AM +0200, Lukas Bulwahn wrote:
>
>
> On Sun, 4 Oct 2020, Mel Gorman wrote:
>
> > On Sun, Oct 04, 2020 at 02:58:27PM +0200, Lukas Bulwahn wrote:
> > > The refactoring to kswapd() in commit e716f2eb24de ("mm, vmscan: prevent
> > > kswapd sleeping prematurely due to mismatched classzone_idx") turned an
> > > assignment to reclaim_order into a dead store, as in all further paths,
> > > reclaim_order will be assigned again before it is used.
> > >
> > > make clang-analyzer on x86_64 tinyconfig caught my attention with:
> > >
> > > mm/vmscan.c: warning: Although the value stored to 'reclaim_order' is
> > > used in the enclosing expression, the value is never actually read from
> > > 'reclaim_order' [clang-analyzer-deadcode.DeadStores]
> > >
> > > Compilers will detect this unneeded assignment and optimize this anyway.
> > > So, the resulting binary is identical before and after this change.
> > >
> > > Simplify the code and remove unneeded assignment to make clang-analyzer
> > > happy.
> > >
> > > No functional change. No change in binary code.
> > >
> > > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> >
> > I'm not really keen on this. With the patch, reclaim_order can be passed
> > uninitialised to kswapd_try_to_sleep. While a sufficiently smart
> > compiler might be able to optimise how reclaim_order is used, it's not
> > guaranteed either. Similarly, a change in kswapd_try_to_sleep and its
> > called functions could rely on reclaim_order being a valid value and
> > then introduce a subtle bug.
> >
>
> Just for my own understanding:
>
> How would you see reclaim_order being passed unitialised to
> kswapd_try_to_sleep?
>
> From kswapd() entry, any path must reach the line
>
> alloc_order = reclaim_order = READ_ONCE(pgdat->kswapd_order);
>
> before kswap_try_to_sleep(...).
>
Bah, I misread the patch because I'm an idiot.
Acked-by: Mel Gorman <mgorman@techsingularity.net>
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2020-10-05 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 12:58 [PATCH] mm/vmscan: drop unneeded assignment in kswapd() Lukas Bulwahn
2020-10-04 19:24 ` Mel Gorman
2020-10-05 6:58 ` Lukas Bulwahn
2020-10-05 7:56 ` Mel Gorman
2020-10-05 7:59 ` Mel Gorman [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=20201005075903.GH3227@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-safety@lists.elisa.tech \
--cc=lukas.bulwahn@gmail.com \
--cc=mhocko@suse.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).