From 5793d80109ac881a1e2a84307a4372f92b97cae0 Mon Sep 17 00:00:00 2001 From: James Simmons Date: Sat, 18 Aug 2018 12:07:12 -0400 Subject: [PATCH] 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 Reviewed-on: https://review.whamcloud.com/33025 Reviewed-by: Andreas Dilger Tested-by: Jenkins Tested-by: Maloo Reviewed-by: Bobi Jam Reviewed-by: Oleg Drokin --- lustre/llite/lproc_llite.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/lustre/llite/lproc_llite.c b/lustre/llite/lproc_llite.c index 113989d..f585dd6 100644 --- 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); -- 1.8.3.1