All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: network support : memory management problem
Date: Wed, 1 Jun 2005 00:56:30 +0200	[thread overview]
Message-ID: <200506010056.30654.okuji@enbug.org> (raw)
In-Reply-To: <429C6B12.4080608@inma.ucl.ac.be>

On Tuesday 31 May 2005 15:48, Vincent Guffens wrote:
> but depending on where in the code I free my data blocks, I sometimes
> get a  "free magic is broken" fatal error msg from grub_free().

Usually, it is due to a buffer overrun or underrun.

> Does someone has an idea ? Is there some documentation available about
> the mm in grub2 ?

It is a typical (simple) malloc implementation. You can look at any textbook 
or web site about heap management to get ideas. The extensions are to always 
use magic to detect overrun / underrun, and to support multiple 
non-contiguous free regions. Have a look at the code. It is very small.

Okuji



      parent reply	other threads:[~2005-05-31 23:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 13:48 network support : memory management problem Vincent Guffens
2005-05-31 16:45 ` Vincent Guffens
2005-05-31 17:08   ` Marco Gerards
2005-06-06 10:03     ` Vincent Guffens
2005-06-08 19:38       ` Marco Gerards
2005-06-09 23:09         ` Vincent Guffens
2005-06-12  8:54           ` Scripting and keystrokes Serbinenko Vladimir
2005-06-13 18:09             ` Serbinenko Vladimir
2005-06-13 18:52               ` Yoshinori K. Okuji
2005-06-13 19:39                 ` Serbinenko Vladimir
2005-06-13 18:50             ` Yoshinori K. Okuji
2005-06-13 19:47               ` Serbinenko Vladimir
2005-05-31 22:56 ` Yoshinori K. Okuji [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=200506010056.30654.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.