Date: Tue, 22 Jan 2019 12:51:28 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 225423] panic: softdep_deallocate_dependencies: dangling deps Message-ID: <bug-225423-3630-qedcVJ6enb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-225423-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-225423-3630@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=3D225423 Arpan Palit <babupalit@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |babupalit@gmail.com --- Comment #22 from Arpan Palit <babupalit@gmail.com> --- Hi, I am using freeBSD stable/11 branch, and still facing the same dangling deps panic as the b_ioflags flag is re-set'ed (i.e., BIO_ERROR not set) and also observed most cases b_error is 0. Testing environment has following commit head. ---------------------------------------------------------------------------= --- commit 7b249ab3e16a3d41d0a58a43d7d89137a1c9ec00 (HEAD -> stable/11, origin/stable/11) Author: delphij <delphij@FreeBSD.org> Date: Tue Jan 22 04:20:52 2019 +0000 ---------------------------------------------------------------------------= --- backtrace: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D fsync: giving up on dirty (error =3D 6) 0xfffff8029cbda938: tag devfs, type= VCHR usecount 1, writecount 0, refcount 15 rdev 0xfffff80247038400 flags (VI_DOOMED|VI_ACTIVE) v_object 0xfffff80247d320f0 ref 0 pages 95 cleanbuf 10 dirtybuf 2 lock type devfs: EXCL by thread 0xfffff8029c84d620 (pid 774, df, tid 100720) dev ada1p1 panic: softdep_deallocate_dependencies: dangling deps cpuid =3D 57 KDB: stack backtrace: #0 0xffffffff80b20d27 at kdb_backtrace+0x67 #1 0xffffffff80add3c7 at vpanic+0x177 #2 0xffffffff80add453 at panic+0x43 #3 0xffffffff80d84376 at softdep_deallocate_dependencies+0x76 #4 0xffffffff80b7cd2c at brelse+0x16c #5 0xffffffff80b9bc5d at flushbuflist+0x15d #6 0xffffffff80b9b891 at bufobj_invalbuf+0x81 #7 0xffffffff80b9f06e at vgonel+0x18e #8 0xffffffff80b9f68f at vgone+0x2f #9 0xffffffff809aba42 at devfs_delete+0x1a2 #10 0xffffffff809ac1e2 at devfs_populate_loop+0x2b2 #11 0xffffffff809abf1a at devfs_populate+0x4a #12 0xffffffff809b0dcc at devfs_populate_vp+0x8c #13 0xffffffff809afa0f at devfs_getattr+0x1f #14 0xffffffff810dc8a7 at VOP_GETATTR_APV+0xf7 #15 0xffffffff80bad553 at vn_stat+0xa3 #16 0xffffffff80bab44f at vn_statfile+0x4f #17 0xffffffff80a8a8a9 at kern_fstat+0xa9 -> Am I missing some patch or the issue still required some potential fix? Thanks, Arpan --=20 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-225423-3630-qedcVJ6enb>