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]

Date:	Thu, 28 Jan 2016 23:06:30 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jeffrey Merkey <jeffmerkey@...il.com>
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

On Thu, 28 Jan 2016, Jeffrey Merkey wrote:
> On 1/28/16, Thomas Gleixner <tglx@...utronix.de> wrote:
> If you don't get it Thomas, I don't know what else to say.  Right now
> the only debugger that provides disassembly on a single running live
> Linux system is the one I use unless you want to use a serial
> connection with kgdb.  All you are convincing me of is that you don't
> use a debugger or sit around looking at dissassembly all day long on
> live linux systems looking for bugs or you would understand why this
> is so helpful.  So I totally understand why you don't get this.

It does not matter a whit whether I use a debugger or not. It matters that I
can find out without too much hassle where this stupid address is where I want
to set my breakpoint. It's not rocket science.
 
> Think of it like git.  Before git was around, everything was done with
> manual patches.  Now we have git, and everything can be automated.
> Same thing here.  Why do I want to grep around looking for a bug when
> I can have linux find it for me.

Using the proper tools you can figure that address out fully automated without
rumaging in disassembly.

You obviously completely ignored this part of my reply:

> > If we follow your argumentation we need another gazillion of conditional
> > breakpoints in the kernel.

Thanks,

	tglx