Re: kern/48135 Bad locking for umount

[David Holland <dholland-bugs%netbsd.org@localhost>]

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

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/48135 Bad locking for umount
Date: Sun, 13 Oct 2013 21:32:59 +0000

 not sent to gnats-bugs
    ------
 
 From: Michael van Elst <mlelstv%serpens.de@localhost>
 To: gnats%netbsd.org@localhost
 Subject: Re: kern/48135 Bad locking for umount
 Date: Sun, 8 Sep 2013 08:13:05 +0200
 
 
 Nothing changed, by looping over an amd mount I can still crash
 the system:
 
 db{1}> bt
 breakpoint() at netbsd:breakpoint+0x5
 vpanic() at netbsd:vpanic+0x136
 printf_nolog() at netbsd:printf_nolog
 lockdebug_more() at netbsd:lockdebug_more
 mutex_destroy() at netbsd:mutex_destroy+0x75
 vfs_destroy() at netbsd:vfs_destroy+0x42
 sys_unmount() at netbsd:sys_unmount+0x15b
 syscall() at netbsd:syscall+0x9a
 --- syscall (number 22) ---
 7f7ff683b86a:
 db{1}> mach cpu 0
 using CPU 0
 db{1}> bt
 spllower() at netbsd:spllower+0xf
 tsleep() at netbsd:tsleep+0x122
 ahci_exec_command() at netbsd:ahci_exec_command+0x10b
 wd_flushcache() at netbsd:wd_flushcache+0xd8
 wdioctl() at netbsd:wdioctl+0x5f7
 bdev_ioctl() at netbsd:bdev_ioctl+0x77
 VOP_IOCTL() at netbsd:VOP_IOCTL+0x3b
 bdev_ioctl() at netbsd:bdev_ioctl+0x77
 VOP_IOCTL() at netbsd:VOP_IOCTL+0x3b
 wapbl_cache_sync() at netbsd:wapbl_cache_sync+0x4d
 wapbl_write_commit() at netbsd:wapbl_write_commit+0x4b
 wapbl_flush() at netbsd:wapbl_flush+0x714
 ffs_sync() at netbsd:ffs_sync+0x2b9
 VFS_SYNC() at netbsd:VFS_SYNC+0x1c
 sync_fsync() at netbsd:sync_fsync+0x78
 VOP_FSYNC() at netbsd:VOP_FSYNC+0x3e
 sched_sync() at netbsd:sched_sync+0xef
 
 
 
 Greetings,
 -- 
                                 Michael van Elst
 Internet: mlelstv%serpens.de@localhost
                                 "A potential Snark may lurk in every tree."