From: Harshvardhan Jha <harshvardhan.j.jha@oracle.com>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.4.y 0/4] Backport fix of CVE-2024-47674 to 5.10
Date: Thu, 14 Nov 2024 21:21:16 +0530 [thread overview]
Message-ID: <de4226be-1b8f-4fdb-86ed-b9b077b839b1@oracle.com> (raw)
In-Reply-To: <20241114153443.505015-1-harshvardhan.j.jha@oracle.com>
Hi there,
On 14/11/24 9:04 PM, Harshvardhan Jha wrote:
> Following series is a backport of CVE-2024-47674 fix "mm: avoid leaving
> partial pfn mappings around in error case" to 5.10.
A small correction, the 5.10 here should be 5.4 and similarly on the
subject line also.
If you want I can send a v2 but I hope that's not necessary.
>
> This required 3 extra commits to make sure all picks were clean. The
> patchset shows no regression compared to v5.4.285 tag.
>
> Alex Zhang (1):
> mm/memory.c: make remap_pfn_range() reject unaligned addr
>
> Christoph Hellwig (1):
> mm: add remap_pfn_range_notrack
>
> WANG Wenhu (1):
> mm: clarify a confusing comment for remap_pfn_range()
>
> chenqiwu (1):
> mm: fix ambiguous comments for better code readability
>
> include/linux/mm.h | 2 ++
> include/linux/mm_types.h | 4 +--
> mm/memory.c | 54 +++++++++++++++++++++++++---------------
> 3 files changed, 38 insertions(+), 22 deletions(-)
>
Thanks & Regards,
Harshvardhan
next prev parent reply other threads:[~2024-11-14 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 15:34 Harshvardhan Jha
2024-11-14 15:34 ` [PATCH 5.4.y 1/4] mm: clarify a confusing comment for remap_pfn_range() Harshvardhan Jha
2024-11-14 15:34 ` [PATCH 5.4.y 2/4] mm: fix ambiguous comments for better code readability Harshvardhan Jha
2024-11-14 15:34 ` [PATCH 5.4.y 3/4] mm/memory.c: make remap_pfn_range() reject unaligned addr Harshvardhan Jha
2024-11-14 15:34 ` [PATCH 5.4.y 4/4] mm: add remap_pfn_range_notrack Harshvardhan Jha
2024-11-14 15:51 ` Harshvardhan Jha [this message]
2024-11-15 5:27 ` [PATCH 5.4.y 0/4] Backport fix of CVE-2024-47674 to 5.10 Greg KH
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=de4226be-1b8f-4fdb-86ed-b9b077b839b1@oracle.com \
--to=harshvardhan.j.jha@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox