From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jgunthorpe:iommufd 7/9] drivers/iommu/iommufd/selftest.c:204:1: warning: the frame size of 1052 bytes is larger than 1024 bytes
Date: Sat, 4 Dec 2021 05:35:46 +0800 [thread overview]
Message-ID: <202112040504.mo85qmGT-lkp@intel.com> (raw)
tree: https://github.com/jgunthorpe/linux iommufd
head: adaf58fcdccd96a03a9d6783e08303612fa3da85
commit: 947b2f74edc5dcad1f9532abd9bdd42a25a00490 [7/9] iommufd: Add a selftest
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20211204/202112040504.mo85qmGT-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/jgunthorpe/linux/commit/947b2f74edc5dcad1f9532abd9bdd42a25a00490
git remote add jgunthorpe https://github.com/jgunthorpe/linux
git fetch --no-tags jgunthorpe iommufd
git checkout 947b2f74edc5dcad1f9532abd9bdd42a25a00490
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/iommu/iommufd/
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 >>):
drivers/iommu/iommufd/selftest.c: In function 'iommufd_test_mock_domain.isra.0':
>> drivers/iommu/iommufd/selftest.c:204:1: warning: the frame size of 1052 bytes is larger than 1024 bytes [-Wframe-larger-than=]
204 | }
| ^
vim +204 drivers/iommu/iommufd/selftest.c
181
182 /* Create an hw_pagetable with the mock domain so we can test the domain ops */
183 static int iommufd_test_mock_domain(struct iommufd_ucmd *ucmd,
184 struct iommu_test_cmd *cmd)
185 {
186 struct bus_type mock_bus = {.iommu_ops = &domain_mock_ops};
187 struct device mock_dev = {.bus = &mock_bus};
188 struct iommufd_hw_pagetable *hwpt;
189
190 hwpt = iommufd_hw_pagetable_from_id(ucmd->ictx, cmd->id, &mock_dev);
191 if (IS_ERR(hwpt))
192 return PTR_ERR(hwpt);
193 if (WARN_ON(refcount_read(&hwpt->obj.users) != 1)) {
194 iommufd_hw_pagetable_put(ucmd->ictx, hwpt);
195 return -EINVAL;
196 }
197
198 /* Convert auto domain to user created */
199 list_del_init(&hwpt->auto_domains_item);
200
201 /* Leak on error */
202 cmd->id = hwpt->obj.id;
203 return iommufd_ucmd_respond(ucmd, sizeof(*cmd));
> 204 }
205
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-12-03 21:36 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=202112040504.mo85qmGT-lkp@intel.com \
--to=lkp@intel.com \
--cc=jgg@nvidia.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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