From: Alejandro Colomar <alx@kernel.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Matthew Wilcox <willy@infradead.org>,
David Howells <dhowells@redhat.com>,
Kees Cook <keescook@chromium.org>,
linux-mm@kvack.org, Rolf Eike Beer <eb@emlix.com>,
Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Dave Jones <davej@redhat.com>
Subject: Re: 'struct dynamic': struct tag leak in UAPI headers
Date: Tue, 29 Aug 2023 19:46:36 +0200 [thread overview]
Message-ID: <ce394c7a-9bc1-7b58-266d-a9ed07b2a02a@kernel.org> (raw)
In-Reply-To: <87wmxdokum.fsf@email.froward.int.ebiederm.org>
[-- Attachment #1.1: Type: text/plain, Size: 1673 bytes --]
Hi Eric!
On 2023-08-29 18:48, Eric W. Biederman wrote:
>
> The kernel rules do allow removing the structure tag if we no one
> is using it. If someone is using it then the bug is a regression.
>
> If you have the energy you can do a good faith search to see if there
> is any likely hood that anyone is using it. At a quick look I don't
> see anything including linux/elf.h. Add in a debian code search
> (is there a github or gitlab code search?) and you can make a
> pretty firm dent how widespread that is.
Thanks for suggesting it. That gave me the energy. ;)
It seems nobody is using it. At least not in Debian.
$ # packages that contain 'include [<"]linux/elf\.h[">]'
$ curl -s https://codesearch.debian.net/results/e5e7c74dfcdae609/packages.txt > include
$ # packages that contain '\bstruct dynamic\b'
$ curl -s https://codesearch.debian.net/results/b23577e099048c6a/packages.txt > struct
$ cat struct include | sort | uniq -d
chromium
hurd
linux
qemu
qt6-webengine
qtwebengine-opensource-src
$ # chromium: Seems to hold a copy of the UAPI header. No uses of the tag.
$ # hurd: Same thing as chromium.
$ # linux: :)
$ # qemu: Same thing as chromium.
$ # qt6-webengine: Same thing as all.
$ # qtwebengine-opensource-src: Yet another copy.
>
> After a good faith search you can merge a patch to remove it,
> and then if anyone reports a problem because you somehow missed
> them you can revert the change.
I've prepared a patch. When it finishes building, I'll send it.
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-29 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 12:08 'struct dynamic': struct tag leak in UAPI headers Alejandro Colomar
2023-08-29 12:24 ` Matthew Wilcox
2023-08-29 13:27 ` Alejandro Colomar
2023-08-29 14:17 ` Matthew Wilcox
2023-08-29 14:20 ` Alejandro Colomar
2023-08-29 16:48 ` Eric W. Biederman
2023-08-29 17:46 ` Alejandro Colomar [this message]
[not found] ` <20230829185121.326228-1-alx@kernel.org>
[not found] ` <6bd4800d-5e99-48a0-a407-2213112f4fb2@kernel.org>
[not found] ` <202309220940.B2730B3B@keescook>
2023-09-22 16:44 ` Ping: [PATCH v1] elf, uapi: Remove struct tag 'dynamic' Kees Cook
2023-09-22 17:01 ` Alejandro Colomar
2023-09-22 17:03 ` 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=ce394c7a-9bc1-7b58-266d-a9ed07b2a02a@kernel.org \
--to=alx@kernel.org \
--cc=arnd@arndb.de \
--cc=davej@redhat.com \
--cc=dhowells@redhat.com \
--cc=eb@emlix.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.