From: kernel test robot <lkp@intel.com>
To: SeongJae Park <sjpark@amazon.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: mm/damon/vaddr-test.h:309:1: warning: the frame size of 1064 bytes is larger than 1024 bytes
Date: Thu, 18 Nov 2021 21:53:55 +0800 [thread overview]
Message-ID: <202111182146.OV3C4uGr-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3453 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 42eb8fdac2fc5d62392dcfcf0253753e821a97b0
commit: 17ccae8bb5c928946f6f3af14626ec458f74e6ad mm/damon: add kunit tests
date: 2 months ago
config: mips-randconfig-c004-20211118 (attached as .config)
compiler: mipsel-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
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17ccae8bb5c928946f6f3af14626ec458f74e6ad
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 17ccae8bb5c928946f6f3af14626ec458f74e6ad
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=mips
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 >>):
In file included from mm/damon/vaddr.c:672:
mm/damon/vaddr-test.h: In function 'damon_test_split_evenly':
>> mm/damon/vaddr-test.h:309:1: warning: the frame size of 1064 bytes is larger than 1024 bytes [-Wframe-larger-than=]
309 | }
| ^
vim +309 mm/damon/vaddr-test.h
254
255 static void damon_test_split_evenly(struct kunit *test)
256 {
257 struct damon_ctx *c = damon_new_ctx();
258 struct damon_target *t;
259 struct damon_region *r;
260 unsigned long i;
261
262 KUNIT_EXPECT_EQ(test, damon_va_evenly_split_region(NULL, NULL, 5),
263 -EINVAL);
264
265 t = damon_new_target(42);
266 r = damon_new_region(0, 100);
267 KUNIT_EXPECT_EQ(test, damon_va_evenly_split_region(t, r, 0), -EINVAL);
268
269 damon_add_region(r, t);
270 KUNIT_EXPECT_EQ(test, damon_va_evenly_split_region(t, r, 10), 0);
271 KUNIT_EXPECT_EQ(test, damon_nr_regions(t), 10u);
272
273 i = 0;
274 damon_for_each_region(r, t) {
275 KUNIT_EXPECT_EQ(test, r->ar.start, i++ * 10);
276 KUNIT_EXPECT_EQ(test, r->ar.end, i * 10);
277 }
278 damon_free_target(t);
279
280 t = damon_new_target(42);
281 r = damon_new_region(5, 59);
282 damon_add_region(r, t);
283 KUNIT_EXPECT_EQ(test, damon_va_evenly_split_region(t, r, 5), 0);
284 KUNIT_EXPECT_EQ(test, damon_nr_regions(t), 5u);
285
286 i = 0;
287 damon_for_each_region(r, t) {
288 if (i == 4)
289 break;
290 KUNIT_EXPECT_EQ(test, r->ar.start, 5 + 10 * i++);
291 KUNIT_EXPECT_EQ(test, r->ar.end, 5 + 10 * i);
292 }
293 KUNIT_EXPECT_EQ(test, r->ar.start, 5 + 10 * i);
294 KUNIT_EXPECT_EQ(test, r->ar.end, 59ul);
295 damon_free_target(t);
296
297 t = damon_new_target(42);
298 r = damon_new_region(5, 6);
299 damon_add_region(r, t);
300 KUNIT_EXPECT_EQ(test, damon_va_evenly_split_region(t, r, 2), -EINVAL);
301 KUNIT_EXPECT_EQ(test, damon_nr_regions(t), 1u);
302
303 damon_for_each_region(r, t) {
304 KUNIT_EXPECT_EQ(test, r->ar.start, 5ul);
305 KUNIT_EXPECT_EQ(test, r->ar.end, 6ul);
306 }
307 damon_free_target(t);
308 damon_destroy_ctx(c);
> 309 }
310
---
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: 34643 bytes --]
next reply other threads:[~2021-11-18 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 13:53 kernel test robot [this message]
2021-12-01 17:35 ` SeongJae Park
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=202111182146.OV3C4uGr-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=brendanhiggins@google.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sjpark@amazon.de \
/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