From: Kees Cook <keescook@chromium.org>
To: Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Eric Biederman <ebiederm@xmission.com>,
Greg Ungerer <gerg@linux-m68k.org>,
Mike Frysinger <vapier@gentoo.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
kernel test robot <lkp@intel.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] binfmt_flat: fix sparse annotation ordering
Date: Mon, 18 Apr 2022 15:01:35 -0700 [thread overview]
Message-ID: <202204181501.D55C8D2A@keescook> (raw)
In-Reply-To: <20220418200834.1501454-1-Niklas.Cassel@wdc.com>
On Mon, Apr 18, 2022 at 08:09:12PM +0000, Niklas Cassel wrote:
> From: Niklas Cassel <niklas.cassel@wdc.com>
>
> The sparse annotation ordering inside the function call is swapped.
>
> Fix the ordering so that we silence the following sparse warnings:
> fs/binfmt_flat.c:816:39: warning: incorrect type in argument 1 (different address spaces)
> fs/binfmt_flat.c:816:39: expected unsigned int [noderef] [usertype] __user *rp
> fs/binfmt_flat.c:816:39: got unsigned int [usertype] *[noderef] __user
>
> No functional change as sparse annotations are ignored by the compiler.
>
> Fixes: a767e6fd68d2 ("binfmt_flat: do not stop relocating GOT entries prematurely on riscv")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
> Cc: <stable@vger.kernel.org>
> ---
> Hello Kees,
>
> Sorry about this.
> Feel free to squash it with the existing patch if you so like.
Ah-ha! Thanks; I was just looking at the sparse email. :)
-Kees
>
> fs/binfmt_flat.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/binfmt_flat.c b/fs/binfmt_flat.c
> index e5e2a03b39c1..dca0b6875f9c 100644
> --- a/fs/binfmt_flat.c
> +++ b/fs/binfmt_flat.c
> @@ -813,7 +813,7 @@ static int load_flat_file(struct linux_binprm *bprm,
> * image.
> */
> if (flags & FLAT_FLAG_GOTPIC) {
> - rp = skip_got_header((u32 * __user) datapos);
> + rp = skip_got_header((u32 __user *) datapos);
> for (; ; rp++) {
> u32 addr, rp_val;
> if (get_user(rp_val, rp))
> --
> 2.35.1
--
Kees Cook
next prev parent reply other threads:[~2022-04-18 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 20:09 Niklas Cassel
2022-04-18 22:01 ` Kees Cook [this message]
2022-04-19 14:16 ` [PATCH] binfmt_flat; Drop vestigates of coredump support Eric W. Biederman
2022-04-19 16:35 ` Niklas Cassel
2022-04-19 17:46 ` (subset) " Kees Cook
2022-04-20 13:48 ` Eric W. Biederman
2022-04-19 23:08 ` Greg Ungerer
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=202204181501.D55C8D2A@keescook \
--to=keescook@chromium.org \
--cc=Niklas.Cassel@wdc.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=ebiederm@xmission.com \
--cc=gerg@linux-m68k.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=stable@vger.kernel.org \
--cc=vapier@gentoo.org \
--cc=viro@zeniv.linux.org.uk \
/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