From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Nikhil Kashyap H R <nikhil.kashyap@iwave-global.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Zhihao Cheng <chengzhihao1@huawei.com>,
linux-arm-kernel@lists.infradead.org, michal.simek@amd.com,
vigneshr@ti.com, richard@nod.at, tudor.ambarus@linaro.org,
pratyush@kernel.org
Subject: Re: Request for Input on UBI System Issues
Date: Mon, 2 Sep 2024 08:50:40 +0200 [thread overview]
Message-ID: <20240902085040.1f3759dd@xps-13> (raw)
In-Reply-To: <f1efa224-ad32-4839-a7ea-4fce2ca9abe2@iwave-global.com>
Hi Nikhil,
> > 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)
> > [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
prev parent reply other threads:[~2024-09-02 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c58aa13e-2b46-416e-b67c-b4a6858b62df@iwave-global.com>
2024-08-31 22:20 ` Request for Input on UBI System Issues Linus Walleij
[not found] ` <3f87ce50-ddd9-4819-9064-149d520151b3@iwave-global.com>
[not found] ` <f1efa224-ad32-4839-a7ea-4fce2ca9abe2@iwave-global.com>
2024-09-02 6:50 ` Miquel Raynal [this message]
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=20240902085040.1f3759dd@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=chengzhihao1@huawei.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=michal.simek@amd.com \
--cc=nikhil.kashyap@iwave-global.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.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