mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "jstancek@redhat.com" <jstancek@redhat.com>
Cc: "naresh.kamboju@linaro.org" <naresh.kamboju@linaro.org>,
	"the_hoang0709@yahoo.com" <the_hoang0709@yahoo.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"ltp@lists.linux.it" <ltp@lists.linux.it>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"chrubis@suse.cz" <chrubis@suse.cz>,
	"alexey.kodanev@oracle.com" <alexey.kodanev@oracle.com>
Subject: Re: Linux-next-20190823: x86_64/i386: prot_hsymlinks.c:325: Failed to run cmd: useradd hsym
Date: Tue, 27 Aug 2019 12:58:16 +0000	[thread overview]
Message-ID: <294428f05e4dba1a6b10b8744cfa5da0637f84a4.camel@hammerspace.com> (raw)
In-Reply-To: <866876796.8349197.1566901536625.JavaMail.zimbra@redhat.com>

On Tue, 2019-08-27 at 06:25 -0400, Jan Stancek wrote:
> That theory is probably not correct for this case, since EIO I see
> appears
> to originate from write and nfs_writeback_result(). This function
> also
> produces message we saw in logs from Naresh.
> 
> I can't find where/how is resp->count updated on WRITE reply in
> NFSv2.
> Issue also goes away with patch below, though I can't speak about its
> correctness:
> 
> NFS version     Type    Test    Return code
> nfsvers=2       tcp     -b:base         0
> nfsvers=2       tcp     -g:general      0
> nfsvers=2       tcp     -s:special      0
> nfsvers=2       tcp     -l:lock         0
> Total time: 141
> 
> diff --git a/fs/nfs/nfs2xdr.c b/fs/nfs/nfs2xdr.c
> index cbc17a203248..4913c6da270b 100644
> --- a/fs/nfs/nfs2xdr.c
> +++ b/fs/nfs/nfs2xdr.c
> @@ -897,6 +897,16 @@ static int nfs2_xdr_dec_writeres(struct rpc_rqst
> *req, struct xdr_stream *xdr,
>                                  void *data)
>  {
>         struct nfs_pgio_res *result = data;
> +       struct rpc_task *rq_task  = req->rq_task;
> +
> +       if (rq_task) {
> +               struct nfs_pgio_args *args = rq_task-
> >tk_msg.rpc_argp;
> +
> +               if (args) {
> +                       result->count = args->count;
> +               }
> +       }
>  
>         /* All NFSv2 writes are "file sync" writes */
>         result->verf->committed = NFS_FILE_SYNC;

Thanks! I've moved the above to nfs_write_done() so that we do it only
on success (see 
http://git.linux-nfs.org/?p=trondmy/linux-nfs.git;a=commitdiff;h=3ba5688da709dd0f7d917029c206bc1848a6ae74
)
-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2019-08-27 12:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26  9:47 Naresh Kamboju
2019-08-26 10:41 ` Cyril Hrubis
2019-08-26 11:05   ` Jan Stancek
2019-08-26 13:50     ` Naresh Kamboju
2019-08-26 14:38       ` Jan Stancek
2019-08-26 15:58         ` Trond Myklebust
2019-08-26 23:12           ` Jan Stancek
2019-08-27  0:59             ` Trond Myklebust
2019-08-27 10:25               ` Jan Stancek
2019-08-27 12:58                 ` Trond Myklebust [this message]
2019-08-27 13:20                   ` Jan Stancek
2019-08-27  6:34             ` Naresh Kamboju

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=294428f05e4dba1a6b10b8744cfa5da0637f84a4.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=alexey.kodanev@oracle.com \
    --cc=chrubis@suse.cz \
    --cc=jstancek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=naresh.kamboju@linaro.org \
    --cc=the_hoang0709@yahoo.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

all inboxes | Powered by JetHome®