From 124b74413e943ab9c02cdff2832d1d81dc9fda87 Mon Sep 17 00:00:00 2001 From: "J. Bruce Fields" Date: Thu, 28 Aug 2008 11:17:34 -0400 Subject: Remove redundant m_path field Contrary to the comment above its definition, the field m_path always has the same value as e_path: the *only* modifications of m_path are all of the form: strncpy(exp->m_export.m_path, exp->m_export.e_path, sizeof (exp->m_export.m_path) - 1); exp->m_export.m_path[sizeof (exp->m_export.m_path) - 1] = '\0'; So m_path is always just a copy of e_path. In places where we need to store a path to a submount of a CROSSMNT-exported filesystem, as in cache.c, we just use a local variable. Signed-off-by: J. Bruce Fields Signed-off-by: Steve Dickson --- support/include/nfslib.h | 5 ----- 1 file changed, 5 deletions(-) (limited to 'support/include') diff --git a/support/include/nfslib.h b/support/include/nfslib.h index 422b012..a51d79d 100644 --- a/support/include/nfslib.h +++ b/support/include/nfslib.h @@ -67,11 +67,6 @@ struct sec_entry { struct exportent { char * e_hostname; char e_path[NFS_MAXPATHLEN+1]; - /* The mount path may be different from the exported path due - to submount. It may change for every mount. The idea is we - set m_path every time when we process a mount. We should not - use it for anything else. */ - char m_path[NFS_MAXPATHLEN+1]; int e_flags; int e_anonuid; int e_anongid; -- cgit