LU-10824 llite: don't use ll_mnt to get fstype name

Originally lustre would report using the fstype proc file either
'lustre' or 'llite'. This required us to query struct super_block
but its been a very long time since that is the case. This also
removes a direct use of ll_mnt. The fix is simply report 'lustre'.

Test-Parameters: trivial

Change-Id: Ia766c8e0a027e58a48de8fa6e2756238e20312b2
Signed-off-by: James Simmons <uja.ornl@yahoo.com>
Reviewed-on: https://review.whamcloud.com/33025
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Tested-by: Jenkins
Tested-by: Maloo <hpdd-maloo@intel.com>
Reviewed-by: Bobi Jam <bobijam@hotmail.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>

diff --git a/lustre/llite/lproc_llite.c b/lustre/llite/lproc_llite.c
index 113989d..f585dd6 100644 (file)
--- a/lustre/llite/lproc_llite.c
+++ b/lustre/llite/lproc_llite.c
@@ -245,10 +245,7 @@ LUSTRE_RO_ATTR(client_type);
 static ssize_t fstype_show(struct kobject *kobj, struct attribute *attr,
                           char *buf)
 {
-       struct ll_sb_info *sbi = container_of(kobj, struct ll_sb_info,
-                                             ll_kset.kobj);
-
-       return sprintf(buf, "%s\n", sbi->ll_mnt.mnt->mnt_sb->s_type->name);
+       return sprintf(buf, "lustre\n");
 }
 LUSTRE_RO_ATTR(fstype);