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 for Android: free password hash cracker in your pocket

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

Message-ID: <20240617-vanille-labil-8de959ba5756@brauner>
Date: Mon, 17 Jun 2024 09:25:24 +0200
From: Christian Brauner <brauner@...nel.org>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Haifeng Xu <haifeng.xu@...pee.com>, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [RFC] fuse: do not generate interrupt requests for fatal signals

On Fri, Jun 14, 2024 at 12:01:39PM GMT, 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?

Fwiw, I'm one of the orignal authors and maintainers of LXCFS so if you
have specific questions, I may be able to help.