linux-kernel - [PATCH v1 16/30] docs: reporting-issues: add fast-track for regressions

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: <279303a7d230ac7c9db13cf7cf807732946badb3.1761481839.git.linux@leemhuis.info>
Date: Sun, 26 Oct 2025 13:42:07 +0100
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Jonathan Corbet <corbet@....net>
Cc: workflows@...r.kernel.org,
	linux-doc@...r.kernel.org,
	regressions@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: [PATCH v1 16/30] docs: reporting-issues: add fast-track for regressions

Some regressions are reported multiple times within a short time frame,
so it's worth asking on the regressions mailing list: subscribers might
already known about them and might safe the reporter a lot of trouble,
as reporting it again is unlikely to do much of a difference.

Signed-off-by: Thorsten Leemhuis <linux@...mhuis.info>
---
 .../admin-guide/reporting-issues.rst          | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst
index be0e49046ec913..f040ca7c0a2f59 100644
--- a/Documentation/admin-guide/reporting-issues.rst
+++ b/Documentation/admin-guide/reporting-issues.rst
@@ -136,6 +136,19 @@ following the others is usually in your own interest.
 
  [:ref:`details <specialtreat_repiref>`]
 
+.. _reginquiry_repisbs:
+
+* Do you face a regression? One still occurring in a kernel version less than
+  two (ideally: one) weeks old? A kernel that is vanilla or close to it? If
+  you answered all three questions with 'yes', feel free to send a brief email
+  to the public 'Linux regressions mailing list <regressions@...ts.linux.dev>'
+  asking if the problem is known. If someone confirms this to be the case,
+  there most likely is no need to follow this guide further; but do so in case
+  there is no reply with a pointer to a matching report within two or three
+  weekdays. You are also free to immediately continue if you feel like it.
+
+ [:ref:`details <reginquiry_repiref>`]
+
  * Create a fresh backup and put system repair and restore tools at hand.
 
  * Ensure your system does not enhance its kernels by building additional
@@ -676,6 +689,22 @@ development process:
 [:ref:`back to step-by-step guide <specialtreat_repisbs>`]
 
 
+.. _reginquiry_repiref:
+
+Fast track for regressions
+--------------------------
+
+  *Do you face a regression? One still occurring in a kernel version less than
+  two (ideally: one) weeks old? A kernel that is vanilla or close to it? If you
+  answered* [:ref:`... <reginquiry_repisbs>`]
+
+This is an optional fast track that might relieve you from further work on
+reporting in case the issue is already known. Note: It are volunteers that
+answer these emails on a best-effort basis.
+
+[:ref:`back to step-by-step guide <reginquiry_repisbs>`]
+
+
 Prepare for emergencies
 -----------------------
 
-- 
2.51.0