From: imran.f.khan@oracle.com
To: kernel test robot <lkp@intel.com>,
vbabka@suse.cz, geert@linux-m68k.org, akpm@linux-foundation.org,
ryabinin.a.a@gmail.com, glider@google.com, andreyknvl@gmail.com,
dvyukov@google.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [PATCH RESEND v2 3/3] lib, stackdepot: Add helper to print stack entries into buffer.
Date: Fri, 17 Sep 2021 01:07:16 +1000 [thread overview]
Message-ID: <c86765b6-8971-6438-e802-dd85772608fb@oracle.com> (raw)
In-Reply-To: <202109162023.62zhNLls-lkp@intel.com>
Hi,
On 16/9/21 10:56 pm, kernel test robot wrote:
> Hi Imran,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on drm-intel/for-linux-next]
> [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://urldefense.com/v3/__https://git-scm.com/docs/git-format-patch__;!!ACWV5N9M2RV99hQ!ZgH7pHrcDP0Zs9Uq1xBK5egXd0EEHO-U04nQ0t2s5Hu1XT_h4Pj3h55Q6CS4G75yKA$ ]
>
> url: https://urldefense.com/v3/__https://github.com/0day-ci/linux/commits/Imran-Khan/lib-stackdepot-check-stackdepot-handle-before-accessing-slabs/20210916-015617__;!!ACWV5N9M2RV99hQ!ZgH7pHrcDP0Zs9Uq1xBK5egXd0EEHO-U04nQ0t2s5Hu1XT_h4Pj3h55Q6CTQWVl4Fg$
> base: git://anongit.freedesktop.org/drm-intel for-linux-next
> config: hexagon-buildonly-randconfig-r006-20210916 (attached as .config)
> compiler: clang version 14.0.0 (https://urldefense.com/v3/__https://github.com/llvm/llvm-project__;!!ACWV5N9M2RV99hQ!ZgH7pHrcDP0Zs9Uq1xBK5egXd0EEHO-U04nQ0t2s5Hu1XT_h4Pj3h55Q6CRjvtK2Pg$ c8b3d7d6d6de37af68b2f379d0e37304f78e115f)
> reproduce (this is a W=1 build):
> wget https://urldefense.com/v3/__https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross__;!!ACWV5N9M2RV99hQ!ZgH7pHrcDP0Zs9Uq1xBK5egXd0EEHO-U04nQ0t2s5Hu1XT_h4Pj3h55Q6CSQGX0obw$ -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://urldefense.com/v3/__https://github.com/0day-ci/linux/commit/c457fdf0bd4d68953ccf968b9570d149ec178602__;!!ACWV5N9M2RV99hQ!ZgH7pHrcDP0Zs9Uq1xBK5egXd0EEHO-U04nQ0t2s5Hu1XT_h4Pj3h55Q6CQitEM8yg$
> git remote add linux-review https://urldefense.com/v3/__https://github.com/0day-ci/linux__;!!ACWV5N9M2RV99hQ!ZgH7pHrcDP0Zs9Uq1xBK5egXd0EEHO-U04nQ0t2s5Hu1XT_h4Pj3h55Q6CRApg1BIA$
> git fetch --no-tags linux-review Imran-Khan/lib-stackdepot-check-stackdepot-handle-before-accessing-slabs/20210916-015617
> git checkout c457fdf0bd4d68953ccf968b9570d149ec178602
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=hexagon
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
> ERROR: modpost: "__raw_writesl" [drivers/i3c/master/dw-i3c-master.ko] undefined!
> ERROR: modpost: "__raw_readsl" [drivers/i3c/master/dw-i3c-master.ko] undefined!
>>> ERROR: modpost: "stack_depot_snprint" [drivers/gpu/drm/drm_kms_helper.ko] undefined!
>
I got this error reported earlier [1] by another CI build system. I have
fixed this now and have sent a v3 [2] of the patchset. v3 contains fix
for this build error.
[1] https://patchwork.freedesktop.org/series/94696/#rev2
[2]
https://lore.kernel.org/lkml/20210916133535.3592491-1-imran.f.khan@oracle.com/
Thanks
-- Imran
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://urldefense.com/v3/__https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org__;!!ACWV5N9M2RV99hQ!ZgH7pHrcDP0Zs9Uq1xBK5egXd0EEHO-U04nQ0t2s5Hu1XT_h4Pj3h55Q6CSBYjBtkg$
>
prev parent reply other threads:[~2021-09-16 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210915175321.3472770-4-imran.f.khan@oracle.com>
2021-09-16 12:56 ` [PATCH RESEND v2 3/3] lib, stackdepot: Add helper to print stack entries into buffer kernel test robot
2021-09-16 15:07 ` imran.f.khan [this message]
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=c86765b6-8971-6438-e802-dd85772608fb@oracle.com \
--to=imran.f.khan@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=geert@linux-m68k.org \
--cc=glider@google.com \
--cc=kbuild-all@lists.01.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=tzimmermann@suse.de \
--cc=vbabka@suse.cz \
/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