RE: memory leak in call_usermodehelper()
From: Srikumar Subramanian (SrikumarS_at_ami.com)
Date: 12/31/03
- Previous message: René Scharfe: "Re: File change notification"
- Maybe in reply to: Srikumar Subramanian: "memory leak in call_usermodehelper()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: "'arjanv@redhat.com'" <arjanv@redhat.com>, Srikumar Subramanian <SrikumarS@ami.com> Date: Wed, 31 Dec 2003 14:43:18 -0500
Basically, I am not intended to have my own syscall.
I am generating a report on all deleted file and directory. For that I
trapped sys_unlink() function and calling a external program using
call_usermodehelper(). Since sys_unlink() is called very frequently in my
case, memory leak caused by calling call_usermodehelper kills all the
process in the system.
Just to narrow down the problem, I introduced my own syscall.
-----Original Message-----
From: Arjan van de Ven [mailto:arjanv@redhat.com]
Sent: Wednesday, December 31, 2003 7:13 AM
To: Srikumar Subramanian
Cc: 'Andrew Morton'; 'linux-kernel@vger.kernel.org'; Boopathi Veerappan
Subject: RE: memory leak in call_usermodehelper()
On Wed, 2003-12-31 at 06:22, Srikumar Subramanian wrote:
>
> Is there any alternative to call_usermodehelper in kernel 2.4.20?
>
most of all don't implement your own syscalls!
> Hi,
> I am using 2.4.20-8 Redhat 9 kernel.
>
well clearly not quite since you're adding syscalls to it.
Also 2.4.20-8 isn't the current Red Hat Linux 9 kernel; 2.4.20-27.9 is.
-
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/
- Previous message: René Scharfe: "Re: File change notification"
- Maybe in reply to: Srikumar Subramanian: "memory leak in call_usermodehelper()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
