From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 1/2] dlmalloc: fix malloc range at end of ram
Date: Wed, 24 Apr 2019 07:52:57 -0400 [thread overview]
Message-ID: <20190424115257.GF31207@bill-the-cat> (raw)
In-Reply-To: <CAAh8qswwVh8Cu6rxd83qWX9GYSBowWwaxLnSudrf5UYHWLFVUA@mail.gmail.com>
On Wed, Apr 24, 2019 at 01:49:52PM +0200, Simon Goldschmidt wrote:
> On Wed, Apr 24, 2019 at 1:27 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Tue, Apr 23, 2019 at 09:54:10PM -0600, Simon Glass wrote:
> > > On Mon, 1 Apr 2019 at 14:01, Simon Goldschmidt
> > > <simon.k.r.goldschmidt@gmail.com> wrote:
> > > >
> > > > If the malloc range passed to mem_malloc_init() is at the end of address
> > > > range and 'start + size' overflows to 0, following allocations fail as
> > > > mem_malloc_end is zero (which looks like uninitialized).
> > > >
> > > > Fix this by subtracting 1 of 'start + size' overflows to zero.
> > > >
> > > > Signed-off-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
> > > > ---
> > > >
> > > > Changes in v4: None
> > > > Changes in v3: None
> > > >
> > > > common/dlmalloc.c | 4 ++++
> > > > 1 file changed, 4 insertions(+)
> > >
> > > Reviewed-by: Simon Glass <sjg@chromium.org>
> >
> > So, the problem with this patch is that it increases the generic malloc
> > code size ever so slightly and blows up smartweb :(
>
> Ehrm, ok, so how do we proceed?
A good question. Take a look at spl/u-boot-spl.map on smartweb and see
if, of the malloc functions it doesn't discard there's something that
maybe could be optimized somewhere?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190424/998a9a69/attachment.sig>
next prev parent reply other threads:[~2019-04-24 11:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 20:01 [U-Boot] [PATCH v4 0/2] spl: full-featured heap cleanups Simon Goldschmidt
2019-04-01 20:01 ` [U-Boot] [PATCH v4 1/2] dlmalloc: fix malloc range at end of ram Simon Goldschmidt
2019-04-24 3:54 ` Simon Glass
2019-04-24 11:26 ` Tom Rini
2019-04-24 11:49 ` Simon Goldschmidt
2019-04-24 11:52 ` Tom Rini [this message]
2019-04-24 23:58 ` Simon Glass
2019-04-25 7:32 ` Simon Goldschmidt
2019-04-25 10:50 ` Tom Rini
2019-04-25 19:24 ` Simon Goldschmidt
2019-04-29 13:06 ` Heiko Schocher
2019-04-29 13:16 ` Simon Goldschmidt
2019-04-29 13:20 ` Tom Rini
2019-04-29 13:19 ` Tom Rini
2019-04-29 15:53 ` Simon Glass
2019-04-01 20:01 ` [U-Boot] [PATCH v4 2/2] dlmalloc: be compatible to tiny printf Simon Goldschmidt
2019-04-24 3:54 ` Simon Glass
2019-04-24 13:31 ` [U-Boot] [U-Boot, v4, " 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=20190424115257.GF31207@bill-the-cat \
--to=trini@konsulko.com \
--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