linux-kernel - Re: Restriction on setting debug registers (HW breakpoint) at kernel space

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]

Message-ID: <alpine.DEB.2.20.1710182239360.2477@nanos>
Date:   Wed, 18 Oct 2017 22:43:12 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Probir Roy <proy.cse@...il.com>
cc:     LKML <linux-kernel@...r.kernel.org>, prasad@...ux.vnet.ibm.com,
        paulus@....ibm.com, Peter Zijlstra <peterz@...radead.org>,
        Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: Restriction on setting debug registers (HW breakpoint) at kernel
 space

On Fri, 13 Oct 2017, Probir Roy wrote:
> I am patching the perf tool of linux to set HW breakpoints at kernel
> space. I found that there is an interface for user-space
> (modify_user_hw_breakpoint) but no interface for system wide
> breakpoint modification. Older version of linux had this support by K.
> Prasad. I was wondering why linux remove this support. Moreover, when
> I patch the perf tool for kernel space breakpoint following steps from
> "modify_user_hw_breakpoint", kernel panics but nothing is written on
> log file. What could be the issue? Is it a race condition while
> modifying the address or is it because kernel restricts it to set HW
> breakpoint at some kernel address(if so, where is it written)?

Can you please provide the patch you use and the perf command line which
causes the kernel to panic?

Also telling which kernel version and hardware system you are using would
be helpful.

Thanks,

	tglx