linux-kernel - Re: [RFC PATCH 2/5] ubifs: Initialize or update ACLs for inode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri, 22 Mar 2024 20:07:02 +0800
From: Zhihao Cheng <chengzhihao1@...wei.com>
To: Li Zetao <lizetao1@...wei.com>, <richard@....at>,
	<kent.overstreet@...ux.dev>, <agruenba@...hat.com>
CC: <linux-kernel@...r.kernel.org>, <linux-mtd@...ts.infradead.org>
Subject: Re: [RFC PATCH 2/5] ubifs: Initialize or update ACLs for inode

在 2024/3/22 19:57, Li Zetao 写道:
> Hi,
> 
> On 2024/3/21 11:47, Zhihao Cheng wrote:
>> 在 2024/3/20 0:16, Li Zetao 写道:
>>> There are two scenarios where ACL needs to be updated, the first one
>>> is when creating the inode, and the second one is in the chmod process.
>>> When creating directories/files/device node/tmpfile, ACLs needs to be
>>> initialized, but symlink do not.Why not support symlink? It looks 
>>> like many filesystems(eg. ext4, f2fs, 
>> btrfs) support it, except xfs.
> Thanks for the reviews, but this is inconsistent with my understanding.
> I think most file systems in Linux do not support it, because most file 
> systems do not register the get/set functions of ACLs for symlink 
> operations. And the posix_acl_create() will determine that it is a 
> symlink type inode, and then skip the creation process. But except for 
> bcachefs, it may be to solve the problem of certain scenarios, so it 
> would be nice if anyone could explain it to us.

You are right, only bcachefs support acl for symlink.