Re: [RFC] fuse: do not generate interrupt requests for fatal signals

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

To: Haifeng Xu <haifeng.xu@xxxxxxxxxx>
Subject: Re: [RFC] fuse: do not generate interrupt requests for fatal signals
From: Miklos Szeredi <miklos@xxxxxxxxxx>
Date: Fri, 14 Jun 2024 12:01:39 +0200
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <a8d0c5da-6935-4d28-9380-68b84b8e6e72@shopee.com>

On Thu, 13 Jun 2024 at 12:44, Haifeng Xu <haifeng.xu@xxxxxxxxxx> wrote:

> So why the client doesn't get woken up?

Need to find out what the server (lxcfs) is doing.  Can you do a
strace of lxcfs to see the communication on the fuse device?

Thanks,
Miklos

Follow-Ups:
- Re: [RFC] fuse: do not generate interrupt requests for fatal signals
  - From: Christian Brauner
- Re: [RFC] fuse: do not generate interrupt requests for fatal signals
  - From: Haifeng Xu

References:
- [RFC] fuse: do not generate interrupt requests for fatal signals
  - From: Haifeng Xu
- Re: [RFC] fuse: do not generate interrupt requests for fatal signals
  - From: Miklos Szeredi
- Re: [RFC] fuse: do not generate interrupt requests for fatal signals
  - From: Haifeng Xu

Prev by Date: Re: [RFC 2/2] rust: sync: Add atomic support
Next by Date: Re: Issue with JFFS2 and a_ops->dirty_folio
Previous by thread: Re: [RFC] fuse: do not generate interrupt requests for fatal signals
Next by thread: Re: [RFC] fuse: do not generate interrupt requests for fatal signals
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