linux-kernel - Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+ekxPXBW0eBF_qV5zrrWYPsdnMm2EnE7Nv9_dgUuLtT0U=sUg@mail.gmail.com>
Date:	Thu, 28 Jan 2016 15:22:39 -0700
From:	Jeffrey Merkey <jeffmerkey@...il.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	dzickus@...hat.com, uobergfe@...hat.com, atomlin@...hat.com,
	mhocko@...e.cz, fweisbec@...il.com, tj@...nel.org,
	hidehiro.kawai.ez@...achi.com, cmetcalf@...hip.com
Subject: Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

>
> You obviously completely ignored this part of my reply:
>
>> > If we follow your argumentation we need another gazillion of
>> > conditional
>> > breakpoints in the kernel

Actually, I was not suggesting this at all.  But now that you mention
it, there is already a BUG() macro that inserts a a two byte u2DA
instruction instead of a one byte CC (int3) breakpoint instruction
that would be a good candidate for setting int3 breakpoints since the
code is already there and its a macro change build option.

Jeff