This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 1 and 2
Revision 1 as of 2006-03-08 02:06:59
Size: 2203
Editor: 58
Comment: Information about canary and guard pages in Ethereal
Revision 2 as of 2006-03-08 02:13:02
Size: 2244
Editor: 58
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
In order to help detect memory over- and under-flows in (se_ and ep_) allocated memory, Ethereal now places canary values (e.g., a gap or no-mans-land) after each allocation. When the memory is later freed, the canary values are checked to make sure that they haven't been changed. If they have, then someone has written past the memory that they allocated. See also [http://gcc.fyxm.net/summit/2003/Stackguard.pdf stackguard]. In order to help detect memory over- and under-flows in ([http://wiki.ethereal.com/EMEMification se_ and ep_]) allocated memory, Ethereal now places canary values (e.g., a gap or no-mans-land) after each allocation. When the memory is later freed, the canary values are checked to make sure that they haven't been changed. If they have, then someone has written past the memory that they allocated. See also [http://gcc.fyxm.net/summit/2003/Stackguard.pdf stackguard].

Canary and Guard Pages in Ethereal

In order to help detect memory over- and under-flows in ([http://wiki.ethereal.com/EMEMification se_ and ep_]) allocated memory, Ethereal now places canary values (e.g., a gap or no-mans-land) after each allocation. When the memory is later freed, the canary values are checked to make sure that they haven't been changed. If they have, then someone has written past the memory that they allocated. See also [http://gcc.fyxm.net/summit/2003/Stackguard.pdf stackguard].

In addition, guard pages are placed before and after each block of memory. These are entire pages of memory that are mprotect()'d against writes so that if the page is written to (because someone went way beyond the end of their allocated memory), Ethereal will get a memory access violation (and hopefully dump core for post-mortem analysis).

With the guard pages in place, memory allocations now look like:

  +----+--------+---+--------+---+--------+---+-------+----+
  | gp | alloc1 | c | alloc2 | c | alloc3 | c |  ...  | gp |
  +----+--------+---+--------+---+--------+---+-------+----+

("gp" = guard page, "allocn" = allocated memory, "c" = canary).

What should I do if Ethereal detects such a canary violation?

If Ethereal exits stating "Per-packet memory corrupted." and exits (possibly leaving a core file (on *NIX, anyway) that points to epan/emem.c around line 600), then Ethereal detected a canary violation. If you're not a developer, you're not compiling Ethereal yourself, or you don't have the time to debug the issue yourself, please [http://bugs.ethereal.com open a bug] and attach a (preferrably small) capture file that exhibits the problem.

If you can debug the issue yourself, the best thing to do (again, on Linux, anyway) is to:

  • first update your source to see if the bug has already been fixed :-)

  • in epan/emem.c, uncomment the #defines of EP_DEBUG_FREE and SE_DEBUG_FREE
  • recompile
  • run ethereal/tethereal under [http://www.valgrind.org Valgrind]

    • unless you did a make install (to get the libtool stuff out of the way), this probably means doing something like:
      • valgrind .libs/lt-tethereal -Vnxr /some/file

Development/Canary (last edited 2008-09-25 13:19:42 by JeffMorriss)