mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Renaud Barbier <Renaud.Barbier@ametek.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
	Barebox List <barebox@lists.infradead.org>
Subject: RE: file system crash
Date: Tue, 17 Mar 2026 14:31:47 +0000	[thread overview]
Message-ID: <SJ0PR07MB976610EF68958EB992C538E0EC41A@SJ0PR07MB9766.namprd07.prod.outlook.com> (raw)
In-Reply-To: <62cdd7a2-f712-44e9-8f3f-785a7af0e659@pengutronix.de>

I meant ARM Cortex-A9

> -----Original Message-----
> From: Ahmad Fatoum <a.fatoum@pengutronix.de>
> Sent: 17 March 2026 11:16
> To: Renaud Barbier <Renaud.Barbier@ametek.com>; Barebox List
> <barebox@lists.infradead.org>
> Subject: Re: file system crash
> 
> ***NOTICE*** This came from an external source. Use caution when
> replying, clicking links, or opening attachments.
> 
> Hello Renaud,
> 
> On 3/17/26 11:58 AM, Renaud Barbier wrote:
> > I have a BSP (not upstreamed) using a ARMv9 that I rebased fromv2025.06
> to 2026.01. This board has a SPI NOR with a UBI volume.
> > The system starts perfectly.
> 
> ARMv9 or ARM9?
> 
> Can you rerun with CONFIG_KASAN=y and report the output?
> 
> Thanks,
> Ahmad
> 
> >
> > When doing an umount or ls -l or reset barebox crashes. Debugging the
> code,  the cdevname pointer in destroy_inode is sometimes (set to 0xffffffff)
> or the string corrupted. Also below the filename is corrupted.
> > OWBOOT> / ls -l /mnt/primary
> > ERROR: RENAUD: cdev_by_name: name = cs0 filename = .ӿk
> > ERROR: RENAUD: cdev_by_name: name = m25p0 filename = .ӿk
> > ERROR: RENAUD: cdev_by_name: name = m25p0.barebox filename = .ӿk
> > ERROR: RENAUD: cdev_by_name: name = m25p0.secondary-barebox
> filename =
> > .ӿk
> > ERROR: RENAUD: cdev_by_name: name = m25p0.barebox-environment
> filename
> > = .ӿk … One can see the filename above is corrupted
> >
> > During reset:
> > ERROR: RENAUD: devfs_open: cdevname = m25p0.boot-vars
> > ERROR: RENAUD: cdev_by_name: name = cs0 filename = m25p0.boot-vars
> > ERROR: RENAUD: cdev_by_name: name = m25p0 filename = m25p0.boot-
> vars
> > ERROR: RENAUD: cdev_by_name: name = m25p0.barebox filename =
> > m25p0.boot-vars
> > ERROR: RENAUD: cdev_by_name: name = m25p0.secondary-barebox
> filename =
> > m25p0.boot-vars
> > ERROR: RENAUD: cdev_by_name: name = m25p0.barebox-environment
> filename
> > = m25p0.boot-vars
> > ERROR: RENAUD: cdev_by_name: name = m25p0.env-secondary filename
> =
> > m25p0.boot-vars
> > ERROR: RENAUD: cdev_by_name: name = m25p0.boot-vars filename =
> > m25p0.boot-vars
> > ERROR: RENAUD: cdev_by_name: found cdev m25p0.boot-vars
> > ERROR: fs_remove: ENTER
> > ERROR: ubifs_remove: ENTER
> > ERROR: ubifs_remove: END
> > ERROR: destroy_inode: inode = bff36380
> > ERROR: destroy_inode: cdevname@ = bff3647c
> > ERROR: RENAUD: destroy_inode cdevname: tc`, len = 5 ???
> > !block_is_last(block)common/tlsf.c 253 [<dfd8387c>]
> > (unwind_backtrace+0x0/0xe4) from [<dfd0a0dc>] (block_next+0x38/0x48)
> > [<dfd0a0dc>] (block_next+0x38/0x48) from [<dfd0a0f8>]
> > (block_link_next+0xc/0x14) [<dfd0a0f8>] (block_link_next+0xc/0x14)
> > from [<dfd0a76c>] (tlsf_free+0x48/0x108) [<dfd0a76c>]
> > (tlsf_free+0x48/0x108) from [<dfd65a74>] (destroy_inode+0x84/0x188)
> > [<dfd65a74>] (destroy_inode+0x84/0x188) from [<dfd671cc>]
> > (dentry_kill+0x18/0x54) [<dfd671cc>] (dentry_kill+0x18/0x54) from
> > [<dfd67e24>] (fs_remove+0x144/0x1b0) [<dfd67e24>]
> > (fs_remove+0x144/0x1b0) from [<dfd12230>]
> (devices_shutdown+0x54/0x68)
> > [<dfd12230>] (devices_shutdown+0x54/0x68) from [<dfd0221c>]
> > (shutdown_barebox+0x44/0x58) [<dfd0221c>]
> (shutdown_barebox+0x44/0x58)
> > from [<dfd48244>] (cmd_reset+0x114/0x154) [<dfd48244>]
> > (cmd_reset+0x114/0x154) from [<dfd06160>]
> (execute_command+0x4c/0x90)
> > [<dfd06160>] (execute_command+0x4c/0x90) from [<dfd0dc98>]
> > (run_list_real.isra.0+0x810/0x8c0)
> > [<dfd0dc98>] (run_list_real.isra.0+0x810/0x8c0) from [<dfd0d13c>]
> > (parse_stream_outer+0x130/0x1f4) [<dfd0d13c>]
> > (parse_stream_outer+0x130/0x1f4) from [<dfd0df04>]
> > (run_shell+0x74/0xb4) [<dfd0df04>] (run_shell+0x74/0xb4) from
> > [<dfd01e80>] (start_barebox+0x58/0x9c) [<dfd01e80>]
> > (start_barebox+0x58/0x9c) from [<dfd7f1b8>]
> > (barebox_non_pbl_start+0xc4/0xdc) [<dfd7f1b8>]
> > (barebox_non_pbl_start+0xc4/0xdc) from [<dfd00004>]
> > (__bare_init_start+0x0/0x10)
> >
> > Again, it seems there is memory corruption of cdevname
> >
> > Has anybody seen this?
> >
> > Note this is not happening with barebox v2025.12.0 and I did notice
> > there was lots of rework on the fs directory from v2026.01
> >
> >
> >
> 
> --
> Pengutronix e.K.                  |                             |
> Steuerwalder Str. 21              |
> https://urldefense.com/v3/__http://www.pengutronix.de/__;!!HKOSU0g!Hv
> VLvDMwr4aG6adXKP423MJRiCOajT_knP3fHFk3vN4LRN7EFCIpUvSk44un5KtT
> BGf-4O9jlbZGI0ejeILvpghDZVQ$   |
> 31137 Hildesheim, Germany         | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |


  reply	other threads:[~2026-03-17 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 10:58 Renaud Barbier
2026-03-17 11:15 ` Ahmad Fatoum
2026-03-17 14:31   ` Renaud Barbier [this message]
2026-03-25 13:39     ` Renaud Barbier

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=SJ0PR07MB976610EF68958EB992C538E0EC41A@SJ0PR07MB9766.namprd07.prod.outlook.com \
    --to=renaud.barbier@ametek.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@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