linux-kernel - [Patch 0/2 v2] Improvements for hw_breakpoint

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]

Message-ID: <20100128111347.GA13935@in.ibm.com>
Date:	Thu, 28 Jan 2010 16:43:47 +0530
From:	"K.Prasad" <prasad@...ux.vnet.ibm.com>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Roland McGrath <roland@...hat.com>,
	Alan Stern <stern@...land.harvard.edu>,
	Jan Kiszka <jan.kiszka@...mens.com>
Subject: [Patch 0/2 v2] Improvements for hw_breakpoint_handler()

Hi Frederic,
        Can you please pull the second version of the patch which perform
the  following.

Patch 1/2: Clears the arch-reserved bits from debug status register. This
helps easy bitwise operations - such as the check for non-trap bits in
hw_breakpoint_handler. A check for the same using
"if (dr6 & (~DR_TRAP_BITS))" throws incorrect results due to the
presence of preset reserved bits.

Patch 2/2: Return NOTIFY_DONE from hw_breakpoint_handler() for interested
user-space breakpoints (and not unconditionally) since this could lead to
further processing in do_debug() with undesirable consequences.

Changelog ver II
----------------
Version I: LKML ref: 20091226182519.GA9494@...ibm.com

- Return NOTIFY_DONE for further processing (i.e. signal delivery) only for
  interested user-space breakpoints i.e. with current->thread.debugreg6 bits
  set.

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/