linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao2.yu@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: early check broken symlink length in the encrypted case
Date: Tue, 29 Dec 2015 16:45:56 -0800	[thread overview]
Message-ID: <20151230004556.GD13809@jaegeuk.local> (raw)
In-Reply-To: <00a701d141db$c2f7d480$48e77d80$@samsung.com>

Hi Chao,

On Tue, Dec 29, 2015 at 09:52:49AM +0800, Chao Yu wrote:
> Hi Jaegeuk,
> 
> > -----Original Message-----
> > From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> > Sent: Tuesday, December 29, 2015 7:32 AM
> > To: linux-kernel@vger.kernel.org; linux-fsdevel@vger.kernel.org;
> > linux-f2fs-devel@lists.sourceforge.net
> > Cc: Jaegeuk Kim
> > Subject: [f2fs-dev] [PATCH 1/3] f2fs: early check broken symlink length in the encrypted case
> > 
> > If link is broken, its len is zero, and we don't need to move forward.
> > 
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> > ---
> >  fs/f2fs/namei.c | 10 ++++++++--
> >  1 file changed, 8 insertions(+), 2 deletions(-)
> > 
> > diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
> > index fb41c80..5cc4128 100644
> > --- a/fs/f2fs/namei.c
> > +++ b/fs/f2fs/namei.c
> > @@ -931,7 +931,7 @@ static const char *f2fs_encrypted_follow_link(struct dentry *dentry, void
> > **cook
> >  {
> >  	struct page *cpage = NULL;
> >  	char *caddr, *paddr = NULL;
> > -	struct f2fs_str cstr;
> > +	struct f2fs_str cstr = FSTR_INIT(NULL, 0);
> >  	struct f2fs_str pstr = FSTR_INIT(NULL, 0);
> >  	struct inode *inode = d_inode(dentry);
> >  	struct f2fs_encrypted_symlink_data *sd;
> > @@ -952,6 +952,12 @@ static const char *f2fs_encrypted_follow_link(struct dentry *dentry, void
> > **cook
> >  	/* Symlink is encrypted */
> >  	sd = (struct f2fs_encrypted_symlink_data *)caddr;
> >  	cstr.len = le16_to_cpu(sd->len);
> > +
> > +	/* this is broken symlink case */
> > +	if (cstr.len == 0) {
> 
> This case seems rare, can we add unlikely here?

Agreed.
Will change them.

Thanks,

> 
> > +		res = -ENOENT;
> > +		goto errout;
> > +	}
> >  	cstr.name = kmalloc(cstr.len, GFP_NOFS);
> >  	if (!cstr.name) {
> >  		res = -ENOMEM;
> > @@ -960,7 +966,7 @@ static const char *f2fs_encrypted_follow_link(struct dentry *dentry, void
> > **cook
> >  	memcpy(cstr.name, sd->encrypted_path, cstr.len);
> > 
> >  	/* this is broken symlink case */
> > -	if (cstr.name[0] == 0 && cstr.len == 0) {
> > +	if (cstr.name[0] == 0) {
> 
> ditto.
> 
> Thanks,
> 
> >  		res = -ENOENT;
> >  		goto errout;
> >  	}
> > --
> > 2.5.4 (Apple Git-61)
> > 
> > 
> > ------------------------------------------------------------------------------
> > _______________________________________________
> > Linux-f2fs-devel mailing list
> > Linux-f2fs-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2015-12-30  0:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 23:31 [PATCH 1/3] f2fs: early check broken symlink length in the encrypted case Jaegeuk Kim
2015-12-28 23:31 ` [PATCH 2/3] f2fs: use i_size_read to get i_size Jaegeuk Kim
2015-12-29  9:18   ` [f2fs-dev] " Chao Yu
2015-12-30  0:53     ` Jaegeuk Kim
2015-12-28 23:31 ` [PATCH 3/3] f2fs: load largest extent all the time Jaegeuk Kim
2015-12-29  9:23   ` [f2fs-dev] " Chao Yu
2015-12-30  0:59     ` Jaegeuk Kim
2015-12-29  1:52 ` [PATCH 1/3] f2fs: early check broken symlink length in the encrypted case Chao Yu
2015-12-30  0:45   ` Jaegeuk Kim [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=20151230004556.GD13809@jaegeuk.local \
    --to=jaegeuk@kernel.org \
    --cc=chao2.yu@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).