From: Kees Cook <keescook@chromium.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-mm@kvack.org, "Eric W. Biederman" <ebiederm@xmission.com>,
Matthew Wilcox <willy@infradead.org>,
David Howells <dhowells@redhat.com>,
Rolf Eike Beer <eb@emlix.com>, Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: Ping: [PATCH v1] elf, uapi: Remove struct tag 'dynamic'
Date: Fri, 22 Sep 2023 09:44:56 -0700 [thread overview]
Message-ID: <202309220943.76F7DBF773@keescook> (raw)
In-Reply-To: <202309220940.B2730B3B@keescook>
On Fri, Sep 22, 2023 at 09:41:10AM -0700, Kees Cook wrote:
> On Fri, Sep 22, 2023 at 05:14:12PM +0200, Alejandro Colomar wrote:
> > Ping
> >
> > On 2023-08-29 20:51, Alejandro Colomar wrote:
> > > Such a generic struct tag shouldn't have been exposed in a public
> > > header. Since it's undocumented, we can assume it's a historical
> > > accident. And since no software (at least on Debian) relies on this
> > > tag, we can safely remove it.
>
> Hm, I can't find this "v1" patch on lore:
>
> https://lore.kernel.org/linux-mm/?q=f%3AAlejandro
Ah, now I see why: linux-mm is on kvack, not vger. Fixed in Cc now...
-Kees
--
Kees Cook
next prev parent reply other threads:[~2023-09-22 16:45 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
[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 ` Kees Cook [this message]
2023-09-22 17:01 ` Ping: [PATCH v1] elf, uapi: Remove struct tag 'dynamic' 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=202309220943.76F7DBF773@keescook \
--to=keescook@chromium.org \
--cc=alx@kernel.org \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=eb@emlix.com \
--cc=ebiederm@xmission.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox