Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH] btrfs-progs: volumes: check stripe end against device boundary
Date: Mon,  3 Aug 2020 15:06:30 +0800	[thread overview]
Message-ID: <20200803070630.33234-1-wqu@suse.com> (raw)

There is a report of kernel generationg READ bio access beyond device
boundary.

To make sure it's not caused by on-disk chunk items, add extra stripe
check against device total_bytes so that btrfs check can detect such
problem early on.

Signed-off-by: Qu Wenruo <wqu@suse.com>
---
 volumes.c | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/volumes.c b/volumes.c
index 538f799e7211..0467dd63d5cb 100644
--- a/volumes.c
+++ b/volumes.c
@@ -1843,6 +1843,7 @@ int btrfs_check_chunk_valid(struct btrfs_fs_info *fs_info,
 	u64 type;
 	u32 chunk_ondisk_size;
 	u32 sectorsize = fs_info->sectorsize;
+	int i;
 
 	/*
 	 * Basic chunk item size check.  Note that btrfs_chunk already contains
@@ -1953,6 +1954,34 @@ int btrfs_check_chunk_valid(struct btrfs_fs_info *fs_info,
 		return -EIO;
 	}
 
+	/*
+	 * Stripe check against device boundary
+	 */
+	for (i = 0; i < num_stripes; i++) {
+		struct btrfs_device *dev;
+		u64 physical;
+		u64 devid;
+		u64 stripe_len;
+
+		devid = btrfs_stripe_devid_nr(leaf, chunk, i);
+		physical = btrfs_stripe_offset_nr(leaf, chunk, i);
+		stripe_len = calc_stripe_length(type, length, num_stripes);
+		dev = btrfs_find_device(fs_info, devid, NULL, NULL);
+		/*
+		 * Device not found? Then we may be in the bootstrap process for
+		 * system chunks. Skip.
+		 */
+		if (!dev)
+			continue;
+		if (physical + stripe_len > dev->total_bytes) {
+			error(
+"chunk %llu stripe %d is beyond device boundary: devid %llu total_bytes %llu stripe start %llu len %llu",
+				logical, i, devid, dev->total_bytes, physical,
+				stripe_len);
+			return -EUCLEAN;
+		}
+	}
+
 	return 0;
 }
 
-- 
2.28.0


             reply	other threads:[~2020-08-03  7:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03  7:06 Qu Wenruo [this message]
2020-08-03  7:13 ` [PATCH] btrfs-progs: volumes: check stripe end against device boundary 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=20200803070630.33234-1-wqu@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@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