Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] revert btrfs-progs: do a separate probe for _transient_ replacing device
Date: Wed, 29 Oct 2014 19:41:43 +0800	[thread overview]
Message-ID: <1414582903.23053.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1414579862-18951-1-git-send-email-anand.jain@oracle.com>

On Wed, 2014-10-29 at 18:51 +0800, Anand Jain wrote:
> There is a compatibility issue with older kernel with the progs commit id as below.
> 
> 05cd2907557ba627cfb86e60b214ea6228613a84

Which tree does this commit id belongs to?
I can't find it anywhere?

> So as of now writing to revert the above commit id.
> The brewing sysfs interface would help to fix the impending issue, which is
> seed device would fail show in 'btrfs fi show' output of a sprout device.
> 
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
>  utils.c | 19 +------------------
>  1 file changed, 1 insertion(+), 18 deletions(-)
> 
> diff --git a/utils.c b/utils.c
> index a8691fe..1d1cc77 100644
> --- a/utils.c
> +++ b/utils.c
> @@ -1869,29 +1869,12 @@ int get_fs_info(char *path, struct btrfs_ioctl_fs_info_args *fi_args,
>  	if (!fi_args->num_devices)
>  		goto out;
>  
> -	/*
> -	 * with kernel patch
> -	 * btrfs: ioctl BTRFS_IOC_FS_INFO and BTRFS_IOC_DEV_INFO miss-matched with slots
> -	 * the kernel now returns total_devices which does not include
> -	 * replacing device if running.
> -	 * As we need to get dev info of the replace device if it is running,
> -	 * so just add one to fi_args->num_devices.
> -	 */
> -
> -	di_args = *di_ret = malloc((fi_args->num_devices + 1) * sizeof(*di_args));
> +	di_args = *di_ret = malloc((fi_args->num_devices) * sizeof(*di_args));
>  	if (!di_args) {
>  		ret = -errno;
>  		goto out;
>  	}
>  
> -	/* get the replace target device if it is there */
> -	ret = get_device_info(fd, i, &di_args[ndevs]);
> -	if (!ret) {
> -		ndevs++;
> -		fi_args->num_devices++;
> -	}
> -	i++;
> -
>  	for (; i <= fi_args->max_id; ++i) {
>  		BUG_ON(ndevs >= fi_args->num_devices);
>  		ret = get_device_info(fd, i, &di_args[ndevs]);



  reply	other threads:[~2014-10-29 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 10:51 [PATCH] revert btrfs-progs: do a separate probe for _transient_ replacing device Anand Jain
2014-10-29 11:41 ` Gui Hecheng [this message]
2014-10-30  4:06   ` Anand Jain
2014-10-30  4:43 ` [PATCH v2] " 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=1414582903.23053.3.camel@localhost.localdomain \
    --to=guihc.fnst@cn.fujitsu.com \
    --cc=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@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