Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush

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

To: Tycho Andersen <tycho@tycho.pizza>
Subject: Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush
From: Miklos Szeredi <miklos@xxxxxxxxxx>
Date: Mon, 14 Aug 2023 16:35:56 +0200
Cc: Jürg Billeter <j@xxxxxxxxx>, "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, regressions@xxxxxxxxxxxxxxx
In-reply-to: <ZNozdrtKgTeTaMpX@tycho.pizza>

On Mon, 14 Aug 2023 at 16:00, Tycho Andersen <tycho@tycho.pizza> wrote:

> It seems like we really do need to wait here. I guess that means we
> need some kind of exit-proof wait?

Could you please recap the original problem?

Thanks,
Miklos

Follow-Ups:
- Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush
  - From: Tycho Andersen

References:
- [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush
  - From: Jürg Billeter
- Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush
  - From: Miklos Szeredi
- Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush
  - From: Tycho Andersen

Prev by Date: [PATCH RFC 4/4] fs: allow mknod in non-initial userns using cgroup device guard
Next by Date: [PATCH RFC 2/4] bpf: provide cgroup_device_guard in bpf_prog_info to user space
Previous by thread: Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush
Next by thread: Re: [REGRESSION] fuse: execve() fails with ETXTBSY due to async fuse_flush
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