linux-kernel - Re: [RFC][PATCH] kmemcheck: divide and conquer

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:	Sat, 14 Jun 2008 08:31:14 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Vegard Nossum <vegard.nossum@...il.com>
Cc:	Pekka Enberg <penberg@...helsinki.fi>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC][PATCH] kmemcheck: divide and conquer


* Vegard Nossum <vegard.nossum@...il.com> wrote:

> Hi,
> 
> I've split the main x86/mm/kmemcheck.c file and made a subdirectory of 
> many files instead.
> 
> I have included the diffstat below, but I think the patch itself is 
> too big for the mailing list. It can instead be viewed at:
> 
> http://www.kernel.org/pub/linux/kernel/people/vegard/patches/0001-kmemcheck-divide-and-conquer.patch
> 
> The RFC part: Is this a good thing to do? I personally hate the 
> 4000-line files that are so commonly found in the kernel, and 
> therefore prefer this split-up. On the other hand, C lacks namespaces, 
> which sometimes leads to some really long and ugly names just to 
> prevent clashes in the future. But it's your call, I'll just do 
> whatever it takes to get in... ;-)

it's a very nice splitup! :-) [ Any Git coordinates to pick it up? ]

such a splitup opens up for future enhancements such as the sharing of 
opcode decoding between kmemcheck, mmiotrace and KVM. It also makes the 
code easier to maintain as there's less risk of patch merge conflicts. 
And not the least, it's easier to read as well if it's split up into 
logical modules.

	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/