From: Andrew Morton <akpm@linux-foundation.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org, Eric Sesterhenn <snakebyte@gmx.de>,
Roman Zippel <zippel@linux-m68k.org>,
550010@bugs.debian.org
Subject: Re: [PATCH] hfsplus: Refuse to mount volumes larger than 2TB
Date: Sun, 11 Oct 2009 00:51:53 -0700 [thread overview]
Message-ID: <20091011005153.cc723dca.akpm@linux-foundation.org> (raw)
In-Reply-To: <1255227087.25061.76.camel@localhost>
On Sun, 11 Oct 2009 03:11:27 +0100 Ben Hutchings <ben@decadent.org.uk> wrote:
> As found in <http://bugs.debian.org/550010>, hfsplus is using type u32
> rather than sector_t for some sector number calculations.
>
> In particular, hfsplus_get_block() does:
>
> u32 ablock, dblock, mask;
> ...
> map_bh(bh_result, sb, (dblock << HFSPLUS_SB(sb).fs_shift) + HFSPLUS_SB(sb).blockoffset + (iblock & mask));
>
> I am not confident that I can find and fix all cases where a sector
> number may be truncated. For now, avoid data loss by refusing to mount
> HFS+ volumes with more than 2^32 sectors (2TB).
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> Cc: stable@kernel.org
> ---
> --- a/fs/hfsplus/wrapper.c
> +++ b/fs/hfsplus/wrapper.c
> @@ -99,6 +99,10 @@
>
> if (hfsplus_get_last_session(sb, &part_start, &part_size))
> return -EINVAL;
> + if (part_start + part_size > 0x100000000) {
> + pr_err("hfs: volumes larger than 2TB are not supported yet\n");
> + return -EINVAL;
> + }
part_start and part_size are sector_t. This code will do weird overflow
things when sector_t is 32-bit. Also 32-bit compilers will get upset at the
excessively large hex constant.
This should fix both issues:
--- a/fs/hfsplus/wrapper.c~hfsplus-refuse-to-mount-volumes-larger-than-2tb-fix
+++ a/fs/hfsplus/wrapper.c
@@ -99,7 +99,7 @@ int hfsplus_read_wrapper(struct super_bl
if (hfsplus_get_last_session(sb, &part_start, &part_size))
return -EINVAL;
- if (part_start + part_size > 0x100000000) {
+ if ((u64)part_start + part_size > 0x100000000ULL) {
pr_err("hfs: volumes larger than 2TB are not supported yet\n");
return -EINVAL;
}
_
next prev parent reply other threads:[~2009-10-11 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 2:51 hfsplus corrupts filesystems >2TB Ben Hutchings
2009-10-11 2:11 ` [PATCH] hfsplus: Refuse to mount volumes larger than 2TB Ben Hutchings
2009-10-11 7:51 ` Andrew Morton [this message]
2009-10-11 17:01 ` Ben Hutchings
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=20091011005153.cc723dca.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=550010@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=snakebyte@gmx.de \
--cc=zippel@linux-m68k.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