From: "Sungjong Seo" <sj1557.seo@samsung.com>
To: "'Dan Carpenter'" <dan.carpenter@linaro.org>,
<oe-kbuild@lists.linux.dev>, <Yuezhang.Mo@sony.com>,
<linkinjeon@kernel.org>
Cc: <lkp@intel.com>, <oe-kbuild-all@lists.linux.dev>,
<linux-fsdevel@vger.kernel.org>, <Andy.Wu@sony.com>,
<Wataru.Aoyama@sony.com>, <cpgs@samsung.com>,
<sj1557.seo@samsung.com>
Subject: RE: [PATCH v5 1/2] exfat: change to get file size from DataLength
Date: Tue, 5 Dec 2023 11:11:56 +0900 [thread overview]
Message-ID: <1891546521.01701742382249.JavaMail.epsvc@epcpadp4> (raw)
In-Reply-To: <4308b820-7d69-42e6-8b07-205e81add314@suswa.mountain>
[snip]
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 515 if (ret < 0)
{
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 516 if
(rw
> & WRITE)
>
> This code works and the checker doesn't complain about it, but for
> consistency I think it should be if (rw == WRITE).
>
> 5f2aa075070cf5b Namjae Jeon 2020-03-02 517
> exfat_write_failed(mapping, size);
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 518
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 519 if
> (ret != -EIOCBQUEUED)
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 520
> return ret;
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 521 } else
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 522 size
=
> pos + ret;
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 523
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 524 /* zero the
> unwritten part in the partially written block */
> 6642222a5afe775 Yuezhang.Mo@sony.com 2023-11-30 @525 if ((rw &
READ)
> && pos < ei->valid_size && ei->valid_size < size) {
>
> I think this should be rw == READ.
You're definitely right.
READ is 0, so it always be false.
Dear Yuezhang,
Can you please send v6 again for this?
It would be nice to include fixes for a minor issue reported
by Kernel test robot.
Thanks
next prev parent reply other threads:[~2023-12-05 2:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 9:58 [PATCH v4 0/2] exfat: get file size from DataLength Yuezhang.Mo
2023-11-30 3:09 ` [PATCH v5 " Yuezhang.Mo
2023-12-05 10:16 ` [PATCH v6 " Yuezhang.Mo
2023-12-12 4:12 ` Namjae Jeon
[not found] ` <PUZPR04MB63160A6FD8E7EF04E4342B1B818EA@PUZPR04MB6316.apcprd04.prod.outlook.com>
2023-12-12 10:29 ` Yuezhang.Mo
2023-12-13 4:14 ` Namjae Jeon
2023-12-05 10:16 ` [PATCH v6 1/2] exfat: change to " Yuezhang.Mo
2023-12-05 10:16 ` [PATCH v6 2/2] exfat: do not zero the extended part Yuezhang.Mo
2023-11-30 3:09 ` [PATCH v5 1/2] exfat: change to get file size from DataLength Yuezhang.Mo
2023-11-30 17:10 ` kernel test robot
2023-11-30 18:04 ` kernel test robot
2023-12-01 8:29 ` Dan Carpenter
2023-12-05 2:11 ` Sungjong Seo [this message]
2023-12-05 3:30 ` Namjae Jeon
[not found] ` <PUZPR04MB6316B8BAC361A5B2A70FD5098185A@PUZPR04MB6316.apcprd04.prod.outlook.com>
2023-12-05 5:29 ` Yuezhang.Mo
2023-11-30 3:09 ` [PATCH v5 2/2] exfat: do not zero the extended part Yuezhang.Mo
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=1891546521.01701742382249.JavaMail.epsvc@epcpadp4 \
--to=sj1557.seo@samsung.com \
--cc=Andy.Wu@sony.com \
--cc=Wataru.Aoyama@sony.com \
--cc=Yuezhang.Mo@sony.com \
--cc=cpgs@samsung.com \
--cc=dan.carpenter@linaro.org \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).