[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141030231310.0b65b762@alan.etchedpixels.co.uk>
Date: Thu, 30 Oct 2014 23:13:10 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Karol Lewandowski <k.lewandowsk@...sung.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Kosina <jkosina@...e.cz>,
Linux API <linux-api@...r.kernel.org>,
linux-kernel@...r.kernel.org, John Stultz <john.stultz@...aro.org>,
Arnd Bergmann <arnd@...db.de>, Tejun Heo <tj@...nel.org>,
Ryan Lortie <desrt@...rt.ca>,
Simon McVittie <simon.mcvittie@...labora.co.uk>,
daniel@...que.org, David Herrmann <dh.herrmann@...il.com>,
Paul Moore <pmoore@...hat.com>,
"casey.schaufler@...el.com" <casey.schaufler@...el.com>,
marcel@...tmann.org, tixxdz@...ndz.org,
javier.martinez@...labora.co.uk, alban.crequy@...labora.co.uk
Subject: Re: [PATCH 00/12] Add kdbus implementation
> > The core calls are already mediated by LSM today, right? We don't want
> > anyone to be parsing the data stream through an LSM, that idea got
> > rejected a long time ago as something that is really not a good idea.
>
> Parsing data is out of question, of course, but this is not what we were
> proposing.
Why is it out of the question. If it's a socket you can just a BPF filter
on it, so why can't kdbus support similar basic functionality ?
Alan
--
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