From: Richard Weinberger <richard@nod.at>
To: 李傲傲 <Carson.Li1@unisoc.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: ubifs: read bad node type in ubifs_tnc_read_wbuf
Date: Tue, 14 Jan 2020 09:09:36 +0100 (CET) [thread overview]
Message-ID: <1323907091.20398.1578989376426.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <5077cb7894bc4b95b09389059edf0ddc@shmbx04.spreadtrum.com>
----- Ursprüngliche Mail -----
> Von: "李傲傲" <Carson.Li1@unisoc.com>
> An: "richard" <richard@nod.at>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>
> Gesendet: Dienstag, 14. Januar 2020 02:09:54
> Betreff: RE: ubifs: read bad node type in ubifs_tnc_read_wbuf
> On Monday, January 13, 2020 7:49 AM Richard <richard@nod.at> wrote:
>>
>>Do you have a test/reproducer for this issue?
>>
> I find out this issue from cases left over which used to happen frequently.
> But when it comes to me, an one month's stress testing doesn't reproduce it.
> it is only occasionally found on products that returned by costumer，but
> with no logs added before to analysis it.
>
>
> The kernel log I pasted before is one of the previous spot, including some
> logs added to analysis it.
> There are two more cases with the same appearance:
Is it always DATAHD which is being garbage collected?
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-01-14 8:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e2d34800d72243ed85e8df63bb80f7ab@shmbx04.spreadtrum.com>
[not found] ` <ce621148db0e4f9c80f32c348975663a@shmbx04.spreadtrum.com>
[not found] ` <ae16d475c0d24c1ba6ab18f1e766e928@shmbx04.spreadtrum.com>
[not found] ` <46e2f6ca11a442f38d476d4346e8034c@shmbx04.spreadtrum.com>
2020-01-12 23:48 ` ubifs: read bad node type in ubifs_tnc_read_wbuf Richard Weinberger
2020-01-14 1:09 ` 李傲傲 (Carson Li1/9542)
2020-01-14 8:09 ` Richard Weinberger [this message]
2020-01-14 8:28 ` 李傲傲 (Carson Li1/9542)
2020-01-14 11:01 ` 李傲傲 (Carson Li1/9542)
2020-01-14 23:16 ` Richard Weinberger
2020-01-16 0:54 ` 李傲傲 (Carson Li1/9542)
2020-02-19 12:03 ` 李傲傲 (Carson Li1/9542)
2020-02-26 12:11 ` Hou Tao
2020-02-27 1:18 ` 李傲傲 (Carson Li1/9542)
2020-02-27 6:34 ` Hou Tao
2020-02-27 6:49 ` 李傲傲 (Carson Li1/9542)
2020-03-02 1:39 ` Hou Tao
2020-03-02 3:12 ` 李傲傲 (Carson Li1/9542)
2020-03-02 6:35 ` Hou Tao
2020-03-02 7:56 ` 李傲傲 (Carson Li1/9542)
2020-03-02 10:23 ` Hou Tao
2020-03-03 1:21 ` 李傲傲 (Carson Li1/9542)
2020-01-10 9:10 李傲傲 (Carson Li1/9542)
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=1323907091.20398.1578989376426.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=Carson.Li1@unisoc.com \
--cc=linux-mtd@lists.infradead.org \
/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).