From: Christian Riesch <christian.riesch@omicron.at>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: mtdchar: Exit write loop when hitting end of OTP memory
Date: Wed, 29 May 2013 15:19:45 +0200 [thread overview]
Message-ID: <51A60071.2060005@omicron.at> (raw)
In-Reply-To: <1369811298.5446.215.camel@sauron.fi.intel.com>
Artem,
Thank you again for your comments.
On 2013-05-29 09:08, Artem Bityutskiy wrote:
> On Fri, 2013-04-26 at 19:56 +0200, Christian Riesch wrote:
>> If a write to one time programmable memory (OTP) hits the end
>> of this memory area, no more data can be written and count does not
>> decrease anymore. We are trapped in the loop forever.
>>
>> Therefore drop the remaining data if retlen != len.
>>
>> Signed-off-by: Christian Riesch <christian.riesch@omicron.at>
>> ---
>> drivers/mtd/mtdchar.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/mtd/mtdchar.c b/drivers/mtd/mtdchar.c
>> index e0e59bf..70c18c2 100644
>> --- a/drivers/mtd/mtdchar.c
>> +++ b/drivers/mtd/mtdchar.c
>> @@ -321,6 +321,10 @@ static ssize_t mtdchar_write(struct file *file, const char __user *buf, size_t c
>> case MTD_FILE_MODE_OTP_USER:
>> ret = mtd_write_user_prot_reg(mtd, *ppos, len,
>> &retlen, kbuf);
>> +
>> + /* if we hit the end of otp memory, drop the rest */
>> + if (retlen != len)
>> + count -= len - retlen;
>> break;
>
> I think the problem is that 'mtd_write_user_prot_reg()' should return an
> error if you try to write more data than it is available. At least this
> is the behavior of 'mtd_write()'.
>
The OTP code for the AMD command set in my recent patchset is modeled
after the existing code in drivers/mtd/chips/cfi_cmdset_0001.c.
Therefore it has a ...walk() function that walks from chip to chip and
tries to write as much data as possible into the OTP memories of these
chips. Until the last iteration of this loop it does not know how much
OTP memory is available. Therefore, a check for insufficient OTP memory
and returning an error before writing any data is not possible.
Of course I could change my code to obtain the available OTP memory
before writing any data. But then the code in cfi_cmdset_0001.c would
still suffer from this issue.
What do you think?
Best regards, Christian
next prev parent reply other threads:[~2013-05-29 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 17:56 [PATCH] mtd: mtdchar: Exit write loop when hitting end of OTP memory Christian Riesch
2013-05-29 7:08 ` Artem Bityutskiy
2013-05-29 13:19 ` Christian Riesch [this message]
2013-05-29 13:56 ` Artem Bityutskiy
2013-05-29 14:27 ` Christian Riesch
2013-06-03 9:39 ` Artem Bityutskiy
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=51A60071.2060005@omicron.at \
--to=christian.riesch@omicron.at \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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.