It turns out this is only a RHEL6 bug. I (stupidly) made the assumption that since the RHEL6 patch cleanly applied to upstream, both streams worked in the same way... which is not the case. With upstream, this mtab code is not even compiled when the libmount code is enabled. Secondly, with later systems /etc/mtab is symbolically linked to /proc/mounts, making the file read-only. Finally when /etc/mtabs is a regular file and is writeable, the SIGXFSZ signal is handled properly in lock_mtab() so there is no corruption. Sorry for the noise. steved. On 10/19/2011 11:34 AM, Steve Dickson wrote: > This patch is a following on to commit 7a802337. Using the > tool in https://bugzilla.redhat.com/show_bug.cgi?id=695916 > caused the fflush() and fclose() to fail in turn causing > corruption in the mtab. > > The failures were in the internals of both calls. Switch those > calls with the actual system calls eliminated the failures. > > Signed-off-by: Steve Dickson <steved@xxxxxxxxxx> > --- > support/nfs/nfs_mntent.c | 4 ++-- > 1 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/support/nfs/nfs_mntent.c b/support/nfs/nfs_mntent.c > index a2118a2..b80f270 100644 > --- a/support/nfs/nfs_mntent.c > +++ b/support/nfs/nfs_mntent.c > @@ -117,7 +117,7 @@ void > nfs_endmntent (mntFILE *mfp) { > if (mfp) { > if (mfp->mntent_fp) > - fclose(mfp->mntent_fp); > + close(fileno(mfp->mntent_fp)); > if (mfp->mntent_file) > free(mfp->mntent_file); > free(mfp); > @@ -147,7 +147,7 @@ nfs_addmntent (mntFILE *mfp, struct mntent *mnt) { > free(m3); > free(m4); > if (res >= 0) { > - res = fflush(mfp->mntent_fp); > + res = fsync(fileno(mfp->mntent_fp)); > if (res < 0) > /* Avoid leaving a corrupt mtab file */ > ftruncate(fileno(mfp->mntent_fp), length); -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
