linux-kernel - [RFC Patch 0/9] Hardware Breakpoint interfaces

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:	Thu, 22 Jan 2009 19:26:40 +0530
From:	"K.Prasad" <prasad@...ux.vnet.ibm.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Roland McGrath <roland@...hat.com>, akpm@...ux-foundation.org,
	mingo@...e.hu, richardj_moore@...ibm.com,
	prasad@...ux.vnet.ibm.com, naren@...ux.vnet.ibm.com
Subject: [RFC Patch 0/9] Hardware Breakpoint interfaces - v4

Hi All,
	Please find the new set of patches that introduce kernel
interfaces to use Hardware Breakpoint registers and an implementation
for x86 (and x86_64) architecture, now labelled as Version IV.

The patches are based on 2.6.29-rc2 and have been tested to work fine on
x86 architecture. Some of the major changes over the previous version of
patches include:
i) A sample kernel module that uses Data Hardware breakpoint over a
kernel variable to monitor write operations. See
samples/hw_breakpoint/data_breakpoint.c.
ii) Changes in the register_kernel_hw_breakpoint() interface to accept
only one parameter - pointer to a 'hw_breakpoint' structure which will
contain all relevant data members.

Attempts to convert KGDB to use the proposed interfaces is stalled due
to an issue with KGDB (detailed here: http://tinyurl.com/aa9agy) and any
help from its maintainers will be gladly welcomed.

Pending any serious issues/comments, the next revision of patches will
be cleaved of the RFC tag and will be requested for inclusion.

Thanks,
K.Prasad

--
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/