linux-kernel - Re: [PATCH] kernel-doc: Add initial binfmt docs

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 for Android: free password hash cracker in your pocket

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

Message-ID: <202504291028.523CF77C@keescook>
Date: Tue, 29 Apr 2025 10:28:58 -0700
From: Kees Cook <kees@...nel.org>
To: Jonathan Corbet <corbet@....net>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
	Randy Dunlap <rdunlap@...radead.org>,
	Bagas Sanjaya <bagasdotme@...il.com>,
	Mike Rapoport <rppt@...nel.org>, Arnd Bergmann <arnd@...db.de>,
	linux-doc@...r.kernel.org, linux-mm@...ck.org,
	Maxime Ripard <mripard@...nel.org>, Tejun Heo <tj@...nel.org>,
	Natalie Vock <natalie.vock@....de>, Xavier <xavier_qy@....com>,
	Samuel Holland <samuel.holland@...ive.com>,
	Maarten Lankhorst <dev@...khorst.se>,
	Dan Williams <dan.j.williams@...el.com>,
	Michael Kelley <mhklinux@...look.com>,
	Kuan-Wei Chiu <visitorckw@...il.com>,
	Christian Brauner <brauner@...nel.org>,
	linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH] kernel-doc: Add initial binfmt docs

On Mon, Apr 28, 2025 at 05:27:15PM -0600, Jonathan Corbet wrote:
> Kees Cook <kees@...nel.org> writes:
> 
> > Adds a framework to hold the initial exec.c and binfmt_elf.c
> > kernel-docs. Updates scripts/kernel-doc to allow leading whitespace so
> > that embedded "DOC:" tags can be found that aren't at the start of a
> > line so that in-function documentation can be found, like that recently
> > marked up in binfmt_elf.c[1].
> 
> Just one tiny little problem ... when you weren't looking, Mauro snuck
> in and replaced scripts/kernel-doc with a shiny new Python
> implementation.  So that part of the patch won't apply to docs-next; if
> you apply it somewhere else, the change will get lost.
> 
> I figured we were going to run into at least one of these ... sorry ...

Oh duh, yeah, I will go re-do this with -next.

-Kees

-- 
Kees Cook