staging/lustre/llite: Fix obd name after c&p error

From: Oleg Drokin <[email protected]>

commit 95745e9b1de2 ("staging: lustre: Use kasprintf.") introduced a copy and paste error causing two different obd types to be assigned same content causing lustre to fail on mount with a warning from procfs followed by a bizzare error about OST not having enough MDS capabilities.

This patch unbreaks Lustre client again.

---
This really came from nowhere and I do not see this patch in any archives of mailinglists I am subscribed to.
In fact Google cannot find it either.

 drivers/staging/lustre/lustre/llite/llite_lib.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

index ee4bd89..bf1ec27 100644
@@ -983,7 +983,7 @@ int ll_fill_super(struct super_block *sb, struct vfsmount *mnt)
 		goto out_free;
 	}
 
-	md = kasprintf(GFP_NOFS, "%s-%p", lprof->lp_dt, cfg->cfg_instance);
+	md = kasprintf(GFP_NOFS, "%s-%p", lprof->lp_md, cfg->cfg_instance);
 	if (!md) {
 		err = -ENOMEM;
 		goto out_free;

2.1.0

I was going to say something similar. It's not in linux-next either.

regards,
dan carpenter

It was sent to the outreachy kernel mailing list, as part of the intern application process.

Sorry for missing this cut and paste error, my fault in reviewing things.

It's not in linux-next as it's in my "staging-testing" branch, which I like to keep around for a day or so before mergeing to a non-rebasable branch that shows up in linux-next.

thanks,

greg k-h