[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1385178592.80194.1695634307277.JavaMail.zimbra@nod.at>
Date: Mon, 25 Sep 2023 11:31:47 +0200 (CEST)
From: Richard Weinberger <richard@....at>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: ZhaoLong Wang <wangzhaolong1@...wei.com>,
Vignesh Raghavendra <vigneshr@...com>,
linux-mtd <linux-mtd@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
chengzhihao1 <chengzhihao1@...wei.com>,
yi zhang <yi.zhang@...wei.com>,
yangerkun <yangerkun@...wei.com>
Subject: Re: [RFC] mtd: Fix error code loss in mtdchar_read() function.
----- Ursprüngliche Mail -----
> Von: "Miquel Raynal" <miquel.raynal@...tlin.com>
>> As pointed out by Miquel, the comment makes it clean that this behavior is
>> on purpose. If we return now all of a sudden -EBADMSG for the described
>> scenario we might even break existing MTD userspace.
>
> The bugzilla link in the commit log [1] mentions:
Ups.
> * dd would just stop in the middle without showing errors
> -> we probably don't care, we expect the userspace to know this is
> NAND when dealing with mtd devices directly, dd is not mtd-aware
> anyway.
Yep. That's fine.
> * ubiformat would loop forever
> -> that one needs attention I guess :)
Hmm. Let me check the source.
Thanks,
//richard
Powered by blists - more mailing lists