Re: Security problems with access(2)?
On Sun, Apr 01, 2001 at 11:02:11PM -0400, Robert Watson wrote: eaccess_file(2) - Using effective credentials, check to see if the requested access is permitted on the file or directory identified by the provided pathname. Why not stick to existing naming practices? eaccess() eaccess_fd(2) - Using effective credentials, check to see if the requested access is permitted on the file or directory associated with the provided open file descriptor. Nope, faccess(2) (see fstat(2), flock(2), fchdir(2),...) and feaccess(2) faccess(3) - Using effective credentials, check to see if the requested access is permitted on the file or directory associated with the provided open file stream. What's wrong with faccess(fileno(...)) and feaccess(fileno(...))? -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 5.0 to have pthreads?
* Arthur Munn [EMAIL PROTECTED] [010401 20:09] wrote: hello all, I was told by a friend that FreeBSD 5.0 is going to be sporting *real* pthreads, I was immediatley very excited and I want to know if this is true, if anyone knows I would really like to have it verified/dismissed. We already have "*real*" pthreads. Pay more attention thanks, -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Security problems with access(2)?
"David O'Brien" wrote: | On Sun, Apr 01, 2001 at 11:02:11PM -0400, Robert Watson wrote: |eaccess_file(2) - Using effective credentials, check to see if the |requested access is permitted on the file or directory identified by the |provided pathname. | | Why not stick to existing naming practices? | eaccess() | |eaccess_fd(2) - Using effective credentials, check to see if the |requested access is permitted on the file or directory associated with |the provided open file descriptor. | | Nope, faccess(2) (see fstat(2), flock(2), fchdir(2),...) | and feaccess(2) | |faccess(3) - Using effective credentials, check to see if the requested |access is permitted on the file or directory associated with the |provided open file stream. | | What's wrong with faccess(fileno(...)) and feaccess(fileno(...))? My earlier agreement was with the concept; I do agree that this is a better naming scheme. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Security problems with access(2)?
In message [EMAIL PROTECTED] "David O'Brien" writes: : On Sun, Apr 01, 2001 at 10:55:23AM +1000, Greg Black wrote: : Many years ago I implemented a new interface that I called : eaccess() which replicated the work of access, but tested : against the effective uid and gid. I'd like to see that : introduced more widely. : : That still isn't suffient (and even more scary) unless the parameter is a : file handle or FILE pointer. We need an faccess() call, plain and : simple. faccess is also dangarous. When you open the file at elevated privs, you run the risk of side effects, such as a tape rewinding on close. facecss won't change that problem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
How do I create .ko files
Hi all, How to create .ko files? Are they simply .o files with some special compile-time options? If yes, what will be the options? The module will act as an network card driver. Thanks. --pradip To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Diskless station!!!
On Mon, Apr 02, 2001 at 12:54:35AM +0300, petro wrote: May be some of you can advice me where I can get nb3c509.com file for my diskless station with 3Com509 Ethernet, beceuse I can't run make in netboot directory. Have you looked at the etherboot port? David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: How do I create .ko files
On 29-Mar-2001 Pradip Kanti Biswas wrote: How to create .ko files? Are they simply .o files with some special compile-time options? If yes, what will be the options? The module will act as an network card driver. Use the bsd.kmod.mk file.. See /usr/src/sys/modules/*/Makefile for examples --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How do I create .ko files
* Pradip Kanti Biswas [EMAIL PROTECTED] [010402 01:23] wrote: Hi all, How to create .ko files? Are they simply .o files with some special compile-time options? If yes, what will be the options? The module will act as an network card driver. See the makefiles in /usr/src/sys/modules/* for examples. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
openssl/mdX.h and mdX.h name clashes
hi, there! /usr/include/mdX.h and /usr/include/openssl/mdX.h both declare structures and functions with the same name (structures are a bit different) and this is a bit troublesome for applications that want to link with both -lmd and -lcrypto can we consider merging our mdX.h enhancements (MD5End, MD5File) to openssl and switching to openssl/mdX.h entirely? /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: openssl/mdX.h and mdX.h name clashes
On Mon, Apr 02, 2001 at 05:03:20PM +0700, Max Khon wrote: hi, there! /usr/include/mdX.h and /usr/include/openssl/mdX.h both declare structures and functions with the same name (structures are a bit different) and this is a bit troublesome for applications that want to link with both -lmd and -lcrypto can we consider merging our mdX.h enhancements (MD5End, MD5File) to openssl and switching to openssl/mdX.h entirely? I believe that this is the way things are supposed to happen; this has been discussed on -arch recently, although somebody stated that OpenSSL already has all the functionality. I wasn't quite able to find analogous functions in the source; and a single function, without setting up a BIO object and stuff, when all you need is the MD5 hash of a file by name, is definitely something useful. G'luck, Peter -- If this sentence were in Chinese, it would say something else. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Dynamic routing table (problem solved, was: server continue dies)
My servers had died every 12h and I spend lots of time to solve problem, I hope the result of my work is interesting for community. The main reason of server fault is overloading of dynamic routing table (netstat -nra | grep W3) Another point - the same software running on non-Intel server (no-name PC with AHA SCSI and DEC net card) works without problems. I. Behavior of dynamic routing table controlled by sysctl variables: net.inet.ip.rtexpire net.inet.ip.rtminexpire net.inet.ip.rtmaxcache IMHO, default values of this variables should be changed to make heavy loaded servers more reliable or at least it should be documented. 1. net.inet.ip.rtexpire should be set to 10 not to 3600 by default This value slow down a bit intranet servers, but make heavy loaded www servers more reliable. I check this variable on some www servers around me and find that all really loaded ones have net.inet.ip.rtexpire=10 2. net.inet.ip.rtmaxcache should depend to maxusers. 3. kernel should drop first entries of DR independently of it's age, and rise appropriate error message to console if the table overloaded. II. I'm not sure whether or not my problem depends of fxp driver, but it's possible. Daniel O'Connor wrote: On 27-Mar-01 Dmitry Samersoff wrote: I also have a kernel crash dump and could post it here if no one can give me a good advice without it ;-))) If you haven't compiled the kernel with debugging symbols then you should do so.. After that get a crash dump and do.. cd /var/crash gdb -k kernel.0 vmcore.0 bt And post the output. When you do post info like your dmesg output and hardware specs. I'm terribly sorry to waste your time but this is critical problem and unfortunately I have no ideas how to solve it or at least find reason of such behavior. It does seem odd given the machien doesn't look _too_ busy. What sort of processes are you running on it? Web server, ftp server, etc? Can you run top or ps and find out what particular processes are running at the time it crashes? --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- Dmitry Samersoff, [EMAIL PROTECTED], ICQ:3161705 http://devnull.wplus.net * There will come soft rains ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Dynamic routing table (problem solved, was: server continue dies)
On Mon, Apr 02, 2001 at 02:03:37PM +0400, Dmitry Samersoff wrote: My servers had died every 12h and I spend lots of time to solve problem, I hope the result of my work is interesting for community. The main reason of server fault is overloading of dynamic routing table (netstat -nra | grep W3) Another point - the same software running on non-Intel server (no-name PC with AHA SCSI and DEC net card) works without problems. I. Behavior of dynamic routing table controlled by sysctl variables: net.inet.ip.rtexpire net.inet.ip.rtminexpire net.inet.ip.rtmaxcache IMHO, default values of this variables should be changed to make heavy loaded servers more reliable or at least it should be documented. I believe the reason those are sysctl's, instead of hard-wired kernel values, is that they be made tweakable (/etc/sysctl.conf comes to mind). As to documentation, yeah, that's a common problem for all the sysctl's :( G'luck, Peter -- Do you think anybody has ever had *precisely this thought* before? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: openssl/mdX.h and mdX.h name clashes
hi, there! On Mon, 2 Apr 2001, Peter Pentchev wrote: /usr/include/mdX.h and /usr/include/openssl/mdX.h both declare structures and functions with the same name (structures are a bit different) and this is a bit troublesome for applications that want to link with both -lmd and -lcrypto can we consider merging our mdX.h enhancements (MD5End, MD5File) to openssl and switching to openssl/mdX.h entirely? I believe that this is the way things are supposed to happen; this has been discussed on -arch recently, although somebody stated that OpenSSL already has all the functionality. I wasn't quite able to find analogous functions in the source; and a single function, without setting up a BIO object and stuff, when all you need is the MD5 hash of a file by name, is definitely something useful. Thanks for the pointer. I'll go read archives. I have already noticed that function names are different (underscores) but the problem remains for compilation time. /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
subscribe
i m intersted in the development project of freebsd. pls send me the technical discussions of this mailing list aditya To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: new rc.diskless{1,2} files
In message [EMAIL PROTECTED]you write:
} http://www.iet.unipi.it/~luigi/clone_root.010401
nice, i just do rsh dump ...| restore
but then again, im still experimenting :-)
}
}and basically nothing else. The modified copies of files which
}have to replace the original ones in the root partition
}are taken from /conf/${IP} or /conf/${SUBNET} or /conf, where
}$IP and $SUBNET are the IP address and the local broadcast address
}of the first configured network interface. The code in /etc/rc.diskless1
}tries to find the longest match from the above.
}
}This lets you centralize the configurations, and yet have
}separate configuration files.
it's not centralized when you start replicating the root-fs.
}It helps a lot to have not just variable assignments in /etc/rc.conf
}(typically a "case" statement to do per-machine settings.)
i like that idea of /etc/rc.conf, one of the changes i did to rc.diskless1 was
that it sources /conf/default/etc/* first - i can't remember why :-(
if [ -d /conf/default/etc ]; then---
cp -Rp /conf/default/etc/* $1
fi
if [ -d /conf/${bootp_ipa} ] ; then
...
elif [ -d /conf/${hostname} ] ; then --
cp -Rp /conf/${hostname}/etc/* $1
now if I could just get /conf from some central repository ...
A tool to do some central management is dhcp, the problem there is that most of
the predefined tags are useless, and the ones needed are not easy to configure.
I managed to used dhcp to select what kernel to load.
Im also trying to set up a way to configure, say X11, and having the XF86Config
saved from the volatile /etc
danny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Security problems with access(2)?
On Sun, 1 Apr 2001, David O'Brien wrote:
On Sun, Apr 01, 2001 at 11:02:11PM -0400, Robert Watson wrote:
eaccess_file(2) - Using effective credentials, check to see if the
requested access is permitted on the file or directory identified by the
provided pathname.
Why not stick to existing naming practices?
eaccess()
I'm not attached to the names, but this is in line with the naming
conventions from POSIX.1e (acl_*_{fd,file}(), cap_*_{fd,file}(), et al).
I'm quite happy to move to an eaccess() and feaccess() model. The patches
are quite minimal, so I'll post them later today when I check that the
name-changed version compiles and runs properly still :-).
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
panic in FFS and other related I/O problems
Hi Everyone,
This is the famous bbs with high loads. We upgraded to 4.3-RC
recently.
The user level we have at this point is not that much compared
to before. 2000 users is what we can usually take on without
problems. Now we panic() 20 times a day.
FreeBSD zoo.ee.ntu.edu.tw 4.3-RC FreeBSD 4.3-RC #0: Tue Apr
3 07:14:31 CST 2001
I am thinking that this is either a bug is FFS I/O operations
or our own bbs having race conditions. However, the bbs
has run fine without problem before.
---
2001/04/02 22:58 options VM_KMEM_SIZE_MAX="(300*1024*1024)"(200-300)
---
2001/04/02 22:43 run-time panic
uptime:10:43¤U¤È up 1:40, 6 users, load averages: 3.69, 2.99, 2.61
bbs:Number of Users:2160
panic: pipeinit: cannot allocate pipe -- out of kvm -- code = 3
mp_lock = 0101; cpuid = 1; lapic.id =
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.597
db tr
Debugger(c0249bf2) at Debugger+0x35
panic(c024b3a0,3,facac440,fe726e7c,c015eaa2) at panic+0xa4
pipespace(facac440) at pipespace+0x58
pipe_write(cacf2540,fe726ed4,ca506300,0,fe55e040) at pipe_write+0x192
dofilewrite(fe55e040,cacf2540,8,80f7000,19fe) at dofilewrite+0xbe
write(fe55e040,fe726f80,2823f0c8,28251008,80f7000) at write+0x3b
syscall2(2f,2f,2f,80f7000,28251008) at syscall2+0x221
Xint0x80_syscall() at Xint0x80_syscall+0x2b
---
2001/04/02 20:52 PMAP_SHPGPERPROC removed from kernel
/bin/mv /etc/vntab.orig /etc/vntab, Add more swap
---
2001/04/02 20:30 run-time panic
Fatal trap 12: page fault while in kernel mode
mp_lock = 0002; cpuid = 0; lapic.id = 0100
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc022fb2b
stack pointer = 0x10:0xfd9d1bcc
frame pointer = 0x10:0xfd9d1bfc
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 4118 (bbsd)
interrupt mask = bio - SMP: XXX
kernel: type 12 trap, code=0
Stopped at generic_bzero+0xf: repe stosl %es:(%edi)
db tr
generic_bzero(1,c755fe00,c7243400,fd9d1c44,100) at generic_bzero+0xf
ffs_vget(c755fe00,5e3f84,fd9d1cb8,0,fbe61 f40) at ffs_vget+0xa4
ufs_lookup(fd9d1d10,fd9d1d24,c01774ca,fd9d1d10,fbe61f40) at ufs_lookup+0x9c7
ufs_vnoperate(fd9d1d10,fbe61f40,ff27941d,fd9d1ef0,fbe62000) at ufs_vnoperate+0x1
5
vfs_cache_lookup(fd9d1d68,fd9d1d78,c017a338,fd9d1d68,ef8c1d00) at vfs_cache_look
up+0x28a
ufs_vnoperate(fd9d1d68,ef8c1d00,fd9d1ef0,fd9d1ec8,fd9b7ac0) at ufs_vnoperate+0x1
5
lookup(fd9d1ec8,0,fd9d1ec8,fd9d1f80,fd9b7ac0) at lookup+0x290
namei(fd9d1ec8,0,ca3ed580,fd9d1f80,fd9d1df8) at namei+0x147
vn_open(fd9d1ec8,1,1a4,3,fd9b7ac0) at vn_open+0x1cd
open(fd9b7ac0,fd9d1f80,281960c8,281a7f00,4) at open+0xb8
syscall2(2f,2f,bfbf002f,4,281a7f00) at syscall2+0x221
Xint0x80_syscall() at Xint0x80_syscall+0x2b
db call boot(0)
boot() called on cpu#0
Waiting (max 60 seconds) for system process `bufdaemon' to stop...
Fatal trap 12: page fault while in kernel mode
mp_lock = 0002; cpuid = 0; lapic.id = 0100
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc02082b3
stack pointer = 0x10:0xfe80adec
frame pointer = 0x10:0xfe80adf8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 7749 (bbsd)
interrupt mask = net tty bio cam - SMP: XXX
kernel: type 12 trap, code=0
Stopped at generic_bzero+0xf: repe stosl %es:(%edi)
---
2000/04/02 08:29 boot panic = lowered PMAP_SHPGPERPROC to 300
panic: swap_pager_swap_init: swap_zone == NULL
mp_lock = 0001; cpuid = 0; lapic.id = 0100
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.597
---
2000/04/02 08:24 change kernel again
options MAXFILES=3
options NMBCLUSTERS=16000(making this smaller)
options PMAP_SHPGPERPROC=720(back to our setup that was stable before)
---
2001/04/02 08:08AM run-time panic
_SimFarm_[root]:/bighead#vim dump1.pl
panic: ffs_valloc: dup alloc
mp_lock = 0101; cpuid = 1; lapic.id =
Debugger("panic")
Readdir() unlink() interaction
Dear All, I'm curious what the specified behaviour is of readdir() after and unlink(). The manual pages of these functions do not specify this. I'm asking this in relation to PR kern/26142, where you will infd a little test program to reproduce the problem. I've just done so on FreeBSD 4.3 RC and and Solaris. FreeBSD NFS mounts cause problems, Solaris NFS or FreeBSD local mounts show expected behaviour. Is there any documentation that specifies unlink()/readdir() interaction? Kees Jan You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: panic in FFS and other related I/O problems
"Michael C . Wu" wrote:
Hi Everyone,
This is the famous bbs with high loads. We upgraded to 4.3-RC
recently.
The user level we have at this point is not that much compared
to before. 2000 users is what we can usually take on without
problems. Now we panic() 20 times a day.
FreeBSD zoo.ee.ntu.edu.tw 4.3-RC FreeBSD 4.3-RC #0: Tue Apr
3 07:14:31 CST 2001
I am thinking that this is either a bug is FFS I/O operations
or our own bbs having race conditions. However, the bbs
has run fine without problem before.
---
2001/04/02 22:58 options VM_KMEM_SIZE_MAX="(300*1024*1024)"(200-300)
---
2001/04/02 22:43 run-time panic
uptime:10:43¤U¤È up 1:40, 6 users, load averages: 3.69, 2.99, 2.61
bbs:Number of Users:2160
panic: pipeinit: cannot allocate pipe -- out of kvm -- code = 3
You have used up you 1G of KVM. I suggest you reconfigure the KVM on your
boxes so that you double it. This will change you from 1G kernel, 3G user
to 2G each.
Suggested patch:
Index: conf/ldscript.i386
===
RCS file: /home/ncvs/src/sys/conf/ldscript.i386,v
retrieving revision 1.4
diff -u -r1.4 ldscript.i386
--- conf/ldscript.i386 2000/01/11 15:35:16 1.4
+++ conf/ldscript.i386 2001/04/02 16:07:18
@@ -6,7 +6,7 @@
SECTIONS
{
/* Read-only sections, merged into text segment: */
- . = 0xc010 + SIZEOF_HEADERS;
+ . = 0x8010 + SIZEOF_HEADERS;
.interp : { *(.interp) }
.hash : { *(.hash) }
.dynsym: { *(.dynsym)}
Index: i386/include/pmap.h
===
RCS file: /home/ncvs/src/sys/i386/include/pmap.h,v
retrieving revision 1.70
diff -u -r1.70 pmap.h
--- i386/include/pmap.h 2000/11/30 01:53:02 1.70
+++ i386/include/pmap.h 2001/04/02 16:07:18
@@ -92,9 +92,9 @@
#endif
#ifndef NKPDE
#ifdef SMP
-#define NKPDE 254 /* addressable number of page tables/pde's */
+#define NKPDE 510 /* addressable number of page tables/pde's */
#else
-#define NKPDE 255 /* addressable number of page tables/pde's */
+#define NKPDE 511 /* addressable number of page tables/pde's */
#endif /* SMP */
#endif
You have basically raised so many limits that you have run out of space
for kernel allocations.
root@overcee[9:09am]/home/src/sys/compile/OVERCEE-103# gdb -k kernel.debug /dev/mem
...
(kgdb) print /x kernel_map.size
$8 = 0x1a658000
With a default start addr of 0xc010, there is nearly 0x400
available. My machine here is using just less than half of it. Yours is
probably almost full.
mp_lock = 0101; cpuid = 1; lapic.id =
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.597
db tr
Debugger(c0249bf2) at Debugger+0x35
panic(c024b3a0,3,facac440,fe726e7c,c015eaa2) at panic+0xa4
pipespace(facac440) at pipespace+0x58
pipe_write(cacf2540,fe726ed4,ca506300,0,fe55e040) at pipe_write+0x192
dofilewrite(fe55e040,cacf2540,8,80f7000,19fe) at dofilewrite+0xbe
write(fe55e040,fe726f80,2823f0c8,28251008,80f7000) at write+0x3b
syscall2(2f,2f,2f,80f7000,28251008) at syscall2+0x221
Xint0x80_syscall() at Xint0x80_syscall+0x2b
---
2001/04/02 20:52 PMAP_SHPGPERPROC removed from kernel
/bin/mv /etc/vntab.orig /etc/vntab, Add more swap
---
2001/04/02 20:30 run-time panic
Fatal trap 12: page fault while in kernel mode
mp_lock = 0002; cpuid = 0; lapic.id = 0100
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc022fb2b
stack pointer = 0x10:0xfd9d1bcc
frame pointer = 0x10:0xfd9d1bfc
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 4118 (bbsd)
interrupt mask = bio - SMP: XXX
kernel: type 12 trap, code=0
Stopped at generic_bzero+0xf: repe stosl %es:(%edi)
db tr
generic_bzero(1,c755fe00,c7243400,fd9d1c44,100) at generic_bzero+0xf
ffs_vget(c755fe00,5e3f84,fd9d1cb8,0,fbe61 f40) at ffs_vget+0xa4
ufs_lookup(fd9d1d10,fd9d1d24,c01774ca,fd9d1d10,fbe61f40) at ufs_lookup+0x9c7
ufs_vnoperate(fd9d1d10,fbe61f40,ff27941d,fd9d1ef0,fbe62000) at ufs_vnoperate+
0x1
5
vfs_cache_lookup(fd9d1d68,fd9d1d78,c017a338,fd9d1d68,ef8c1d00) at vfs_cache_l
ook
up+0x28a
ufs_vnoperate(fd9d1d68,ef8c1d00,fd9d1ef0,fd9d1ec8,fd9b7ac0) at ufs_vnoperate+
0x1
5
Re: panic in FFS and other related I/O problems
Hi everyone,
After I applied this patch, something happens to my system(zoo.ee.ntu.edu.tw).
It seemed that all programs using pthread would coredump with signal 6.
and show some messages like this:
Apr 3 00:32:32 zoo /kernel: pid 341 (logind), uid 0: exited on signal 6 (core d
umped)
Fatal error 'Cannot allocate red zone for initial thread' at line ? in file /usr
/src/lib/libc_r/uthread/uthread_init.c (errno = ?)
Abort trap - core dumped
I had already tried recompiled /usr/src/lib but there were no use.
Please advice. :)
Thanks all,
- Original Message -
From: "Peter Wemm" [EMAIL PROTECTED]
To: "Michael C . Wu" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, April 03, 2001 12:12 AM
Subject: Re: panic in FFS and other related I/O problems
: "Michael C . Wu" wrote:
: Hi Everyone,
:
: This is the famous bbs with high loads. We upgraded to 4.3-RC
: recently.
:
: The user level we have at this point is not that much compared
: to before. 2000 users is what we can usually take on without
: problems. Now we panic() 20 times a day.
:
: FreeBSD zoo.ee.ntu.edu.tw 4.3-RC FreeBSD 4.3-RC #0: Tue Apr
: 3 07:14:31 CST 2001
:
: I am thinking that this is either a bug is FFS I/O operations
: or our own bbs having race conditions. However, the bbs
: has run fine without problem before.
:
: ---
: 2001/04/02 22:58 options VM_KMEM_SIZE_MAX="(300*1024*1024)"(200-300)
: ---
: 2001/04/02 22:43 run-time panic
: uptime:10:43¤U¤È up 1:40, 6 users, load averages: 3.69, 2.99, 2.61
: bbs:Number of Users:2160
: panic: pipeinit: cannot allocate pipe -- out of kvm -- code = 3
:
: You have used up you 1G of KVM. I suggest you reconfigure the KVM on your
: boxes so that you double it. This will change you from 1G kernel, 3G user
: to 2G each.
:
: Suggested patch:
: Index: conf/ldscript.i386
: ===
: RCS file: /home/ncvs/src/sys/conf/ldscript.i386,v
: retrieving revision 1.4
: diff -u -r1.4 ldscript.i386
: --- conf/ldscript.i386 2000/01/11 15:35:16 1.4
: +++ conf/ldscript.i386 2001/04/02 16:07:18
: @@ -6,7 +6,7 @@
: SECTIONS
: {
:/* Read-only sections, merged into text segment: */
: - . = 0xc010 + SIZEOF_HEADERS;
: + . = 0x8010 + SIZEOF_HEADERS;
:.interp : { *(.interp) }
:.hash : { *(.hash) }
:.dynsym: { *(.dynsym) }
: Index: i386/include/pmap.h
: ===
: RCS file: /home/ncvs/src/sys/i386/include/pmap.h,v
: retrieving revision 1.70
: diff -u -r1.70 pmap.h
: --- i386/include/pmap.h 2000/11/30 01:53:02 1.70
: +++ i386/include/pmap.h 2001/04/02 16:07:18
: @@ -92,9 +92,9 @@
: #endif
: #ifndef NKPDE
: #ifdef SMP
: -#define NKPDE 254 /* addressable number of page tables/pde's */
: +#define NKPDE 510 /* addressable number of page tables/pde's */
: #else
: -#define NKPDE 255 /* addressable number of page tables/pde's */
: +#define NKPDE 511 /* addressable number of page tables/pde's */
: #endif /* SMP */
: #endif
:
: You have basically raised so many limits that you have run out of space
: for kernel allocations.
: root@overcee[9:09am]/home/src/sys/compile/OVERCEE-103# gdb -k kernel.debug /dev/mem
: ...
: (kgdb) print /x kernel_map.size
: $8 = 0x1a658000
:
: With a default start addr of 0xc010, there is nearly 0x400
: available. My machine here is using just less than half of it. Yours is
: probably almost full.
:
:
: mp_lock = 0101; cpuid = 1; lapic.id =
: Debugger("panic")
: Stopped at Debugger+0x35: movb$0,in_Debugger.597
: db tr
: Debugger(c0249bf2) at Debugger+0x35
: panic(c024b3a0,3,facac440,fe726e7c,c015eaa2) at panic+0xa4
: pipespace(facac440) at pipespace+0x58
: pipe_write(cacf2540,fe726ed4,ca506300,0,fe55e040) at pipe_write+0x192
: dofilewrite(fe55e040,cacf2540,8,80f7000,19fe) at dofilewrite+0xbe
: write(fe55e040,fe726f80,2823f0c8,28251008,80f7000) at write+0x3b
: syscall2(2f,2f,2f,80f7000,28251008) at syscall2+0x221
: Xint0x80_syscall() at Xint0x80_syscall+0x2b
: ---
: 2001/04/02 20:52 PMAP_SHPGPERPROC removed from kernel
: /bin/mv /etc/vntab.orig /etc/vntab, Add more swap
: ---
: 2001/04/02 20:30 run-time panic
: Fatal trap 12: page fault while in kernel mode
: mp_lock = 0002; cpuid = 0; lapic.id = 0100
: fault virtual address = 0x0
: fault code = supervisor write, page not present
: instruction pointer = 0x8:0xc022fb2b
: stack pointer = 0x10:0xfd9d1bcc
: frame pointer = 0x10:0xfd9d1bfc
: code segment= base 0x0, limit 0xf, type 0x1b
: = DPL 0,
RELEASE versus STABLE
Hi there, When I read the FreeBSD handbook, I found only "Current versus Releases" description. But yesterday, I confused because I was suggested to change/upgrade my FreeBSD 4.2 Release to 4.2 Stable. Today I want to ask you, are 4.2 Release is not same with 4.2 Stable ? Thats mean, FreeBSD had threes branch of development ??? I mention current, release, and Stable. I was think if release mention final / stable release branch. I need that 4.2 release cause I need "awi" driver for my Intersil / Harris Prism I card. So anybody could told me, where I can download 4.2 STABLE ? Thank's for any kind attention and help. Regards, SA -- Email ini dikirim oleh PlasaCom : http://www.plasa.com Cepat di-download via TelkomNet Instan http://www.plasa.com/instan Rindukah Anda bertemu dengan ex teman-teman satu sekolah dulu ? Kunjungilah mereka (41.203 anggota) di KSI : http://ksi.plasa.com -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: RELEASE versus STABLE
On Tue, Apr 03, 2001 at 03:27:42AM +0700, SysAdmin wrote: Hi there, When I read the FreeBSD handbook, I found only "Current versus Releases" description. But yesterday, I confused because I was suggested to change/upgrade my FreeBSD 4.2 Release to 4.2 Stable. Today I want to ask you, are 4.2 Release is not same with 4.2 Stable ? Thats mean, FreeBSD had threes branch of development ??? I mention current, release, and Stable. I was think if release mention final / stable release branch. I need that 4.2 release cause I need "awi" driver for my Intersil / Harris Prism I card. So anybody could told me, where I can download 4.2 STABLE ? Thank's for any kind attention and help. Regards, SA Please do not cross-post. If you can't generate a response in one list, then try another list, but don't submit a message to multiple lists at one time. Furthermore, this question is not appropriate for freebsd-hackers. This list is meant for people with bug notices, programming suggestions, and code to discuss. freebsd-questions is for questions about the basic operation of FreeBSD. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
No Subject
__ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/?.refer=text To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
