From: kernel test robot <lkp@intel.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 5/7] ksmbd: lazy v2 lease break on smb2_write()
Date: Wed, 6 Dec 2023 20:41:26 +0800 [thread overview]
Message-ID: <202312062020.FbeMXJCT-lkp@intel.com> (raw)
In-Reply-To: <20231204134509.11413-5-linkinjeon@kernel.org>
Hi Namjae,
kernel test robot noticed the following build warnings:
[auto build test WARNING on cifs/for-next]
[also build test WARNING on linus/master v6.7-rc4 next-20231206]
[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/Namjae-Jeon/ksmbd-set-v2-lease-capability/20231204-214847
base: git://git.samba.org/sfrench/cifs-2.6.git for-next
patch link: https://lore.kernel.org/r/20231204134509.11413-5-linkinjeon%40kernel.org
patch subject: [PATCH 5/7] ksmbd: lazy v2 lease break on smb2_write()
config: parisc-randconfig-r122-20231206 (https://download.01.org/0day-ci/archive/20231206/202312062020.FbeMXJCT-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20231206/202312062020.FbeMXJCT-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/202312062020.FbeMXJCT-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/smb/server/oplock.c: note: in included file (through include/linux/dcache.h, include/linux/unicode.h, fs/smb/server/unicode.h, ...):
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
>> fs/smb/server/oplock.c:1120:16: sparse: sparse: dereference of noderef expression
fs/smb/server/oplock.c:1120:42: sparse: sparse: dereference of noderef expression
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
include/linux/list.h:83:21: sparse: sparse: self-comparison always evaluates to true
vim +1120 fs/smb/server/oplock.c
1114
1115 void smb_lazy_parent_lease_break_close(struct ksmbd_file *fp)
1116 {
1117 struct oplock_info *opinfo;
1118 struct ksmbd_inode *p_ci = NULL;
1119
> 1120 if (!fp->f_opinfo->is_lease || fp->f_opinfo->o_lease->version != 2)
1121 return;
1122
1123 p_ci = ksmbd_inode_lookup_lock(fp->filp->f_path.dentry->d_parent);
1124 if (!p_ci)
1125 return;
1126
1127 list_for_each_entry(opinfo, &p_ci->m_op_list, op_entry) {
1128 if (!opinfo->is_lease)
1129 continue;
1130
1131 if (opinfo->o_lease->state != SMB2_OPLOCK_LEVEL_NONE)
1132 oplock_break(opinfo, SMB2_OPLOCK_LEVEL_NONE);
1133 }
1134
1135 ksmbd_inode_put(p_ci);
1136 }
1137
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-06 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 13:45 [PATCH 1/7] ksmbd: set epoch in create context v2 lease Namjae Jeon
2023-12-04 13:45 ` [PATCH 2/7] ksmbd: set v2 lease capability Namjae Jeon
2023-12-04 13:45 ` [PATCH 3/7] ksmbd: downgrade RWH lease caching state to RH for directory Namjae Jeon
2023-12-05 11:15 ` kernel test robot
2023-12-05 12:04 ` Namjae Jeon
2023-12-04 13:45 ` [PATCH 4/7] ksmbd: send v2 lease break notification " Namjae Jeon
2023-12-04 13:45 ` [PATCH 5/7] ksmbd: lazy v2 lease break on smb2_write() Namjae Jeon
2023-12-06 12:41 ` kernel test robot [this message]
2023-12-06 13:12 ` Namjae Jeon
2023-12-04 13:45 ` [PATCH 6/7] ksmbd: avoid duplicate opinfo_put() call on error of smb21_lease_break_ack() Namjae Jeon
2023-12-04 13:45 ` [PATCH 7/7] ksmbd: fix wrong allocation size update in smb2_open() Namjae Jeon
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=202312062020.FbeMXJCT-lkp@intel.com \
--to=lkp@intel.com \
--cc=linkinjeon@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.