From: "Günther Noack" <gnoack@google.com>
To: linux-security-module@vger.kernel.org,
"Mickaël Salaün" <mic@digikod.net>
Cc: Jeff Xu <jeffxu@google.com>,
Jorge Lucangeli Obes <jorgelo@chromium.org>,
Allen Webb <allenwebb@google.com>,
Dmitry Torokhov <dtor@google.com>,
Paul Moore <paul@paul-moore.com>,
Konstantin Meskhidze <konstantin.meskhidze@huawei.com>,
Matt Bobrowski <repnop@google.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] landlock: Add ioctl access right
Date: Mon, 14 Aug 2023 19:43:08 +0200 [thread overview]
Message-ID: <ZNpnrCjYqFoGkwyf@google.com> (raw)
In-Reply-To: <20230814172816.3907299-2-gnoack@google.com>
Hi!
On Mon, Aug 14, 2023 at 07:28:12PM +0200, Günther Noack wrote:
> @@ -1207,7 +1209,8 @@ static int hook_file_open(struct file *const file)
> {
> layer_mask_t layer_masks[LANDLOCK_NUM_ACCESS_FS] = {};
> access_mask_t open_access_request, full_access_request, allowed_access;
> - const access_mask_t optional_access = LANDLOCK_ACCESS_FS_TRUNCATE;
> + const access_mask_t optional_access = LANDLOCK_ACCESS_FS_TRUNCATE |
> + LANDLOCK_ACCESS_FS_IOCTL;
> const struct landlock_ruleset *const dom =
> landlock_get_current_domain();
>
> @@ -1280,6 +1283,36 @@ static int hook_file_truncate(struct file *const file)
> return -EACCES;
> }
About the error code:
The ioctl(2) man page documents ENOTTY as "The specified request does not apply
to this kind of object". It does not document EACCES. EACCES would be slightly
more appropriate semantically, but existing programs might be more well-equipped
to handle ENOTTY.
Do you think we should return ENOTTY here?
—Günther
--
Sent using Mutt 🐕 Woof Woof
next prev parent reply other threads:[~2023-08-14 17:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 17:28 [PATCH v3 0/5] Landlock: IOCTL support Günther Noack
2023-08-14 17:28 ` [PATCH v3 1/5] landlock: Add ioctl access right Günther Noack
2023-08-14 17:43 ` Günther Noack [this message]
2023-08-14 17:28 ` [PATCH v3 2/5] selftests/landlock: Test ioctl support Günther Noack
2023-08-18 17:06 ` Mickaël Salaün
2023-08-25 15:51 ` Günther Noack
2023-08-25 17:07 ` Mickaël Salaün
2023-09-01 13:35 ` Günther Noack
2023-09-01 20:24 ` Mickaël Salaün
2023-08-14 17:28 ` [PATCH v3 3/5] selftests/landlock: Test ioctl with memfds Günther Noack
2023-08-14 17:28 ` [PATCH v3 4/5] samples/landlock: Add support for LANDLOCK_ACCESS_FS_IOCTL Günther Noack
2023-08-14 17:28 ` [PATCH v3 5/5] landlock: Document ioctl support Günther Noack
2023-08-18 16:28 ` Mickaël Salaün
2023-08-25 11:55 ` Günther Noack
2023-08-18 13:26 ` [PATCH v3 0/5] Landlock: IOCTL support Mickaël Salaün
2023-08-18 13:39 ` Mickaël Salaün
2023-08-25 15:03 ` Günther Noack
2023-08-25 16:50 ` Mickaël Salaün
2023-08-26 18:26 ` Mickaël Salaün
2023-09-02 11:53 ` Günther Noack
2023-09-04 18:08 ` Mickaël Salaün
2023-09-11 10:02 ` Günther Noack
2023-09-11 15:25 ` Mickaël Salaün
2023-09-11 16:34 ` Mickaël Salaün
2023-10-19 22:09 ` Günther Noack
2023-10-20 14:57 ` Mickaël Salaün
2023-10-25 22:07 ` Günther Noack
2023-10-26 14:55 ` Mickaël Salaün
2023-11-03 13:06 ` Günther Noack
2023-11-03 15:12 ` Mickaël Salaün
2023-08-22 14:39 ` [PATCH v3 0/5] Landlock: IOCTL support - TTY restrictions RFC Mickaël Salaün
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=ZNpnrCjYqFoGkwyf@google.com \
--to=gnoack@google.com \
--cc=allenwebb@google.com \
--cc=dtor@google.com \
--cc=jeffxu@google.com \
--cc=jorgelo@chromium.org \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=repnop@google.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;
as well as URLs for NNTP newsgroup(s).