From: Christoph Hellwig <hch@lst.de>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Christian Brauner" <brauner@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Xiu Jianfeng" <xiujianfeng@huawei.com>,
gregkh@linuxfoundation.org, rafael@kernel.org,
viro@zeniv.linux.org.uk, dhowells@redhat.com, code@tyhicks.com,
hirofumi@mail.parknet.co.jp, linkinjeon@kernel.org,
sfrench@samba.org, senozhatsky@chromium.org, tom@talpey.com,
chuck.lever@oracle.com, jlayton@kernel.org, miklos@szeredi.hu,
paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com,
stephen.smalley.work@gmail.com, eparis@parisplace.org,
dchinner@redhat.com, john.johansen@canonical.com,
mcgrof@kernel.org, mortonm@chromium.org, fred@cloudflare.com,
mpe@ellerman.id.au, nathanl@linux.ibm.com, gnoack3000@gmail.com,
roberto.sassu@huawei.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-cachefs@redhat.com,
ecryptfs@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-nfs@vger.kernel.org, linux-unionfs@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
wangweiyang2@huawei.com
Subject: Re: [PATCH -next 0/2] lsm: Change inode_setattr() to take struct
Date: Wed, 31 May 2023 15:22:00 +0200 [thread overview]
Message-ID: <20230531132200.GB30016@lst.de> (raw)
In-Reply-To: <301a58de-e03f-02fd-57c5-1267876eb2df@schaufler-ca.com>
On Tue, May 30, 2023 at 07:55:17AM -0700, Casey Schaufler wrote:
> Which LSM(s) do you think ought to be deprecated?
I have no idea. But what I want is less weirdo things messing with
VFS semantics.
>
> I only see one that I
> might consider a candidate. As for weird behavior, that's what LSMs are
> for, and the really weird ones proposed (e.g. pathname character set limitations)
> (and excepting for BPF, of course) haven't gotten far.
They haven't gotten far for a reason usually. Trying to sneak things in
through the back door is exactly what is the problem with LSMs.
>
---end quoted text---
next prev parent reply other threads:[~2023-05-31 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 8:11 [PATCH -next 0/2] lsm: Change inode_setattr() to take struct Xiu Jianfeng
2023-05-05 8:11 ` [PATCH -next 1/2] fs: Change notify_change() to take struct path argument Xiu Jianfeng
2023-05-05 17:22 ` [PATCH -next 1/2] " Chuck Lever III
2023-05-05 8:12 ` [PATCH -next 2/2] lsm: Change inode_setattr hook " Xiu Jianfeng
2023-05-10 0:58 ` [PATCH -next 0/2] lsm: Change inode_setattr() to take struct xiujianfeng
2023-05-15 15:12 ` Christian Brauner
2023-05-26 16:33 ` Mickaël Salaün
2023-05-30 13:58 ` Christian Brauner
2023-05-30 14:28 ` Christoph Hellwig
2023-05-30 14:55 ` Casey Schaufler
2023-05-30 16:01 ` Christian Brauner
2023-05-30 22:15 ` Casey Schaufler
2023-05-31 8:36 ` Christian Brauner
2023-05-31 16:44 ` Casey Schaufler
2023-05-31 13:22 ` Christoph Hellwig [this message]
2023-05-31 14:17 ` Casey Schaufler
2023-05-31 15:22 ` 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=20230531132200.GB30016@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=chuck.lever@oracle.com \
--cc=code@tyhicks.com \
--cc=dchinner@redhat.com \
--cc=dhowells@redhat.com \
--cc=ecryptfs@vger.kernel.org \
--cc=eparis@parisplace.org \
--cc=fred@cloudflare.com \
--cc=gnoack3000@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jlayton@kernel.org \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mic@digikod.net \
--cc=miklos@szeredi.hu \
--cc=mortonm@chromium.org \
--cc=mpe@ellerman.id.au \
--cc=nathanl@linux.ibm.com \
--cc=paul@paul-moore.com \
--cc=rafael@kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=selinux@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=serge@hallyn.com \
--cc=sfrench@samba.org \
--cc=stephen.smalley.work@gmail.com \
--cc=tom@talpey.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wangweiyang2@huawei.com \
--cc=xiujianfeng@huawei.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).