Re: kern/46377 (Use of Coda file system triggers an immediate kernel panic)

[u-bsdmwle%aetey.se@localhost]

The following reply was made to PR kern/46377; it has been noted by GNATS.

From: u-bsdmwle%aetey.se@localhost
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
        netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/46377 (Use of Coda file system triggers an immediate kernel
 panic)
Date: Sat, 5 May 2012 18:18:05 +0000

 On Fri, May 04, 2012 at 06:00:08PM +0000, Christos Zoulas wrote:
 >  13 == EACCES, means that you cannot do the operation on this file;
 >  perfectly normal. I have commented out all the vnops debugging printfs
 >  now.
 
 I can confirm that reading works, without any console messages now.
 
 Bad news are that writing to Coda still triggers a crash:
 
 -----
 lock error
 fatal breakpoint trap in supervisor mode
 trap type 1 code 0 eip .........
 Stopped in pid 831.1 (ksh) at .........
 db{0}> bt
 breakpoint(.....)
 vpanic(.....)
 printf_nolog(.....)
 lockdebug_abort(.....)
 rw_abort(.....)
 rw_vector_exit(.....)
 genfs_unlock(.....)
 VOP_UNLOCK(.....)
 do_open(.....)
 sys_open(.....)
 syscall(.....)
 db{0}>
 -----
 
 The sequence for triggering the crash was (retyping, not copy/pasting) :
 
 -----
 $ clog guest%testserver.coda.cs.cmu.edu@localhost
 Password: guest
 $ cat >/coda/testserver.coda.cs.cmu.edu/playground/nb.test0
 [crash output on the console]
 -----
 
 Rune