linux-kernel - Re: kgdb test suite failure

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]

Date:	Tue, 27 May 2008 20:43:17 -0500
From:	Jason Wessel <jason.wessel@...driver.com>
To:	David Miller <davem@...emloft.net>
CC:	tglx@...utronix.de, a.beregalov@...il.com,
	kgdb-bugreport@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	mingo@...e.hu
Subject: Re: kgdb test suite failure

David Miller wrote:
> From: Thomas Gleixner <tglx@...utronix.de>
> Date: Thu, 22 May 2008 23:14:23 +0200 (CEST)
>
>> Please use HW breakpoints in the test suite. The RFC patch looks
>> horrible :)
>
> ftrace needs basically the same kind of facility as kgdb
> needs here. So bypassing the need for kgdb won't get around
> the problem in general.

It does seem like there should be a general way to force a controlled
write to a read-only page. That would certainly allow for the use of
software breakpoints with KGDB. At the point in time that such calls
come into existence I would certainly consider adding a toggle which
you can use from the debugger to provide such access.

At least for the current time for kgdb, we will use hardware
breakpoints.

Jason.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/