From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hugh Dickins <hughd@google.com>
Cc: Nick Hu <nickhu@andestech.com>, Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>,
iLifetruth <yixiaonn@gmail.com>, Michal Hocko <mhocko@suse.com>,
Qiang Liu <cyruscyliu@gmail.com>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] nds32: fix up stack guard gap
Date: Wed, 30 Jun 2021 11:04:50 +0200 [thread overview]
Message-ID: <YNwzsi3GHRBppvlo@kroah.com> (raw)
In-Reply-To: <382e353f-7489-d8c8-5711-a2d99b0b7f0@google.com>
On Tue, Jun 29, 2021 at 01:33:14PM -0700, Hugh Dickins wrote:
> On Tue, 29 Jun 2021, Greg Kroah-Hartman wrote:
>
> > Commit 1be7107fbe18 ("mm: larger stack guard gap, between vmas") fixed
> > up almost all architectures to deal with the stack guard gap, but forgit
> > nds32.
> >
> > Resolve this by properly fixing up the nsd32's version of
> > arch_get_unmapped_area()
> >
> > Reported-by: iLifetruth <yixiaonn@gmail.com>
> > Cc: Nick Hu <nickhu@andestech.com>
> > Cc: Greentime Hu <green.hu@gmail.com>
> > Cc: Vincent Chen <deanbo422@gmail.com>
> > Cc: Michal Hocko <mhocko@suse.com>
> > Cc: Hugh Dickins <hughd@google.com>
> > Cc: Qiang Liu <cyruscyliu@gmail.com>
> > Cc: stable <stable@vger.kernel.org>
> > Fixes: 1be7107fbe18 ("mm: larger stack guard gap, between vmas")
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> Acked-by: Hugh Dickins <hughd@google.com>
>
> but it's a bit unfair to say that commit forgot nds32:
> nds32 came into the tree nearly a year later.
Ah, missed that. I will change the text to say that.
greg k-h
prev parent reply other threads:[~2021-06-30 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 10:40 [PATCH] nds32: fix up stack guard gap Greg Kroah-Hartman
2021-06-29 20:33 ` Hugh Dickins
2021-06-30 2:33 ` Qiang Liu
2021-06-30 9:05 ` Greg Kroah-Hartman
2021-06-30 9:04 ` Greg Kroah-Hartman [this message]
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=YNwzsi3GHRBppvlo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cyruscyliu@gmail.com \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=hughd@google.com \
--cc=mhocko@suse.com \
--cc=nickhu@andestech.com \
--cc=stable@vger.kernel.org \
--cc=yixiaonn@gmail.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