From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul@paul-moore.com>, linux-security-module@vger.kernel.org
Cc: selinux@vger.kernel.org,
"John Johansen" <john.johansen@canonical.com>,
"Mickaël Salaün" <mic@digikod.net>,
"Casey Schaufler" <casey@schaufler-ca.com>
Subject: Re: [RFC PATCH 0/3] LSM syscall tweaks
Date: Wed, 1 Nov 2023 15:26:23 -0700 [thread overview]
Message-ID: <2c71a8a6-cadc-474f-bb70-857ac91a7313@schaufler-ca.com> (raw)
In-Reply-To: <CAHC9VhQwwqji4m3mXLVzy6cY8G5ObbH3pv+AgsunQypi84cX1w@mail.gmail.com>
On 11/1/2023 2:24 PM, Paul Moore wrote:
> On Tue, Oct 24, 2023 at 5:39 PM Paul Moore <paul@paul-moore.com> wrote:
>> Three rather small LSM patches to address some minor issues found during
>> the review of the latest LSM syscall patchset that now lives in the
>> lsm/next-queue tree.
>>
>> I'm marking these as RFC patches as they have yet to be properly tested,
>> but I'm building a kernel now to do that and I'll report back when testing
>> has completed. In the meantime, reviews and ACKs are appreciated.
> I went ahead and merged these into lsm/dev-staging and rebased the
> branch on Linus' latest to incorporate the syscall additions in his
> tree. As the merge window is open, I did not do the corresponding
> update to the lsm/next branch, that will be updated when the merge
> window is closed and -rc1 is released.
Excellent. Thank you.
next prev parent reply other threads:[~2023-11-01 22:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 21:35 [RFC PATCH 0/3] LSM syscall tweaks Paul Moore
2023-10-24 21:35 ` [RFC PATCH 1/3] lsm: cleanup the size counters in security_getselfattr() Paul Moore
2023-10-24 22:23 ` Casey Schaufler
2023-10-25 1:43 ` Paul Moore
2023-10-25 15:19 ` Casey Schaufler
2023-10-25 22:06 ` Paul Moore
2023-10-26 14:59 ` Mickaël Salaün
2023-10-24 21:35 ` [RFC PATCH 2/3] lsm: correct error codes " Paul Moore
2023-10-24 22:23 ` Casey Schaufler
2023-10-26 15:00 ` Mickaël Salaün
2023-10-24 21:35 ` [RFC PATCH 3/3] lsm: consolidate buffer size handling into lsm_fill_user_ctx() Paul Moore
2023-10-26 15:13 ` Mickaël Salaün
2023-10-26 15:38 ` Paul Moore
2023-12-20 22:31 ` Aishwarya TCV
2023-12-21 1:40 ` Paul Moore
2023-12-21 13:01 ` Mark Brown
2023-12-21 15:21 ` Paul Moore
2023-12-21 18:50 ` Mark Brown
2023-11-01 21:24 ` [RFC PATCH 0/3] LSM syscall tweaks Paul Moore
2023-11-01 22:26 ` Casey Schaufler [this message]
2023-11-13 4:07 ` Paul Moore
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=2c71a8a6-cadc-474f-bb70-857ac91a7313@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=john.johansen@canonical.com \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.