From: Anand Jain <Anand.Jain@oracle.com>
To: miaox@cn.fujitsu.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 4/4] btrfs: update sprout seed pointer when seed fs is relinquished
Date: Tue, 12 Aug 2014 15:56:50 +0800 [thread overview]
Message-ID: <53E9C8C2.5020409@oracle.com> (raw)
In-Reply-To: <53E9C134.5020706@cn.fujitsu.com>
On 12/08/2014 15:24, Miao Xie wrote:
> On Mon, 11 Aug 2014 17:42:56 +0800, Anand Jain wrote:
>> We are not updating sprout fs seed pointer when all seed device
>> is replaced. This patch will check if all seed device has been
>> replaced and then update the sprout pointer accordingly.
>>
>> Same reproducer as in the previous patch would apply here.
>> And notice that btrfs_close_device will check if seed fs is
>> present and spits out the error with out this patch.
>>
>> int btrfs_close_devices(struct btrfs_fs_devices *fs_devices)
>> {
>> ::
>> seed_devices = fs_devices->seed;
>> ::
>> while (seed_devices) {
>> fs_devices = seed_devices;
>> seed_devices = fs_devices->seed;
>> __btrfs_close_devices(fs_devices);
>> free_fs_devices(fs_devices);
>> }
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> fs/btrfs/volumes.c | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>>
>> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
>> index f098ae7..bfdc11f 100644
>> --- a/fs/btrfs/volumes.c
>> +++ b/fs/btrfs/volumes.c
>> @@ -1992,6 +1992,25 @@ void btrfs_rm_dev_replace_srcdev(struct btrfs_fs_info *fs_info,
>> btrfs_scratch_superblock(srcdev);
>> }
>>
>> + /* unless fs_devices is seed fs, num_devices shouldn't go
>> + * zero
>> + */
>
> According to coding style, the preferred style for multi-line comments is(except files in net
> subsystem):
>
> /*
> * <comment>
> */
>
>> + BUG_ON(!fs_devices->num_devices && !fs_devices->seeding);
>
> Use ASSERT?
>
>> + /* if this is no devs we rather delete the fs_devices */
>> + if (!fs_devices->num_devices) {
>> + struct btrfs_fs_devices *tmp_fs_devices;
>> +
>> + tmp_fs_devices = fs_info->fs_devices;
>> + while (tmp_fs_devices) {
>> + if (tmp_fs_devices->seed == fs_devices) {
>> + tmp_fs_devices->seed = fs_devices->seed;
>> + break;
>> + }
>> + tmp_fs_devices = tmp_fs_devices->seed;
>> + }
>> + fs_devices->seed = NULL;
>
> Why not free fs_devices like btrfs_rm_device?
Thanks for the review. ! Yes memory leak is another bug
I have the patch for it will send it soon. the bug trying
to address here is fs_devices stale seed pointer.
Anand
> The other is OK.
>
> Reviewed-by: Miao Xie <miaox@cn.fujitsu.com>
>
>> + }
>> call_rcu(&srcdev->rcu, free_device);
>> }
>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-08-12 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 9:42 [PATCH 1/4] btrfs: preparatory to make btrfs_rm_dev_replace_srcdev() seed aware Anand Jain
2014-08-11 9:42 ` [PATCH 2/4] btrfs: replace seed device followed by unmount causes kernel WARNING Anand Jain
2014-08-12 7:27 ` Miao Xie
2014-08-11 9:42 ` [PATCH 3/4] btrfs: fix rw_devices miss match after seed replace Anand Jain
2014-08-12 7:29 ` Miao Xie
2014-08-12 8:00 ` Anand Jain
2014-08-11 9:42 ` [PATCH 4/4] btrfs: update sprout seed pointer when seed fs is relinquished Anand Jain
2014-08-12 7:24 ` Miao Xie
2014-08-12 7:56 ` Anand Jain [this message]
2014-08-12 7:30 ` [PATCH 1/4] btrfs: preparatory to make btrfs_rm_dev_replace_srcdev() seed aware Miao Xie
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=53E9C8C2.5020409@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).