linux-kernel - Re: [PATCH v2] fuse: allow FUSE drivers to declare themselves free from outside changes

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] [day] [month] [year] [list]

Date: Tue, 02 Apr 2024 10:57:49 -0400
From: Jeff Layton <jlayton@...nel.org>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Amir Goldstein <amir73il@...il.com>, Bernd Schubert
	 <bernd.schubert@...tmail.fm>, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] fuse: allow FUSE drivers to declare themselves free
 from outside changes

On Tue, 2024-04-02 at 16:54 +0200, Miklos Szeredi wrote:
> On Tue, 2 Apr 2024 at 16:51, Jeff Layton <jlayton@...nel.org> wrote:
> > 
> > I'm fine with whatever verbiage you prefer. Let me know if you need me
> > to resend.
> 
> I'll do this, no need to resend.
> 
> > Another thing to consider: what about fsnotify? Should notifications be
> > allowed when this flag isn't set?
> 
> Aren't local notification done for all network filesystems?
> 

I think you may be correct. I suppose we lost that battle years ago.
-- 
Jeff Layton <jlayton@...nel.org>