From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: drivers/gpu/drm/xe/xe_guc_relay.c:598 relay_handle_failure() warn: passing zero to 'ERR_PTR'
Date: Sun, 15 Dec 2024 02:11:17 +0800 [thread overview]
Message-ID: <202412150254.vl3tkK75-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Michal Wajdeczko <michal.wajdeczko@intel.com>
CC: "José Roberto de Souza" <jose.souza@intel.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a446e965a188ee8f745859e63ce046fe98577d45
commit: 2b35ae108c7f5486adbc9e70377110ab8c91f61b drm/xe: Fix compilation without CONFIG_KUNIT
date: 11 months ago
:::::: branch date: 16 hours ago
:::::: commit date: 11 months ago
config: x86_64-randconfig-r073-20241208 (https://download.01.org/0day-ci/archive/20241215/202412150254.vl3tkK75-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202412150254.vl3tkK75-lkp@intel.com/
smatch warnings:
drivers/gpu/drm/xe/xe_guc_relay.c:598 relay_handle_failure() warn: passing zero to 'ERR_PTR'
vim +/ERR_PTR +598 drivers/gpu/drm/xe/xe_guc_relay.c
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 590
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 591 static int relay_handle_failure(struct xe_guc_relay *relay, u32 origin,
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 592 u32 rid, const u32 *msg, u32 len)
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 593 {
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 594 int error = FIELD_GET(GUC_HXG_FAILURE_MSG_0_ERROR, msg[0]);
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 595 u32 hint __maybe_unused = FIELD_GET(GUC_HXG_FAILURE_MSG_0_HINT, msg[0]);
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 596
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 597 relay_assert(relay, len);
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 @598 relay_debug(relay, "%u.%u error %#x (%pe) hint %u debug %*ph\n",
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 599 origin, rid, error, ERR_PTR(-error), hint, 4 * (len - 1), msg + 1);
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 600
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 601 return relay_handle_reply(relay, origin, rid, error ?: -EREMOTEIO, NULL, 0);
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 602 }
811fe9f556fcb28 Michal Wajdeczko 2024-01-04 603
:::::: The code at line 598 was first introduced by commit
:::::: 811fe9f556fcb281ea2db1b0fff3bab20f0a4d42 drm/xe/guc: Introduce Relay Communication for SR-IOV
:::::: TO: Michal Wajdeczko <michal.wajdeczko@intel.com>
:::::: CC: Michal Wajdeczko <michal.wajdeczko@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-12-14 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 18:11 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-09 22:24 drivers/gpu/drm/xe/xe_guc_relay.c:598 relay_handle_failure() warn: passing zero to 'ERR_PTR' 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=202412150254.vl3tkK75-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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.