From: Chao Yu <yuchao0@huawei.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
<linux-f2fs-devel@lists.sourceforge.net>, <jaegeuk@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 1/1] f2fs: fix validation of the block count in sanity_check_raw_super
Date: Sat, 22 Dec 2018 10:24:43 +0800 [thread overview]
Message-ID: <093ddec0-1cbd-d5c4-2bbc-8cfb9eddd447@huawei.com> (raw)
In-Reply-To: <20181221192820.26222-2-martin.blumenstingl@googlemail.com>
On 2018/12/22 3:28, Martin Blumenstingl wrote:
> Treat "block_count" from struct f2fs_super_block as 64-bit little endian
> value in sanity_check_raw_super() because struct f2fs_super_block
> declares "block_count" as "__le64".
>
> This fixes a bug where the superblock validation fails on big endian
> devices with the following error:
> F2FS-fs (sda1): Wrong segment_count / block_count (61439 > 0)
> F2FS-fs (sda1): Can't find valid F2FS filesystem in 1th superblock
> F2FS-fs (sda1): Wrong segment_count / block_count (61439 > 0)
> F2FS-fs (sda1): Can't find valid F2FS filesystem in 2th superblock
> As result of this the partition cannot be mounted.
>
> With this patch applied the superblock validation works fine and the
> partition can be mounted again:
> F2FS-fs (sda1): Mounted with checkpoint version = 7c84
>
> My little endian x86-64 hardware was able to mount the partition without
> this fix.
> To confirm that mounting f2fs filesystems works on big endian machines
> again I tested this on a 32-bit MIPS big endian (lantiq) device.
>
> Fixes: 0cfe75c5b01199 ("f2fs: enhance sanity_check_raw_super() to avoid potential overflows")
> Cc: stable@vger.kernel.org
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
next prev parent reply other threads:[~2018-12-22 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 19:28 [PATCH 0/1] f2fs: fix sanity_check_raw_super on big endian machines Martin Blumenstingl
2018-12-21 19:28 ` [PATCH 1/1] f2fs: fix validation of the block count in sanity_check_raw_super Martin Blumenstingl
2018-12-22 2:24 ` Chao Yu [this message]
2018-12-22 7:00 ` kbuild test robot
2018-12-22 11:08 ` Martin Blumenstingl
2018-12-24 8:18 ` Chao Yu
2018-12-22 9:30 ` kbuild test robot
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=093ddec0-1cbd-d5c4-2bbc-8cfb9eddd447@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®