linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Vagin <avagin@google.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Kees Cook <kees@kernel.org>,
	linux-kernel@vger.kernel.org,  linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org, criu@lists.linux.dev,
	 Andrew Morton <akpm@linux-foundation.org>,
	Chen Ridong <chenridong@huawei.com>,
	 Christian Brauner <brauner@kernel.org>,
	David Hildenbrand <david@kernel.org>,
	 Eric Biederman <ebiederm@xmission.com>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [PATCH 2/3] exec: inherit HWCAPs from the parent process
Date: Mon, 12 Jan 2026 14:18:18 -0800	[thread overview]
Message-ID: <CAEWA0a4s+Uhm405CnvNsE61ed5_xJ8PUZqL74zfeZnivw1BChA@mail.gmail.com> (raw)
In-Reply-To: <wfl47fj3l4xhffrwuqfn5pgtrrn3s64lxxodnz5forx7d4x443@spsi3sx33lnf>

On Mon, Jan 12, 2026 at 4:46 AM Michal Koutný <mkoutny@suse.com> wrote:
>
> On Thu, Jan 08, 2026 at 05:07:47AM +0000, Andrei Vagin <avagin@google.com> wrote:
> > @@ -1780,6 +1791,50 @@ static int bprm_execve(struct linux_binprm *bprm)
> >       return retval;
> >  }
> >
> > +static void inherit_hwcap(struct linux_binprm *bprm)
> > +{
> > +     int i, n;
> > +
> > +#ifdef ELF_HWCAP4
> > +     n = 4;
> > +#elif defined(ELF_HWCAP3)
> > +     n = 3;
> > +#elif defined(ELF_HWCAP2)
> > +     n = 2;
> > +#else
> > +     n = 1;
> > +#endif
>
> Is it guaranteed that HWCAP n+1 exists only when n does?
> (To make this work.)
>

It is true for all existing arch-es. I can't imagine why we would want to
define ELF_HWCAP{n+1} without having ELF_HWCAP{n}. If you think we need
to handle this case, I can address it in the next version.

It is just a small optimization to stop iterating after handling all
entries. The code will work correctly even when HWCAP n+1 exists but n
doesn't.

>
> > +
> > +     for (i = 0; n && i < AT_VECTOR_SIZE; i += 2) {
> > +             long val = current->mm->saved_auxv[i + 1];
> > +
> > +             switch (current->mm->saved_auxv[i]) {
> > +             case AT_HWCAP:
> > +                     bprm->hwcap = val & ELF_HWCAP;
> > +                     break;
> > +#ifdef ELF_HWCAP2
> > +             case AT_HWCAP2:
> > +                     bprm->hwcap2 = val & ELF_HWCAP2;
> > +                     break;
> > +#endif
> > +#ifdef ELF_HWCAP3
> > +             case AT_HWCAP3:
> > +                     bprm->hwcap3 = val & ELF_HWCAP3;
> > +                     break;
> > +#endif
> > +#ifdef ELF_HWCAP4
> > +             case AT_HWCAP4:
> > +                     bprm->hwcap4 = val & ELF_HWCAP4;
> > +                     break;
> > +#endif
> > +             default:
> > +                     continue;
> > +             }
> > +             n--;
> > +     }
> > +     mm_flags_set(MMF_USER_HWCAP, bprm->mm);
>
> Will this work when mm->saved_auxv isn't set by the prctl (it is
> zeroes?)?

The inherit_hwcap function is only called if MMF_USER_HWCAP is set (auxv was
modified via prctl). However, even if mm->saved_auxv hasn't been
modified, it still
contains valid values.

Thanks,
Andrei

ps: Please ignore the html version I mistakenly sent.


  parent reply	other threads:[~2026-01-12 22:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08  5:07 [PATCH 0/3 v2] " Andrei Vagin
2026-01-08  5:07 ` [PATCH 1/3] binfmt_elf_fdpic: fix AUXV size calculation for ELF_HWCAP3 and ELF_HWCAP4 Andrei Vagin
2026-01-08 11:31   ` Mark Brown
2026-01-12 12:38   ` Michal Koutný
2026-01-08  5:07 ` [PATCH 2/3] exec: inherit HWCAPs from the parent process Andrei Vagin
2026-01-12 12:46   ` Michal Koutný
2026-01-12 21:56     ` Andrei Vagin
2026-01-12 22:18     ` Andrei Vagin [this message]
2026-01-08  5:07 ` [PATCH 3/3] selftests/exec: add test for HWCAP inheritance Andrei Vagin

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=CAEWA0a4s+Uhm405CnvNsE61ed5_xJ8PUZqL74zfeZnivw1BChA@mail.gmail.com \
    --to=avagin@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=chenridong@huawei.com \
    --cc=criu@lists.linux.dev \
    --cc=david@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=kees@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mkoutny@suse.com \
    /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