From: Greg KH <gregkh@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Sasha Levin" <sashal@kernel.org>,
"# 3.4.x" <stable@vger.kernel.org>,
"Miles Chen (陳民樺)" <miles.chen@mediatek.com>,
mike.kravetz@oracle.com, "Nathan Chancellor" <nathan@kernel.org>,
dbueso@suse.de, "Andrew Morton" <akpm@linux-foundation.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: please pick 552546366a30 to 5.4.y
Date: Wed, 24 Mar 2021 18:21:11 +0100 [thread overview]
Message-ID: <YFt1Bx32z8UiLJcl@kroah.com> (raw)
In-Reply-To: <CAKwvOd=2k_NaC1U9MwNHzfCHAfhwi55fyoTa+AHFM=drh9d3Ng@mail.gmail.com>
On Wed, Mar 24, 2021 at 10:09:08AM -0700, Nick Desaulniers wrote:
> On Wed, Mar 24, 2021 at 10:06 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Wed, Mar 24, 2021 at 09:47:49AM -0700, Nick Desaulniers wrote:
> > > Dear stable kernel maintainers,
> > > Please consider cherry-picking
> > > commit 552546366a30 ("hugetlbfs: hugetlb_fault_mutex_hash() cleanup")
> > > to linux-5.4.y. It first landed in v5.5-rc1 and fixes an instance of
> > > the warning -Wsizeof-array-div.
> >
> > What shows that warning? I don't see it here with my gcc builds :)
>
> $ make LLVM=1 -j72 defconfig
> $ ./scripts/config -e CONFIG_HUGETLBFS
> $ make LLVM=1 -j72 mm/hugetlb.o
> ...
> CC mm/hugetlb.o
> mm/hugetlb.c:4159:40: warning: expression does not compute the number
> of elements in this array; element type is 'unsigned long', not 'u32'
> (aka 'unsigned int') [-Wsizeof-array-div]
> hash = jhash2((u32 *)&key, sizeof(key)/sizeof(u32), 0);
> ~~~ ^
> mm/hugetlb.c:4153:16: note: array 'key' declared here
> unsigned long key[2];
> ^
> mm/hugetlb.c:4159:40: note: place parentheses around the 'sizeof(u32)'
> expression to silence this warning
> hash = jhash2((u32 *)&key, sizeof(key)/sizeof(u32), 0);
> ^
Ok, will queue it up, thanks.
greg k-h
prev parent reply other threads:[~2021-03-24 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 16:47 please pick 552546366a30 to 5.4.y Nick Desaulniers
2021-03-24 17:06 ` Greg KH
2021-03-24 17:09 ` Nick Desaulniers
2021-03-24 17:21 ` Greg KH [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=YFt1Bx32z8UiLJcl@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dbueso@suse.de \
--cc=mike.kravetz@oracle.com \
--cc=miles.chen@mediatek.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=sashal@kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox