From: Ben Smith <ben.smith@crowdstrike.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
"linux-security-module@vger.kernel.org"
<linux-security-module@vger.kernel.org>
Subject: Re: [External] Re: security_file_free contract/expectations
Date: Thu, 25 Jan 2024 19:26:04 +0000 [thread overview]
Message-ID: <1286AF3E-772D-4666-93DC-F9D4A57DF77C@crowdstrike.com> (raw)
In-Reply-To: <CAHC9VhQo7NLqyPSacjVpwtFaW-_3YaHn=-N4qaik+z+9rY-ejA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On 1/25/24, 11:03 AM, "Paul Moore" <paul@paul-moore.com <mailto:paul@paul-moore.com>> wrote:
> I also want to make it clear that there are no guarantees that the LSM
> hooks you're concerned about won't change tomorrow; the kernel's
> stable ABI guarantee does not extend to the LSM hooks. If you, or
> your company, make the decision to support out-of-tree kernel code
> that relies on the LSM hooks, the expectation is that you will be
> shouldering the support burden yourself.
Yes, we're aware that this is not guaranteed to be stable. The question was mainly
about existing kernels, which is what we have to support.
Unfortunately, it'll be a little while before we get to use any new hooks.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4406 bytes --]
prev parent reply other threads:[~2024-01-25 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 23:46 security_file_free contract/expectations Ben Smith
2024-01-25 1:14 ` Casey Schaufler
2024-01-25 8:47 ` Roberto Sassu
2024-01-25 16:43 ` [External] " Ben Smith
2024-01-25 16:36 ` Ben Smith
2024-01-25 15:19 ` Tetsuo Handa
2024-01-25 17:18 ` [External] " Ben Smith
2024-01-25 19:03 ` Paul Moore
2024-01-25 19:26 ` Ben Smith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1286AF3E-772D-4666-93DC-F9D4A57DF77C@crowdstrike.com \
--to=ben.smith@crowdstrike.com \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).