* Michael Scheidell <[EMAIL PROTECTED]> [011227 14:48] wrote:
>
> same place as before:
>
> 0 fstatfs (p=0xce1bd260, uap=0xce216f80) at ../../kern/vfs_syscalls.c:684
> 684 error = VFS_STATFS(mp, sp, p);
> 680 if ((error = getvnode(p->p_fd, SCARG(uap, fd), &fp)) != 0)
> 681 return (error);
> 682 mp = ((struct vnode *)fp->f_data)->v_mount;
> 683 sp = &mp->mnt_stat;
> 684 error = VFS_STATFS(mp, sp, p);
> 685 if (error)
> 686 return (error);
> 687 sp->f_flags = mp->mnt_flag & MNT_VISFLAGMASK;
> 688 if (suser_xxx(p->p_ucred, 0, 0)) {
> (kgdb) print mp
> $1 = (struct mount *) 0x28121604
> (kgdb) print sp
> $2 = (struct statfs *) 0x7
> (kgdb) print p
> $3 = (struct proc *) 0x8000
> (kgdb) print sp->f_flags
> Cannot access memory at address 0x37.
Ah, ok, I did see this before.
Can you print:
*mp, *sp, *p, *((struct vnode *)fp->f_data)
Can you tell me what filesystem this is over? Do you have
any special tunables set in your kernel? Anything you can
divulge about how this program operates?
--
-Alfred Perlstein [[EMAIL PROTECTED]]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
Tax deductable donations for FreeBSD: http://www.freebsdfoundation.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
