From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org,
Marcos Paulo de Souza <marcos@mpdesouza.com>
Subject: Re: [PATCH] btrfs: discard: reduce the block group ref when grabbing from unused block group list
Date: Tue, 7 Jul 2020 16:06:43 +0200 [thread overview]
Message-ID: <20200707140643.GI27795@twin.jikos.cz> (raw)
In-Reply-To: <20200703070550.39299-1-wqu@suse.com>
On Fri, Jul 03, 2020 at 03:05:50PM +0800, Qu Wenruo wrote:
> [BUG]
> The following small test script can trigger ASSERT() at unmount time:
>
> mkfs.btrfs -f $dev
> mount $dev $mnt
> mount -o remount,discard=async $mnt
> umount $mnt
>
> The call trace:
> assertion failed: atomic_read(&block_group->count) == 1, in fs/btrfs/block-group.c:3431
> ------------[ cut here ]------------
> kernel BUG at fs/btrfs/ctree.h:3204!
> invalid opcode: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 4 PID: 10389 Comm: umount Tainted: G O 5.8.0-rc3-custom+ #68
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
> Call Trace:
> btrfs_free_block_groups.cold+0x22/0x55 [btrfs]
> close_ctree+0x2cb/0x323 [btrfs]
> btrfs_put_super+0x15/0x17 [btrfs]
> generic_shutdown_super+0x72/0x110
> kill_anon_super+0x18/0x30
> btrfs_kill_super+0x17/0x30 [btrfs]
> deactivate_locked_super+0x3b/0xa0
> deactivate_super+0x40/0x50
> cleanup_mnt+0x135/0x190
> __cleanup_mnt+0x12/0x20
> task_work_run+0x64/0xb0
> __prepare_exit_to_usermode+0x1bc/0x1c0
> __syscall_return_slowpath+0x47/0x230
> do_syscall_64+0x64/0xb0
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
>
> The code:
> ASSERT(atomic_read(&block_group->count) == 1);
> btrfs_put_block_group(block_group);
>
> [CAUSE]
> Obviously it's some btrfs_get_block_group() call doesn't get its put
> call.
>
> The offending btrfs_get_block_group() happens here:
>
> void btrfs_mark_bg_unused(struct btrfs_block_group *bg)
> {
> if (list_empty(&bg->bg_list)) {
> btrfs_get_block_group(bg);
> list_add_tail(&bg->bg_list, &fs_info->unused_bgs);
> }
> }
>
> So every call sites removing the block group from unused_bgs list should
> reduce the ref count of that block group.
>
> However for async discard, it didn't follow the call convention:
>
> void btrfs_discard_punt_unused_bgs_list(struct btrfs_fs_info *fs_info)
> {
> list_for_each_entry_safe(block_group, next, &fs_info->unused_bgs,
> bg_list) {
> list_del_init(&block_group->bg_list);
> btrfs_discard_queue_work(&fs_info->discard_ctl, block_group);
> }
> }
>
> And in btrfs_discard_queue_work(), it doesn't call
> btrfs_put_block_group() either.
>
> [FIX]
> Fix the problem by reducing the reference count when we grab the block
> group from unused_bgs list.
>
> Reported-by: Marcos Paulo de Souza <marcos@mpdesouza.com>
> Fixes: 6e80d4f8c422 ("btrfs: handle empty block_group removal for async discard")
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Added it misc-next, thanks.
prev parent reply other threads:[~2020-07-07 14:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 7:05 [PATCH] btrfs: discard: reduce the block group ref when grabbing from unused block group list Qu Wenruo
2020-07-03 13:01 ` Qu Wenruo
2020-07-03 13:31 ` David Sterba
2020-07-04 21:45 ` Marcos Paulo de Souza
2020-07-06 5:18 ` Anand Jain
2020-07-07 14:06 ` David Sterba [this message]
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=20200707140643.GI27795@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcos@mpdesouza.com \
--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