linux-kernel - Re: [PATCH v1 1/1] kernel-doc: Issue warnings that were silently discarded

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: <87sees73i5.fsf@trenco.lwn.net>
Date: Wed, 05 Nov 2025 11:12:18 -0700
From: Jonathan Corbet <corbet@....net>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, Mauro Carvalho
 Chehab <mchehab+huawei@...nel.org>, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, Stephen Rothwell
 <sfr@...b.auug.org.au>
Subject: Re: [PATCH v1 1/1] kernel-doc: Issue warnings that were silently
 discarded

[Heads up to Stephen: this change will add a bunch of warnings that had
been dropped before.]

Andy Shevchenko <andriy.shevchenko@...ux.intel.com> writes:

> When kernel-doc parses the sections for the documentation some errors
> may occur. In many cases the warning is simply stored to the current
> "entry" object. However, in the most of such cases this object gets
> discarded and there is no way for the output engine to even know about
> that. To avoid that, check if the "entry" is going to be discarded and
> if there warnings have been collected, issue them to the current logger
> as is and then flush the "entry". This fixes the problem that original
> Perl implementation doesn't have.

I would really like to redo how some of that logging is done, but that
is an exercise for another day.  For now, I have applied this one,
thanks.

jon