mirror of https://lore.kernel.org/lkml/
 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-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs crypto: check context consistent for rename2
Date: Thu, 28 May 2015 19:29:20 -0700	[thread overview]
Message-ID: <20150529022920.GA18700@jaegeuk-mac02.mot.com> (raw)
In-Reply-To: <20150528170726.GB11631@jaegeuk-mac02.mot.com>

On Thu, May 28, 2015 at 10:07:26AM -0700, Jaegeuk Kim wrote:
> Hi Chao,
> 
> On Mon, May 25, 2015 at 06:07:02PM +0800, Chao Yu wrote:
> > For exchange rename, we should check context consistent of encryption
> > between new_dir and old_inode or old_dir and new_inode. Otherwise
> > inheritance of parent's encryption context will be broken.
> > 
> > Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> > ---
> >  fs/f2fs/namei.c | 9 +++++++++
> >  1 file changed, 9 insertions(+)
> > 
> > diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
> > index daed09c..3188464 100644
> > --- a/fs/f2fs/namei.c
> > +++ b/fs/f2fs/namei.c
> > @@ -754,6 +754,15 @@ static int f2fs_cross_rename(struct inode *old_dir, struct dentry *old_dentry,
> >  	int old_nlink = 0, new_nlink = 0;
> >  	int err = -ENOENT;
> >  
> > +	if ((old_dir != new_dir) &&
> > +		(!f2fs_is_child_context_consistent_with_parent(new_dir,
> > +							old_inode) ||
> > +		!f2fs_is_child_context_consistent_with_parent(old_dir,
> > +							new_inode))) {
> > +		err = -EPERM;
> > +		goto out;
> > +	}
> > +
> 
> Seems like we need this?
> 
> ---
>  fs/f2fs/namei.c | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
> index 55d0d27..4772c14 100644
> --- a/fs/f2fs/namei.c
> +++ b/fs/f2fs/namei.c
> @@ -756,6 +756,21 @@ static int f2fs_cross_rename(struct inode *old_dir, struct dentry *old_dentry,
>  	int old_nlink = 0, new_nlink = 0;
>  	int err = -ENOENT;
>  
> +	if (old_dir != new_dir) {
> +		if (f2fs_encrypted_inode(new_dir) &&
> +			!f2fs_is_child_context_consistent_with_parent(new_dir,
> +							old_inode)) {
> +			err = -EPERM;
> +			goto out;
> +		}
> +		if (f2fs_encrypted_inode(old_dir) &&
> +			!f2fs_is_child_context_consistent_with_parent(old_dir,
> +							new_inode)) {
> +			err = -EPERM;
> +			goto out;
> +		}
> +	}

It needs to sync with ext4 patch published by Ted.

Thanks,

> +
>  	f2fs_balance_fs(sbi);
>  
>  	old_entry = f2fs_find_entry(old_dir, &old_dentry->d_name, &old_page);
> -- 
> 2.1.1
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2015-05-29  2:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 10:07 Chao Yu
2015-05-28 17:07 ` Jaegeuk Kim
2015-05-29  2:29   ` Jaegeuk Kim [this message]
2015-05-29  2:54     ` [f2fs-dev] " Chao Yu

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=20150529022920.GA18700@jaegeuk-mac02.mot.com \
    --to=jaegeuk@kernel.org \
    --cc=chao2.yu@samsung.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --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

all inboxes | Powered by JetHome®