From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: oe-kbuild-all@lists.linux.dev, Carlos Maiolino <cem@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>
Subject: [xfs:xfs-7.4-merge 38/42] fs/xfs/xfs_ioctl32.c:74:33: warning: variable 'in' set but not used
Date: Sat, 05 Sep 2026 02:07:39 +0800 [thread overview]
Message-ID: <202609050143.6VQfT7oG-lkp@intel.com> (raw)
tree: git://git.kernel.org:/pub/scm/fs/xfs/xfs-linux xfs-7.4-merge
head: c44f3db4f4c00c5250ddb290bb7cbd2a5ed40155
commit: 1e4c3089ab63d3afee702243630d9c3c919a046b [38/42] xfs: split out the handlers for XFS_IOC_FSGROWFS_*_32
config: x86_64-randconfig-012-20251225 (https://download.01.org/0day-ci/archive/20260905/202609050143.6VQfT7oG-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260905/202609050143.6VQfT7oG-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/202609050143.6VQfT7oG-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/xfs/xfs_ioctl32.c: In function 'xfs_compat_ioc_growfs_rt':
>> fs/xfs/xfs_ioctl32.c:74:33: warning: variable 'in' set but not used [-Wunused-but-set-variable]
74 | struct xfs_growfs_rt in = {};
| ^~
vim +/in +74 fs/xfs/xfs_ioctl32.c
67
68 static int
69 xfs_compat_ioc_growfs_rt(
70 struct file *file,
71 struct xfs_mount *mp,
72 struct compat_xfs_growfs_rt __user *arg32)
73 {
> 74 struct xfs_growfs_rt in = {};
75 int error;
76
77 if (get_user(in.newblocks, &arg32->newblocks) ||
78 get_user(in.extsize, &arg32->extsize))
79 return -EFAULT;
80
81 error = mnt_want_write_file(file);
82 if (error)
83 return error;
84 error = xfs_growfs_rt(mp, &in);
85 mnt_drop_write_file(file);
86 return error;
87 }
88
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-04 18:07 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=202609050143.6VQfT7oG-lkp@intel.com \
--to=lkp@intel.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--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.