Date: Fri, 16 Oct 2015 12:54:24 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 201912] panic in smbfs during mount Message-ID: <bug-201912-3630-McrqjjdCtb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201912-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-201912-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=201912 Rick Macklem <rmacklem@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmacklem@FreeBSD.org --- Comment #5 from Rick Macklem <rmacklem@FreeBSD.org> --- Created attachment 162117 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162117&action=edit fix a race between smb_iod_destroy() and the smd_iod thread that destroys mutexes and frees the iod structure prematurely I think this patch might fix the problem that caused your crash. Your crash does look somewhat different than PR#172942, but it does call smb_iod_destroy() via smb_vc_gone() and that is where the race was. Unfortunately your crash does suggest that the mount was trying to do another smb_iod_destroy() when it had already happened and this might suggest an additional race that the patch doesn't address. Since it is somewhat different, I haven't marked it as a duplicate of PR#172942. I will do that if Martin reports back that the patch seems to have stopped the crashes from occurring. (I have no idea how reproducible these crashes are? -- 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-201912-3630-McrqjjdCtb>