From: kernel test robot <lkp@intel.com>
To: Byungchul Park <byungchul@sk.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, kernel_team@skhynix.com,
torvalds@linux-foundation.org, damien.lemoal@opensource.wdc.com,
linux-ide@vger.kernel.org, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, mingo@redhat.com,
peterz@infradead.org, will@kernel.org, tglx@linutronix.de,
rostedt@goodmis.org, joel@joelfernandes.org, sashal@kernel.org,
daniel.vetter@ffwll.ch, duyuyang@gmail.com,
johannes.berg@intel.com, tj@kernel.org, tytso@mit.edu,
willy@infradead.org, david@fromorbit.com, amir73il@gmail.com,
gregkh@linuxfoundation.org, kernel-team@lge.com,
linux-mm@kvack.org, akpm@linux-foundation.org, mhocko@kernel.org,
minchan@kernel.org, hannes@cmpxchg.org, vdavydov.dev@gmail.com
Subject: Re: [PATCH v11 25/26] dept: Print event context requestor's stacktrace on report
Date: Sun, 28 Jan 2024 22:44:42 +0800 [thread overview]
Message-ID: <202401282254.iwdPYJ9E-lkp@intel.com> (raw)
In-Reply-To: <20240124115938.80132-26-byungchul@sk.com>
Hi Byungchul,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 0dd3ee31125508cd67f7e7172247f05b7fd1753a]
url: https://github.com/intel-lab-lkp/linux/commits/Byungchul-Park/llist-Move-llist_-head-node-definition-to-types-h/20240124-200243
base: 0dd3ee31125508cd67f7e7172247f05b7fd1753a
patch link: https://lore.kernel.org/r/20240124115938.80132-26-byungchul%40sk.com
patch subject: [PATCH v11 25/26] dept: Print event context requestor's stacktrace on report
config: microblaze-allmodconfig (https://download.01.org/0day-ci/archive/20240128/202401282254.iwdPYJ9E-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240128/202401282254.iwdPYJ9E-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/202401282254.iwdPYJ9E-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/tests/drm_exec_test.c: In function 'test_prepare_array':
>> drivers/gpu/drm/tests/drm_exec_test.c:171:1: warning: the frame size of 1028 bytes is larger than 1024 bytes [-Wframe-larger-than=]
171 | }
| ^
vim +171 drivers/gpu/drm/tests/drm_exec_test.c
9710631cc8f367 Christian König 2022-04-13 149
9710631cc8f367 Christian König 2022-04-13 150 static void test_prepare_array(struct kunit *test)
9710631cc8f367 Christian König 2022-04-13 151 {
0f249678fef433 Arthur Grillo 2023-07-31 152 struct drm_exec_priv *priv = test->priv;
9710631cc8f367 Christian König 2022-04-13 153 struct drm_gem_object gobj1 = { };
9710631cc8f367 Christian König 2022-04-13 154 struct drm_gem_object gobj2 = { };
9710631cc8f367 Christian König 2022-04-13 155 struct drm_gem_object *array[] = { &gobj1, &gobj2 };
9710631cc8f367 Christian König 2022-04-13 156 struct drm_exec exec;
9710631cc8f367 Christian König 2022-04-13 157 int ret;
9710631cc8f367 Christian König 2022-04-13 158
0f249678fef433 Arthur Grillo 2023-07-31 159 drm_gem_private_object_init(priv->drm, &gobj1, PAGE_SIZE);
0f249678fef433 Arthur Grillo 2023-07-31 160 drm_gem_private_object_init(priv->drm, &gobj2, PAGE_SIZE);
9710631cc8f367 Christian König 2022-04-13 161
9710631cc8f367 Christian König 2022-04-13 162 drm_exec_init(&exec, DRM_EXEC_INTERRUPTIBLE_WAIT);
9710631cc8f367 Christian König 2022-04-13 163 drm_exec_until_all_locked(&exec)
9710631cc8f367 Christian König 2022-04-13 164 ret = drm_exec_prepare_array(&exec, array, ARRAY_SIZE(array),
9710631cc8f367 Christian König 2022-04-13 165 1);
9710631cc8f367 Christian König 2022-04-13 166 KUNIT_EXPECT_EQ(test, ret, 0);
9710631cc8f367 Christian König 2022-04-13 167 drm_exec_fini(&exec);
806fd6d005ad7a Danilo Krummrich 2023-08-10 168
806fd6d005ad7a Danilo Krummrich 2023-08-10 169 drm_gem_private_object_fini(&gobj1);
806fd6d005ad7a Danilo Krummrich 2023-08-10 170 drm_gem_private_object_fini(&gobj2);
9710631cc8f367 Christian König 2022-04-13 @171 }
9710631cc8f367 Christian König 2022-04-13 172
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-01-28 14:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 11:59 [PATCH v11 00/26] DEPT(Dependency Tracker) Byungchul Park
2024-01-24 11:59 ` [PATCH v11 01/26] llist: Move llist_{head,node} definition to types.h Byungchul Park
2024-01-24 11:59 ` [PATCH v11 02/26] dept: Implement Dept(Dependency Tracker) Byungchul Park
2024-01-24 11:59 ` [PATCH v11 03/26] dept: Add single event dependency tracker APIs Byungchul Park
2024-01-24 11:59 ` [PATCH v11 04/26] dept: Add lock " Byungchul Park
2024-01-24 11:59 ` [PATCH v11 05/26] dept: Tie to Lockdep and IRQ tracing Byungchul Park
2024-01-28 13:10 ` kernel test robot
2024-01-28 15:58 ` kernel test robot
2024-01-24 11:59 ` [PATCH v11 06/26] dept: Add proc knobs to show stats and dependency graph Byungchul Park
2024-01-24 11:59 ` [PATCH v11 07/26] dept: Apply sdt_might_sleep_{start,end}() to wait_for_completion()/complete() Byungchul Park
2024-01-24 11:59 ` [PATCH v11 08/26] dept: Apply sdt_might_sleep_{start,end}() to swait Byungchul Park
2024-01-24 11:59 ` [PATCH v11 09/26] dept: Apply sdt_might_sleep_{start,end}() to waitqueue wait Byungchul Park
2024-01-24 11:59 ` [PATCH v11 10/26] dept: Apply sdt_might_sleep_{start,end}() to hashed-waitqueue wait Byungchul Park
2024-01-24 11:59 ` [PATCH v11 11/26] dept: Distinguish each syscall context from another Byungchul Park
2024-01-24 11:59 ` [PATCH v11 12/26] dept: Distinguish each work " Byungchul Park
2024-01-24 11:59 ` [PATCH v11 13/26] dept: Add a mechanism to refill the internal memory pools on running out Byungchul Park
2024-01-24 11:59 ` [PATCH v11 14/26] locking/lockdep, cpu/hotplus: Use a weaker annotation in AP thread Byungchul Park
2024-01-26 17:30 ` Thomas Gleixner
2024-01-29 4:20 ` Byungchul Park
2024-01-30 2:58 ` Byungchul Park
2024-02-12 15:16 ` Thomas Gleixner
2024-02-13 1:18 ` Byungchul Park
2024-06-04 3:10 ` Byungchul Park
2024-01-24 11:59 ` [PATCH v11 15/26] dept: Apply sdt_might_sleep_{start,end}() to dma fence wait Byungchul Park
2024-01-24 11:59 ` [PATCH v11 16/26] dept: Track timeout waits separately with a new Kconfig Byungchul Park
2024-01-24 11:59 ` [PATCH v11 17/26] dept: Apply timeout consideration to wait_for_completion()/complete() Byungchul Park
2024-01-24 11:59 ` [PATCH v11 18/26] dept: Apply timeout consideration to swait Byungchul Park
2024-01-24 11:59 ` [PATCH v11 19/26] dept: Apply timeout consideration to waitqueue wait Byungchul Park
2024-01-24 11:59 ` [PATCH v11 20/26] dept: Apply timeout consideration to hashed-waitqueue wait Byungchul Park
2024-01-24 11:59 ` [PATCH v11 21/26] dept: Apply timeout consideration to dma fence wait Byungchul Park
2024-01-24 11:59 ` [PATCH v11 22/26] dept: Record the latest one out of consecutive waits of the same class Byungchul Park
2024-01-24 11:59 ` [PATCH v11 23/26] dept: Make Dept able to work with an external wgen Byungchul Park
2024-01-24 11:59 ` [PATCH v11 24/26] dept: Track PG_locked with dept Byungchul Park
2024-01-24 11:59 ` [PATCH v11 25/26] dept: Print event context requestor's stacktrace on report Byungchul Park
2024-01-28 14:44 ` kernel test robot [this message]
2024-01-24 11:59 ` [PATCH v11 26/26] locking/lockdep, fs/jbd2: Use a weaker annotation in journal handling Byungchul 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=202401282254.iwdPYJ9E-lkp@intel.com \
--to=lkp@intel.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=byungchul@sk.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel.vetter@ffwll.ch \
--cc=david@fromorbit.com \
--cc=duyuyang@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=joel@joelfernandes.org \
--cc=johannes.berg@intel.com \
--cc=kernel-team@lge.com \
--cc=kernel_team@skhynix.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=vdavydov.dev@gmail.com \
--cc=will@kernel.org \
--cc=willy@infradead.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