From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Hyeongseok Kim'" <hyeongseok@gmail.com>, <sj1557.seo@samsung.com>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] exfat: fix wrong size update of stream entry by typo
Date: Fri, 10 Jul 2020 14:12:24 +0900 [thread overview]
Message-ID: <00b301d65678$b268b880$173a2980$@samsung.com> (raw)
In-Reply-To: <20200708095233.56131-1-hyeongseok@gmail.com>
> The stream.size field is updated to the value of create timestamp of the file entry. Fix this to use
> correct stream entry pointer.
>
> Fixes: 29bbb14bfc80 ("exfat: fix incorrect update of stream entry in __exfat_truncate()")
> Signed-off-by: Hyeongseok Kim <hyeongseok@gmail.com>
My bad, Pushed it into exfat #dev.
Thanks!
prev parent reply other threads:[~2020-07-10 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200708095242epcas1p2a106825fa23003abb184739703c594cc@epcas1p2.samsung.com>
2020-07-08 9:52 ` [PATCH] exfat: fix wrong size update of stream entry by typo Hyeongseok Kim
2020-07-10 5:12 ` Namjae Jeon [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='00b301d65678$b268b880$173a2980$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=hyeongseok@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
/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).