linux-kernel - [PATCH 0/2] uprobes: Change handle_swbp() to expose bp_vaddr to handler

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: <20121230154657.GA28488@redhat.com>
Date:	Sun, 30 Dec 2012 16:46:57 +0100
From:	Oleg Nesterov <oleg@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>,
	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
Cc:	Ananth N Mavinakayanahalli <ananth@...ibm.com>,
	Anton Arapov <anton@...hat.com>,
	Frank Eigler <fche@...hat.com>,
	Josh Stone <jistone@...hat.com>,
	"Suzuki K. Poulose" <suzuki@...ibm.com>,
	linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] uprobes: Change handle_swbp() to expose bp_vaddr to
	handler_chain()

Hello.

Inspired by the recent uretrpobe RFC's. I think it simply makes no sense
to call handler/skip/arch_uprobe_pre_xol with regs->ip pointing to the
"random" address after the task hits bp.

Ananth, could you please confirm 2/2 can't break powerpc? It "obviously"
shouldn't because uprobe_get_swbp_addr() is a "nop" on ppc, but still
your ack is welcomed.

Oleg.

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