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: <87seq1xffx.fsf@trenco.lwn.net>
Date: Thu, 02 Jan 2025 11:01:54 -0700
From: Jonathan Corbet <corbet@....net>
To: "Russell King (Oracle)" <linux@...linux.org.uk>, Oleksij Rempel
 <o.rempel@...gutronix.de>
Cc: Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet
 <edumazet@...gle.com>, Andrew Lunn <andrew+netdev@...n.ch>, Heiner
 Kallweit <hkallweit1@...il.com>, kernel@...gutronix.de,
 linux-kernel@...r.kernel.org, netdev@...r.kernel.org, Simon Horman
 <horms@...nel.org>, Maxime Chevallier <maxime.chevallier@...tlin.com>,
 linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next v1 1/1] net: phy: Move callback comments from
 struct to kernel-doc section

"Russell King (Oracle)" <linux@...linux.org.uk> writes:

> This is the fundamental problem with kernel-doc, when it's missing
> something that really should already be there. It's not like we're
> the first to use function pointers in structs - that's a thing that
> the kernel has been doing for decades.

Unfortunately, kernel-doc is a gnarly collection of Perl regexes that
first appeared in 2.3.52pre1 some 25 years ago and has only grown more
gnarly since.

> I also have no desire to attempt to fix kernel-doc -

Neither does anybody else.  There are a few of us who will mount an
expedition into those dark woods on occasion to fix something, but there
is little desire on any part to make significant improvements, including
adding things that should already be there.  It's just barely
maintainable.

The proper solution is to reimplement kernel-doc in a language that
people actually want to deal with, cleaning out 25 years of cruft in the
process.  One way to do that would be to bring that functionality
directly into our Sphinx extension, rewriting it in Python.  An
alternative I have been considering, as a learning project that would
make me One Of The Cool Kids again, would be to do it in Rust instead.

For the time being, though, I wouldn't hold my breath for getting this
kind of improvement into kernel-doc.  I wish I could say otherwise.

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ