[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.DEB.2.10.1507081411410.12441@AMDC1262.digital.local>
Date: Wed, 08 Jul 2015 14:12:03 +0200 (CEST)
From: Paul Osmialowski <p.osmialowsk@...sung.com>
To: Lukasz Pawelczyk <l.pawelczyk@...sung.com>
Cc: Paul Moore <pmoore@...hat.com>,
James Morris <james.l.morris@...cle.com>,
Casey Schaufler <casey@...aufler-ca.com>,
"Serge E. Hallyn" <serge@...lyn.com>,
Kees Cook <keescook@...omium.org>,
Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
Stephen Smalley <sds@...ho.nsa.gov>,
Neil Brown <neilb@...e.de>,
Mark Rustad <mark.d.rustad@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Daniel Mack <daniel@...que.org>,
David Herrmann <dh.herrmann@...glemail.com>,
Djalal Harouni <tixxdz@...ndz.org>,
Shuah Khan <shuahkh@....samsung.com>,
Al Viro <viro@...iv.linux.org.uk>,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
Karol Lewandowski <k.lewandowsk@...sung.com>,
Lukasz Skalski <l.skalski@...sung.com>
Subject: Re: [RFC 5/8] kdbus: use LSM hooks in kdbus code
You're right about it. To be fixed. Thanks for spotting this.
On Wed, 8 Jul 2015, Lukasz Pawelczyk wrote:
>> + ret = -EPERM;
>> + goto exit_unref;
>> + }
>
> Also, why aren't the error codes passed from LSM? LSM can return
> anything, from EINVAL, to ENOMEM. Returning EPERM can be misleading.
>
View attachment "0005-kdbus-use-LSM-hooks-in-kdbus-code.patch" of type "TEXT/x-diff" (13167 bytes)
Powered by blists - more mailing lists