lkml.org 
[lkml]   [2006]   [Jun]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 2.6.17-rc6 7/9] Remove some of the kmemleak false positives
On 13/06/06, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On 13/06/06, Pekka J Enberg <penberg@cs.helsinki.fi> wrote:
> > > As far as I understood, Ingo is worried about:
> > >
> > > struct s { /* some fields */; char *buf; };
> > >
> > > struct s *p = kmalloc(sizeof(struct s) + BUF_SIZE);
> > > p->buf = p + sizeof(struct s);
> > >
> > > Which could lead to false negative due to p->buf pointing to p. However,
> > > for us to even _find_ p->buf, we would need an incoming pointer _to_ p
> > > which makes me think this is not a problem in practice. Hmm?
>
> On 6/13/06, Catalin Marinas <catalin.marinas@gmail.com> wrote:
> > Not exactly. In the above case, Ingo (and me) is worried about having
> > a incoming pointer (from other block) equal to p->buf and therefore
> > inside the block allocated with kmalloc.
>
> Ah, right, I overlooked that case. But, is it really a leak? That is,
> even though we currently don't have a pointer to the beginning fo the
> block, we don't know for sure it was a leak. You're now allowed to do:
>
> p = kmalloc(...);
> p = p + HDR_SIZE;
>
> /* ... */
>
> kfree(p - HDR_SIZE);
>
> Do you think we should ban the above?

I don't think you can ban this because of places where the structure
needs to be aligned to a certain value. Look in the false positives
patch for the memleak_padding() calls with the 2nd argument not zero.

--
Catalin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-06-13 12:40    [W:0.074 / U:1.224 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site