From: Richard Weinberger <richard@nod.at>
To: Eddie James <eajames@linux.ibm.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
chengzhihao1 <chengzhihao1@huawei.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
sethjenkins@google.com, adobriyan <adobriyan@gmail.com>
Subject: Re: UBIFS errors since Linux 5.15
Date: Fri, 7 Nov 2025 21:03:19 +0100 (CET) [thread overview]
Message-ID: <55378147.159026.1762545799936.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <068ba254-0053-46d5-bff4-74c948d2e8ac@linux.ibm.com>
Eddie,
----- Ursprüngliche Mail -----
> Von: "Eddie James" <eajames@linux.ibm.com>
> An: "linux-mtd" <linux-mtd@lists.infradead.org>, "richard" <richard@nod.at>, "chengzhihao1" <chengzhihao1@huawei.com>,
> "OpenBMC Maillist" <openbmc@lists.ozlabs.org>, "linux-kernel" <linux-kernel@vger.kernel.org>, sethjenkins@google.com,
> "adobriyan" <adobriyan@gmail.com>
> Gesendet: Freitag, 7. November 2025 18:38:54
> Betreff: UBIFS errors since Linux 5.15
> Hello,
>
> We are updating some BMC (Aspeed AST2600, ARM32) systems that were on
> Linux 5.4 but observe consistent UBIFS errors with Linux 5.15 and later.
> The errors seem to vary; there is a sampling below.
>
>
> We performed a git bisect and came up with the following commit, which
> of course is completely unrelated to UBIFS. Reverting it does prevent
> the issue... Does anyone have any suggestions?
>
> commit 33fc9e26b7cb39f0d4219c875a2451802249c225
> Author: Seth Jenkins <sethjenkins@google.com>
> Date: Thu Oct 27 11:36:52 2022 -0400
That's indeed strange.
Are you absolutely sure that this commit triggers the issue?
E.g. if you revert it on top of 5.15 the issue vanishes and when you
re-apply it, the issue is back?
Thanks,
//richard
next prev parent reply other threads:[~2025-11-07 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 17:38 Eddie James
2025-11-07 20:03 ` Richard Weinberger [this message]
2025-11-07 23:49 ` Eddie James
2025-11-08 3:03 ` Zhihao Cheng
2025-11-08 3:10 ` Zhihao Cheng
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=55378147.159026.1762545799936.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=adobriyan@gmail.com \
--cc=chengzhihao1@huawei.com \
--cc=eajames@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=openbmc@lists.ozlabs.org \
--cc=sethjenkins@google.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
all inboxes | Powered by JetHome®