public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Tomas Alvarez Vanoli <tomas.alvarez-vanoli@hitachienergy.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [BUG] UBIFS corruption on powerpc 32-bit targets
Date: Thu, 12 Feb 2026 09:19:41 +0800	[thread overview]
Message-ID: <01bac338-856c-599d-85d5-ed6485707310@huawei.com> (raw)
In-Reply-To: <DB9PR06MB7849403569974A214C101D77C263A@DB9PR06MB7849.eurprd06.prod.outlook.com>

在 2026/2/12 0:51, Tomas Alvarez Vanoli 写道:
>> What does 'application' mean?
> I meant just completely changing the kernel and rootfs that is there as a backup
> image and using a more recent kernel.
> Yes, it will prevent the problem too.
>>
>> Apply following patch in 6.12:
>> [...]
> 
> Unfortunately on my system this just gets stuck, because the only way
> write_orph_node gets called is through do_commit calling
> ubifs_orphan_end_commit, but that path is never executed (except when mounting).
> 
> I tried mounting with and without sync, same results.
> 

The 'sync' syscall will call ubifs_orphan_end_commit if the orhpan list 
is not empty.
ubifs_sync_fs -> ubifs_run_commit -> do_commit -> ubifs_orphan_end_commit

In ubifs_create, the new inode will be added into orphan list.
ubifs_create -> ubifs_new_inode -> ubifs_add_orphan

You can add some debug messages to check which condition is broken.
> Best Regards,
> Tomas
> .
> 


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

  reply	other threads:[~2026-02-12  1:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 10:30 [BUG] UBIFS corruption on powerpc 32-bit targets Tomas Alvarez Vanoli
2026-01-30  1:34 ` Zhihao Cheng
2026-02-03  9:12   ` Tomas Alvarez Vanoli
2026-02-04  4:54     ` Zhihao Cheng
2026-02-04 14:04       ` Tomas Alvarez Vanoli
2026-02-05  2:14         ` Zhihao Cheng
2026-02-05 15:47           ` Tomas Alvarez Vanoli
2026-02-06  2:21             ` Zhihao Cheng
2026-02-06 16:14               ` Tomas Alvarez Vanoli
2026-02-07  2:58                 ` Zhihao Cheng
2026-02-09 15:45                   ` Tomas Alvarez Vanoli
2026-02-10  2:38                     ` Zhihao Cheng
2026-02-10 16:40                       ` Tomas Alvarez Vanoli
2026-02-11  6:58                         ` Zhihao Cheng
2026-02-11  7:01                           ` Zhihao Cheng
2026-02-11 16:51                             ` Tomas Alvarez Vanoli
2026-02-12  1:19                               ` Zhihao Cheng [this message]
2026-02-12 15:43                                 ` Tomas Alvarez Vanoli
2026-02-13  1:16                                   ` 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=01bac338-856c-599d-85d5-ed6485707310@huawei.com \
    --to=chengzhihao1@huawei.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tomas.alvarez-vanoli@hitachienergy.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