linux-kernel - Re: [PATCH] kconfig: Avoid buffer underrun in choice input

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] [day] [month] [year] [list]

Message-ID: <BANLkTi=dbWOPcSqg5ueDzGJMoGDa9Bp3fA@mail.gmail.com>
Date:	Wed, 27 Apr 2011 10:35:49 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Michal Marek <mmarek@...e.cz>
Cc:	Ben Hutchings <ben@...adent.org.uk>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-kbuild@...r.kernel.org, Roman Zippel <zippel@...ux-m68k.org>
Subject: Re: [PATCH] kconfig: Avoid buffer underrun in choice input

On Wed, Apr 27, 2011 at 4:19 AM, Michal Marek <mmarek@...e.cz> wrote:
>
> I applied this on 8th April, see
> http://www.spinics.net/lists/linux-kbuild/msg04431.html. Please check
> linux-next before reposting patches next time, now I either have to rewind
> the kconfig branch or let Linus merge it with a duplicate commit :-(.

Merging the occasional duplicate is normal flow, don't worry about it.
I'd much rather see the occasional smaller diffstat due to a diff that
got applied in both sides than I'd see people rebasing just to avoid
some silly duplicate.

It's if two branches consistently have many duplicates that I react,
because it tends to be some systematic error (often excessive
rebasing, but it could be some "ownership" argument too)

The "occasionally the same fix made it through two different trees" is
not just normal, it's _expected_ in distributed development. If it
never happens, that's a sign that people are serializing overmuch.

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