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.6.y 5/6] binfmt_elf: Only report padzero() errors when PROT_WRITE
Date: Wed, 2 Apr 2025 17:25:03 -0400 [thread overview]
Message-ID: <20250402135512-c05d3309eed84a41@stable.kernel.org> (raw)
In-Reply-To: <20250402082656.4177277-6-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: f9c0a39d95301a36baacfd3495374c6128d662fa
WARNING: Author mismatch between patch and upstream commit:
Backport author: Kang Wenlin<wenlin.kang@windriver.com>
Commit author: Kees Cook<keescook@chromium.org>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
1: f9c0a39d95301 ! 1: d7251c2864622 binfmt_elf: Only report padzero() errors when PROT_WRITE
@@ Metadata
## Commit message ##
binfmt_elf: Only report padzero() errors when PROT_WRITE
+ commit f9c0a39d95301a36baacfd3495374c6128d662fa upstream
+
Errors with padzero() should be caught unless we're expecting a
pathological (non-writable) segment. Report -EFAULT only when PROT_WRITE
is present.
@@ Commit message
Signed-off-by: Sebastian Ott <sebott@redhat.com>
Link: https://lore.kernel.org/r/20230929032435.2391507-5-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 = {
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
next prev parent reply other threads:[~2025-04-02 21:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 8:26 [PATCH 6.6.y 0/6] Backported patches to fix selftest tpdir2 Kang Wenlin
2025-04-02 8:26 ` [PATCH 6.6.y 1/6] binfmt_elf: Support segments with 0 filesz and misaligned starts Kang Wenlin
2025-04-02 21:25 ` Sasha Levin
2025-04-02 8:26 ` [PATCH 6.6.y 2/6] binfmt_elf: elf_bss no longer used by load_elf_binary() Kang Wenlin
2025-04-02 21:25 ` Sasha Levin
2025-04-02 8:26 ` [PATCH 6.6.y 3/6] binfmt_elf: Use elf_load() for interpreter Kang Wenlin
2025-04-02 21:25 ` Sasha Levin
2025-04-02 8:26 ` [PATCH 6.6.y 4/6] binfmt_elf: Use elf_load() for library Kang Wenlin
2025-04-02 21:25 ` Sasha Levin
2025-04-02 8:26 ` [PATCH 6.6.y 5/6] binfmt_elf: Only report padzero() errors when PROT_WRITE Kang Wenlin
2025-04-02 21:25 ` Sasha Levin [this message]
2025-04-02 8:26 ` [PATCH 6.6.y 6/6] mm: Remove unused vm_brk() Kang Wenlin
2025-04-02 21:25 ` Sasha Levin
2025-04-03 14:52 ` [PATCH 6.6.y 0/6] Backported patches to fix selftest tpdir2 Greg KH
2025-04-04 7:58 ` Kang Wenlin
2025-04-08 9:06 ` Greg KH
2025-04-08 9:50 ` Wenlin Kang
2025-04-08 9:55 ` Greg KH
2025-04-08 14:39 ` Kang Wenlin
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=20250402135512-c05d3309eed84a41@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 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.