Hi!
> >>From: Catalin Marinas <[email protected]>
> >>+ memleak_debug_not_leak(res);
> >
> > I'd suggest some shorter/more generic name.
> >
> > not_freed(res); ?
> >
> > alloc_forever(res); ?
>
> It's true that the names are a bit long ("debug" is even superfluous). I
> would, however, keep the memleak_ prefix as I think it makes the code
> clearer (i.e. the function belongs to a certain part of the kernel).
Well, in future some other leak detector may want to use these hooks.
Anyway memleak_not_leak() is already quite good.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
