From: "Dmitry V. Levin" <ldv@strace.io>
To: Casey Schaufler <casey@schaufler-ca.com>,
Paul Moore <paul@paul-moore.com>
Cc: "LSM List" <linux-security-module@vger.kernel.org>,
"Linux kernel mailing list" <linux-kernel@vger.kernel.org>,
linux-api@vger.kernel.org, "Mickaël Salaün" <mic@digikod.net>,
"James Morris" <jmorris@namei.org>,
"Serge Hallyn" <serge@hallyn.com>,
"John Johansen" <john.johansen@canonical.com>,
"Tetsuo Handa" <penguin-kernel@i-love.sakura.ne.jp>,
"Stephen Smalley" <stephen.smalley.work@gmail.com>
Subject: Re: [PATCH v3] LSM: use 32 bit compatible data types in LSM syscalls.
Date: Wed, 13 Mar 2024 21:42:21 +0200 [thread overview]
Message-ID: <20240313194221.GA18631@altlinux.org> (raw)
In-Reply-To: <da4d181d-16b9-4e0f-a744-ac61702e0b63@schaufler-ca.com>
On Wed, Mar 13, 2024 at 12:32:37PM -0700, Casey Schaufler wrote:
> LSM: use 32 bit compatible data types in LSM syscalls.
>
> Change the size parameters in lsm_list_modules(), lsm_set_self_attr()
> and lsm_get_self_attr() from size_t to u32. This avoids the need to
> have different interfaces for 32 and 64 bit systems.
>
> Cc: stable@vger.kernel.org
> Fixes: a04a1198088a: ("LSM: syscalls for current process attributes")
> Fixes: ad4aff9ec25f: ("LSM: Create lsm_list_modules system call")
> Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
Reported-and-reviewed-by: Dmitry V. Levin <ldv@strace.io>
--
ldv
next prev parent reply other threads:[~2024-03-13 19:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00734a64-a5fe-420c-bf6e-bee27c9d83be.ref@schaufler-ca.com>
2024-03-12 22:13 ` [PATCH] LSM: use 32 bit compatible data types in LSM syscalls Casey Schaufler
2024-03-13 15:56 ` [PATCH v2] " Casey Schaufler
2024-03-13 18:46 ` Paul Moore
2024-03-13 18:57 ` Casey Schaufler
2024-03-13 19:32 ` [PATCH v3] " Casey Schaufler
2024-03-13 19:42 ` Dmitry V. Levin [this message]
2024-03-13 20:07 ` Paul Moore
2024-03-13 22:37 ` Paul Moore
2024-03-13 22:48 ` Casey Schaufler
2024-03-14 1:44 ` Paul Moore
2024-03-14 2:25 ` Paul Moore
2024-03-14 15:30 ` Paul Moore
2024-03-14 15:45 ` Casey Schaufler
2024-03-14 18:01 ` Dmitry V. Levin
2024-03-14 18:18 ` 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=20240313194221.GA18631@altlinux.org \
--to=ldv@strace.io \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--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 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.