From: Greg KH <gregkh@linuxfoundation.org>
To: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
Cc: stable@vger.kernel.org, sashal@kernel.org
Subject: Re: [RFC/PATCH 0/2] Backports CVE-2021-21781 for 4.4 and 4.9
Date: Fri, 30 Jul 2021 08:36:29 +0200 [thread overview]
Message-ID: <YQOd7bjtdgrTmoSd@kroah.com> (raw)
In-Reply-To: <20210730060805.342577-1-nobuhiro1.iwamatsu@toshiba.co.jp>
On Fri, Jul 30, 2021 at 03:08:03PM +0900, Nobuhiro Iwamatsu wrote:
> Hi,
>
> This is a patch series to CVE-2021-21781.
> The patch 9c698bff66ab ("RM: ensure the signal page contains defined
> contents") depepds on memset32. However, this function is not provided
> in 4.4 and 4.9. Therefore, we need the patch 3b3c4babd898 ("lib/string.c:
> add multibyte memset functions") to apply this feature.
> Another option is to implement only the memset32 function in
> arch/arm/kernel/signal.c only or using loop memset, but for simplicity
> we have taken the way of applying the original patch 3b3c4babd898
> ("lib/string.c: add multibyte memset functions") that provides memset32
> in mainline kernel.
All now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2021-07-30 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 6:08 [RFC/PATCH 0/2] Backports CVE-2021-21781 for 4.4 and 4.9 Nobuhiro Iwamatsu
2021-07-30 6:08 ` [PATCH 1/2 for 4.4 and 4.9] lib/string.c: add multibyte memset functions Nobuhiro Iwamatsu
2021-07-30 6:08 ` [PATCH 2/2 for 4.4, 4.9] ARM: ensure the signal page contains defined contents Nobuhiro Iwamatsu
2021-07-30 6:27 ` [RFC/PATCH 0/2] Backports CVE-2021-21781 for 4.4 and 4.9 Greg KH
2021-07-30 6:28 ` Greg KH
2021-07-30 6:36 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-30 6:06 Nobuhiro Iwamatsu
2021-07-30 6:05 Nobuhiro Iwamatsu
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=YQOd7bjtdgrTmoSd@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=sashal@kernel.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