From: kernel test robot <lkp@intel.com>
To: Steve French <stfrench@microsoft.com>
Cc: kbuild-all@lists.01.org, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org,
Ronnie Sahlberg <lsahlber@redhat.com>
Subject: [cifs:for-next 3/4] fs/smbfs_client/ioctl.c:324:17: warning: variable 'caps' set but not used
Date: Tue, 14 Sep 2021 17:29:35 +0800 [thread overview]
Message-ID: <202109141712.zewNJ6VW-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2897 bytes --]
Hi Steve,
First bad commit (maybe != root cause):
tree: git://git.samba.org/sfrench/cifs-2.6.git for-next
head: c1abf13059571edd59d42d676ffe593fb987c019
commit: b4a8c8f8fa8b7b86bb62257fbb27e7bde58ac97e [3/4] cifs: rename fs/cifs directory to fs/smbfs_client
config: ia64-defconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add cifs git://git.samba.org/sfrench/cifs-2.6.git
git fetch --no-tags cifs for-next
git checkout b4a8c8f8fa8b7b86bb62257fbb27e7bde58ac97e
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=ia64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
fs/smbfs_client/ioctl.c: In function 'cifs_ioctl':
>> fs/smbfs_client/ioctl.c:324:17: warning: variable 'caps' set but not used [-Wunused-but-set-variable]
324 | __u64 caps;
| ^~~~
vim +/caps +324 fs/smbfs_client/ioctl.c
7ba3d1cdb7988ccf fs/cifs/ioctl.c Steve French 2021-05-02 312
f9ddcca4cf7d9523 fs/cifs/ioctl.c Steve French 2008-05-15 313 long cifs_ioctl(struct file *filep, unsigned int command, unsigned long arg)
^1da177e4c3f4152 fs/cifs/ioctl.c Linus Torvalds 2005-04-16 314 {
496ad9aa8ef44805 fs/cifs/ioctl.c Al Viro 2013-01-23 315 struct inode *inode = file_inode(filep);
7e7db86c7e1088e7 fs/cifs/ioctl.c Steve French 2019-09-19 316 struct smb3_key_debug_info pkey_inf;
^1da177e4c3f4152 fs/cifs/ioctl.c Linus Torvalds 2005-04-16 317 int rc = -ENOTTY; /* strange error - but the precedent */
6d5786a34d98bffb fs/cifs/ioctl.c Pavel Shilovsky 2012-06-20 318 unsigned int xid;
ba00ba64cf0895e4 fs/cifs/ioctl.c Jeff Layton 2010-09-20 319 struct cifsFileInfo *pSMBFile = filep->private_data;
96daf2b09178d8eb fs/cifs/ioctl.c Steve French 2011-05-27 320 struct cifs_tcon *tcon;
a77592a70081edb5 fs/cifs/ioctl.c Ronnie Sahlberg 2020-07-09 321 struct tcon_link *tlink;
d26c2ddd33569667 fs/cifs/ioctl.c Steve French 2020-02-06 322 struct cifs_sb_info *cifs_sb;
f654bac2227adc5c fs/cifs/ioctl.c Steve French 2005-04-28 323 __u64 ExtAttrBits = 0;
618763958b2291a0 fs/cifs/ioctl.c Jeff Layton 2010-11-08 @324 __u64 caps;
:::::: The code at line 324 was first introduced by commit
:::::: 618763958b2291a09057dbfa553da6ded93dcfad cifs: make cifs_ioctl handle NULL filp->private_data correctly
:::::: TO: Jeff Layton <jlayton@redhat.com>
:::::: CC: Steve French <sfrench@us.ibm.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 19993 bytes --]
reply other threads:[~2021-09-14 9:30 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=202109141712.zewNJ6VW-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-cifs@vger.kernel.org \
--cc=lsahlber@redhat.com \
--cc=samba-technical@lists.samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox