[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <488305749.81257.1695653971403.JavaMail.zimbra@nod.at>
Date: Mon, 25 Sep 2023 16:59:31 +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>
>> Given this a second thought. I don't think a NAND driver is allowed to return
>> less than requests bytes and setting EBADMSG.
>> UBI's IO path has a comment on that:
>>
>> /*
>> * The driver should never return -EBADMSG if it failed to read
>> * all the requested data. But some buggy drivers might do
>> * this, so we change it to -EIO.
>> */
>> if (read != len && mtd_is_eccerr(err)) {
>> ubi_assert(0);
>> err = -EIO;
>> }
>
> Interesting. Shall we add this check to the mtd_read() path as well?
>
> Maybe with a WARN_ON()?
WARN_ON_ONCE(), please. But yes, let's add it.
Thanks,
//richard
Powered by blists - more mailing lists