Date: Mon, 25 Jun 2012 11:30:14 GMT From: Kristof Provost <kristof@sigsegv.be> To: freebsd-arm@FreeBSD.org Subject: Re: arm/149288: mail/dovecot causes panic during configure on Sheevaplug (ARM) Message-ID: <201206251130.q5PBUEXl099764@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR arm/149288; it has been noted by GNATS.
From: Kristof Provost <kristof@sigsegv.be>
To: bug-followup@FreeBSD.org
Cc:
Subject: Re: arm/149288: mail/dovecot causes panic during configure on
Sheevaplug (ARM)
Date: Mon, 25 Jun 2012 13:25:29 +0200
The problem appears to be fixed in HEAD, by commit r237367 (Enable
deadlock avoidance code for NFS client.).
As near as I can tell this fixes the panic:
diff --git a/sys/fs/nfsclient/nfs_clvfsops.c b/sys/fs/nfsclient/nfs_clvfsops.c
index af0e33b..966688f 100644
--- a/sys/fs/nfsclient/nfs_clvfsops.c
+++ b/sys/fs/nfsclient/nfs_clvfsops.c
@@ -1136,7 +1136,8 @@ nfs_mount(struct mount *mp)
out:
if (!error) {
MNT_ILOCK(mp);
- mp->mnt_kern_flag |= (MNTK_MPSAFE|MNTK_LOOKUP_SHARED);
+ mp->mnt_kern_flag |= MNTK_MPSAFE | MNTK_LOOKUP_SHARED |
+ MNTK_NO_IOPF;
MNT_IUNLOCK(mp);
}
return (error);
I'm not quite sure why that is, but I can now run both the sample code above
and the dovecot configure script without panics.
--
Kristof
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201206251130.q5PBUEXl099764>