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  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]
Date:	Fri, 6 Jul 2007 17:19:34 +1000
From:	Nigel Cunningham <>
To:	Miklos Szeredi <>
Subject: Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer


On Friday 06 July 2007 17:13:27 Miklos Szeredi wrote:
> > To get more serious and practical though, I think the solution is to
> > fuzz the userspace/kernelspace distinction. What we really want to
> > do is freeze things that submit I/O, then sync, then freeze anything
> > that processes I/O and needs to be frozen. In effect, redefine fuse
> > processes as freezeable kernel threads.
> Another myth, that has been debunked already.  The problem is: how do
> you define fuse processes?  There's no theoretical or even practial
> way to do that.

No theoretical or practical way?! I'll freely admit to being quite ignorant 
about fuse, but surely there's some way by which they can be distinguished.


See for Howtos, FAQs, mailing
lists, wiki and bugzilla info.

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists