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]

Date:   Fri, 06 Mar 2020 12:40:39 +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:

> 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.