Date: Fri, 03 Oct 2014 14:05:40 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 193803] zvol rename failing due to out of order locking Message-ID: <bug-193803-8-fhTutGoL3E@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193803-8@https.bugs.freebsd.org/bugzilla/> References: <bug-193803-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193803 --- Comment #31 from Steven Hartland <smh@FreeBSD.org> --- (In reply to kash from comment #30) > (In reply to Steven Hartland from comment #28) > > So just to confirm, this does fix your deadlock issue? > > > > For reference the current locking for zvol changes is actually quite > > specific to FreeBSD so not really an upstream issue. > > Richard Yao was saying there's potential for converging the pathways still, > ZoL and Illumos have different ways of structuring locks, and thought the > way this was handled is a bit too similar to the Big Kernel Lock, but I > don't know much about this, I'm a less articulate coder. I believe this is around FS locking. The reason for the divergence in the code bases around ZVOLs is due to the fact that upstream creates ZVOL dev entries on the demand when a /dev/ lookup takes place. This is something FreeBSD currently can't do hence the various static create/destroy/rename in various places so they are always available. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193803-8-fhTutGoL3E>