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] f2fs: check filename length in recover_dentry
Date: Mon, 23 Dec 2013 10:28:52 +0800 [thread overview]
Message-ID: <002101ceff86$d50072c0$7f015840$@samsung.com> (raw)
In-Reply-To: <1387761931.2101.289.camel@kjgkr>
Hi Kim,
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk.kim@samsung.com]
> Sent: Monday, December 23, 2013 9:26 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] f2fs: check filename length in recover_dentry
>
> 2013-12-21 (토), 18:01 +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.
> >
> > Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> > ---
> > fs/f2fs/dir.c | 3 ---
> > fs/f2fs/recovery.c | 5 +++++
> > 2 files changed, 5 insertions(+), 3 deletions(-)
> >
> > diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c
> > index 0cc26ba..3f3b661 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..fdd175b 100644
> > --- a/fs/f2fs/recovery.c
> > +++ b/fs/f2fs/recovery.c
> > @@ -62,6 +62,11 @@ 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)) {
> > + err = -ENAMETOOLONG;
> > + goto out;
> > + }
>
> Have you seen this before?
Not yet.
> This is a trivial bug case, so, if you have got this bug, we should fix
> the bug first instead of adding any workaround patch.
What I worry about is that not only f2fs bug lead to this trivial problem,
but also other program with operation in raw disk could do this.
> Let's add WARN_ON() at least.
Alright.
Thanks.
> Thanks,
>
> > retry:
> > de = f2fs_find_entry(dir, &name, &page);
> > if (de && inode->i_ino == le32_to_cpu(de->ino))
>
> --
> Jaegeuk Kim
> Samsung
prev parent reply other threads:[~2013-12-23 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 10:01 [PATCH 1/3] f2fs: check filename length in recover_dentry Chao Yu
2013-12-23 1:25 ` Jaegeuk Kim
2013-12-23 2:28 ` 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='002101ceff86$d50072c0$7f015840$@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).