public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Kang Wenlin <wenlin.kang@windriver.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y 2/7] binfmt_elf: Support segments with 0 filesz and misaligned starts
Date: Tue, 25 Mar 2025 07:38:12 -0400	[thread overview]
Message-ID: <20250324220941-eede19a4ec65505d@stable.kernel.org> (raw)
In-Reply-To: <20250324071942.2553928-3-wenlin.kang@windriver.com>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 585a018627b4d7ed37387211f667916840b5c5ea

WARNING: Author mismatch between patch and upstream commit:
Backport author: Kang Wenlin<wenlin.kang@windriver.com>
Commit author: Eric W. Biederman<ebiederm@xmission.com>

Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Not found

Note: The patch differs from the upstream commit:
---
1:  585a018627b4d ! 1:  f14beae673802 binfmt_elf: Support segments with 0 filesz and misaligned starts
    @@ Metadata
      ## Commit message ##
         binfmt_elf: Support segments with 0 filesz and misaligned starts
     
    +    commit 585a018627b4d7ed37387211f667916840b5c5ea upstream
    +
         Implement a helper elf_load() that wraps elf_map() and performs all
         of the necessary work to ensure that when "memsz > filesz" the bytes
         described by "memsz > filesz" are zeroed.
    @@ Commit message
         Signed-off-by: Sebastian Ott <sebott@redhat.com>
         Link: https://lore.kernel.org/r/20230929032435.2391507-1-keescook@chromium.org
         Signed-off-by: Kees Cook <keescook@chromium.org>
    +    Signed-off-by: Wenlin Kang <wenlin.kang@windriver.com>
     
      ## fs/binfmt_elf.c ##
     @@ fs/binfmt_elf.c: static struct linux_binfmt elf_format = {
    @@ fs/binfmt_elf.c: static int load_elf_binary(struct linux_binprm *bprm)
      
     -		if (unlikely (elf_brk > elf_bss)) {
     -			unsigned long nbyte;
    --
    +-	            
     -			/* There was a PT_LOAD segment with p_memsz > p_filesz
     -			   before this one. Map anonymous pages, if needed,
     -			   and clear the area.  */
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y        |  Success    |  Success   |

  reply	other threads:[~2025-03-25 11:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-24  7:19 [PATCH 6.1.y 0/7] Backported patches to fix selftest tpdir2 Kang Wenlin
2025-03-24  7:19 ` [PATCH 6.1.y 1/7] binfmt_elf: replace IS_ERR() with IS_ERR_VALUE() Kang Wenlin
2025-03-25 11:33   ` Sasha Levin
2025-03-24  7:19 ` [PATCH 6.1.y 2/7] binfmt_elf: Support segments with 0 filesz and misaligned starts Kang Wenlin
2025-03-25 11:38   ` Sasha Levin [this message]
2025-03-24  7:19 ` [PATCH 6.1.y 3/7] binfmt_elf: elf_bss no longer used by load_elf_binary() Kang Wenlin
2025-03-25 11:33   ` Sasha Levin
2025-03-24  7:19 ` [PATCH 6.1.y 4/7] binfmt_elf: Use elf_load() for interpreter Kang Wenlin
2025-03-25 11:33   ` Sasha Levin
2025-03-24  7:19 ` [PATCH 6.1.y 5/7] binfmt_elf: Use elf_load() for library Kang Wenlin
2025-03-25 11:38   ` Sasha Levin
2025-03-24  7:19 ` [PATCH 6.1.y 6/7] binfmt_elf: Only report padzero() errors when PROT_WRITE Kang Wenlin
2025-03-25 11:33   ` Sasha Levin
2025-04-01  9:58   ` Greg KH
2025-04-02  3:00     ` Wenlin Kang
2025-03-24  7:19 ` [PATCH 6.1.y 7/7] mm: Remove unused vm_brk() Kang Wenlin
2025-03-25 11:33   ` Sasha Levin
     [not found] ` <DS0PR11MB6325BD9BB3C4B176CADD0472E1AC2@DS0PR11MB6325.namprd11.prod.outlook.com>
2025-04-01  6:58   ` [PATCH 6.1.y 0/7] Backported patches to fix selftest tpdir2 gregkh

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=20250324220941-eede19a4ec65505d@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=wenlin.kang@windriver.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