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? -- Thanks, //richard ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
Re: kernel BUG at fs/jffs2/gc.c:395!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: kernel BUG at fs/jffs2/gc.c:395!
- From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
- Date: Sun, 25 Aug 2019 21:22:56 +0200
- Cc: Tao Ren <taoren@xxxxxx>, OpenBMC Maillist <openbmc@xxxxxxxxxxxxxxxx>, "linux-mtd@xxxxxxxxxxxxxxxxxxx" <linux-mtd@xxxxxxxxxxxxxxxxxxx>
- In-reply-to: <afe2b8f2-d1be-4cd2-971a-b13c1e38da67@www.fastmail.com>
- References: <e8bde724-46fd-4264-ea3f-a84a792bcad8@fb.com> <236e95be-a2cd-3b44-36c5-121678f7c009@fb.com> <afe2b8f2-d1be-4cd2-971a-b13c1e38da67@www.fastmail.com>
- Follow-Ups:
- Re: kernel BUG at fs/jffs2/gc.c:395!
- From: Andrew Jeffery
- Re: kernel BUG at fs/jffs2/gc.c:395!
- From: Tao Ren
- Re: kernel BUG at fs/jffs2/gc.c:395!
- References:
- kernel BUG at fs/jffs2/gc.c:395!
- From: Tao Ren
- Re: kernel BUG at fs/jffs2/gc.c:395!
- From: Tao Ren
- Re: kernel BUG at fs/jffs2/gc.c:395!
- From: Andrew Jeffery
- kernel BUG at fs/jffs2/gc.c:395!
- Prev by Date: Re: ubifs_check_node: bad CRC
- Next by Date: Re: Debian 10 boot problems with corrupted rw /var
- Previous by thread: Re: kernel BUG at fs/jffs2/gc.c:395!
- Next by thread: Re: kernel BUG at fs/jffs2/gc.c:395!
- Index(es):
 |