From: Christoph Hellwig Subject: Re: [PATCH] vfs: freeze filesystems just prior to reboot Date: Sat, 5 Aug 2017 07:16:21 -0700 Message-ID: <20170805141621.GA10457@infradead.org> References: <20170519002032.GA21202@birch.djwong.org> <1495202431.1896310.982081664.066926F8@webmail.messagingengine.com> <20170519190115.GJ4519@birch.djwong.org> <1501791890.2285873.1062452112.61520C55@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Darrick J. Wong" , xfs , linux-fsdevel , linux-ext4 To: Colin Walters Return-path: Content-Disposition: inline In-Reply-To: <1501791890.2285873.1062452112.61520C55@webmail.messagingengine.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org > 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.