linux-kernel - Update "If something goes wrong" in Documentation/admin-guide/README.rst

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

Date:   Wed, 13 Jul 2022 09:26:50 +0200
From:   Lukas Bulwahn <lukas.bulwahn@...il.com>
To:     Thorsten Leemhuis <linux@...mhuis.info>,
        Jonathan Corbet <corbet@....net>,
        "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Update "If something goes wrong" in Documentation/admin-guide/README.rst

Dear Thorsten, dear Jonathan,

During some other unrelated clean-up work, I stumbled upon the section
'If something goes wrong' in Documentation/admin-guide/README.rst
(https://www.kernel.org/doc/html/latest/admin-guide/README.html).
README.rst is---as it seems---the intended first summary page of the
documentation for any user of the kernel (the kernel's release notes
document).

The section 'If something goes wrong' describes what to do when
encountering a bug and how to report it. The second sentence in that
section is especially historic and probably just discouraging for most
bug reporters ( ..."the second best thing is to mail them to me
(torvalds@...ux-foundation.org)"...). Some random user (potentially
even unknown to the community) sending an email to Linus is most
probably the last best thing to do and is most likely just ignored,
right?

Probably this section in README.rst needs a rewrite (summarizing
Thorsten's reporting-issues.rst, or just copying the summary from
there) and should then refer to reporting-issues.rst for more details.

Thorsten, do you have time to prepare a change to that document that
gives a short summary on how to report potential issues and
regressions? Otherwise, I will happily put that on my todo list and
probably can suggest some RFC patch in a week or two.

Best regards,

Lukas