From: Richard Weinberger <richard@nod.at>
To: Tao Ren <taoren@fb.com>
Cc: Andrew Jeffery <andrew@aj.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: kernel BUG at fs/jffs2/gc.c:395!
Date: Mon, 26 Aug 2019 00:29:28 +0200 (CEST) [thread overview]
Message-ID: <216516045.73889.1566772168645.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <4dee9f54-1cf4-94ca-4ddc-2b1f8892d9b1@fb.com>
----- Ursprüngliche Mail -----
> Von: "Tao Ren" <taoren@fb.com>
> An: "Richard Weinberger" <richard.weinberger@gmail.com>, "Andrew Jeffery" <andrew@aj.id.au>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>, "OpenBMC Maillist" <openbmc@lists.ozlabs.org>
> 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@aj.id.au> 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/
next prev parent reply other threads:[~2019-08-25 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 23:09 kernel BUG at fs/jffs2/gc.c:395! Tao Ren
2019-08-20 23:11 ` Tao Ren
2019-08-21 0:06 ` Andrew Jeffery
2019-08-21 0:20 ` Tao Ren
2019-08-25 19:22 ` Richard Weinberger
2019-08-25 22:08 ` Tao Ren
2019-08-25 22:29 ` Richard Weinberger [this message]
2019-08-27 4:42 ` Tao Ren
2019-08-28 0:08 ` [Potential Spoof] " Tao Ren
2019-08-26 0:33 ` Andrew Jeffery
2019-08-26 7:42 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=216516045.73889.1566772168645.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=andrew@aj.id.au \
--cc=linux-mtd@lists.infradead.org \
--cc=openbmc@lists.ozlabs.org \
--cc=taoren@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).