From: Jan Kara <jack@suse.cz>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 4/4] fsfreeze: return EINTR from mnt_want_write and mnt_want_write_file
Date: Mon, 29 Apr 2013 14:35:07 +0200 [thread overview]
Message-ID: <20130429123507.GB21982@quack.suse.cz> (raw)
In-Reply-To: <517A4087.9090704@gmail.com>
On Fri 26-04-13 10:53:27, Marco Stornelli wrote:
> Replaced sb_start_write with sb_start_write_killable inside
> mnt_want_write and mnt_want_write_file.
The patch looks good. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
>
> Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
> ---
> fs/namei.c | 6 ++++++
> fs/namespace.c | 8 ++++++--
> ipc/mqueue.c | 6 +++++-
> 3 files changed, 17 insertions(+), 3 deletions(-)
>
> diff --git a/fs/namei.c b/fs/namei.c
> index 57ae9c8..5f239fd 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -2750,6 +2750,8 @@ static int do_last(struct nameidata *nd, struct path *path,
> retry_lookup:
> if (op->open_flag & (O_CREAT | O_TRUNC | O_WRONLY | O_RDWR)) {
> error = mnt_want_write(nd->path.mnt);
> + if (error == -EINTR)
> + goto out;
> if (!error)
> got_write = true;
> /*
> @@ -3053,6 +3055,10 @@ struct dentry *kern_path_create(int dfd, const char *pathname,
>
> /* don't fail immediately if it's r/o, at least try to report other errors */
> err2 = mnt_want_write(nd.path.mnt);
> + if (err2 == -EINTR) {
> + dentry = ERR_PTR(-EINTR);
> + goto out;
> + }
> /*
> * Do the final lookup.
> */
> diff --git a/fs/namespace.c b/fs/namespace.c
> index af73554..db09ecb 100644
> --- a/fs/namespace.c
> +++ b/fs/namespace.c
> @@ -344,7 +344,9 @@ int mnt_want_write(struct vfsmount *m)
> {
> int ret;
>
> - sb_start_write(m->mnt_sb);
> + ret = sb_start_write_killable(m->mnt_sb);
> + if (ret < 0)
> + return ret;
> ret = __mnt_want_write(m);
> if (ret)
> sb_end_write(m->mnt_sb);
> @@ -404,7 +406,9 @@ int mnt_want_write_file(struct file *file)
> {
> int ret;
>
> - sb_start_write(file->f_path.mnt->mnt_sb);
> + ret = sb_start_write_killable(file->f_path.mnt->mnt_sb);
> + if (ret < 0)
> + return ret;
> ret = __mnt_want_write_file(file);
> if (ret)
> sb_end_write(file->f_path.mnt->mnt_sb);
> diff --git a/ipc/mqueue.c b/ipc/mqueue.c
> index e4e47f6..e8fdc03 100644
> --- a/ipc/mqueue.c
> +++ b/ipc/mqueue.c
> @@ -800,7 +800,11 @@ SYSCALL_DEFINE4(mq_open, const char __user *, u_name, int, oflag, umode_t, mode,
> if (fd < 0)
> goto out_putname;
>
> - ro = mnt_want_write(mnt); /* we'll drop it in any case */
> + ro = mnt_want_write(mnt);
> + if (ro == -EINTR) {
> + fd = ro;
> + goto out_putname;
> + }
> error = 0;
> mutex_lock(&root->d_inode->i_mutex);
> path.dentry = lookup_one_len(name->name, root, strlen(name->name));
> --
> 1.7.3.4
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-04-29 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 8:53 [PATCH 4/4] fsfreeze: return EINTR from mnt_want_write and mnt_want_write_file Marco Stornelli
2013-04-29 12:35 ` Jan Kara [this message]
2013-04-30 6:18 ` Marco Stornelli
-- strict thread matches above, loose matches on Subject: below --
2013-05-04 6:50 Marco Stornelli
2013-07-04 16:19 Gmail
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=20130429123507.GB21982@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--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).