From: Richard Weinberger <richard@nod.at>
To: Tudor Ambarus <tudor.ambarus@linaro.org>
Cc: Jan Kara <jack@suse.cz>,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
chengzhihao1 <chengzhihao1@huawei.com>, Yu Hao <yhao016@ucr.edu>
Subject: Re: [PATCH] ubi: Reject device with erasesize 0
Date: Fri, 1 Sep 2023 11:38:38 +0200 (CEST) [thread overview]
Message-ID: <1877357554.4324.1693561118827.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <26cd7b8f-abcc-410f-a7c7-e691999f4e3b@linaro.org>
----- Ursprüngliche Mail -----
> Von: "Tudor Ambarus" <tudor.ambarus@linaro.org>
> An: "Jan Kara" <jack@suse.cz>, "richard" <richard@nod.at>, "Miquel Raynal" <miquel.raynal@bootlin.com>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>, "chengzhihao1" <chengzhihao1@huawei.com>, "Yu Hao" <yhao016@ucr.edu>
> Gesendet: Freitag, 1. September 2023 11:25:11
> Betreff: Re: [PATCH] ubi: Reject device with erasesize 0
> Hi, Richard,
>
> On 8/31/23 12:11, Jan Kara wrote:
>> In principle MTD device with erasesize 0 can exist and it is possible to create
>> them e.g. via KVM. If that happens UBI layer currently crashes
>
> mtd devices are organized in erase blocks, having a mtd with erase
> size zero looks suspicious to me. Do you know if there are any mtd
> devices with erasesize of zero?
Yes. There are. So, the fix is fine.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2023-09-01 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 11:11 [PATCH] ubi: Reject device with erasesize 0 Jan Kara
2023-09-01 1:11 ` Zhihao Cheng
2023-09-01 6:17 ` Richard Weinberger
2023-09-01 9:09 ` Jan Kara
2023-09-01 9:25 ` Tudor Ambarus
2023-09-01 9:37 ` Jan Kara
2023-09-01 10:22 ` Tudor Ambarus
2023-09-01 9:38 ` Richard Weinberger [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=1877357554.4324.1693561118827.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=chengzhihao1@huawei.com \
--cc=jack@suse.cz \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=tudor.ambarus@linaro.org \
--cc=yhao016@ucr.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.