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

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

[green]

From: Oleg Drokin <green@linuxhacker.ru>

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.

Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
CC: Navya Sri Nizamkari <navyasri.tech@gmail.com>
CC: Julia Lawall <julia.lawall@lip6.fr>
---
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(-)

diff --git a/drivers/staging/lustre/lustre/llite/llite_lib.c b/drivers/staging/lustre/lustre/llite/llite_lib.c
index ee4bd89..bf1ec27 100644
--- a/drivers/staging/lustre/lustre/llite/llite_lib.c
+++ b/drivers/staging/lustre/lustre/llite/llite_lib.c
@@ -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

Re: [PATCH] staging/lustre/llite: Fix obd name after c&p error

[Dan Carpenter]

On Tue, Mar 03, 2015 at 02:39:36AM -0500, green@linuxhacker.ru wrote:

> 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.

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

regards,
dan carpenter

Re: [PATCH] staging/lustre/llite: Fix obd name after c&p error

[Greg Kroah-Hartman]

On Tue, Mar 03, 2015 at 11:28:25AM +0300, Dan Carpenter wrote:
> On Tue, Mar 03, 2015 at 02:39:36AM -0500, green@linuxhacker.ru wrote:
> 
> > 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.
> 
> I was going to say something similar.  It's not in linux-next either.

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