linux-ext4 - Re: [PATCH] vfs: freeze filesystems just prior to reboot

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170805141621.GA10457@infradead.org>
Date:   Sat, 5 Aug 2017 07:16:21 -0700
From:   Christoph Hellwig <hch@...radead.org>
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

> Any objections to something like an ioctl (fd, FIFREEZETHAW, 0) ?

It's going to be completely trivial, which argues for it.  The only
points left woul be bikeshedding over the name, and how to describe
its semantics.

> in the end probably the real fix is probably something like storing
> multiple copies of the bootloader config with checksums that grub
> can verify.  Basically teach grub to try really hard to extract known-good
> data from the FS.  For file-level consistency that'd be pretty easy,
> we could have e.g. 

The real answer is to have a filesystem that does the above for you
for the boot partition, e.g. one where the kernel and grub have
a common consistency protocol for.