From: Alin Dobre <alin.dobre@elastichosts.com>
To: Dominique Martinet <dominique.martinet@cea.fr>,
v9fs-developer@lists.sourceforge.net,
Eric Van Hensbergen <ericvh@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Ron Minnich <rminnich@sandia.gov>,
Latchesar Ionkov <lucho@ionkov.net>
Subject: Re: [PATCH] 9P: fix return value in v9fs_fid_xattr_set
Date: Wed, 21 May 2014 14:14:07 +0100 [thread overview]
Message-ID: <537CA69F.7080603@elastichosts.com> (raw)
In-Reply-To: <1400659332-21498-1-git-send-email-dominique.martinet@cea.fr>
On 21/05/14 09:02, Dominique Martinet wrote:
> v9fs_fid_xattr_set is supposed to return 0 on success.
>
> This corrects the behaviour introduced in commit
> bdd5c28dcb8330b9074404cc92a0b83aae5606a
> "9p: fix return value in case in v9fs_fid_xattr_set()"
>
> (The function returns a negative error on error, as expected)
>
> Signed-off-by: Dominique Martinet <dominique.martinet@cea.fr>
> ---
> fs/9p/xattr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/9p/xattr.c b/fs/9p/xattr.c
> index 04133a1..f95e01e 100644
> --- a/fs/9p/xattr.c
> +++ b/fs/9p/xattr.c
> @@ -156,7 +156,7 @@ int v9fs_fid_xattr_set(struct p9_fid *fid, const char *name,
> offset += write_count;
> value_len -= write_count;
> }
> - retval = offset;
> + retval = 0;
> err:
> p9_client_clunk(fid);
> return retval;
>
This patch seems to be fixing the problem, thanks!
next prev parent reply other threads:[~2014-05-21 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 17:03 Containers over 9p in 3.14 Alin Dobre
2014-05-21 6:52 ` [V9fs-developer] " Dominique Martinet
2014-05-21 8:02 ` [PATCH] 9P: fix return value in v9fs_fid_xattr_set Dominique Martinet
2014-05-21 13:14 ` Alin Dobre [this message]
2014-05-21 8:07 ` [V9fs-developer] Containers over 9p in 3.14 Alin Dobre
[not found] ` <537B8AFA.4080303-1hSFou9RDDldEee+Cai+ZQ@public.gmane.org>
2014-05-21 6:52 ` Dominique Martinet
2014-05-21 21:15 ` Eric W. Biederman
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=537CA69F.7080603@elastichosts.com \
--to=alin.dobre@elastichosts.com \
--cc=dominique.martinet@cea.fr \
--cc=ebiederm@xmission.com \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=rminnich@sandia.gov \
--cc=v9fs-developer@lists.sourceforge.net \
/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.