From: Kees Cook <keescook@chromium.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: {standard input}:24403: Error: Insn slot not set in unwind record.
Date: Fri, 21 Oct 2022 09:13:29 -0700 [thread overview]
Message-ID: <202210210913.11F9095@keescook> (raw)
In-Reply-To: <202210211348.RQ11yRji-lkp@intel.com>
On Fri, Oct 21, 2022 at 01:32:16PM +0800, kernel test robot wrote:
> Hi Kees,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: aae703b02f92bde9264366c545e87cec451de471
> commit: a82adfd5c7cb4b8bb37ef439aed954f9972bb618 hardening: Introduce CONFIG_ZERO_CALL_USED_REGS
> date: 1 year, 3 months ago
> config: ia64-randconfig-r024-20221020
> compiler: ia64-linux-gcc (GCC) 12.1.0
This feature isn't supported on ia64 -- I don't see how this commit
could be causing the warnings.
--
Kees Cook
next prev parent reply other threads:[~2022-10-21 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 5:32 {standard input}:24403: Error: Insn slot not set in unwind record kernel test robot
2022-10-21 16:13 ` Kees Cook [this message]
2022-10-25 0:52 ` [kbuild-all] " Chen, Rong A
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=202210210913.11F9095@keescook \
--to=keescook@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@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