From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-security-module@vger.kernel.org, jmorris@namei.org,
serge@hallyn.com, keescook@chromium.org,
john.johansen@canonical.com, penguin-kernel@i-love.sakura.ne.jp,
stephen.smalley.work@gmail.com, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, mic@digikod.net,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH v14 4/11] LSM: syscalls for current process attributes
Date: Thu, 7 Sep 2023 15:15:52 -0700 [thread overview]
Message-ID: <159ad121-e7e7-7d5a-c208-983c7a2b8d6e@schaufler-ca.com> (raw)
In-Reply-To: <CAHC9VhT-GVq1D-AKMv_R3uKNm_iDV8uA3pB1ky5ScBnEdoPuvg@mail.gmail.com>
On 9/7/2023 8:42 AM, Paul Moore wrote:
> ...
>> Yes. I have a fix ready. There are a couple other touch-ups, too.
> Great. Since you are doing another revision, can you double check all
> of the patch subject lines to ensure you don't have any double spaces?
> I see at least one, possibly two more.
Where do you see that? I'm not finding it.
next prev parent reply other threads:[~2023-09-07 22:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230828195802.135055-1-casey.ref@schaufler-ca.com>
2023-08-28 19:57 ` [PATCH v14 00/11] LSM: Three basic syscalls Casey Schaufler
2023-08-28 19:57 ` [PATCH v14 01/11] LSM: Identify modules by more than name Casey Schaufler
2023-08-28 19:57 ` [PATCH v14 02/11] LSM: Maintain a table of LSM attribute data Casey Schaufler
2023-08-28 19:57 ` [PATCH v14 03/11] proc: Use lsmids instead of lsm names for attrs Casey Schaufler
2023-08-28 19:57 ` [PATCH v14 04/11] LSM: syscalls for current process attributes Casey Schaufler
2023-09-06 23:22 ` [PATCH v14 4/11] " Paul Moore
2023-09-06 23:48 ` Casey Schaufler
2023-09-07 15:37 ` Mickaël Salaün
2023-09-07 15:43 ` Paul Moore
2023-09-07 15:42 ` Paul Moore
2023-09-07 22:15 ` Casey Schaufler [this message]
2023-09-07 23:05 ` Paul Moore
2023-09-07 15:37 ` [PATCH v14 04/11] " Mickaël Salaün
2023-09-11 22:08 ` Casey Schaufler
2023-08-28 19:57 ` [PATCH v14 05/11] LSM: Create lsm_list_modules system call Casey Schaufler
2023-08-28 19:57 ` [PATCH v14 06/11] LSM: wireup Linux Security Module syscalls Casey Schaufler
2023-08-28 19:57 ` [PATCH v14 07/11] LSM: Helpers for attribute names and filling lsm_ctx Casey Schaufler
2023-08-28 19:57 ` [PATCH v14 08/11] Smack: implement setselfattr and getselfattr hooks Casey Schaufler
2023-08-28 19:57 ` [PATCH v14 09/11] AppArmor: Add selfattr hooks Casey Schaufler
2023-08-28 19:58 ` [PATCH v14 10/11] SELinux: " Casey Schaufler
2023-08-28 19:58 ` [PATCH v14 11/11] LSM: selftests for Linux Security Module syscalls Casey Schaufler
2023-09-06 23:22 ` 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=159ad121-e7e7-7d5a-c208-983c7a2b8d6e@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=serge@hallyn.com \
--cc=stephen.smalley.work@gmail.com \
/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