From: Chao Yu <chao2.yu@samsung.com>
To: jaegeuk.kim@samsung.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH 1/3 V2] f2fs: check filename length in recover_dentry
Date: Thu, 26 Dec 2013 10:53:39 +0800 [thread overview]
Message-ID: <000001cf01e5$c9e8a7c0$5db9f740$@samsung.com> (raw)
In-Reply-To: <1388012129.2101.302.camel@kjgkr>
Hi,
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk.kim@samsung.com]
> Sent: Thursday, December 26, 2013 6:55 AM
> To: Chao Yu
> Cc: linux-fsdevel@vger.kernel.org; linux-kernel@vger.kernel.org; linux-f2fs-devel@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH 1/3 V2] f2fs: check filename length in recover_dentry
>
> Hi,
>
> 2013-12-23 (월), 11:12 +0800, Chao Yu:
> > In current flow, we will get Null return value of f2fs_find_entry in
> > recover_dentry when name.len is bigger than F2FS_NAME_LEN, and then we
> > still add this inode into its dir entry.
> > To avoid this situation, we must check filename length before we use it.
> >
> > Another point is that we could remove the code of checking filename length
> > In f2fs_find_entry, because f2fs_lookup will be called previously to ensure of
> > validity of filename length.
>
> The f2fs_find_entry is called by f2fs_unlink and f2fs_rename too.
As I check code and test, f2fs_unlink and f2fs_rename is protected by
f2fs_lookup well.
Oldfile/newfile/deletedfile name length is check previously in f2fs_lookup.
> So, you can't remove this, instead it'd be better remove it from
> f2fs_lookup.
I think verification of filename length could not be removed from lookup.
Ever you remove it, we could create file in f2fs device with filename length
that vfs not supported.
In my test, kernel seems not be stable after that kind of file created in f2fs.
> Thanks,
>
> >
> > V2:
> > o add WARN_ON() as Jaegeuk Kim suggested.
> >
> > Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> > ---
> > fs/f2fs/dir.c | 3 ---
> > fs/f2fs/recovery.c | 6 ++++++
> > 2 files changed, 6 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c
> > index 07ad850..f0b4630 100644
> > --- a/fs/f2fs/dir.c
> > +++ b/fs/f2fs/dir.c
> > @@ -190,9 +190,6 @@ struct f2fs_dir_entry *f2fs_find_entry(struct inode *dir,
> > unsigned int max_depth;
> > unsigned int level;
> >
> > - if (unlikely(namelen > F2FS_NAME_LEN))
> > - return NULL;
> > -
> > if (npages == 0)
> > return NULL;
> >
> > diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
> > index a3f4542..4d411a2 100644
> > --- a/fs/f2fs/recovery.c
> > +++ b/fs/f2fs/recovery.c
> > @@ -62,6 +62,12 @@ static int recover_dentry(struct page *ipage, struct inode *inode)
> >
> > name.len = le32_to_cpu(raw_inode->i_namelen);
> > name.name = raw_inode->i_name;
> > +
> > + if (unlikely(name.len > F2FS_NAME_LEN)) {
> > + WARN_ON(1);
> > + err = -ENAMETOOLONG;
> > + goto out;
> > + }
> > retry:
> > de = f2fs_find_entry(dir, &name, &page);
> > if (de && inode->i_ino == le32_to_cpu(de->ino))
>
> --
> Jaegeuk Kim
> Samsung
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-12-26 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 3:12 [PATCH 1/3 V2] f2fs: check filename length in recover_dentry Chao Yu
2013-12-25 22:55 ` Jaegeuk Kim
2013-12-26 2:53 ` Chao Yu [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='000001cf01e5$c9e8a7c0$5db9f740$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).