From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] env: fix potential stack overflow in environment functions
Date: Fri, 22 Mar 2013 23:04:26 +0100 [thread overview]
Message-ID: <20130322220426.EF69A2014CE@gemini.denx.de> (raw)
In-Reply-To: <1363987581-28050-1-git-send-email-robherring2@gmail.com>
Dear Rob Herring,
In message <1363987581-28050-1-git-send-email-robherring2@gmail.com> you wrote:
>
> Most of the various environment functions create CONFIG_ENV_SIZE buffers on
> the stack. At least on ARM and PPC which have 4KB stacks, this can overflow
> the stack if we have large environment sizes. So move all the buffers off
> the stack to static buffers.
Could you please explain what exactly you mean with this "have 4KB
stacks" statement?
Also, why do you think there is more space for data then for stack?
Has this patch been tested on any actual hardware?
I would expect problems, as this code is running before relocation,
i. e. when the data segment is not writable?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
F u cn rd ths u cnt spl wrth a dm!
next prev parent reply other threads:[~2013-03-22 22:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 21:26 [U-Boot] [PATCH] env: fix potential stack overflow in environment functions Rob Herring
2013-03-22 22:04 ` Wolfgang Denk [this message]
2013-03-22 22:56 ` Rob Herring
2013-03-23 0:29 ` Wolfgang Denk
2013-04-03 15:30 ` [U-Boot] " Tom Rini
2013-04-05 11:17 ` Wolfgang Denk
2013-04-05 15:26 ` Rob Herring
2013-04-05 16:15 ` Wolfgang Denk
2013-04-05 16:21 ` Wolfgang Denk
2013-04-05 16:24 ` Wolfgang Denk
2013-04-05 16:40 ` Rob Herring
2013-04-05 17:13 ` Wolfgang Denk
2013-04-05 18:16 ` Rob Herring
2013-04-05 18:47 ` Wolfgang Denk
2013-04-05 23:17 ` Scott Wood
2013-04-06 7:06 ` Wolfgang Denk
2013-04-05 18:49 ` Tom Rini
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=20130322220426.EF69A2014CE@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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