linux-kernel - [PATCH v1 21/30] docs: reporting-issues: improve text on backup et. al

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: <13046cae22b876d818a8c49939bf5daac0437c5e.1761481839.git.linux@leemhuis.info>
Date: Sun, 26 Oct 2025 13:42:12 +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 21/30] docs: reporting-issues: improve text on backup et. al

Fine-tune the instructions about creating a backup and preparing for
emergencies.

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

diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst
index c34a95d5af4ac6..824b7b5394440e 100644
--- a/Documentation/admin-guide/reporting-issues.rst
+++ b/Documentation/admin-guide/reporting-issues.rst
@@ -176,7 +176,12 @@ following the others is usually in your own interest.
 
  [:ref:`details <otherplaces_repiref>`]
 
- * Create a fresh backup and put system repair and restore tools at hand.
+.. _backup_repisbs:
+
+* You might want to create a fresh backup and put both system repair and
+  restore tools at hand.
+
+ [:ref:`details <backup_repiref>`]
 
  * Ensure your system does not enhance its kernels by building additional
    kernel modules on-the-fly, which solutions like DKMS might be doing locally
@@ -904,17 +909,21 @@ or even more time can save everyone, including you, quite some trouble.
 [:ref:`back to step-by-step guide <otherplaces_repisbs>`]
 
 
+.. _backup_repiref:
+
 Prepare for emergencies
 -----------------------
 
-    *Create a fresh backup and put system repair and restore tools at hand.*
+  *You might want to create a fresh backup and put both* [:ref:`... <backup_repisbs>`]
+
+Remember, you are dealing with computers, which sometimes do unexpected things,
+especially if you fiddle with crucial parts like their operating system kernel.
+That is what you are about to do in this process. You thus better want to create
+a fresh backup. In case you need to install a kernel during the bug reporting
+process, also ensure you have all tools at hand to repair or reinstall the
+operating system as well as everything you need to restore the backup.
 
-Reminder, you are dealing with computers, which sometimes do unexpected things,
-especially if you fiddle with crucial parts like the kernel of its operating
-system. That's what you are about to do in this process. Thus, make sure to
-create a fresh backup; also ensure you have all tools at hand to repair or
-reinstall the operating system as well as everything you need to restore the
-backup.
+[:ref:`back to step-by-step guide <backup_repisbs>`]
 
 
 Make sure your kernel doesn't get enhanced
-- 
2.51.0