Re: evecv/memory leak
- From: "bill pursell" <bill.pursell@xxxxxxxxx>
- Date: 6 Jan 2006 10:55:27 -0800
Kasper Dupont wrote:
> bill pursell wrote:
> >
> > I am (with extreme reluctance) using a 3rd party kernel module that I
> > do not trust.
> [...]
> >
> > I was thinking of replacing clean_up() with an exec that simply
> > calls itself. ie, the program will now look like:
> > int
> > main(int ac, char **av)
> > {
> > process_stuff();
> > execv(av[0],av);
> > }
>
> You seem to be mixing up kernel and user code.
> So which is it?
>>From user-space, I'm calling into a library which is
part of a kernel module. I have tried using the supplied free*
calls with no success, and was fairly regularly
getting a kernel panic. Instead of trying to use the supplied
free() calls, I figured it would be safer to shut down
the process and restart, and that actually seems to have
worked. I followed David Schwartz's suggestion and
did a full fork, and I haven't had the problem since.
thanks to everyone for the suggestions.
.
- Prev by Date: Re: how to get the file name
- Next by Date: Re: how to get the file name
- Previous by thread: how to get the file name
- Next by thread: Re: evecv/memory leak
- Index(es):
Relevant Pages
|
