From: Nikolay Borisov <nborisov@suse.com> To: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com>, clm@fb.com, josef@toxicpanda.com, dsterba@suse.com Cc: anand.jain@oracle.com, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org, skhan@linuxfoundation.org, gregkh@linuxfoundation.org, linux-kernel-mentees@lists.linuxfoundation.org, syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com Subject: Re: [PATCH] btrfs: fix rw device counting in __btrfs_free_extra_devids Date: Thu, 15 Jul 2021 14:55:37 +0300 [thread overview] Message-ID: <7ae7a858-9893-c41c-ed96-10651c295087@suse.com> (raw) In-Reply-To: <20210715103403.176695-1-desmondcheongzx@gmail.com> On 15.07.21 г. 13:34, Desmond Cheong Zhi Xi wrote: > Syzbot reports a warning in close_fs_devices that happens because > fs_devices->rw_devices is not 0 after calling btrfs_close_one_device > on each device. > > This happens when a writeable device is removed in > __btrfs_free_extra_devids, but the rw device count is not decremented > accordingly. So when close_fs_devices is called, the removed device is > still counted and we get an off by 1 error. > > Here is one call trace that was observed: > btrfs_mount_root(): > btrfs_scan_one_device(): > device_list_add(); <---------------- device added > btrfs_open_devices(): > open_fs_devices(): > btrfs_open_one_device(); <-------- rw device count ++ > btrfs_fill_super(): > open_ctree(): > btrfs_free_extra_devids(): > __btrfs_free_extra_devids(); <--- device removed > fail_tree_roots: > btrfs_close_devices(): > close_fs_devices(); <------- rw device count off by 1 > > Fixes: cf89af146b7e ("btrfs: dev-replace: fail mount if we don't have replace item with target device") > Reported-by: syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com > Tested-by: syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com > Signed-off-by: Desmond Cheong Zhi Xi <desmondcheongzx@gmail.com> Is there a reliable reproducer from syzbot? Can this be turned into an xfstest? > --- > fs/btrfs/volumes.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c > index 807502cd6510..916c25371658 100644 > --- a/fs/btrfs/volumes.c > +++ b/fs/btrfs/volumes.c > @@ -1078,6 +1078,7 @@ static void __btrfs_free_extra_devids(struct btrfs_fs_devices *fs_devices, > if (test_bit(BTRFS_DEV_STATE_WRITEABLE, &device->dev_state)) { > list_del_init(&device->dev_alloc_list); > clear_bit(BTRFS_DEV_STATE_WRITEABLE, &device->dev_state); > + fs_devices->rw_devices--; > } > list_del_init(&device->dev_list); > fs_devices->num_devices--; >
next prev parent reply other threads:[~2021-07-15 11:55 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-15 10:34 Desmond Cheong Zhi Xi 2021-07-15 11:23 ` Anand Jain 2021-07-15 11:55 ` Nikolay Borisov [this message] 2021-07-15 13:11 ` Desmond Cheong Zhi Xi 2021-07-21 13:34 ` David Sterba 2021-07-21 17:59 ` David Sterba 2021-07-25 6:19 ` Desmond Cheong Zhi Xi 2021-07-26 17:52 ` David Sterba 2021-07-26 23:07 ` Desmond Cheong Zhi Xi 2021-07-25 13:49 ` Anand Jain
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=7ae7a858-9893-c41c-ed96-10651c295087@suse.com \ --to=nborisov@suse.com \ --cc=anand.jain@oracle.com \ --cc=clm@fb.com \ --cc=desmondcheongzx@gmail.com \ --cc=dsterba@suse.com \ --cc=gregkh@linuxfoundation.org \ --cc=josef@toxicpanda.com \ --cc=linux-btrfs@vger.kernel.org \ --cc=linux-kernel-mentees@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=skhan@linuxfoundation.org \ --cc=syzbot+a70e2ad0879f160b9217@syzkaller.appspotmail.com \ --subject='Re: [PATCH] btrfs: fix rw device counting in __btrfs_free_extra_devids' \ /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
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).