a bug detected in ubifs

ZHANG Hui P Hui.P.Zhang at alcatel-sbell.com.cn
Tue May 16 19:25:44 PDT 2017

On Tue, May 9, 2017 at 7:18 AM, ZHANG Hui P <Hui.P.Zhang at alcatel-sbell.com.cn> wrote:
>          Then I dump the lpt, and checked the pnode at 8:24749 , it is
> LEB 8:24749, pnode,  0:128408:1, 0:176:0, 0:130160:1, 0:128448:1  //the print order is :        for (i = 0; i < UBIFS_LPT_FANOUT; i++) {
>                                                                                                                                   printk(KERN_CONT "%d:%d:%d", pnode.lprops[i].free,
> pnode.lprops[i].dirty,pnode.lprops[i].flags);
>          so the problem is the lprops[2], which dirty is 130160, howerver ,the leb_size is 129024, so it is returned "-EINVAL" while calling "validate_pnode"
>          do you see this problem before? Or can you give me some suggestion for the further investgate?

I have one issue on my radar which could be related, but not sure.
What kernel version is this?

From: Richard Weinberger [mailto:richard at nod.at] 
Sent: 2017年5月10日 15:13
Cc: linux-mtd at lists.infradead.org
Subject: Re: a bug detected in ubifs

Am 10.05.2017 um 02:21 schrieb ZHANG Hui P:
> Hi Richard:
>     The kernel version is quite old:

So, first thing would be back-porting all UBIFS fixes to this kernel. Maybe Artem fixed this a long time ago...


-----Original Message-----
Hi Richard:
	For this bug is not reproduced , I'm not sure update to latest ubifs version can fix it. Can you tell me about the root cause of this issue?

More information about the linux-mtd mailing list