Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "vishal.l.verma@intel.com" <vishal.l.verma@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v4] ndctl: add clear error support for ndctl
Date: Tue, 2 May 2017 18:57:16 +0000	[thread overview]
Message-ID: <1493751433.30303.40.camel@hpe.com> (raw)
In-Reply-To: <20170502184309.GA11414@omniknight.lm.intel.com>

On Tue, 2017-05-02 at 12:43 -0600, Vishal Verma wrote:
> On 05/02, Kani, Toshimitsu wrote:
> > On Tue, 2017-05-02 at 09:18 -0700, Dave Jiang wrote:
> > > > +-l::
> > > > > +--len::
> > > > > +The number of badblocks to clear in size of 512 bytes
> > > > > increments. The
> > > > > +length must fit within the badblocks range. If the length
> > > > > exceeds the
> > > > > +badblock range or is 0, the command will fail.
> > > > 
> > > > Actually, I am seeing '-l 0' works just like '-l 1'.
> > > 
> > > Oh now I remembered that Vishal requested that no length does 1
> > > block clear. Do you want me to correct documentation or behavior?
> > 
> > What is the reason behind of his request?
> 
> Ah, so my intention/reasoning was if someone does a simple:
>   ndctl clear-error -s 'X'
> without providing a -l argument, it should dimply clear that one
> block. However I wouldn't think -l0 should clear one block, we should
> either error out, or treat it as a dry-run (perhaps this could be an
> indirect way to check if a certain block is in the badblocks list?)
> 
> Anyway, I'm not too attached to the "should work without providing a
> -l" thing, and we can make -l mandatory again if that makes most
> sense.

Thanks for the clarification.  That makes sense.  I do not have a
strong opinion and am fine with either way Vishal proposed here.  I
just did not feel right to clear with -l 0.

-Toshi


_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

      parent reply	other threads:[~2017-05-02 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01 23:33 [PATCH v4] ndctl: add clear error support for ndctl Dave Jiang
2017-05-02  0:16 ` Kani, Toshimitsu
2017-05-02 16:18   ` Dave Jiang
2017-05-02 16:48     ` Kani, Toshimitsu
2017-05-02 18:43       ` Vishal Verma
2017-05-02 18:51         ` Dan Williams
2017-05-02 18:57         ` Kani, Toshimitsu [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=1493751433.30303.40.camel@hpe.com \
    --to=toshi.kani@hpe.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=vishal.l.verma@intel.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