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

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <39f3f4ae-4875-4cd5-ac2e-9a704750eff6@shopee.com>
Date: Sat, 15 Jun 2024 20:19:22 +0800
From: Haifeng Xu <haifeng.xu@...pee.com>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC] fuse: do not generate interrupt requests for fatal signals



On 2024/6/14 18:01, Miklos Szeredi wrote:
> On Thu, 13 Jun 2024 at 12:44, Haifeng Xu <haifeng.xu@...pee.com> 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?

ok, I use strace to track one of the server threads. The output
can be seen in attachment. 

FD: 6 DIR  /run/lxcfs/controllers/sys/fs/cgroup/
FD: 7 CHR  /dev/fuse


> 
> Thanks,
> Miklos
View attachment "95344.txt" of type "text/plain" (312893 bytes)