From: Greg KH <gregkh@linuxfoundation.org>
To: Kang Wenlin <wenlin.kang@windriver.com>
Cc: regkh@linuxfoundation.org, stable@vger.kernel.org,
viro@zeniv.linux.org.uk, ebiederm@xmission.com,
keescook@chromium.org, akpm@linux-foundation.org
Subject: Re: [PATCH 6.1.y 6/7] binfmt_elf: Only report padzero() errors when PROT_WRITE
Date: Tue, 1 Apr 2025 10:58:04 +0100 [thread overview]
Message-ID: <2025040101-riverbank-kilt-459b@gregkh> (raw)
In-Reply-To: <20250324071942.2553928-7-wenlin.kang@windriver.com>
On Mon, Mar 24, 2025 at 03:19:41PM +0800, Kang Wenlin wrote:
> From: Kees Cook <keescook@chromium.org>
>
> commit f9c0a39d95301a36baacfd3495374c6128d662fa upstream
We obviously can not take a patch for 6.1.y that is not already in
6.6.y, right? Otherwise when you upgrade to the newer version you will
have a regression.
Please fix this up by sending the newer kernel backports first, and
then, if they are accepted, send the older ones. As it is, we can't
take this series at all, sorry.
greg k-h
next prev parent reply other threads:[~2025-04-01 9:59 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
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 [this message]
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=2025040101-riverbank-kilt-459b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=regkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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.