From: hujianyang <hujianyang@huawei.com>
To: Seunghun Lee <waydi1@gmail.com>
Cc: <miklos@szeredi.hu>, <linux-unionfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] ovl: Fix condition check for workdir
Date: Fri, 9 Jan 2015 10:40:32 +0800 [thread overview]
Message-ID: <54AF3FA0.8010808@huawei.com> (raw)
In-Reply-To: <1420720880-28459-1-git-send-email-waydi1@gmail.com>
On 2015/1/8 20:41, Seunghun Lee wrote:
> When file system is mounted read-only workdir is not needed.
>
> Signed-off-by: Seunghun Lee <waydi1@gmail.com>
> ---
> fs/overlayfs/super.c | 35 +++++++++++++++++++++++------------
> 1 file changed, 23 insertions(+), 12 deletions(-)
>
> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
> index 84f3144..4e50617 100644
> --- a/fs/overlayfs/super.c
> +++ b/fs/overlayfs/super.c
> @@ -30,6 +30,7 @@ struct ovl_config {
> char *lowerdir;
> char *upperdir;
> char *workdir;
> + bool is_rw;
> };
>
> /* private information held for overlayfs's superblock */
> @@ -515,10 +516,11 @@ static int ovl_show_options(struct seq_file *m, struct dentry *dentry)
> struct ovl_fs *ufs = sb->s_fs_info;
>
> seq_printf(m, ",lowerdir=%s", ufs->config.lowerdir);
> - if (ufs->config.upperdir) {
> + if (ufs->config.upperdir)
> seq_printf(m, ",upperdir=%s", ufs->config.upperdir);
> + if (ufs->config.is_rw)
> seq_printf(m, ",workdir=%s", ufs->config.workdir);
> - }
> +
> return 0;
> }
>
> @@ -822,16 +824,27 @@ static int ovl_fill_super(struct super_block *sb, void *data, int silent)
>
> sb->s_stack_depth = 0;
> if (ufs->config.upperdir) {
> - /* FIXME: workdir is not needed for a R/O mount */
> + err = ovl_mount_dir(ufs->config.upperdir, &upperpath);
> + if (err)
> + goto out_free_config;
> +
> + sb->s_stack_depth = upperpath.mnt->mnt_sb->s_stack_depth;
> + }
> +
> + /* If the upper fs is r/o or nonexistent, we mark overlayfs r/o too */
> + if (!upperpath.mnt || (upperpath.mnt->mnt_sb->s_flags & MS_RDONLY)) {
> + ufs->config.is_rw = false;
> + sb->s_flags |= MS_RDONLY;
> + } else {
> + ufs->config.is_rw = true;
> + }
Hi Seunghun,
A partition can be mounted with ro flag. I think workdir is not
needed in this way either.
> +
> + if (ufs->config.is_rw) {
> if (!ufs->config.workdir) {
> pr_err("overlayfs: missing 'workdir'\n");
> goto out_free_config;
> }
>
> - err = ovl_mount_dir(ufs->config.upperdir, &upperpath);
> - if (err)
> - goto out_free_config;
> -
> err = ovl_mount_dir(ufs->config.workdir, &workpath);
> if (err)
> goto out_put_upperpath;
> @@ -844,8 +857,8 @@ static int ovl_fill_super(struct super_block *sb, void *data, int silent)
> pr_err("overlayfs: workdir and upperdir must be separate subtrees\n");
> goto out_put_workpath;
> }
> - sb->s_stack_depth = upperpath.mnt->mnt_sb->s_stack_depth;
> }
> +
> err = -ENOMEM;
> lowertmp = kstrdup(ufs->config.lowerdir, GFP_KERNEL);
> if (!lowertmp)
> @@ -884,7 +897,9 @@ static int ovl_fill_super(struct super_block *sb, void *data, int silent)
> pr_err("overlayfs: failed to clone upperpath\n");
> goto out_put_lowerpath;
> }
> + }
>
> + if (ufs->config.is_rw) {
> ufs->workdir = ovl_workdir_create(ufs->upper_mnt, workpath.dentry);
> err = PTR_ERR(ufs->workdir);
> if (IS_ERR(ufs->workdir)) {
> @@ -914,10 +929,6 @@ static int ovl_fill_super(struct super_block *sb, void *data, int silent)
> ufs->numlower++;
> }
>
> - /* If the upper fs is r/o or nonexistent, we mark overlayfs r/o too */
> - if (!ufs->upper_mnt || (ufs->upper_mnt->mnt_sb->s_flags & MS_RDONLY))
> - sb->s_flags |= MS_RDONLY;
> -
> sb->s_d_op = &ovl_dentry_operations;
>
> err = -ENOMEM;
>
next prev parent reply other threads:[~2015-01-09 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 12:41 [PATCH] ovl: Fix condition check for workdir Seunghun Lee
2015-01-09 2:40 ` hujianyang [this message]
2015-01-09 18:11 ` Seunghun Lee
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=54AF3FA0.8010808@huawei.com \
--to=hujianyang@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=waydi1@gmail.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 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).