From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 6/6] ovl: concurrent copy up of regular files
Date: Mon, 16 Jan 2017 13:31:21 +0200 [thread overview]
Message-ID: <CAOQ4uxiCfkkYs0e2Qjr=Mjt_OC54c6YDKJYv_k+WrA3amZ5fdg@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegva4NT=ssF5AQvh24Qdijuff--EKJ7PyP1TXN7qf5HMCw@mail.gmail.com>
On Mon, Jan 16, 2017 at 1:05 PM, Miklos Szeredi <miklos@szeredi.hu> wrote:
> On Sun, Jan 15, 2017 at 2:57 PM, Amir Goldstein <amir73il@gmail.com> wrote:
>> Now that copy up of regular file is done using O_TMPFILE,
>> we don't need to hold rename_lock throughout copy up.
>>
>> Use the copy up waitqueue to synchronize concurrent copy up
>> of the same file. Different regular files can be copied up
>> concurrently.
>>
>> The upper dir inode_lock is taken instead of rename_lock,
>> because it is needed for lookup and later for linking the
>> temp file, but it is released while copying up data.
>>
>> Suggested-by: Al Viro <viro@zeniv.linux.org.uk>
>> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
>> ---
>> fs/overlayfs/copy_up.c | 23 +++++++++++++++++++++++
>> 1 file changed, 23 insertions(+)
>>
>> diff --git a/fs/overlayfs/copy_up.c b/fs/overlayfs/copy_up.c
>> index d3b6c15..ddf5e2d 100644
>> --- a/fs/overlayfs/copy_up.c
>> +++ b/fs/overlayfs/copy_up.c
>> @@ -291,7 +291,14 @@ static int ovl_copy_up_locked(struct dentry *workdir, struct dentry *upperdir,
>> BUG_ON(upperpath.dentry != NULL);
>> upperpath.dentry = temp;
>>
>> + if (tmpfile)
>> + inode_unlock(udir);
>> +
>> err = ovl_copy_up_data(lowerpath, &upperpath, stat->size);
>> +
>> + if (tmpfile)
>> + inode_lock_nested(udir, I_MUTEX_PARENT);
>> +
>> if (err)
>> goto out_cleanup;
>> }
>> @@ -371,6 +378,19 @@ static int ovl_copy_up_one(struct dentry *parent, struct dentry *dentry,
>> return PTR_ERR(link);
>> }
>>
>> + if (tmpfile) {
>> + err = ovl_copy_up_start(dentry);
>> + /* err < 0: interrupted, err > 0: raced with another copy-up */
>> + if (unlikely(err)) {
>> + pr_debug("ovl_copy_up_start(%pd2) = %i\n", dentry, err);
>> + if (err > 0)
>> + err = 0;
>> + goto out_done;
>> + }
>> + /* lock_rename/unlock_rename will lock/unlock only upperdir */
>> + workdir = upperdir;
>
> Unnecessary obfuscation. Just do lock_inode(); ovl_copy_up_locked();
> unlokc_inode();.
>
upperdir still needs to be locked for ovl_set_timestamps(), so I can do:
+ inode_lock_nested(udir, I_MUTEX_PARENT)
+ } else {
>> if (lock_rename(workdir, upperdir) != NULL) {
>> pr_err("overlayfs: failed to lock workdir+upperdir\n");
...
>> out_unlock:
+ if (tmpfile)
+ inode_unlock(udir);
+ else
>> unlock_rename(workdir, upperdir);
>> + if (tmpfile)
>> + ovl_copy_up_end(dentry);
>> +out_done:
>> do_delayed_call(&done);
>>
>> return err;
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2017-01-16 11:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 13:57 [PATCH 0/6] ovl: concurrent copy up Amir Goldstein
2017-01-15 13:57 ` [PATCH 1/6] vfs: create vfs helper vfs_tmpfile() Amir Goldstein
2017-01-16 11:00 ` Miklos Szeredi
2017-01-16 11:19 ` Amir Goldstein
2017-01-16 13:22 ` Miklos Szeredi
2017-01-16 14:04 ` Amir Goldstein
2017-01-16 14:15 ` Miklos Szeredi
2017-01-15 13:57 ` [PATCH 2/6] ovl: check if upperdir fs supports O_TMPFILE Amir Goldstein
2017-01-16 14:02 ` Miklos Szeredi
2017-01-16 14:16 ` Amir Goldstein
2017-01-16 14:29 ` Miklos Szeredi
2017-01-15 13:57 ` [PATCH 3/6] ovl: rearrange code in ovl_copy_up_locked() Amir Goldstein
2017-01-15 13:57 ` [PATCH 4/6] ovl: copy up regular file using O_TMPFILE Amir Goldstein
2017-01-15 13:57 ` [PATCH 5/6] ovl: introduce copy up waitqueue Amir Goldstein
2017-01-15 13:57 ` [PATCH 6/6] ovl: concurrent copy up of regular files Amir Goldstein
2017-01-16 11:05 ` Miklos Szeredi
2017-01-16 11:31 ` Amir Goldstein [this message]
2017-01-16 11:58 ` [PATCH v2 " Amir Goldstein
2017-01-16 13:29 ` Miklos Szeredi
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='CAOQ4uxiCfkkYs0e2Qjr=Mjt_OC54c6YDKJYv_k+WrA3amZ5fdg@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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).