linux-kernel - Re: [PATCH 0/2] kgdb: x86: fix breakpoint removal problems

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: <20240813171055.f8805c1db539dfa18e80026b@linux-foundation.org>
Date: Tue, 13 Aug 2024 17:10:55 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Florian Rommel <mail@...rommel.de>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
 Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
 "H . Peter Anvin" <hpa@...or.com>, Jason Wessel
 <jason.wessel@...driver.com>, Daniel Thompson <daniel.thompson@...aro.org>,
 Douglas Anderson <dianders@...omium.org>, Lorena Kretzschmar
 <qy15sije@....cs.fau.de>, Stefan Saecherl <stefan.saecherl@....de>, Peter
 Zijlstra <peterz@...radead.org>, Christophe JAILLET
 <christophe.jaillet@...adoo.fr>, Randy Dunlap <rdunlap@...radead.org>,
 Masami Hiramatsu <mhiramat@...nel.org>, Christophe Leroy
 <christophe.leroy@...roup.eu>, Geert Uytterhoeven
 <geert+renesas@...der.be>, kgdb-bugreport@...ts.sourceforge.net,
 x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] kgdb: x86: fix breakpoint removal problems

On Mon, 12 Aug 2024 01:22:06 +0200 Florian Rommel <mail@...rommel.de> wrote:

> This series fixes two problems with KGDB on x86 concerning the removal
> of breakpoints, causing the kernel to hang.  Note that breakpoint
> removal is not only performed when explicitly deleting a breakpoint,
> but also happens before continuing execution or single stepping.

Neat.  It would be nice to fix earlier kernels; for that it is
desirable to identify a Fixes: target.  From a quick look it appears
this issue is more than a decade old, in which case I don't believe a
Fixes: is needed - our request becomes "please backport to everything".