From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Conrad Meyer <cemeyer@uw.edu>
Cc: linux-kernel@vger.kernel.org, Mark <markk@clara.co.uk>,
Conrad Meyer <cse.cem@gmail.com>
Subject: Re: [PATCH] fs: FAT: Add support for DOS 1.x formatted volumes
Date: Sun, 30 Mar 2014 02:56:46 +0900 [thread overview]
Message-ID: <87mwg8ga75.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1396045290-9795-1-git-send-email-cse.cem@gmail.com> (Conrad Meyer's message of "Fri, 28 Mar 2014 15:21:30 -0700")
Conrad Meyer <cemeyer@uw.edu> writes:
Hi,
> When possible, infer DOS 2.x BIOS Parameter Block from block device
> geometry (for floppies and floppy images). Update in-memory only. We
> only perform this update when the entire BPB region is zeroed, like
> produced by DOS 1.x-era FORMAT (and other OEM variations on DOS).
>
> Fixes kernel.org bug #42617.
>
> BPB default values are inferred from media size and a table.[0] Media
> size is assumed to be static for archaic FAT volumes. See also [1].
>
> [0]: https://en.wikipedia.org/wiki/File_Allocation_Table#Exceptions
> [1]: http://www.win.tue.nl/~aeb/linux/fs/fat/fat-1.html
[...]
> +static void fat_update_archaic_boot_sector(struct super_block *sb,
> + struct fat_boot_sector *b)
> +{
> + sector_t bd_sects;
> +
> + if (get_unaligned_le16(&b->sector_size) != 0 || b->sec_per_clus != 0 ||
> + b->reserved != 0 || b->fats != 0 ||
> + get_unaligned_le16(&b->dir_entries) != 0 ||
> + get_unaligned_le16(&b->sectors) != 0 || b->media != 0 ||
> + b->fat_length != 0 || b->secs_track != 0 || b->heads != 0 ||
> + b->secs_track != 0 || b->heads != 0)
> + return;
> +
> + bd_sects = part_nr_sects_read(sb->s_bdev->bd_part);
> + switch (bd_sects) {
> + case 160 * KB_IN_SECTORS:
> + b->sec_per_clus = 1;
> + put_unaligned_le16(64, &b->dir_entries);
> + b->media = 0xFE;
> + b->fat_length = cpu_to_le16(1);
> + break;
[...]
Hm, this looks like check the volume size. But if there is newer fat
format on same volume size, how to detect it? Or, it is conflicting?
[BTW, we should avoid to mount if it doesn't seem fatfs, to prevent
mis-mount as fatfs (auto mount is depending on this detection).]
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2014-03-29 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 22:21 Conrad Meyer
2014-03-29 17:56 ` OGAWA Hirofumi [this message]
2014-03-29 18:49 ` Conrad Meyer
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=87mwg8ga75.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=cemeyer@uw.edu \
--cc=cse.cem@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markk@clara.co.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
Powered by JetHome