linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maurizio Lombardi <mlombard@redhat.com>
To: "Pali Rohár" <pali.rohar@gmail.com>,
	"Konstantin Komarov" <almaz.alexandrovich@paragon-software.com>
Cc: "viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] fs: exFAT read-only driver GPL implementation by Paragon Software.
Date: Mon, 21 Oct 2019 13:37:13 +0200	[thread overview]
Message-ID: <a4c42aa5-f9b7-4e74-2c11-220d45cb3669@redhat.com> (raw)
In-Reply-To: <20191021111136.adpxjxmmz4p2vud2@pali>



Dne 21.10.2019 v 13:11 Pali Rohár napsal(a):
> Are you going to add support also for TexFAT? Or at least for more two
> FAT tables (like is used in FAT32)?
> 

Just a small note here, differences between FAT and exFAT:

1) Contiguous files get a special treatment by exFAT: they do not use the FAT cluster chain.
2) exFAT doesn't use the FAT to track free space, it uses a bitmap.

So, 2 FAT tables are probably not sufficient for recovery, 2 bitmaps are needed too.[1]
Btw, only Windows CE supported this.

[1] http://www.ntfs.com/exfat-allocation-bitmap.htm

Maurizio


  reply	other threads:[~2019-10-21 11:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <453A1153-9493-4A04-BF66-CE6A572DEBDB@paragon-software.com>
2019-10-19 23:34 ` [PATCH] fs: exFAT read-only driver GPL implementation by Paragon Software Pali Rohár
2019-10-22 17:13   ` [PATCH] " Konstantin Komarov
2019-10-20 18:08 ` [PATCH] fs: " Richard Weinberger
2019-10-21 10:54   ` Pali Rohár
2019-10-21 11:08     ` Maurizio Lombardi
2019-10-21 11:13       ` Pali Rohár
2019-10-21 11:31         ` Richard Weinberger
2019-10-21 11:11 ` Pali Rohár
2019-10-21 11:37   ` Maurizio Lombardi [this message]
2019-10-21 11:45     ` Pali Rohár
2019-10-21 12:01       ` Maurizio Lombardi

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=a4c42aa5-f9b7-4e74-2c11-220d45cb3669@redhat.com \
    --to=mlombard@redhat.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).