From: Chris Murphy <lists@colorremedies.com>
To: Colin Walters <walters@verbum.org>
Cc: "Chris Murphy" <lists@colorremedies.com>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Richard Weinberger" <richard.weinberger@gmail.com>,
"Linux FS Devel" <linux-fsdevel@vger.kernel.org>
Subject: Re: Is rename(2) atomic on FAT?
Date: Wed, 23 Oct 2019 16:24:09 +0200 [thread overview]
Message-ID: <CAJCQCtSPkcrNfP89SNJzkaVuAL3FehUQLL9ZhU0ouhNdcOu+Yw@mail.gmail.com> (raw)
In-Reply-To: <521a5d27-dae9-44a3-bb90-43793bbde7d5@www.fastmail.com>
On Wed, Oct 23, 2019 at 2:53 PM Colin Walters <walters@verbum.org> wrote:
>
>
>
> On Tue, Oct 22, 2019, at 8:10 PM, Chris Murphy wrote:
> >
> > For multiple kernels, it doesn't matter if a crash happens anywhere
> > from new kernel being written to FAT, through initramfs, because the
> > old bootloader configuration still points to old kernel + initramfs.
> > But in multiple kernel distros, the bootloader configuration needs
> > modification or a new drop in scriptlet to point to the new
> > kernel+initramfs pair. And that needs to be completely atomic: write
> > new files to a tmp location, that way a crash won't matter. The tricky
> > part is to write out the bootloader configuration change such that it
> > can be an atomic operation.
>
> Related: https://github.com/ostreedev/ostree/issues/1951
> There I'm proposing there to not try to fix this at the kernel/filesystem
> level (since we can't do much on FAT, and even on real filesystems we
> have the journaling-vs-bootloader issues), but instead create a protocol
> between things writing bootloader data and the bootloaders to help
> verify integrity.
The symlink method now being used, you describe as an OSTree-specific
invention. How is the new method you're proposing more generic such
that it's not also an OSTree-specific invention?
--
Chris Murphy
next prev parent reply other threads:[~2019-10-23 14:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 19:57 Is rename(2) atomic on FAT? Chris Murphy
2019-10-21 21:44 ` Richard Weinberger
2019-10-22 10:54 ` Pali Rohár
2019-10-23 0:10 ` Chris Murphy
2019-10-23 11:50 ` Pali Rohár
2019-10-23 14:21 ` Chris Murphy
2019-10-23 17:16 ` Pali Rohár
2019-10-23 19:18 ` Chris Murphy
2019-10-23 21:21 ` Richard Weinberger
2019-10-23 21:56 ` Chris Murphy
2019-10-23 22:22 ` Richard Weinberger
2019-10-24 21:46 ` Chris Murphy
2019-10-24 21:57 ` Pali Rohár
2019-10-24 22:19 ` Chris Murphy
2019-10-24 22:16 ` Richard Weinberger
2019-10-24 22:26 ` Chris Murphy
2019-10-24 22:33 ` Richard Weinberger
2019-10-25 9:22 ` Chris Murphy
2019-10-25 9:50 ` Richard Weinberger
2019-10-23 12:53 ` Colin Walters
2019-10-23 14:24 ` Chris Murphy [this message]
2019-10-23 17:26 ` Colin Walters
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=CAJCQCtSPkcrNfP89SNJzkaVuAL3FehUQLL9ZhU0ouhNdcOu+Yw@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=richard.weinberger@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.