From: Amon Ott <ao@rsbac.org>
Subject: Re: Better syscall handling
Date: Fri, 8 Jun 2001 11:05:25 +0200
Next Article (by Subject): Re: Better syscall handling Amon Ott
Previous Article (by Subject): Better syscall handling Douglas Ostling
Next in Thread: Better syscall handling Douglas Ostling
Articles sorted by: [Date]
[Author]
[Subject]
On Mit, 06 Jun 2001 Douglas Ostling wrote: > On Wed, Jun 06, 2001 at 09:35:26AM +0200, Amon Ott wrote: > > On Mit, 06 Jun 2001 Douglas Ostling wrote: > > > How would I go about creating better recovery for handling syscall > > > interception? As things are now, the system slows down impossibly > > > to the point of a hang. > > > > You are the first one ever reporting such a behaviour. It does not happen on > > all PCs I ever used RSBAC on. > > > > What exactly happens on your system? > This is an exact duplicate of the kernel syslog message from the most recent > event of this nature while doing a recursive ftp download with wget from off > the Interent: > > Jun 5 12:10:50 zone kernel: kernel BUG at vmalloc.c:236! > Jun 5 12:10:50 zone kernel: Call Trace: [do_scan_sock+1241/1872] [do_scan_sock > Do you make sense of it? Please turn off MS option 'socket scan', which uses the function do_scan_sock. I will have another look into the allocation code there. Amon. - To unsubscribe from the rsbac list, send a mail to majordomo@rsbac.org with unsubscribe rsbac as single line in the body.
Next Article (by Subject): Re: Better syscall handling Amon Ott
Previous Article (by Subject): Better syscall handling Douglas Ostling
Next in Thread: Better syscall handling Douglas Ostling
Articles sorted by: [Date]
[Author]
[Subject]