NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/54541: kernel panic using "zfs diff"



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

From: christos%zoulas.com@localhost (Christos Zoulas)
To: gnats-bugs%netbsd.org@localhost, kern-bug-people%netbsd.org@localhost, 
	gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, joernc%posteo.de@localhost
Cc: 
Subject: Re: kern/54541: kernel panic using "zfs diff"
Date: Fri, 11 Oct 2019 14:44:16 -0400

 On Oct 11,  4:05pm, prlw1%cam.ac.uk@localhost (Patrick Welche) wrote:
 -- Subject: Re: kern/54541: kernel panic using "zfs diff"
 
 | The following reply was made to PR kern/54541; it has been noted by GNATS.
 | 
 | From: Patrick Welche <prlw1%cam.ac.uk@localhost>
 | To: gnats-bugs%netbsd.org@localhost
 | Cc: 
 | Subject: Re: kern/54541: kernel panic using "zfs diff"
 | Date: Fri, 11 Oct 2019 17:01:34 +0100
 | 
 |  On Wed, Oct 09, 2019 at 05:05:01PM +0000, Christos Zoulas wrote:
 |  >  Something seems to not understand that this is a hijacked fd which it seems
 |  >  to be: 133 (128 + 5)...
 |  
 |  /dev/zfs is hijacked:
 |  export RUMPHIJACK=blanket=/dev/zfs:/dk:/storage,sysctl=yes,modctl=yes
 |  
 |  rumpns_fd_getfile receives the 133 rather than 5 so complains.
 |  So I seem to be seeing a rump issue rather than a zfs issue?
 
 Well, from the stacktrace it seems that it does not get hijacked for some
 reason. Why don't you try to break with gdb in the ioctl call?
 
 christos
 


Home | Main Index | Thread Index | Old Index