mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jessica Yu <jeyu@kernel.org>,
	mcgrof@kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Modules updates for v5.16-rc1
Date: Fri, 5 Nov 2021 15:33:46 -0700	[thread overview]
Message-ID: <YYWxSlB1CNhhjUTQ@bombadil.infradead.org> (raw)

Hi Linus,

As requested by Jessica, I'm stepping in to help with modules
maintenance. This is my my first pull request, so if there are any
issues with it please let me know so I can fix things for the next
time around to make it even smoother for you.

Nothing exciting here, except a warning enhancement and a fix for
insanely large modules.

Thank you,

  Luis

The following changes since commit 7fd982f394c42f25a73fe9dfbf1e6b11fa26b40a:

  module: change to print useful messages from elf_validity_check() (2021-11-05 15:13:10 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/ tags/modules-5.16-rc1

for you to fetch changes up to 7fd982f394c42f25a73fe9dfbf1e6b11fa26b40a:

  module: change to print useful messages from elf_validity_check() (2021-11-05 15:13:10 -0700)

----------------------------------------------------------------
modules patches for 5.16-rc1

As requested by Jessica I'm stepping in to help with modules
maintenance. This is my first pull request to you.

I've collected only two patches for modules for the 5.16-rc1 merge
window. These patches are from Shuah Khan as she debugged some corner
case error with modules. The error messages are improved for
elf_validity_check(). While doing this work a corner case fix was
spotted on validate_section_offset() due to a possible overflow bug
on 64-bit. The impact of this fix is low given this just limits
module section headers placed within the 32-bit boundary, and we
obviously don't have insane module sizes. Even if a specially crafted
module is constructed later checks would invalidate the module right
away.

I've let this sit through 0-day testing since October 15th with no
issues found.

Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>

----------------------------------------------------------------

             reply	other threads:[~2021-11-05 22:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 22:33 Luis Chamberlain [this message]
2021-11-07 19:08 ` Linus Torvalds
2021-11-08 16:05   ` Luis Chamberlain
2021-11-08 17:07     ` Linus Torvalds
2021-11-08 23:27       ` Luis Chamberlain
2021-11-08 17:39 ` pr-tracker-bot

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=YYWxSlB1CNhhjUTQ@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=jeyu@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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®