All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] [RFC] nfs4: inject process namespace into COMPOUND tag
Date: Thu, 6 Aug 2026 14:40:07 +0800	[thread overview]
Message-ID: <202608061449.3hOd5Rkm-lkp@intel.com> (raw)
In-Reply-To: <20260626151029.1516839-1-tigran.mkrtchyan@desy.de>

Hi Tigran,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on trondmy-nfs/linux-next]
[also build test ERROR on linus/master v7.2-rc6 next-20260805]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Tigran-Mkrtchyan/nfs4-inject-process-namespace-into-COMPOUND-tag/20260806-105541
base:   git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
patch link:    https://lore.kernel.org/r/20260626151029.1516839-1-tigran.mkrtchyan%40desy.de
patch subject: [PATCH] [RFC] nfs4: inject process namespace into COMPOUND tag
config: alpha-allmodconfig (https://download.01.org/0day-ci/archive/20260806/202608061449.3hOd5Rkm-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260806/202608061449.3hOd5Rkm-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608061449.3hOd5Rkm-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

   fs/nfs/nfs4xdr.c: In function 'encode_compound_hdr':
>> fs/nfs/nfs4xdr.c:1039:21: error: 'taks' undeclared (first use in this function); did you mean 'task'?
    1039 |                 if (taks->tk_ns_inum != 0) {
         |                     ^~~~
         |                     task
   fs/nfs/nfs4xdr.c:1039:21: note: each undeclared identifier is reported only once for each function it appears in
>> fs/nfs/nfs4xdr.c:1037:34: warning: unused variable 'task' [-Wunused-variable]
    1037 |                 struct rpc_task *task = req->rq_task;
         |                                  ^~~~


vim +1039 fs/nfs/nfs4xdr.c

  1027	
  1028	static void encode_compound_hdr(struct xdr_stream *xdr,
  1029					struct rpc_rqst *req,
  1030					struct compound_hdr *hdr)
  1031	{
  1032		__be32 *p;
  1033	
  1034		/* Inject namespace info into compound tag if not already set */
  1035		if (hdr->taglen == 0 && req->rq_task != NULL) {
  1036			/* Use namespace info captured at task creation time */
> 1037			struct rpc_task *task = req->rq_task;
  1038	
> 1039			if (taks->tk_ns_inum != 0) {
  1040				char ns_tag[NFS4_MAXTAGLEN + 1];
  1041	
  1042				hdr->taglen = snprintf(ns_tag, sizeof(ns_tag), "ns:%u", taks->tk_ns_inum);
  1043				if (hdr->taglen > NFS4_MAXTAGLEN) {
  1044					hdr->taglen = NFS4_MAXTAGLEN;
  1045					ns_tag[NFS4_MAXTAGLEN] = '\0';
  1046				}
  1047				hdr->tag = ns_tag;
  1048			}
  1049		}
  1050	
  1051		/* initialize running count of expected bytes in reply.
  1052		 * NOTE: the replied tag SHOULD be the same is the one sent,
  1053		 * but this is not required as a MUST for the server to do so. */
  1054		hdr->replen = 3 + hdr->taglen;
  1055	
  1056		WARN_ON_ONCE(hdr->taglen > NFS4_MAXTAGLEN);
  1057		encode_string(xdr, hdr->taglen, hdr->tag);
  1058		p = reserve_space(xdr, 8);
  1059		*p++ = cpu_to_be32(hdr->minorversion);
  1060		hdr->nops_p = p;
  1061		*p = cpu_to_be32(hdr->nops);
  1062	}
  1063	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2026-08-06  6:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 15:10 [PATCH] [RFC] nfs4: inject process namespace into COMPOUND tag Tigran Mkrtchyan
2026-06-28 21:15 ` Trond Myklebust
2026-06-30 13:48   ` Mkrtchyan, Tigran
2026-08-06  6:40 ` kernel test robot [this message]
2026-08-06  9:43 ` kernel test robot
2026-08-07  5:02 ` kernel test robot

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=202608061449.3hOd5Rkm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tigran.mkrtchyan@desy.de \
    /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.