From: "Pali Rohár" <pali.rohar@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: Is rename(2) atomic on FAT?
Date: Thu, 24 Oct 2019 23:57:40 +0200 [thread overview]
Message-ID: <20191024215740.dtcudmehqvywfnks@pali> (raw)
In-Reply-To: <CAJCQCtQhCRPG-UV+pcraCLXM5cVW887uX1UoymQ8=3Mk56w1Ag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
On Thursday 24 October 2019 23:46:43 Chris Murphy wrote:
> So that leads me to, what about FAT? i.e. how does this get solved on FAT?
Hi Chris! I think that for FAT in most cases it used ostrich algorithm.
Probability that kernel crashes in the middle of operation which is
updating kernel image on boot partition is very low.
I'm Looking at grub's fat source code and there is no handling of dirty
bit... http://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/fs/fat.c
It just expects that whole FAT fs is in consistent state.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-10-24 21:57 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 [this message]
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
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=20191024215740.dtcudmehqvywfnks@pali \
--to=pali.rohar@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=richard.weinberger@gmail.com \
/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.