From: kernel test robot <lkp@intel.com>
To: zhang.guodong@linux.dev, smfrench@gmail.com,
linkinjeon@kernel.org, pc@manguebit.org,
ronniesahlberg@gmail.com, sprasad@microsoft.com, tom@talpey.com,
bharathsm@microsoft.com, senozhatsky@chromium.org,
dhowells@redhat.com, chenxiaosong@kylinos.cn,
chenxiaosong.chenxiaosong@linux.dev
Cc: oe-kbuild-all@lists.linux.dev, linux-cifs@vger.kernel.org,
ZhangGuoDong <zhangguodong@kylinos.cn>
Subject: Re: [PATCH v3 4/5] smb: introduce struct create_posix_ctxt_rsp
Date: Tue, 17 Feb 2026 02:22:42 +0800 [thread overview]
Message-ID: <202602170244.C33LgPOh-lkp@intel.com> (raw)
In-Reply-To: <20260216082018.156695-5-zhang.guodong@linux.dev>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on cifs/for-next]
[also build test WARNING on brauner-vfs/vfs.all linus/master next-20260216]
[cannot apply to v6.19]
[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/zhang-guodong-linux-dev/smb-move-smb3_fs_vol_info-into-common-fscc-h/20260216-162407
base: git://git.samba.org/sfrench/cifs-2.6.git for-next
patch link: https://lore.kernel.org/r/20260216082018.156695-5-zhang.guodong%40linux.dev
patch subject: [PATCH v3 4/5] smb: introduce struct create_posix_ctxt_rsp
config: i386-randconfig-r123-20260216 (https://download.01.org/0day-ci/archive/20260217/202602170244.C33LgPOh-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260217/202602170244.C33LgPOh-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/202602170244.C33LgPOh-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/smb/client/smb2pdu.c:2365:31: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le32 [usertype] nlink @@ got unsigned int [usertype] @@
fs/smb/client/smb2pdu.c:2365:31: sparse: expected restricted __le32 [usertype] nlink
fs/smb/client/smb2pdu.c:2365:31: sparse: got unsigned int [usertype]
>> fs/smb/client/smb2pdu.c:2366:37: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le32 [usertype] reparse_tag @@ got unsigned int [usertype] @@
fs/smb/client/smb2pdu.c:2366:37: sparse: expected restricted __le32 [usertype] reparse_tag
fs/smb/client/smb2pdu.c:2366:37: sparse: got unsigned int [usertype]
>> fs/smb/client/smb2pdu.c:2367:30: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le32 [usertype] mode @@ got unsigned int [usertype] @@
fs/smb/client/smb2pdu.c:2367:30: sparse: expected restricted __le32 [usertype] mode
fs/smb/client/smb2pdu.c:2367:30: sparse: got unsigned int [usertype]
fs/smb/client/smb2pdu.c:6231:41: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned int [usertype] vol_serial_number @@ got restricted __le32 [usertype] VolumeSerialNumber @@
fs/smb/client/smb2pdu.c:6231:41: sparse: expected unsigned int [usertype] vol_serial_number
fs/smb/client/smb2pdu.c:6231:41: sparse: got restricted __le32 [usertype] VolumeSerialNumber
vim +2365 fs/smb/client/smb2pdu.c
2353
2354 static void
2355 parse_posix_ctxt(struct create_context *cc, struct smb2_file_all_info *info,
2356 struct create_posix_rsp *posix)
2357 {
2358 int sid_len;
2359 u8 *beg = (u8 *)cc + le16_to_cpu(cc->DataOffset);
2360 u8 *end = beg + le32_to_cpu(cc->DataLength);
2361 u8 *sid;
2362
2363 memset(posix, 0, sizeof(*posix));
2364
> 2365 posix->ctxt_rsp.nlink = le32_to_cpu(*(__le32 *)(beg + 0));
> 2366 posix->ctxt_rsp.reparse_tag = le32_to_cpu(*(__le32 *)(beg + 4));
> 2367 posix->ctxt_rsp.mode = le32_to_cpu(*(__le32 *)(beg + 8));
2368
2369 sid = beg + 12;
2370 sid_len = posix_info_sid_size(sid, end);
2371 if (sid_len < 0) {
2372 cifs_dbg(VFS, "bad owner sid in posix create response\n");
2373 return;
2374 }
2375 memcpy(&posix->owner, sid, sid_len);
2376
2377 sid = sid + sid_len;
2378 sid_len = posix_info_sid_size(sid, end);
2379 if (sid_len < 0) {
2380 cifs_dbg(VFS, "bad group sid in posix create response\n");
2381 return;
2382 }
2383 memcpy(&posix->group, sid, sid_len);
2384
2385 cifs_dbg(FYI, "nlink=%d mode=%o reparse_tag=%x\n",
2386 posix->ctxt_rsp.nlink, posix->ctxt_rsp.mode,
2387 posix->ctxt_rsp.reparse_tag);
2388 }
2389
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-16 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 8:20 [PATCH v3 0/5] smb: move duplicate definitions into common header file, part 2 zhang.guodong
2026-02-16 8:20 ` [PATCH v3 1/5] smb: move smb3_fs_vol_info into common/fscc.h zhang.guodong
2026-02-16 16:05 ` kernel test robot
2026-02-16 8:20 ` [PATCH v3 2/5] smb: move some definitions from common/smb2pdu.h " zhang.guodong
2026-02-16 8:20 ` [PATCH v3 3/5] smb: move file_basic_info " zhang.guodong
2026-02-16 8:20 ` [PATCH v3 4/5] smb: introduce struct create_posix_ctxt_rsp zhang.guodong
2026-02-16 18:22 ` kernel test robot [this message]
2026-02-17 14:20 ` ZhangGuoDong
[not found] ` <CAH2r5muK5WrHkJsJ=Rix7ceFFZNzpQkUZSaSsHi8PMXVpw88pw@mail.gmail.com>
[not found] ` <b840459a-8a31-46e7-817a-3b80e9ed1353@linux.dev>
[not found] ` <CAH2r5muScb7NmeJa1BNwAt8Qzb7WmwVfvskZ=9LEV6WWyO5HyQ@mail.gmail.com>
[not found] ` <d6149e9f-9607-4379-a74d-c4bbe12fef00@linux.dev>
2026-02-19 8:16 ` ChenXiaoSong
2026-02-19 13:14 ` ChenXiaoSong
2026-02-16 8:20 ` [PATCH v3 5/5] smb: introduce struct file_posix_info zhang.guodong
2026-02-20 1:27 ` [PATCH v3 0/5] smb: move duplicate definitions into common header file, part 2 Namjae Jeon
2026-02-20 10:54 ` ZhangGuoDong
2026-02-22 7:39 ` ChenXiaoSong
2026-02-22 15:26 ` ChenXiaoSong
2026-02-22 15:42 ` ChenXiaoSong
2026-02-25 3:14 ` ZhangGuoDong
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=202602170244.C33LgPOh-lkp@intel.com \
--to=lkp@intel.com \
--cc=bharathsm@microsoft.com \
--cc=chenxiaosong.chenxiaosong@linux.dev \
--cc=chenxiaosong@kylinos.cn \
--cc=dhowells@redhat.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=sprasad@microsoft.com \
--cc=tom@talpey.com \
--cc=zhang.guodong@linux.dev \
--cc=zhangguodong@kylinos.cn \
/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