From: Kees Cook <kees@kernel.org>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
Cc: kernel test robot <lkp@intel.com>,
linux-hardening@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, tony.luck@intel.com,
kernel-dev@igalia.com, kernel@gpiccoli.net,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] pstore/ftrace: Factor KASLR offset in the core kernel instruction addresses
Date: Thu, 9 Apr 2026 09:31:20 -0700 [thread overview]
Message-ID: <202604090930.6FAF3E5A@keescook> (raw)
In-Reply-To: <202604051301.skV8JLnH-lkp@intel.com>
On Tue, Apr 07, 2026 at 11:58:56AM +0800, kernel test robot wrote:
> Hi Guilherme,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on kees/for-next/pstore]
> [also build test ERROR on kees/for-next/kspp linus/master v7.0-rc6 next-20260403]
> [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/Guilherme-G-Piccoli/pstore-ftrace-Factor-KASLR-offset-in-the-core-kernel-instruction-addresses/20260315-152241
> base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/pstore
> patch link: https://lore.kernel.org/r/20260313201010.1622406-3-gpiccoli%40igalia.com
> patch subject: [PATCH] pstore/ftrace: Factor KASLR offset in the core kernel instruction addresses
> config: parisc-allmodconfig (https://download.01.org/0day-ci/archive/20260405/202604051301.skV8JLnH-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 15.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260405/202604051301.skV8JLnH-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/202604051301.skV8JLnH-lkp@intel.com/
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
> >> ERROR: modpost: "core_kernel_text" [fs/pstore/pstore.ko] undefined!
Oops, doing a modular PSTORE build shows this error even with v2. I've dropped the
patch from the tree for now.
-Kees
--
Kees Cook
next prev parent reply other threads:[~2026-04-09 16:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 20:00 [PATCH] pstore/ftrace: Factor KASLR offset in the core kernel instruction addresses Guilherme G. Piccoli
2026-03-13 20:22 ` Guilherme G. Piccoli
2026-03-13 20:28 ` Steven Rostedt
2026-03-13 20:57 ` Guilherme G. Piccoli
2026-03-15 14:09 ` Steven Rostedt
2026-03-15 15:02 ` Guilherme G. Piccoli
2026-03-28 21:47 ` Guilherme G. Piccoli
2026-03-31 21:48 ` Kees Cook
2026-04-01 22:28 ` Guilherme G. Piccoli
2026-04-09 16:13 ` Guilherme G. Piccoli
2026-04-07 3:58 ` kernel test robot
2026-04-09 16:31 ` Kees Cook [this message]
2026-04-09 18:57 ` Guilherme G. Piccoli
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=202604090930.6FAF3E5A@keescook \
--to=kees@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=tony.luck@intel.com \
/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