From: Mimi Zohar <zohar@linux.ibm.com>
To: David Howells <dhowells@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <christian@brauner.io>
Cc: Marc Dionne <marc.dionne@auristor.com>,
Jeffrey Altman <jaltman@auristor.com>,
Steve French <sfrench@samba.org>,
linux-afs@lists.infradead.org, openafs-devel@openafs.org,
linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Etienne Champetier <champetier.etienne@gmail.com>,
Chet Ramey <chet.ramey@case.edu>,
Cheyenne Wills <cwills@sinenomine.net>,
Christian Brauner <brauner@kernel.org>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v3 1/2] vfs: Allow filesystems with foreign owner IDs to override UID checks
Date: Thu, 30 Jul 2026 19:35:24 -0400 [thread overview]
Message-ID: <4bdf58bd593d9a54aa20760fd49aaa1df57ef216.camel@linux.ibm.com> (raw)
In-Reply-To: <20260728141344.1811120-2-dhowells@redhat.com>
Hi David,
On Tue, 2026-07-28 at 15:13 +0100, David Howells wrote:
>
> (*) IMA policy ops.
>
> Unchanged for now. I'm not sure what the best way to deal with this
> is - if, indeed, it needs any changes.
IMA policy rules may be written in terms of the uid, euid and fowner. Any
changes, if necessary, would need to be made to ima_match_rules().
Mimi
next prev parent reply other threads:[~2026-07-30 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 14:13 [PATCH v3 0/2] vfs, afs, bash: Fix miscomparison of foreign user IDs in the VFS David Howells
2026-07-28 14:13 ` [PATCH v3 1/2] vfs: Allow filesystems with foreign owner IDs to override UID checks David Howells
2026-07-30 23:35 ` Mimi Zohar [this message]
2026-07-28 14:13 ` [PATCH v3 2/2] afs, bash: Fix open(O_CREAT) on an extant AFS file in a sticky dir David Howells
2026-07-30 10:46 ` Marc Dionne
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=4bdf58bd593d9a54aa20760fd49aaa1df57ef216.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=brauner@kernel.org \
--cc=champetier.etienne@gmail.com \
--cc=chet.ramey@case.edu \
--cc=christian@brauner.io \
--cc=cwills@sinenomine.net \
--cc=dhowells@redhat.com \
--cc=jaltman@auristor.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=openafs-devel@openafs.org \
--cc=sfrench@samba.org \
--cc=viro@zeniv.linux.org.uk \
/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