Thread (1 message) 1 message, 1 author, 2024-09-02

Re: Request for Input on UBI System Issues

flat view

From: Miquel Raynal <miquel.raynal@bootlin.com>
Date: 2024-09-02 06:51:54

Hi Nikhil,
quoted
PC is at ____cache_alloc+0x60/0x790
[<c01ec1c4>] (____cache_alloc) from [<c01ecb94>] (__kmalloc+0x58/0xb8)
[<c01ecb94>] (__kmalloc) from [<c01c1f64>] (kvmalloc_node+0x40/0x74)
[<c01c1f64>] (kvmalloc_node) from [<c021c3d4>] (seq_read+0x17c/0x38c)
[<c021c3d4>] (seq_read) from [<c0250420>] (proc_reg_read+0x58/0x6c)
[<c0250420>] (proc_reg_read) from [<c01fbfb8>] (__vfs_read+0x2c/0xe4)
[<c01fbfb8>] (__vfs_read) from [<c01fc0fc>] (vfs_read+0x8c/0xa8)
[<c01fc0fc>] (vfs_read) from [<c01fc2d0>] (ksys_read+0x74/0xc4)
[<c01fc2d0>] (ksys_read) from [<c0101000>] (ret_fast_syscall+0x0/0x54)
quoted
[2024-06-11 08:35:05.502] PC is at ____cache_alloc+0x60/0x790
[2024-06-11 08:35:05.653] [<c01ea94c>] (____cache_alloc) from > [<c01eb31c>] (__kmalloc+0x58/0xb8)
[2024-06-11 08:35:05.659] [<c01eb31c>] (__kmalloc) from [<c01c00f0>] > (kvmalloc_node+0x40/0x74)
[2024-06-11 08:35:05.669] [<c01c00f0>] (kvmalloc_node) from > [<c021ac4c>] (seq_read+0x17c/0x38c)
[2024-06-11 08:35:05.672] [<c021ac4c>] (seq_read) from [<c01fa740>] > (__vfs_read+0x2c/0xe4)
[2024-06-11 08:35:05.679] [<c01fa740>] (__vfs_read) from [<c01fa884>] > (vfs_read+0x8c/0xa8)
[2024-06-11 08:35:05.682] [<c01fa884>] (vfs_read) from [<c01faa58>] > (ksys_read+0x74/0xc4)
[2024-06-11 08:35:05.689] [<c01faa58>] (ksys_read) from [<c0101000>] > (ret_fast_syscall+0x0/0x54)
...
I am using a NAND device for testing UBI commands. My workflow
involves initializing the device by formatting it with UBI, creating a
volume, and attaching that partition.

After detaching the partition, I perform some raw NAND operations.
I guess modifying manually the content is supposed to crash, but not
crash the kernel like that. What did you do exactly? Both in terms of
modifications and access when it crashes (looks like you're using
'cat').
However, when I attempt to mount the UBI node afterward, I encounter 
above listed *case no 1* and *case no 2* error message.
This issue suggests a problem with the compatibility of the UBI and 
UBIFS modules with the currently running kernel, which needs to be
resolved to successfully mount the UBI node after performing raw
operations.
Thanks,
Miquèl
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help