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:   Fri, 19 May 2017 11:27:34 -0400
From:   Theodore Ts'o <tytso@....edu>
To:     Colin Walters <walters@...bum.org>
Cc:     "Darrick J. Wong" <darrick.wong@...cle.com>,
        xfs <linux-xfs@...r.kernel.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] vfs: freeze filesystems just prior to reboot

On Fri, May 19, 2017 at 10:00:31AM -0400, Colin Walters wrote:
> As a maintainer of one of those userspace tools (https://github.com/ostreedev/ostree),
> which I don't think is the one in question here, but likely has the same
> issue - I'd like to have some sort of API to fix this - maybe flush the journal *without*
> remounting r/o?
> 
> Unlike the case you're talking about with rebooting into a special
> update mode, libostree constructs a new root with hardlinks while
> the system is running.  Hence, system downtime is just reboot, like
> dual-partition update systems, except we're more flexible.
> 
> Although hm...I guess an API to flush the journal would only narrow
> the race.
> 
> Is the single partition case really just doomed?

One of the things that came up when Darrick and I discussed this on
the weekly ext4 developer's conference call was our mutual wonderment
that none of the userspace tools implemented a reboot by created a
tmpfs chroot, pivoting into the chroot, and then unmounting all of the
remaining file systems.

This would also allow update schemes who want to enable various new
file system features, or upgrade the root file system somehow, to be
able to do so while the root file system is completely and cleanly
unmounted.

The other thing that would be useful is if grub2 would actually be
able to replay the file system journal --- but given that grub2 is
GPLv3, and both ext4 and xfs are GPLv2-only, and given that past
attempts of teams attempting to do clean room reimplementations of
complex code bases for licensing reasons only (cough, make_ext4fs,
*cough*) have not necessarily turned out well, I'm at least not going
to hold my breath.

   	   			- Ted

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ