NetBSD Problem Report #41811

From www@NetBSD.org  Tue Aug  4 05:37:27 2009
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 38B6B63BDF9
	for <gnats-bugs@gnats.netbsd.org>; Tue,  4 Aug 2009 05:37:27 +0000 (UTC)
Message-Id: <20090804053727.04CB363BD7C@www.NetBSD.org>
Date: Tue,  4 Aug 2009 05:37:27 +0000 (UTC)
From: lloyd@must-have-coffee.gen.nz
Reply-To: lloyd@must-have-coffee.gen.nz
To: gnats-bugs@NetBSD.org
Subject: mounting unconfigured vnd devices causes a hang
X-Send-Pr-Version: www-1.0

>Number:         41811
>Category:       kern
>Synopsis:       mounting unconfigured vnd devices causes a hang
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 04 05:40:00 +0000 2009
>Closed-Date:    Sun Jun 03 11:12:01 +0000 2018
>Last-Modified:  Sun Jun 03 11:12:01 +0000 2018
>Originator:     Lloyd Parkes
>Release:        5.99.12
>Organization:
Must Have Coffee
>Environment:
NetBSD evbarm 5.99.12 NetBSD 5.99.12 (TS7200) #3: Tue Aug  4 15:54:46 NZST 2009  lloyd@rhox.must-have-coffee.gen.nz:/vol/scratch/build-gsoc/obj.evbarm/sys/arch/evbarm/compile/TS7200 evbarm

>Description:
Trying to mount a filesystem from a vnd device before you have remembered to configure the device causes the mount command to hang. 

# /sbin/mount -t ffs /dev/vnd1a /mnt
^C
# ps ax
PID TTY STAT    TIME COMMAND
  0 ?   DKl  0:23.48 [system]
  1 ?   Is   0:00.24 init 
204 ?   D    0:00.04 mount_ffs /dev/vnd1a /mnt 
230 ?   Is   0:00.83 login 
234 ?   S    0:00.16 -csh 
235 ?   O+   0:00.07 ps -ax 

>How-To-Repeat:
/sbin/mount -t ffs /dev/vnd1a /mnt

>Fix:

>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->analyzed
State-Changed-By: pooka@NetBSD.org
State-Changed-When: Tue, 04 Aug 2009 12:57:57 +0300
State-Changed-Why:
This is a combinaton of the new module autoload code doing vnode 
unlock in spec_open() and the historic behaviour of file systems   
not locking the device vnode mounttime due the possibility of
deadlock.  In other words, it's another fine lose/lose mess someone 
else will be happy to deal with.


State-Changed-From-To: analyzed->closed
State-Changed-By: maya@NetBSD.org
State-Changed-When: Sun, 03 Jun 2018 11:12:01 +0000
State-Changed-Why:
Can't reproduce with -current. I suspect this was fixed in the meantime. Feel free to reply if it is indeed unfixed in some scenario.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.