From: Eric Biggers <ebiggers@kernel.org>
To: Alfred Piccioni <alpic@google.com>
Cc: Paul Moore <paul@paul-moore.com>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Eric Paris <eparis@parisplace.org>,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org,
selinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] security: new security_file_ioctl_compat() hook
Date: Wed, 20 Dec 2023 12:48:59 -0600 [thread overview]
Message-ID: <20231220184859.GB119068@quark.localdomain> (raw)
In-Reply-To: <20231219090909.2827497-1-alpic@google.com>
On Tue, Dec 19, 2023 at 10:09:09AM +0100, Alfred Piccioni wrote:
>
> base-commit: 196e95aa8305aecafc4e1857b7d3eff200d953b6
> --
Where can I get this base commit?
- Eric
next prev parent reply other threads:[~2023-12-20 18:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 10:25 [PATCH] SELinux: Check correct permissions for FS_IOC32_* Alfred Piccioni
2023-09-06 10:28 ` kernel test robot
2023-09-06 11:59 ` [PATCH V2] " Alfred Piccioni
2023-09-06 17:49 ` Stephen Smalley
2023-09-08 22:54 ` kernel test robot
2023-09-11 13:19 ` Stephen Smalley
2023-09-11 13:49 ` Stephen Smalley
2023-09-12 9:00 ` Alfred Piccioni
2023-09-12 12:00 ` Stephen Smalley
2023-09-12 15:46 ` Mickaël Salaün
2023-09-13 3:52 ` Paul Moore
2023-12-18 12:41 ` [PATCH] SELinux: Introduce security_file_ioctl_compat hook Alfred Piccioni
2023-12-18 13:46 ` Stephen Smalley
2023-12-18 13:50 ` Stephen Smalley
2023-12-19 9:09 ` [PATCH] security: new security_file_ioctl_compat() hook Alfred Piccioni
2023-12-19 9:10 ` Alfred Piccioni
2023-12-20 14:38 ` Alfred Piccioni
2023-12-20 15:34 ` Stephen Smalley
2023-12-23 14:41 ` Tetsuo Handa
2023-12-20 17:31 ` Stephen Smalley
2023-12-20 18:48 ` Eric Biggers [this message]
2023-12-23 1:23 ` Paul Moore
2023-12-23 10:48 ` Tetsuo Handa
2023-12-24 19:58 ` Paul Moore
2023-12-23 15:34 ` Eric Biggers
2023-12-24 20:00 ` Paul Moore
2023-12-24 20:09 ` Paul Moore
2023-12-23 17:54 ` Casey Schaufler
2023-12-24 20:53 ` Paul Moore
2023-12-27 4:43 ` Eric Biggers
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=20231220184859.GB119068@quark.localdomain \
--to=ebiggers@kernel.org \
--cc=alpic@google.com \
--cc=eparis@parisplace.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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