linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v7] Add cli and ioctl to forget scanned device(s)
Date: Wed, 18 Jul 2018 11:18:55 +0800	[thread overview]
Message-ID: <44ea10b7-736c-792e-51e0-40434024da74@oracle.com> (raw)
In-Reply-To: <20180718030801.31617-1-anand.jain@oracle.com>


  Please ignore this. There is a line of code which is un-commit.
  I am sending this series again. Sorry for the noise.

Thanks, Anand



On 07/18/2018 11:07 AM, Anand Jain wrote:
> v7:
>   Availalbe for pull from
>    btrfs-progs:
>     git@github.com:asj/btrfs-progs.git forget
>    btrfs.ko:
>     git@github.com:asj/btrfs-devel.git misc-next-jul18
> 
>   Use struct btrfs_ioctl_vol_args (instead of struct
>    btrfs_ioctl_vol_args_v2) as its inline with other ioctl
>    btrfs-control
>   The CLI usage remains same. However internally the ioctl flag is not
>    required to delete all the unmounted devices. Instead leave
>    btrfs_ioctl_vol_args::name NULL.
> 
> v6:
>   Use the changed fn name btrfs_free_stale_devices().
> 
>   Change in title:
>   Old v5:
>   Cover-letter:
>    [PATCH v5] Add cli and ioctl to ignore a scanned device
>   Kernel:
>    [PATCH v5] btrfs: introduce feature to ignore a btrfs device
>   Progs:
>    [PATCH v5] btrfs-progs: add 'btrfs device ignore' cli
> 
> v5:
>    Adds feature to delete all stale devices
>    Reuses btrfs_free_stale_devices() fn and so depends on the
>      patch-set [1] in the ML.
>    Uses struct btrfs_ioctl_vol_args_v2 instead of
>      struct btrfs_ioctl_vol_args as arg
>    Does the device path matching instead of btrfs_device matching
>      (we won't delete the mounted device as btrfs_free_stale_devices()
>      checks for it)
> v4:
>    No change. But as the ML thread may be confusing, so resend.
> v3:
>    No change. Send to correct ML.
> v2:
>    Accepts review from Nikolay, details are in the specific patch.
>    Patch 1/2 is renamed from
>      [PATCH 1/2] btrfs: refactor btrfs_free_stale_device() to get device list delete
>    to
>      [PATCH 1/2] btrfs: add function to device list delete
> 
> Adds cli and ioctl to forget a scanned device or forget all stale
> devices in the kernel.
> 
> Anand Jain (1):
>    btrfs: introduce feature to forget a btrfs device
> 
>   fs/btrfs/super.c           | 3 +++
>   fs/btrfs/volumes.c         | 9 +++++++++
>   fs/btrfs/volumes.h         | 1 +
>   include/uapi/linux/btrfs.h | 2 ++
>   4 files changed, 15 insertions(+)
> 
> Anand Jain (1):
>    btrfs-progs: add cli to forget one or all scanned devices
> 
>   cmds-device.c | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>   ioctl.h       |  2 ++
>   2 files changed, 60 insertions(+)
> 

      parent reply	other threads:[~2018-07-18  3:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18  3:07 [PATCH v7] Add cli and ioctl to forget scanned device(s) Anand Jain
2018-07-18  3:08 ` [PATCH v7] btrfs: introduce feature to forget a btrfs device Anand Jain
2018-07-18  3:08 ` [PATCH v7] btrfs-progs: add cli to forget one or all scanned devices Anand Jain
2018-07-18  3:18 ` 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=44ea10b7-736c-792e-51e0-40434024da74@oracle.com \
    --to=anand.jain@oracle.com \
    --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;
as well as URLs for NNTP newsgroup(s).