Re: [PATCH] fuse: Return EPERM rather than ENOSYS from link()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Matt Johnston <matt@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH] fuse: Return EPERM rather than ENOSYS from link()
From: Miklos Szeredi <miklos@xxxxxxxxxx>
Date: Fri, 14 Feb 2025 11:06:24 +0100
Cc: linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <20250214-fuse-link-eperm-v1-1-8c241d987008@codeconstruct.com.au>

On Fri, 14 Feb 2025 at 02:18, Matt Johnston <matt@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> link() is documented to return EPERM when a filesystem doesn't support
> the operation, return that instead.

Applied, thanks.

Also added the following optimization patch if link is not supported.

Thanks,
Miklos

References:
- [PATCH] fuse: Return EPERM rather than ENOSYS from link()
  - From: Matt Johnston

Prev by Date: [PATCH] fuse: optmize missing FUSE_LINK support
Next by Date: Re: [PATCH] fuse: don't set file->private_data in fuse_conn_waiting_read
Previous by thread: [PATCH] fuse: Return EPERM rather than ENOSYS from link()
Next by thread: [RFC] odd check in ceph_encode_encrypted_dname()
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux