linux-kernel - Re: [git pull] x86 updates for v2.6.28, phase #6, misc

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 09 Oct 2008 21:18:23 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Nick Piggin <nickpiggin@...oo.com.au>
CC:	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [git pull] x86 updates for v2.6.28, phase #6, misc

Nick Piggin wrote:
> On Friday 10 October 2008 11:08, Ingo Molnar wrote:
>
>   
>> out-of-topic modifications in x86-v28-for-linus-phase6:
>> -------------------------------------------------------
>> include/linux/kernel.h             # d974ae3: generic, memparse(): constify
>> arg include/linux/mm.h                 # f7d0b92: mm: define
>> USE_SPLIT_PTLOCKS rath # 59ea746: MM: virtual address debug
>> include/linux/mm_types.h           # f7d0b92: mm: define USE_SPLIT_PTLOCKS
>> rath include/linux/mmdebug.h            # 7aa413d: x86, MM: virtual address
>> debug, c # 59ea746: MM: virtual address debug lib/cmdline.c                
>>      # d974ae3: generic, memparse(): constify arg mm/vmalloc.c             
>>          # 7aa413d: x86, MM: virtual address debug, c # 59ea746: MM:
>> virtual address debug
>>     
>
>
> How come these kinds of things go into the x86 tree? Can't they
> be sent to other maintainer first (probably Andrew, in the case
> of random -mm stuff).
>
> OK, it's pretty trivial stuff, but just on principle I can't see
> an advantage, and only disadvantages to doing this (and also I
> see the vmalloc change clashed with the vmalloc rewrite in -mm).

The memparse and split ptlocks changes went past Andrew.  They ended up 
in Ingo's tree because 1) they're pretty trivial, and 2) there's 
x86-specific stuff which depends on them.  Don't know about the vmalloc 
change.

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