linux-kernel - Re: [Ksummit-2012-discuss] [ATTEND or not ATTEND] That's the question!

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: <20120615233413.GB8894@kroah.com>
Date:	Fri, 15 Jun 2012 16:34:13 -0700
From:	Greg KH <greg@...ah.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	ksummit-2012-discuss@...ts.linux-foundation.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-2012-discuss] [ATTEND or not ATTEND] That's the
 question!

On Sat, Jun 16, 2012 at 12:56:36AM +0200, Thomas Gleixner wrote:
> So the main questions I want to raise on Kernel Summit are:
> 
>    - How do we cope with the need to review the increasing amount of
>      (insane) patches and their potential integration?

That's a very good question, and I've been wondering if someone is
trying to flood us with crap submissions just to try to DoS us and slow
us down.  If not, it's an interesting "attack" vector onto our
development process that we need to be able to handle better.

>    - How do we prevent further insanity to known problem spaces (like
>      cpu hotplug) without stopping progress?

Progress can slow, if we want it to, in some areas, just to let people
get the time to fix up the issues we currently have.  That saves time in
the long run, but requires that someone make it very clear as to what is
going on and how it will change in the future.

But, both of these are great things to talk about, I like it.

> A side question, but definitely related is:
> 
>    - How do we handle "established maintainers" who are mainly
>      interested in their own personal agenda and ignoring justified
>      criticism just because they can?

The wonderful, "how do we remove a maintainer who isn't working out"
problem.  It's a tough one, I don't think we really have any standard
way.  Luckily in the past, the insane ones went away on their own :)

greg k-h
--
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/