From: Johannes Thumshirn <jthumshirn@suse.de>
To: Andrea Righi <andrea.righi@canonical.com>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: raid56: properly unmap parity page in finish_parity_scrub()
Date: Wed, 13 Mar 2019 11:59:48 +0100 [thread overview]
Message-ID: <34adab7d-6c71-c4d5-ac5b-9aa2187481ef@suse.de> (raw)
In-Reply-To: <20190313101703.GA9155@xps-13>
On 13/03/2019 11:17, Andrea Righi wrote:
> Parity page is incorrectly unmapped in finish_parity_scrub(), triggering
> a reference counter bug on i386, i.e.:
>
> [ 157.662401] kernel BUG at mm/highmem.c:349!
> [ 157.666725] invalid opcode: 0000 [#1] SMP PTI
>
> Steps to reproduce the bug:
> - create a raid5 btrfs filesystem:
> # mkfs.btrfs -m raid5 -d raid5 /dev/sdb /dev/sdc /dev/sdd /dev/sde
>
> - mount it:
> # mount /dev/sdb /mnt
>
> - run btrfs scrub in a loop:
> # while :; do btrfs scrub start -BR /mnt; done
>
> BugLink: https://bugs.launchpad.net/bugs/1812845
> Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
> ---
> fs/btrfs/raid56.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/raid56.c b/fs/btrfs/raid56.c
> index 1869ba8e5981..67a6f7d47402 100644
> --- a/fs/btrfs/raid56.c
> +++ b/fs/btrfs/raid56.c
> @@ -2430,8 +2430,9 @@ static noinline void finish_parity_scrub(struct btrfs_raid_bio *rbio,
> bitmap_clear(rbio->dbitmap, pagenr, 1);
> kunmap(p);
>
> - for (stripe = 0; stripe < rbio->real_stripes; stripe++)
> + for (stripe = 0; stripe < nr_data; stripe++)
> kunmap(page_in_rbio(rbio, stripe, pagenr, 0));
> + kunmap(p_page);
> }
>
> __free_page(p_page);
>
Code wise this looks ok, but the changelog could really describe what
you're changing and why it is correct.
I.e. the kunmap(p_page) was completely left out, so we never did an
unmap for the p_page and the loop unmapping the rbio page was iterating
over the wrong number of stripes, the map is done with nr_data vs
rbio->real_stripes for the unmap.
With the above (roughly) placed in the changelog:
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2019-03-13 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 10:17 Andrea Righi
2019-03-13 10:59 ` Johannes Thumshirn [this message]
2019-03-14 7:56 ` [PATCH v2] " Andrea Righi
2019-03-18 18:47 ` 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=34adab7d-6c71-c4d5-ac5b-9aa2187481ef@suse.de \
--to=jthumshirn@suse.de \
--cc=andrea.righi@canonical.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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®