From: Greg Ungerer <gregungerer@westnet.com.au>
To: Max Filippov <jcmvbkbc@gmail.com>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Eric Biederman <ebiederm@xmission.com>,
Kees Cook <kees@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] binfmt_elf_fdpic: fix AUXV size calculation when ELF_HWCAP2 is defined
Date: Mon, 26 Aug 2024 17:00:13 +1000 [thread overview]
Message-ID: <aa4af643-47d3-4c26-8537-d86c1f73af68@westnet.com.au> (raw)
In-Reply-To: <20240826032745.3423812-1-jcmvbkbc@gmail.com>
Hi Max,
On 26/8/24 13:27, Max Filippov wrote:
> create_elf_fdpic_tables() does not correctly account the space for the
> AUX vector when an architecture has ELF_HWCAP2 defined. Prior to the
> commit 10e29251be0e ("binfmt_elf_fdpic: fix /proc/<pid>/auxv") it
> resulted in the last entry of the AUX vector being set to zero, but with
> that change it results in a kernel BUG.
>
> Fix that by adding one to the number of AUXV entries (nitems) when
> ELF_HWCAP2 is defined.
>
> Fixes: 10e29251be0e ("binfmt_elf_fdpic: fix /proc/<pid>/auxv")
> Cc: stable@vger.kernel.org
> Reported-by: Greg Ungerer <gregungerer@westnet.com.au>
Feel free to use my gerg@kernel.org email for this.
> Closes: https://lore.kernel.org/lkml/5b51975f-6d0b-413c-8b38-39a6a45e8821@westnet.com.au/
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
Certainly fixes it for all my failing test cases, so:
Tested-by: Greg Ungerer <gerg@kernel.org>
Thanks for looking into it and the fix.
Regards
Greg
> ---
> fs/binfmt_elf_fdpic.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/binfmt_elf_fdpic.c b/fs/binfmt_elf_fdpic.c
> index c11289e1301b..a5cb45cb30c8 100644
> --- a/fs/binfmt_elf_fdpic.c
> +++ b/fs/binfmt_elf_fdpic.c
> @@ -594,6 +594,9 @@ static int create_elf_fdpic_tables(struct linux_binprm *bprm,
>
> if (bprm->have_execfd)
> nitems++;
> +#ifdef ELF_HWCAP2
> + nitems++;
> +#endif
>
> csp = sp;
> sp -= nitems * 2 * sizeof(unsigned long);
next prev parent reply other threads:[~2024-08-26 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 3:27 Max Filippov
2024-08-26 7:00 ` Greg Ungerer [this message]
2024-08-26 20:06 ` Kees Cook
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=aa4af643-47d3-4c26-8537-d86c1f73af68@westnet.com.au \
--to=gregungerer@westnet.com.au \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=jack@suse.cz \
--cc=jcmvbkbc@gmail.com \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.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