From: Su Yue <suy.fnst@cn.fujitsu.com>
To: Qu Wenruo <wqu@suse.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 2/3] btrfs-progs: check/original: Add checks for compressed extent without csum
Date: Mon, 14 May 2018 15:24:37 +0800 [thread overview]
Message-ID: <fbad04c1-1aa3-b94c-68d0-f550be95f176@cn.fujitsu.com> (raw)
In-Reply-To: <20180514070310.27197-3-wqu@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2911 bytes --]
On 05/14/2018 03:03 PM, Qu Wenruo wrote:
> There is one report of compressed extent happens in btrfs, but has no
> csum and then leads to possible decompress error screwing up kernel
> memory.
>
> Although it's a kernel bug, and won't cause problem until compressed
> data get corrupted, let's catch such problem in advance.
>
> This patch will catch any unexpected compressed extent with:
>
> 1) 0 or less than expected csum
>
> 2) nodatasum flag set in the inode item
>
> This is for original mode.
>
> Reported-by: James Harvey <jamespharvey20@gmail.com>
> Issue: #134
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Su Yue <suy.fnst@cn.fujitsu.com>
> ---
> check/main.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/check/main.c b/check/main.c
> index 891a6d797756..db064b27e84b 100644
> --- a/check/main.c
> +++ b/check/main.c
> @@ -1437,6 +1437,7 @@ static int process_file_extent(struct btrfs_root *root,
> u64 mask = root->fs_info->sectorsize - 1;
> u32 max_inline_size = min_t(u32, mask,
> BTRFS_MAX_INLINE_DATA_SIZE(root->fs_info));
> + u8 compression;
> int extent_type;
> int ret;
>
> @@ -1460,9 +1461,9 @@ static int process_file_extent(struct btrfs_root *root,
>
> fi = btrfs_item_ptr(eb, slot, struct btrfs_file_extent_item);
> extent_type = btrfs_file_extent_type(eb, fi);
> + compression = btrfs_file_extent_compression(eb, fi);
>
> if (extent_type == BTRFS_FILE_EXTENT_INLINE) {
> - u8 compression = btrfs_file_extent_compression(eb, fi);
> struct btrfs_item *item = btrfs_item_nr(slot);
>
> num_bytes = btrfs_file_extent_inline_len(eb, slot, fi);
> @@ -1494,6 +1495,8 @@ static int process_file_extent(struct btrfs_root *root,
> btrfs_file_extent_encryption(eb, fi) ||
> btrfs_file_extent_other_encoding(eb, fi)))
> rec->errors |= I_ERR_BAD_FILE_EXTENT;
> + if (compression && rec->nodatasum)
> + rec->errors |= I_ERR_BAD_FILE_EXTENT;
> if (disk_bytenr > 0)
> rec->found_size += num_bytes;
> } else {
> @@ -1512,7 +1515,8 @@ static int process_file_extent(struct btrfs_root *root,
> if (disk_bytenr > 0 &&
> btrfs_header_owner(eb) != BTRFS_DATA_RELOC_TREE_OBJECTID) {
> u64 found;
> - if (btrfs_file_extent_compression(eb, fi))
> +
> + if (compression)
> num_bytes = btrfs_file_extent_disk_num_bytes(eb, fi);
> else
> disk_bytenr += extent_offset;
> @@ -1526,6 +1530,8 @@ static int process_file_extent(struct btrfs_root *root,
> rec->found_csum_item = 1;
> if (found < num_bytes)
> rec->some_csum_missing = 1;
> + if (compression && found < num_bytes)
> + rec->errors |= I_ERR_SOME_CSUM_MISSING;
> } else if (extent_type == BTRFS_FILE_EXTENT_PREALLOC) {
> if (found > 0) {
> ret = check_prealloc_extent_written(root->fs_info,
>
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1791 bytes --]
next prev parent reply other threads:[~2018-05-14 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 7:03 [PATCH 0/3] btrfs-progs: Detect compressed extent without csum Qu Wenruo
2018-05-14 7:03 ` [PATCH 1/3] btrfs-progs: check/lowmem: Add checks for " Qu Wenruo
2018-05-14 7:24 ` Su Yue
2018-05-14 7:03 ` [PATCH 2/3] btrfs-progs: check/original: " Qu Wenruo
2018-05-14 7:24 ` Su Yue [this message]
2018-05-14 7:03 ` [PATCH 3/3] btrfs-progs: fsck-tests: Add test case for detecting " Qu Wenruo
-- strict thread matches above, loose matches on Subject: below --
2018-05-14 6:54 [PATCH 0/3] btrfs-progs: Detect " Qu Wenruo
2018-05-14 6:54 ` [PATCH 2/3] btrfs-progs: check/original: Add checks for " Qu Wenruo
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=fbad04c1-1aa3-b94c-68d0-f550be95f176@cn.fujitsu.com \
--to=suy.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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 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).