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]
Date:   Wed, 4 Oct 2017 15:25:07 +0000
From:   Bart Van Assche <Bart.VanAssche@....com>
To:     "boris.ostrovsky@...cle.com" <boris.ostrovsky@...cle.com>,
        "ONeukum@...e.com" <ONeukum@...e.com>,
        "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "nborisov@...e.com" <nborisov@...e.com>,
        "oleg.b.antonyan@...il.com" <oleg.b.antonyan@...il.com>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
        "linux-xfs@...r.kernel.org" <linux-xfs@...r.kernel.org>,
        "pavel@....cz" <pavel@....cz>,
        "darrick.wong@...cle.com" <darrick.wong@...cle.com>,
        "viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
        "ming.lei@...hat.com" <ming.lei@...hat.com>,
        "rjw@...ysocki.net" <rjw@...ysocki.net>,
        "jgross@...e.com" <jgross@...e.com>,
        "oleksandr@...alenko.name" <oleksandr@...alenko.name>,
        "todd.e.brandt@...ux.intel.com" <todd.e.brandt@...ux.intel.com>,
        "martin.petersen@...cle.com" <martin.petersen@...cle.com>,
        "mcgrof@...nel.org" <mcgrof@...nel.org>,
        "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
        "jikos@...nel.org" <jikos@...nel.org>,
        "len.brown@...el.com" <len.brown@...el.com>,
        "tytso@....edu" <tytso@....edu>,
        "david@...morbit.com" <david@...morbit.com>,
        "jack@...e.cz" <jack@...e.cz>
Subject: Re: [RFC 4/5] ext4: add fs freezing support on suspend/hibernation

On Wed, 2017-10-04 at 18:05 +1100, Dave Chinner wrote:
> Basically, before thawing filesystems the rest of the kernel
> infrastructure needs to have been restarted. i.e. the order
> needs to be:
> 
> freeze userspace
> freeze filesystems
> freeze kernel threads
> freeze workqueues
> 
> thaw workqueues
> thaw kernel threads
> thaw filesystems
> thaw userspace
> 
> and it should end up that way.

Does this order support filesystems that have been implemented in user space,
e.g. filesystems based on FUSE?

Thanks,

Bart.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ