All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Tetsuhiro Kohada'" <kohada.t2@gmail.com>
Cc: "'Mori.Takahiro@ab.MitsubishiElectric.co.jp'" 
	<Mori.Takahiro@ab.mitsubishielectric.co.jp>,
	"'Motai.Hirotaka@aj.MitsubishiElectric.co.jp'" 
	<Motai.Hirotaka@aj.mitsubishielectric.co.jp>,
	<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"'Sungjong Seo'" <sj1557.seo@samsung.com>,
	"'Namjae Jeon'" <linkinjeon@kernel.org>,
	"'Kohada.Tetsuhiro@dc.MitsubishiElectric.co.jp'" 
	<Kohada.Tetsuhiro@dc.mitsubishielectric.co.jp>
Subject: RE: [PATCH] exfat: optimize dir-cache
Date: Thu, 28 May 2020 14:05:52 +0900	[thread overview]
Message-ID: <015501d634ad$a8dcd680$fa968380$@samsung.com> (raw)
In-Reply-To: <22dfcd8a-4416-e2a7-b8a7-0375660ba465@gmail.com>

> >>>   > In order to prevent illegal accesses to bh and dentries, it
> >>> would be better to check validation for num and bh.
> >>>
> >>>   There is no new error checking for same reason as above.
> >>>
> >>>   I'll try to add error checking to this v2 patch.
> >>>   Or is it better to add error checking in another patch?
> >> The latter:)
> >> Thanks!
> >
> > Yes, the latter looks better.
> 
> I will do so.
> 
> I will post additional patches for error checking, after this patch is merged into tree.
> OK?
Okay.
> 
> 



  reply	other threads:[~2020-05-28  5:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200520075735epcas1p269372d222e25f3fd51b7979f5b7cdc61@epcas1p2.samsung.com>
2020-05-20  7:56 ` [PATCH] exfat: optimize dir-cache Tetsuhiro Kohada
2020-05-26  2:36   ` Sungjong Seo
2020-05-27  8:00     ` Kohada.Tetsuhiro
2020-05-27 11:29       ` Namjae Jeon
2020-05-27 14:25         ` Sungjong Seo
2020-05-28  0:12           ` Tetsuhiro Kohada
2020-05-28  5:05             ` Namjae Jeon [this message]
2020-05-28  4:42   ` Namjae Jeon
2020-06-01 12:08   ` Sungjong Seo
2020-06-02  6:33     ` Namjae Jeon

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='015501d634ad$a8dcd680$fa968380$@samsung.com' \
    --to=namjae.jeon@samsung.com \
    --cc=Kohada.Tetsuhiro@dc.mitsubishielectric.co.jp \
    --cc=Mori.Takahiro@ab.mitsubishielectric.co.jp \
    --cc=Motai.Hirotaka@aj.mitsubishielectric.co.jp \
    --cc=kohada.t2@gmail.com \
    --cc=linkinjeon@kernel.org \
    --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 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.