linux-kernel - Re: Announce: Linux-next (Or Andrew's dream :-))

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: <adar6fivzvj.fsf@cisco.com>
Date:	Tue, 12 Feb 2008 09:38:40 -0800
From:	Roland Dreier <rdreier@...co.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Jeff Garzik <jeff@...zik.org>, David Miller <davem@...emloft.net>,
	arjan@...radead.org, greg@...ah.com, sfr@...b.auug.org.au,
	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
	linux-arch@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))

 > The other is that once somebody says "ok, I *really* need to cause this 
 > breakage, because there's a major bug or we need it for fundamental reason 
 > XYZ", then that person should
 > 
 >  (a) create a base tree with _just_ that fundamental infrastructure change,
 >      and make sure that base branch is so obviously good that there is no 
 >      question about merging it.

I don't disagree with this, but I think I should point out that making
something "obviously good" may be pretty hard.  It's clearly a common
case that the infrastructure change goes through several rounds of
change -- perhaps prompted by exposure in -mm that shows a subtle
issue.  So then if all other maintainers based their trees on this
tree, we're left with two not-so-great alternatives:

 1) merge the original, broken infrastructure change into your
    (Linus's) tree, leaving a known problem for bisecters to trip
    over.

 2) rebase the world.

I don't know if there's really a perfect answer here.  I hope that
tree-wide infrastructure breakage is uncommon enough that we can just
handle these issues "by hand" as they come up.

 - R.
--
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/