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: <552E3522.8030206@nod.at>
Date:	Wed, 15 Apr 2015 11:53:38 +0200
From:	Richard Weinberger <richard@....at>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:	Borislav Petkov <bp@...en8.de>,
	Andy Lutomirski <luto@...capital.net>,
	Al Viro <viro@...iv.linux.org.uk>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Arnd Bergmann <arnd@...db.de>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Tom Gundersen <teg@...m.no>, Jiri Kosina <jkosina@...e.cz>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Daniel Mack <daniel@...que.org>,
	David Herrmann <dh.herrmann@...il.com>,
	Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1

Am 15.04.2015 um 11:49 schrieb Greg Kroah-Hartman:
> On Wed, Apr 15, 2015 at 11:30:52AM +0200, Richard Weinberger wrote:
>> Am 15.04.2015 um 11:27 schrieb Greg Kroah-Hartman:
>>> On Wed, Apr 15, 2015 at 11:21:49AM +0200, Borislav Petkov wrote:
>>>> On Wed, Apr 15, 2015 at 11:20:34AM +0200, Greg Kroah-Hartman wrote:
>>>>>> We're all forced to use cgroups, systemd, udev unless we want to have busybox
>>>>>> as userland. That's a fact.
>>>>>
>>>>> Is that a problem?
>>>>
>>>> I'm amazed that you're really actually asking that question :-(
>>>
>>> Really?  Why can't userspace rely on the features that the kernel
>>> provides them?  If not, why would the feature be created and supported
>>> by us kernel developers in the first place?
>>
>> This IMHO not the problem.
>> But if we add a new component to the kernel which *will* be used
>> by almost every userland out there (systemd won the "init wars")
>> we have to make sure that we're all fine with it.
> 
> Sure, but why would this be different from any other kernel feature that
> we add?  We have to be sure we are fine with everything we merge, as we
> are saying we are going to maintain this stuff for forever.

There is nothing different. The series has currently two NACKs,
0 ACKs and 0 Reviews.
I don't think that any other series would get merged in such a state.

>> Andy and Eric have some very valid concerns.
> 
> I've tried to address Andy's concerns, Eric is not being very specific,
> so there's nothing I can do there :)

What about Stevens proposal to talk at Plumbers?
I fear the discussion is at a dead end and needs a face to face
resolution.

Thanks,
//richard
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ