From: kernel test robot <lkp@intel.com>
To: Byungchul Park <max.byungchul.park@gmail.com>,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, 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,
sj@kernel.org
Subject: Re: [PATCH v8 05/25] dept: Tie to Lockdep and IRQ tracing
Date: Sun, 29 Jan 2023 16:56:55 +0800 [thread overview]
Message-ID: <202301291601.7591xziv-lkp@intel.com> (raw)
In-Reply-To: <1674782358-25542-6-git-send-email-max.byungchul.park@gmail.com>
Hi Byungchul,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/locking/core]
[also build test WARNING on tip/sched/core drm-misc/drm-misc-next linus/master v6.2-rc5]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Byungchul-Park/llist-Move-llist_-head-node-definition-to-types-h/20230128-102456
patch link: https://lore.kernel.org/r/1674782358-25542-6-git-send-email-max.byungchul.park%40gmail.com
patch subject: [PATCH v8 05/25] dept: Tie to Lockdep and IRQ tracing
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20230129/202301291601.7591xziv-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/aed5169e3b6767146ee602447fcf75b4c734d2db
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Byungchul-Park/llist-Move-llist_-head-node-definition-to-types-h/20230128-102456
git checkout aed5169e3b6767146ee602447fcf75b4c734d2db
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 olddefconfig
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/net/ethernet/microchip/vcap/ drivers/platform/chrome/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
drivers/platform/chrome/cros_ec_proto_test.c: In function 'cros_ec_proto_test_get_sensor_count_xfer_error':
>> drivers/platform/chrome/cros_ec_proto_test.c:2528:1: warning: the frame size of 2072 bytes is larger than 2048 bytes [-Wframe-larger-than=]
2528 | }
| ^
drivers/platform/chrome/cros_ec_proto_test.c: In function 'cros_ec_proto_test_get_sensor_count_normal':
drivers/platform/chrome/cros_ec_proto_test.c:2488:1: warning: the frame size of 2072 bytes is larger than 2048 bytes [-Wframe-larger-than=]
2488 | }
| ^
drivers/platform/chrome/cros_ec_proto_test.c: In function 'cros_ec_proto_test_get_sensor_count_legacy':
drivers/platform/chrome/cros_ec_proto_test.c:2593:1: warning: the frame size of 2136 bytes is larger than 2048 bytes [-Wframe-larger-than=]
2593 | }
| ^
drivers/platform/chrome/cros_ec_proto_test.c: In function 'cros_ec_proto_test_check_features_not_cached':
drivers/platform/chrome/cros_ec_proto_test.c:2443:1: warning: the frame size of 2056 bytes is larger than 2048 bytes [-Wframe-larger-than=]
2443 | }
| ^
--
In file included from drivers/net/ethernet/microchip/vcap/vcap_api.c:2882:
drivers/net/ethernet/microchip/vcap/vcap_api_kunit.c: In function 'vcap_api_next_lookup_advanced_test':
>> drivers/net/ethernet/microchip/vcap/vcap_api_kunit.c:1955:1: warning: the frame size of 2240 bytes is larger than 2048 bytes [-Wframe-larger-than=]
1955 | }
| ^
vim +2528 drivers/platform/chrome/cros_ec_proto_test.c
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2489
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2490 static void cros_ec_proto_test_get_sensor_count_xfer_error(struct kunit *test)
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2491 {
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2492 struct cros_ec_proto_test_priv *priv = test->priv;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2493 struct cros_ec_device *ec_dev = &priv->ec_dev;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2494 struct ec_xfer_mock *mock;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2495 int ret;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2496 struct cros_ec_dev ec;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2497
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2498 ec_dev->max_request = 0xff;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2499 ec_dev->max_response = 0xee;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2500 ec.ec_dev = ec_dev;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2501 ec.dev = ec_dev->dev;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2502 ec.cmd_offset = 0;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2503
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2504 /* For EC_CMD_MOTION_SENSE_CMD. */
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2505 {
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2506 mock = cros_kunit_ec_xfer_mock_addx(test, -EPROTO, EC_RES_SUCCESS, 0);
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2507 KUNIT_ASSERT_PTR_NE(test, mock, NULL);
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2508 }
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2509
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2510 ret = cros_ec_get_sensor_count(&ec);
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2511 KUNIT_EXPECT_EQ(test, ret, -EPROTO);
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2512
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2513 /* For EC_CMD_MOTION_SENSE_CMD. */
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2514 {
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2515 struct ec_params_motion_sense *data;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2516
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2517 mock = cros_kunit_ec_xfer_mock_next();
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2518 KUNIT_EXPECT_PTR_NE(test, mock, NULL);
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2519
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2520 KUNIT_EXPECT_EQ(test, mock->msg.version, 1);
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2521 KUNIT_EXPECT_EQ(test, mock->msg.command, EC_CMD_MOTION_SENSE_CMD);
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2522 KUNIT_EXPECT_EQ(test, mock->msg.insize, sizeof(struct ec_response_motion_sense));
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2523 KUNIT_EXPECT_EQ(test, mock->msg.outsize, sizeof(*data));
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2524
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2525 data = (struct ec_params_motion_sense *)mock->i_data;
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2526 KUNIT_EXPECT_EQ(test, data->cmd, MOTIONSENSE_CMD_DUMP);
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2527 }
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 @2528 }
33f0fdba6066b5 Tzung-Bi Shih 2022-06-22 2529
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-01-29 8:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 1:18 [PATCH v8 00/25] DEPT(Dependency Tracker) Byungchul Park
2023-01-27 1:18 ` [PATCH v8 01/25] llist: Move llist_{head,node} definition to types.h Byungchul Park
2023-01-27 1:18 ` [PATCH v8 02/25] dept: Implement Dept(Dependency Tracker) Byungchul Park
2023-01-27 1:18 ` [PATCH v8 03/25] dept: Add single event dependency tracker APIs Byungchul Park
2023-01-27 1:18 ` [PATCH v8 04/25] dept: Add lock " Byungchul Park
2023-01-27 1:18 ` [PATCH v8 05/25] dept: Tie to Lockdep and IRQ tracing Byungchul Park
2023-01-28 7:24 ` kernel test robot
2023-01-29 8:56 ` kernel test robot [this message]
2023-01-27 1:18 ` [PATCH v8 06/25] dept: Add proc knobs to show stats and dependency graph Byungchul Park
2023-01-27 1:19 ` [PATCH v8 07/25] dept: Apply sdt_might_sleep_{start,end}() to wait_for_completion()/complete() Byungchul Park
2023-01-27 1:19 ` [PATCH v8 08/25] dept: Apply sdt_might_sleep_{start,end}() to PG_{locked,writeback} wait Byungchul Park
2023-01-27 1:19 ` [PATCH v8 09/25] dept: Apply sdt_might_sleep_{start,end}() to swait Byungchul Park
2023-01-27 1:19 ` [PATCH v8 10/25] dept: Apply sdt_might_sleep_{start,end}() to waitqueue wait Byungchul Park
2023-01-27 1:19 ` [PATCH v8 11/25] dept: Apply sdt_might_sleep_{start,end}() to hashed-waitqueue wait Byungchul Park
2023-01-27 1:19 ` [PATCH v8 12/25] dept: Distinguish each syscall context from another Byungchul Park
2023-01-27 1:19 ` [PATCH v8 13/25] dept: Distinguish each work " Byungchul Park
2023-01-27 1:19 ` [PATCH v8 14/25] dept: Add a mechanism to refill the internal memory pools on running out Byungchul Park
2023-01-27 1:19 ` [PATCH v8 15/25] locking/lockdep, cpu/hotplus: Use a weaker annotation in AP thread Byungchul Park
2023-01-27 1:19 ` [PATCH v8 16/25] dept: Apply sdt_might_sleep_{start,end}() to dma fence wait Byungchul Park
2023-01-27 1:19 ` [PATCH v8 17/25] dept: Track timeout waits separately with a new Kconfig Byungchul Park
2023-01-27 1:19 ` [PATCH v8 18/25] dept: Apply timeout consideration to wait_for_completion()/complete() Byungchul Park
2023-01-27 1:19 ` [PATCH v8 19/25] dept: Apply timeout consideration to swait Byungchul Park
2023-01-27 1:19 ` [PATCH v8 20/25] dept: Apply timeout consideration to waitqueue wait Byungchul Park
2023-01-27 1:19 ` [PATCH v8 21/25] dept: Apply timeout consideration to hashed-waitqueue wait Byungchul Park
2023-01-27 1:19 ` [PATCH v8 22/25] dept: Apply timeout consideration to dma fence wait Byungchul Park
2023-01-27 1:19 ` [PATCH v8 23/25] dept: Record the latest one out of consecutive waits of the same class Byungchul Park
2023-01-27 1:19 ` [PATCH v8 24/25] dept: Make Dept able to work with an external wgen Byungchul Park
2023-01-27 1:19 ` [PATCH v8 25/25] dept: Track the potential waits of PG_{locked,writeback} Byungchul Park
2023-01-28 20:30 ` kernel test robot
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=202301291601.7591xziv-lkp@intel.com \
--to=lkp@intel.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.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=linux-ext4@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=max.byungchul.park@gmail.com \
--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=sj@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;
as well as URLs for NNTP newsgroup(s).