From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'hyeongseok.kim'" <hyeongseok@gmail.com>
Cc: <linux-fsdevel@vger.kernel.org>,
"'Sungjong Seo'" <sj1557.seo@samsung.com>
Subject: RE: [PATCH] exfat: fix range validation error in alloc and free cluster
Date: Fri, 5 Jun 2020 16:53:48 +0900 [thread overview]
Message-ID: <000501d63b0e$727aa6f0$576ff4d0$@samsung.com> (raw)
In-Reply-To: <3b5501d63a4d$4213b950$c63b2bf0$@samsung.com>
>
> > There is check error in range condition that can never be entered even
> > with invalid input.
> > Replace incorrent checking code with already existing valid checker.
> >
> > Signed-off-by: hyeongseok.kim <hyeongseok@gmail.com>
>
> Acked-by: Sungjong Seo <sj1557.seo@samsung.com>
>
> Looks good. Thank you!
Applied. Thanks!
prev parent reply other threads:[~2020-06-05 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200604045437epcas1p17180ef9b61d8ff1d4877c49755e766a2@epcas1p1.samsung.com>
2020-06-04 4:54 ` [PATCH] exfat: fix range validation error in alloc and free cluster hyeongseok.kim
2020-06-04 8:50 ` Sungjong Seo
2020-06-05 7:53 ` 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='000501d63b0e$727aa6f0$576ff4d0$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=hyeongseok@gmail.com \
--cc=linux-fsdevel@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).