* Matthew Jacob <[EMAIL PROTECTED]> [010122 15:32] wrote:
> Debugger("panic")
> Stopped at      Debugger+0x44:  pushl   %ebx
> db> t
> Debugger(c02b8303) at Debugger+0x44
> panic(c02c9040,bfc00000,581000,c02ea620,c030ab0c) at panic+0x70
> kmem_malloc(c0312d20,bfc00000,8,bfbff810,c8dddd98) at kmem_malloc+0xd7
> malloc(bfbff810,c02ea620,8,c0ff1e00,c8dddd98) at malloc+0x248
> vfs_hang_addrlist(c0ff1e00,c0feac6c,c8dddd98,c0ff5000,c80c9f00) at
> vfs_hang_addrlist+0x8f
> vfs_export(c0ff1e00,c0feac6c,c8dddd98,4,c0ff1e00) at vfs_export+0x61
> ffs_mount(c0ff1e00,809f0b0,bfbff6b8,c8ddde9c,c7add980) at ffs_mount+0x3ee
> mount(c7add980,c8dddf80,809f0b1,0,0) at mount+0x5e7
> syscall2(2f,2f,2f,0,0) at syscall2+0x285
> Xint0x80_syscall() at Xint0x80_syscall+0x23
> --- syscall 0x15, eip = 0x804f51c, esp = 0xbfbff684, ebp = 0xbfbff780 ---
> mountd exporting stuff causes a panic.

This is and isn't my fault, struct ucred needs a lock for refcounts.
Since mount uses ucreds in userspace and passes them to the kernel
we have a issue when struct mtx changes.  I'm going to take a shot
at removing struct ucred from userland this weekend, but you can
have a shot at it if you'd like.

The other option is to at least fix mount and friends to use
something other than ucred, and slowly remove it (struct ucred)
from userland.

"I have the heart of a child; I keep it in a jar on my desk."

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to