linux-kernel - Re: [PATCH] binfmt_misc: pass binfmt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87r1y5zny2.fsf@mid.deneb.enyo.de>
Date:   Fri, 06 Mar 2020 13:07:33 +0100
From:   Florian Weimer <fw@...eb.enyo.de>
To:     YunQiang Su <syq@...ian.org>
Cc:     Laurent Vivier <laurent@...ier.eu>, torvalds@...ux-foundation.org,
        Greg KH <gregkh@...uxfoundation.org>,
        akpm@...ux-foundation.org, Al Viro <viro@...iv.linux.org.uk>,
        James Bottomley <James.Bottomley@...senpartnership.com>,
        linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-arch@...r.kernel.org, linux-api@...r.kernel.org,
        libc-alpha@...rceware.org
Subject: Re: [PATCH] binfmt_misc: pass binfmt_misc P flag to the interpreter

* YunQiang Su:

> Florian Weimer <fw@...eb.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?