From: kernel test robot <lkp@intel.com>
To: Steve French <stfrench@microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [smfrench-smb3:pr/255 1/1] fs/smb/client/reparse.c:434:33: error: too many arguments to function call, expected 8, have 9
Date: Tue, 07 Jul 2026 06:07:37 +0200 [thread overview]
Message-ID: <202607070617.CHVxp8by-lkp@intel.com> (raw)
tree: https://github.com/smfrench/smb3-kernel.git pr/255
head: 7ad4ba8846086dd14f26bed6dd56de6d0050dfb4
commit: 7ad4ba8846086dd14f26bed6dd56de6d0050dfb4 [1/1] cifs: Create native Window socket file compatible also with WSL subsystem
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260707/202607070617.CHVxp8by-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260707/202607070617.CHVxp8by-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/202607070617.CHVxp8by-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/smb/client/reparse.c:434:33: error: too many arguments to function call, expected 8, have 9
429 | tcon->ses->server->ops->set_EA(xid, tcon, full_path,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
430 | true /* open reparse point */,
431 | SMB2_WSL_XATTR_MODE,
432 | &xattr_mode_val,
433 | SMB2_WSL_XATTR_MODE_SIZE,
434 | cifs_sb->local_nls, cifs_sb);
| ^~~~~~~
1 error generated.
vim +434 fs/smb/client/reparse.c
384
385 static int create_native_socket(const unsigned int xid, struct inode *inode,
386 struct dentry *dentry, struct cifs_tcon *tcon,
387 const char *full_path, umode_t mode)
388 {
389 struct reparse_data_buffer buf = {
390 .ReparseTag = cpu_to_le32(IO_REPARSE_TAG_AF_UNIX),
391 .ReparseDataLength = cpu_to_le16(0),
392 };
393 struct cifs_open_info_data data = {
394 .reparse_point = true,
395 .reparse = { .tag = IO_REPARSE_TAG_AF_UNIX, .buf = &buf, },
396 };
397 struct kvec iov = {
398 .iov_base = &buf,
399 .iov_len = sizeof(buf),
400 };
401 #ifdef CONFIG_CIFS_XATTR
402 const __le64 xattr_mode_val = cpu_to_le64(mode);
403 struct cifs_sb_info *cifs_sb = CIFS_SB(inode->i_sb);
404 #endif
405 struct inode *new;
406 int rc = 0;
407
408 new = tcon->ses->server->ops->create_reparse_inode(
409 &data, inode->i_sb, xid,
410 tcon, full_path, false, &iov, NULL);
411 if (!IS_ERR(new))
412 d_instantiate(dentry, new);
413 else
414 rc = PTR_ERR(new);
415
416 /*
417 * Try to set also optional WSL EA $LXMOD but ignore errors.
418 * WSL socket and native Win32/NT sockets uses same reparse point
419 * tag IO_REPARSE_TAG_AF_UNIX. WSL subsystem additionally requires
420 * EA $LXMOD to be set with the S_IFSOCK value. So setting this EA
421 * allows native socket to be recognized also by WSL subsystem.
422 * Note that setting of both EAs and reparse points is not supported
423 * by NTFS filesystem on Windows 8 / Windows Server 2012 and always
424 * fails. So ignore failures from this set_EA call.
425 */
426 #ifdef CONFIG_CIFS_XATTR
427 if (!rc && tcon->ses->server->ops->set_EA &&
428 (le32_to_cpu(tcon->fsAttrInfo.Attributes) & FILE_SUPPORTS_EXTENDED_ATTRIBUTES))
429 tcon->ses->server->ops->set_EA(xid, tcon, full_path,
430 true /* open reparse point */,
431 SMB2_WSL_XATTR_MODE,
432 &xattr_mode_val,
433 SMB2_WSL_XATTR_MODE_SIZE,
> 434 cifs_sb->local_nls, cifs_sb);
435 #endif
436
437 cifs_free_open_info(&data);
438 return rc;
439 }
440
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-07 4:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202607070617.CHVxp8by-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stfrench@microsoft.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 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.