[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150413195458.GA11672@kroah.com>
Date: Mon, 13 Apr 2015 21:54:58 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Richard Weinberger <richard.weinberger@...il.com>
Cc: "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>,
Andy Lutomirski <luto@...capital.net>,
LKML <linux-kernel@...r.kernel.org>, daniel@...que.org,
David Herrmann <dh.herrmann@...il.com>,
Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1
On Mon, Apr 13, 2015 at 09:49:27PM +0200, Richard Weinberger wrote:
> On Mon, Apr 13, 2015 at 9:42 PM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> >> I remain opposed to this half thought out trash of an ABI for the
> >> meta-data.
> >
> > You don't have to enable the metadata if you don't want to use it, it's
> > an option :)
>
> Wasn't this also an argument for CONFIG_CGROUPS?
> Now we're forced to enable it by default to boot a recent distro
> and CONFIG_CGROUPS is still not fixed.
CONFIG_CGROUPS is "not fixed"? I think Tejun would like to have some
words with you :)
Anyway, yes, it's an option, but given that people are using this
metadata today in userspace just fine, I fail to see how having the
kernel be a transport for this same data is an issue. When the kernel
is the transport, it can do so in a race-free way, and you can properly
do security tests/logic based on it.
thanks,
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/
Powered by blists - more mailing lists