Re: kernel BUG at fs/jffs2/gc.c:395!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- Ursprüngliche Mail -----
> Von: "Tao Ren" <taoren@xxxxxx>
> An: "Richard Weinberger" <richard.weinberger@xxxxxxxxx>, "Andrew Jeffery" <andrew@xxxxxxxx>
> CC: "linux-mtd" <linux-mtd@xxxxxxxxxxxxxxxxxxx>, "OpenBMC Maillist" <openbmc@xxxxxxxxxxxxxxxx>
> Gesendet: Montag, 26. August 2019 00:08:08
> Betreff: Re: kernel BUG at fs/jffs2/gc.c:395!

> On 8/25/19 12:22 PM, Richard Weinberger wrote:
>> On Wed, Aug 21, 2019 at 2:06 AM Andrew Jeffery <andrew@xxxxxxxx> wrote:
>>> Looks like a lack of robustness to filesystem corruption to me. LWN
>> 
>> What exactly makes you think so?
>> The inode cache entry is in state INO_STATE_UNCHECKED while GC run,
>> which is not allowed.
>> 
>> Tao, is the error persistent or did it happen only once?
> 
> Hi Richard,
> 
> It rarely happens (~1 out of 1000 machines in my environment), but once it
> happens, it's persistent: the machine will fall into reboot loop due to the
> crash.

Can you provide me an image of the filesystem such that I can have a look?
An image where the issue is persistent...

Thanks,
//richard

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/




[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux