mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>, <linux-kbuild@vger.kernel.org>
Subject: Re: [linus:master] [kconfig] f79dc03fe6: segfault_at_ip_sp_error
Date: Fri, 9 Aug 2024 09:12:49 +0800	[thread overview]
Message-ID: <ZrVtEbZjRYmCGS5t@xsang-OptiPlex-9020> (raw)
In-Reply-To: <CAK7LNARFuUHiEVDF3O-aFc+awXM5QdCUCUu5wqbTcZQgLLWsuA@mail.gmail.com>

hi, Masahiro Yamada,

On Thu, Aug 08, 2024 at 05:27:40PM +0900, Masahiro Yamada wrote:

[...]

> See this line in the error report:
> 
> [   15.209351][  T483] depmod[483]: segfault at 0 ip b7abe4f6 sp
> bfb00aa4 error 4 in libc-2.31.so[8c4f6,b7a4b000+155000] likely on CPU
> 0 (core 0, socket 0)
> 
> > > What is your depmod (kmod) version?
> >
> > our kmod version is 28
> 
> See this again:
> https://lore.kernel.org/linux-kbuild/E1rNVlL-000qDm-Pg@rmk-PC.armlinux.org.uk/
> 
> It clearly explains when the issue happens:
> 
>  When using the SHA3 module signing options, kmod 28 segfaults during
>  "make modules_install" on the build host.
> 
> If you are using kmod 28, upgrading it will presumably fix the issue.

thanks a lot for guidance! we will follow this.

> > >
> > > The crash of kmod<=28 with CONFIG_MODULE_SIG_SHA3_384=y is a known issue:
> > >
> > > https://lore.kernel.org/linux-kbuild/E1rNVlL-000qDm-Pg@rmk-PC.armlinux.org.uk/
> > >

      reply	other threads:[~2024-08-09  1:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06  8:21 kernel test robot
2024-08-06  8:57 ` Masahiro Yamada
2024-08-08  7:53   ` Oliver Sang
2024-08-08  8:27     ` Masahiro Yamada
2024-08-09  1:12       ` Oliver Sang [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=ZrVtEbZjRYmCGS5t@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=masahiroy@kernel.org \
    --cc=oe-lkp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®