[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200820223136.162850ce@oasis.local.home>
Date: Thu, 20 Aug 2020 22:31:36 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Stephen Smalley <stephen.smalley.work@...il.com>
Cc: Thiébaud Weksteen <tweek@...gle.com>,
Paul Moore <paul@...l-moore.com>,
Nick Kralevich <nnk@...gle.com>,
Peter Enderborg <peter.enderborg@...y.com>,
Eric Paris <eparis@...isplace.org>,
Ingo Molnar <mingo@...hat.com>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Rob Herring <robh@...nel.org>, linux-kernel@...r.kernel.org,
selinux@...r.kernel.org
Subject: Re: [PATCH v3 3/3] selinux: add permission names to trace event
On Wed, 19 Aug 2020 09:11:08 -0400
Stephen Smalley <stephen.smalley.work@...il.com> wrote:
> So we'll need to update this plugin whenever we modify
> security/selinux/include/classmap.h to keep them in sync. Is that a
> concern? I don't suppose the plugin could directly include classmap.h?
> I guess we'd have to export it as a public header. It isn't considered
> to be part of the kernel API/ABI and can change anytime (but in practice
> changes are not that frequent, and usually just additive in nature).
Yes, it would require some stability between userspace and the plugin.
If the value indexes don't change then that would work fine. If you add
new ones, that too should be OK, just have a way to state "unknown" in
the plugin.
-- Steve
Powered by blists - more mailing lists