From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org, dsterba@suse.cz
Subject: Re: [PATCH RESEND 1/2] btrfs-progs: check for no result before using results
Date: Fri, 25 Jan 2019 19:21:13 +0800 [thread overview]
Message-ID: <f06e2e0b-7038-f35d-afbc-7f20d34d4aac@oracle.com> (raw)
In-Reply-To: <1547608406-6430-1-git-send-email-anand.jain@oracle.com>
On 1/16/19 11:13 AM, Anand Jain wrote:
> User space understands the ioctl BTRFS_IOC_DEV_REPLACE command status
> using the struct btrfs_ioctl_dev_replace_args::result, and so userspace
> initializes this to BTRFS_IOCTL_DEV_REPLACE_RESULT_NO_RESULT, so exclude
> this value in checking for the error.
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
Ping.
> ---
> cmds-replace.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/cmds-replace.c b/cmds-replace.c
> index b30e6c781e64..42de4de8c031 100644
> --- a/cmds-replace.c
> +++ b/cmds-replace.c
> @@ -296,6 +296,8 @@ static int cmd_replace_start(int argc, char **argv)
> }
>
> if (start_args.result !=
> + BTRFS_IOCTL_DEV_REPLACE_RESULT_NO_RESULT &&
> + start_args.result !=
> BTRFS_IOCTL_DEV_REPLACE_RESULT_NO_ERROR) {
> error("ioctl(DEV_REPLACE_START) on '%s' returns error: %s",
> path,
>
next prev parent reply other threads:[~2019-01-25 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 3:13 [PATCH RESEND 1/2] btrfs-progs: check for no result before using results Anand Jain
2019-01-16 3:13 ` [PATCH RESEND 2/2] btrfs-progs: replace: gracefully handle the exclusive operation report Anand Jain
2019-01-25 11:21 ` Anand Jain [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-22 17:43 [PATCH RESEND 1/2] btrfs-progs: check for no result before using results Anand Jain
2019-01-31 10:05 Anand Jain
2019-02-07 21:38 ` Anand Jain
2019-03-01 16:41 ` David Sterba
2019-03-02 10:19 ` Anand Jain
2019-01-08 4:09 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=f06e2e0b-7038-f35d-afbc-7f20d34d4aac@oracle.com \
--to=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;
as well as URLs for NNTP newsgroup(s).