linux-kernel - Re: [PATCH v2 0/6] docs: verify/bisect: fine tuning, testing fixes, build host, order

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] [day] [month] [year] [list]

Message-ID: <87bk6awr64.fsf@meer.lwn.net>
Date: Mon, 15 Apr 2024 10:01:55 -0600
From: Jonathan Corbet <corbet@....net>
To: Thorsten Leemhuis <linux@...mhuis.info>
Cc: regressions@...ts.linux.dev, linux-doc@...r.kernel.org,
 linux-kernel@...r.kernel.org, Bagas Sanjaya <bagasdotme@...il.com>, Petr
 Tesařík <petr@...arici.cz>
Subject: Re: [PATCH v2 0/6] docs: verify/bisect: fine tuning, testing fixes,
 build host, order

Thorsten Leemhuis <linux@...mhuis.info> writes:

> A quick series with various improvements for
> Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst after
> receiving feedback on the text or seeing people struggle with certain
> tasks.
>
> * The first two patches contains various fixes and some fine tuning.
>
> * The third is mainly a layout improvement that results in a somewhat
>   large patch.
>
> * The fourth adds instructions for later testing of reverts, fixes, or
>   newer versions. This was already hinted at; but during some early
>   work on Documentation/admin-guide/reporting-issues.rst to better
>   reconcile the two it seemed wise to cover this properly here.
>
> * The fifth patch briefly outlines how to build kernels on a different
>   host; it came into being after a second user within one week asked for
>   this. That also allowed the text to briefly cover cross-compilation.
>
> * The sixth makes users that face a regression within a stable series
>   test that series first before they are told to test mainline.
> ---
>
> Hi! While at it let me mention one more thing unrelated to the changes
> that came up where I'm unsure if the current approach by the text was
> a wise choice:
>
> * Should the document tell users to avoid mainline during merge windows?
>
> Some input from the community on this would be splendid.
>
> Ciao, Thorsten
>
> P.S.: Not totally sure, but I think this should go into 6.9 as this is
> a new document; if not I guess it would be wise to pick the first two,
> as they fix bugs.

Nobody seems to be complaining, so I've gone ahead and applied the set
to docs-fixes.

Thanks,

jon