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: <E1I6kA9-0003Zt-00@dorka.pomaz.szeredi.hu>
Date:	Fri, 06 Jul 2007 11:31:41 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	nigel@...pend2.net
CC:	miklos@...redi.hu, benh@...nel.crashing.org, nigel@...pend2.net,
	rjw@...k.pl, pavel@....cz, linux-pm@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, mjg59@...f.ucam.org,
	oliver@...kum.org, paulus@...ba.org, mingo@...e.hu
Subject: Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer

> > > On Fri, 2007-07-06 at 09:13 +0200, Miklos Szeredi wrote:
> > > > 
> > > > 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.
> > > 
> > > It could if they told the kernel via some black magic ...
> > > 
> > > But that still suck. The freezer sucks :-)
> > 
> > Yeah, and it wouldn't work in practice, since the auxilary tasks might
> > be part of a library which is not even aware of being used by a "fuse
> > task".
> 
> This is why I think the whole concept of filesystems in userspace is broken. 
> Trying to shift things that need special privilege and special handling to 
> userspace is just asking for trouble.

I'm not claiming fuse doesn't introduce problems.  I've been tackling
those problems for a number of years now.  Suspend/hibernate is just
the next thing that needs looking at.

Just blaming either suspend or fuse for these problems is unproductive
and stupid.  The problems _are_ solvable if not always simply.

> You can say it's the kernel code's fault, but then you have to
> explain why it's only fuse (yeah ok, and XFS) that have problems.

I'm not faulting anythig.  My opinion, is that the freezer is not
needed for suspend, and removing it will not just solve the problems
with fuse but several others.  It probably needs a lot of work, but
hey, that's why we are here.

The patch posted by Rafael, which lets the freezer skip uninterrupible
tasks is a step in the right direction.

Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ