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, 29 Nov 2007 13:23:24 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Roland McGrath <roland@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH x86/mm 01/11] x86-32 thread_struct.debugreg


thanks, i've merged your 11 patches - they passed a basic build and boot 
test as well.

Roland, you've done a lot of gdb / strace / glibc development, what 
would you suggest for us to use as a ptrace regression checker? The 
problem is that ptrace is not normally used on a default bootup of a 
distro, and some of the ptrace features are really arcane. UML is an 
extensive ptrace user, so running it might be a good start, but do you 
know of any, more directed testsuite that is expected to hit all (or at 
least a substantial percentage of) the various ptrace features that we 
are affecting with these ptrace patches?

btw., your cleanup patches are having a nice effect on code quality as 
well:

                               errors   lines of code   errors/KLOC
   [before]    arch/x86/         5231          116998          44.7
   [after]     arch/x86/         5132          116656          43.9

(the 'errors' column is the sum of all .c files as per the error count 
of scripts/checkpatch.pl --file output)

it's refreshing to see life being brought back into the ptrace code 
again :-)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ