Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] patch for memory overrun on Linux(i386)

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Maurice Gittens <mgittens(at)david(dot)gits(dot)nl>
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] patch for memory overrun on Linux(i386)
Date: 1998-03-21 23:55:39
Message-ID: Pine.BSF.3.96.980321195410.324A-100000@thelab.hub.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Some things just require confirmation...can someone else (Thomas?) running
Linux comment on this before I apply it?  I just find it kinda unexpected
to see something that doesn't work for SCO doesn't work for Linux too :)

On Sat, 21 Mar 1998, Maurice Gittens wrote:

> Hi,
> 
> It turns of that one of the bugs I detected with Electric Fence
> is caused by an assumption that memory return by palloc and malloc 
> is aligned on 8 bytes boundaries (double alignment). 
> Adjusting this to correspond with the reality of the malloc
> implementation on my pentium based linux box fixes the problem.
> 
> The following simple patch to include/utils/memutils.h
> will fix the problem.
> 
> 85c85
> < #if ! defined(sco)
> ---
> > #if ! defined(sco) && !defined(linux)
> 
> There is still another buffer overrun which I will try to find. 
> The remaining one is triggered by creating a sequence.
> 
> I hope this patch will be applied if it makes sense to 
> you guys.
> 
> With regards from Maurice.
> 
> 

Marc G. Fournier                                
Systems Administrator @ hub.org 
primary: scrappy(at)hub(dot)org           secondary: scrappy(at){freebsd|postgresql}.org 


In response to

Responses

pgsql-hackers by date

Next:From: ocieDate: 1998-03-22 00:37:34
Subject: Re: [HACKERS] patch for memory overrun on Linux(i386)
Previous:From: Hannu KrosingDate: 1998-03-21 19:58:56
Subject: Re: expr ? trueval : falseval

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group