From: Max Filippov <jcmvbkbc@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: David Laight <David.Laight@aculab.com>,
Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chris Zankel <chris@zankel.net>
Subject: Re: [PATCH] xtensa: Increase size of gcc stack frame check
Date: Tue, 14 Sep 2021 10:24:14 -0700 [thread overview]
Message-ID: <CAMo8Bf+rFk_CJiUOdQC5yLuMT+y-awgS9MSx0g3-DqLXYEeX7w@mail.gmail.com> (raw)
In-Reply-To: <a34cac4a-dc17-acf0-f24e-69c06217adb6@roeck-us.net>
On Tue, Sep 14, 2021 at 7:02 AM Guenter Roeck <linux@roeck-us.net> wrote:
> I still don't think that those stack limit warnings (now errors)
> will ever get fixed. Which is the point I was trying to make,
> and your observation that the stack frames are really that large
> because of KASAN just makes that argument stronger.
>
> Other than that, it is not my call to make that to do with this
> patch. If you think that it is inappropriate, by all means
> reject it.
I like it, also for the reason that with KASAN enabled
kernel stack size on xtensa is 4 times bigger.
--
Thanks.
-- Max
prev parent reply other threads:[~2021-09-14 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 2:52 [PATCH] xtensa: Increase size of gcc stack frame check Guenter Roeck
2021-09-12 3:05 ` Max Filippov
2021-09-12 4:02 ` Guenter Roeck
2021-09-12 5:16 ` Max Filippov
2021-09-13 15:57 ` David Laight
2021-09-13 16:11 ` Guenter Roeck
2021-09-14 7:04 ` Max Filippov
2021-09-14 14:02 ` Guenter Roeck
2021-09-14 17:24 ` Max Filippov [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=CAMo8Bf+rFk_CJiUOdQC5yLuMT+y-awgS9MSx0g3-DqLXYEeX7w@mail.gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=chris@zankel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linux@roeck-us.net \
--cc=masahiroy@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;
as well as URLs for NNTP newsgroup(s).