From: Christoph Hellwig <hch@infradead.org>
To: Colin Walters <walters@verbum.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] vfs: freeze filesystems just prior to reboot
Date: Sat, 5 Aug 2017 07:16:21 -0700 [thread overview]
Message-ID: <20170805141621.GA10457@infradead.org> (raw)
In-Reply-To: <1501791890.2285873.1062452112.61520C55@webmail.messagingengine.com>
> 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.
next prev parent reply other threads:[~2017-08-05 14:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 0:20 [PATCH] vfs: freeze filesystems just prior to reboot Darrick J. Wong
2017-05-19 8:29 ` Amir Goldstein
2017-05-19 18:58 ` Darrick J. Wong
2017-05-19 14:00 ` Colin Walters
2017-05-19 15:27 ` Theodore Ts'o
2017-05-19 16:34 ` Colin Walters
2017-05-19 16:48 ` Colin Walters
2017-05-19 18:20 ` Theodore Ts'o
2017-05-19 19:41 ` Darrick J. Wong
2017-05-23 11:10 ` Jan Kara
2017-05-19 19:01 ` Darrick J. Wong
2017-08-03 20:24 ` Colin Walters
2017-08-05 14:16 ` Christoph Hellwig [this message]
2017-08-05 15:45 ` Darrick J. Wong
2017-08-11 10:02 ` Christoph Hellwig
2017-08-11 16:26 ` Darrick J. Wong
2017-08-11 16:27 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170805141621.GA10457@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=walters@verbum.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).