From: Josh Wu <josh.wu@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fs: fat: fix bug when write size is less than a sector size
Date: Tue, 23 Jul 2013 18:16:18 +0800 [thread overview]
Message-ID: <51EE57F2.9040408@atmel.com> (raw)
In-Reply-To: <20130719112034.C5F09380ADF@gemini.denx.de>
Hi, Dear Wolfgang Denk
On 7/19/2013 7:20 PM, Wolfgang Denk wrote:
> Dear Josh Wu,
>
> In message <51E90A3D.6000007@atmel.com> you wrote:
>>> Why would this be needed? The case of a partial write is covered
>>> further down below in the code, in the "if (size % mydata->sect_size)"
>>> part...
>> The call of disk_write() will pass the sector size as 0. That will cause
>> the mmc driver stalled.
> I think instead of "sector size" you mean the number of sectors. The
> sector size is fixed.
yes, I mean the number of sectors.
>
> Big question: why should we call disk_write() at all when the count is
> zero? Maybe a simple
>
> if ((size / mydata->sect_size) > 0) {
> if (disk_write(startsect, size / mydata->sect_size, buffer) < 0) {
> ...
> }
> }
>
> would fix this issue?
I agree with above changes. It make the logical clearer:
Step 1. write buffer in sectors. If buffer size is less than one
sector we don't need to call disk_write() with zero sector.
Step 2. write remain buffer in one sector.
So I think I will send a v2 patch according to your suggestion. Thanks.
>
>
> Best regards,
>
> Wolfgang Denk
>
Best Regards,
Josh Wu
prev parent reply other threads:[~2013-07-23 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 8:07 [U-Boot] [PATCH] fs: fat: fix bug when write size is less than a sector size Josh Wu
2013-07-18 8:24 ` Wolfgang Denk
2013-07-19 9:43 ` Josh Wu
2013-07-19 11:20 ` Wolfgang Denk
2013-07-23 10:16 ` Josh Wu [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=51EE57F2.9040408@atmel.com \
--to=josh.wu@atmel.com \
--cc=u-boot@lists.denx.de \
/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.