From: Florian Weimer <fw@deneb.enyo.de>
To: YunQiang Su <syq@debian.org>
Cc: Laurent Vivier <laurent@vivier.eu>,
torvalds@linux-foundation.org,
Greg KH <gregkh@linuxfoundation.org>,
akpm@linux-foundation.org, Al Viro <viro@zeniv.linux.org.uk>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-arch@vger.kernel.org, linux-api@vger.kernel.org,
libc-alpha@sourceware.org
Subject: Re: [PATCH] binfmt_misc: pass binfmt_misc P flag to the interpreter
Date: Fri, 06 Mar 2020 13:07:33 +0100 [thread overview]
Message-ID: <87r1y5zny2.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CAKcpw6VF1N2gTVXeWLU4aVOuARf5oN6yPg9O=RCzgkMrjXmxYQ@mail.gmail.com> (YunQiang Su's message of "Fri, 6 Mar 2020 19:48:35 +0800")
* YunQiang Su:
> Florian Weimer <fw@deneb.enyo.de> 于2020年3月6日周五 下午7:42写道：
>>
>> * YunQiang Su:
>>
>> > AT_* only has 32 slot and now. I was afraid that maybe we shouldn't take one.
>> > /* AT_* values 18 through 22 are reserved */
>> > 27,28,29,30 are not used now.
>> > Which should we use?
>>
>> Where does this limit of 32 tags come from? I don't see it from a
>> userspace perspective.
>
> Sorry it is my mistake: In linux/auxvec.h, I saw
>
> #define AT_RANDOM 25 /* address of 16 random bytes */
> #define AT_HWCAP2 26 /* extension of AT_HWCAP */
>
> #define AT_EXECFN 31 /* filename of program */
>
> The number jump to 31 from 26.
>
> It is my fault: in x86_64-linux-gnu/bits/auxv.h, the max number is 47 now.
So AT_* tags aren't a scarce resource after all?
next prev parent reply other threads:[~2020-03-06 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 8:09 [PATCH] binfmt_misc: pass binfmt_misc P flag to the interpreter YunQiang Su
2020-03-06 8:13 ` Florian Weimer
2020-03-06 8:21 ` Laurent Vivier
2020-03-06 8:37 ` Florian Weimer
2020-03-06 11:13 ` Laurent Vivier
2020-03-06 11:29 ` YunQiang Su
2020-03-06 11:40 ` Florian Weimer
2020-03-06 11:48 ` YunQiang Su
2020-03-06 12:07 ` Florian Weimer [this message]
2020-03-06 12:07 ` Laurent Vivier
2020-03-11 9:09 ` Laurent Vivier
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=87r1y5zny2.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=laurent@vivier.eu \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syq@debian.org \
--cc=torvalds@linux-foundation.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