From: Anand Jain <Anand.Jain@oracle.com>
To: Liu Bo <bo.li.liu@oracle.com>, linux-btrfs@vger.kernel.org
Cc: Chris Murphy <lists@colorremedies.com>
Subject: Re: [PATCH] Btrfs: fix NULL pointer crash of deleting a seed device
Date: Fri, 16 May 2014 23:16:26 +0800 [thread overview]
Message-ID: <53762BCA.8010302@oracle.com> (raw)
In-Reply-To: <1399821299-15131-1-git-send-email-bo.li.liu@oracle.com>
Tested-by: Anand Jain <anand.jain@oracle.com>
On 11/05/14 23:14, Liu Bo wrote:
> Same as normal devices, seed devices should be initialized with
> fs_info->dev_root as well, otherwise we'll get a NULL pointer crash.
>
> Cc: Chris Murphy <lists@colorremedies.com>
> Reported-by: Chris Murphy <lists@colorremedies.com>
> Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> ---
> fs/btrfs/volumes.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 49d7fab..bddf2bd 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -6058,10 +6058,14 @@ void btrfs_init_devices_late(struct btrfs_fs_info *fs_info)
> struct btrfs_fs_devices *fs_devices = fs_info->fs_devices;
> struct btrfs_device *device;
>
> - mutex_lock(&fs_devices->device_list_mutex);
> - list_for_each_entry(device, &fs_devices->devices, dev_list)
> - device->dev_root = fs_info->dev_root;
> - mutex_unlock(&fs_devices->device_list_mutex);
> + while (fs_devices) {
> + mutex_lock(&fs_devices->device_list_mutex);
> + list_for_each_entry(device, &fs_devices->devices, dev_list)
> + device->dev_root = fs_info->dev_root;
> + mutex_unlock(&fs_devices->device_list_mutex);
> +
> + fs_devices = fs_devices->seed;
> + }
> }
>
> static void __btrfs_reset_dev_stats(struct btrfs_device *dev)
>
prev parent reply other threads:[~2014-05-16 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 15:14 [PATCH] Btrfs: fix NULL pointer crash of deleting a seed device Liu Bo
2014-05-16 15:16 ` Anand Jain [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=53762BCA.8010302@oracle.com \
--to=anand.jain@oracle.com \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.