From: John David Anglin <dave.anglin@bell.net>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
Mike Frysinger <vapier@gentoo.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Helge Deller <deller@gmx.de>
Subject: Re: [PATCH] Fix stack memory protection on targets where the stack grows upward
Date: Mon, 17 Apr 2017 11:58:00 -0000 [thread overview]
Message-ID: <B29193E6-CF6A-45ED-BF94-05E0E1321FA0@bell.net> (raw)
In-Reply-To: <87d1cbh67a.fsf@mid.deneb.enyo.de>
On 2017-04-17, at 2:57 AM, Florian Weimer wrote:
> * John David Anglin:
>
>> On 2017-04-16, at 5:27 PM, Florian Weimer wrote:
>>
>>> This is essentially HPPA-specific code, right? So I guess we can do
>>> whatever it takes there.
>>
>> I believe the metag architecture also has a stack that grows up.
>
> I'm sure there are others, but HPPA is the only one with a glibc port.
Correct.
--
John David Anglin dave.anglin@bell.net
prev parent reply other threads:[~2017-04-17 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 17:20 John David Anglin
2017-04-16 20:06 ` Andreas Schwab
2017-04-17 12:13 ` [PATCH v2] " John David Anglin
2017-04-16 21:27 ` [PATCH] " Florian Weimer
2017-04-16 23:03 ` John David Anglin
2017-04-17 6:57 ` Florian Weimer
2017-04-17 11:58 ` John David Anglin [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=B29193E6-CF6A-45ED-BF94-05E0E1321FA0@bell.net \
--to=dave.anglin@bell.net \
--cc=aurelien@aurel32.net \
--cc=carlos@redhat.com \
--cc=deller@gmx.de \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).