All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Eliyam Levy <eliyamlevy@gmail.com>
Cc: linux-modules@vger.kernel.org, linux-newbie@vger.kernel.org
Subject: Re: INVALID ELF STRUCTURES
Date: Tue, 21 Dec 2021 13:44:54 -0800	[thread overview]
Message-ID: <YcJK1rPwQVu/pX+S@bombadil.infradead.org> (raw)
In-Reply-To: <CAD9KO1=gjhe1sc3MNyc3QawQgJAgwptFgsTZE903PCi3_DEyPg@mail.gmail.com>

On Tue, Dec 21, 2021 at 11:54:09AM -0500, Eliyam Levy wrote:
> Hi,
> 
> I'm on Ubuntu 20.04 with kernel version 5.11 and I keep hitting the
> "Module has invalid ELF structures" error on a kernel module I'm
> building. I know this is related to the "harden ELF info handling"
> patch that was introduced. Are there any useful ways to debug this? Is
> there anything I should be mindful of when building the kernel module
> to avoid this?

Look for the already merged patch, "module: change to print useful
messages from elf_validity_check()".

$ git describe --contains 7fd982f394c42f25a73fe9dfbf1e6b11fa26b40a
v5.16-rc1~95^2    

  Luis

WARNING: multiple messages have this Message-ID (diff)
From: Luis Chamberlain <mcgrof-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Eliyam Levy <eliyamlevy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-modules-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-newbie-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: INVALID ELF STRUCTURES
Date: Tue, 21 Dec 2021 13:44:54 -0800	[thread overview]
Message-ID: <YcJK1rPwQVu/pX+S@bombadil.infradead.org> (raw)
In-Reply-To: <CAD9KO1=gjhe1sc3MNyc3QawQgJAgwptFgsTZE903PCi3_DEyPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Tue, Dec 21, 2021 at 11:54:09AM -0500, Eliyam Levy wrote:
> Hi,
> 
> I'm on Ubuntu 20.04 with kernel version 5.11 and I keep hitting the
> "Module has invalid ELF structures" error on a kernel module I'm
> building. I know this is related to the "harden ELF info handling"
> patch that was introduced. Are there any useful ways to debug this? Is
> there anything I should be mindful of when building the kernel module
> to avoid this?

Look for the already merged patch, "module: change to print useful
messages from elf_validity_check()".

$ git describe --contains 7fd982f394c42f25a73fe9dfbf1e6b11fa26b40a
v5.16-rc1~95^2    

  Luis

  reply	other threads:[~2021-12-21 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 16:54 INVALID ELF STRUCTURES Eliyam Levy
2021-12-21 16:54 ` Eliyam Levy
2021-12-21 21:44 ` Luis Chamberlain [this message]
2021-12-21 21:44   ` Luis Chamberlain

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=YcJK1rPwQVu/pX+S@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=eliyamlevy@gmail.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux-newbie@vger.kernel.org \
    /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.