From: Sanidhya Solanki <lkml.page@gmail.com> (by way of Sanidhya Solanki <lkml.page@gmail.com>)
To: Ashish Samant <ashish.samant@oracle.com>
Cc: linux-btrfs-owner@vger.kernel.org
Subject: Re: [PATCH] btrfs: Fix BUG_ON condition in scrub_setup_recheck_block()
Date: Sat, 30 Apr 2016 12:33:57 -0400 [thread overview]
Message-ID: <20160430123357.060e5db1@jpage> (raw)
In-Reply-To: <1461980039-25200-1-git-send-email-ashish.samant@oracle.com>
On Fri, 29 Apr 2016 18:33:59 -0700
Ashish Samant <ashish.samant@oracle.com> wrote:
> pagev array in scrub_block{} is of size SCRUB_MAX_PAGES_PER_BLOCK.
> page_index should be checked with the same to trigger BUG_ON().
>
> Signed-off-by: Ashish Samant <ashish.samant@oracle.com>
> ---
> fs/btrfs/scrub.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/scrub.c b/fs/btrfs/scrub.c
> index 4678f03..376a6dd 100644
> --- a/fs/btrfs/scrub.c
> +++ b/fs/btrfs/scrub.c
> @@ -1350,7 +1350,7 @@ static int scrub_setup_recheck_block(struct scrub_block *original_sblock,
> recover->bbio = bbio;
> recover->map_length = mapped_length;
>
> - BUG_ON(page_index >= SCRUB_PAGES_PER_RD_BIO);
> + BUG_ON(page_index >= SCRUB_MAX_PAGES_PER_BLOCK);
>
> nmirrors = min(scrub_nr_raid_mirrors(bbio), BTRFS_MAX_MIRRORS);
>
Hello
I am trying to implement a user-space IOCTL option to change the RAID Stripe Size.
I have run into an issue in the code included here, specifically in line 64 of scrub.c.
#define SCRUB_MAX_PAGES_PER_BLOCK 16 /* 64k per node/leaf/sector */
This line should become a user-space variable if SCRUB_MAX_PAGES_PER_BLOCK is
related in any way to the definition of BTrFS Stripe Length (defined in
volume.h) being equal to a product of Super_blk and RAID Stripe Length, as it was
before mid-December before the patch
"http://article.gmane.org/gmane.comp.file-systems.btrfs/51221/" modified it. If
SCRUB_MAX_PAGES_PER_BLOCK is related to Super_blk, then it too will need to be
changed from a macro to something that is runtime configurable.
Could those more familiar with the code base let me know.
Thanks
next prev parent reply other threads:[~2016-05-04 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 1:33 [PATCH] btrfs: Fix BUG_ON condition in scrub_setup_recheck_block() Ashish Samant
2016-04-30 16:33 ` Sanidhya Solanki [this message]
2016-05-02 9:39 ` David Sterba
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=20160430123357.060e5db1@jpage \
--to=lkml.page@gmail.com \
--cc=ashish.samant@oracle.com \
--cc=linux-btrfs-owner@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;
as well as URLs for NNTP newsgroup(s).