From: Xiubo Li <xiubli@redhat.com>
To: Hu Weiwen <sehuww@mail.scut.edu.cn>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] ceph: don't truncate file in atomic_open
Date: Fri, 1 Jul 2022 09:31:44 +0800 [thread overview]
Message-ID: <6f7d30bf-a83d-efe6-4cd0-53e4f56ef352@redhat.com> (raw)
In-Reply-To: <20220630020010.17148-1-sehuww@mail.scut.edu.cn>
On 6/30/22 10:00 AM, Hu Weiwen wrote:
> Clear O_TRUNC from the flags sent in the MDS create request.
>
> `atomic_open' is called before permission check. We should not do any
> modification to the file here. The caller will do the truncation
> afterward.
>
> Fixes: 124e68e74099 ("ceph: file operations")
> Signed-off-by: Hu Weiwen <sehuww@mail.scut.edu.cn>
> ---
> fs/ceph/file.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ceph/file.c b/fs/ceph/file.c
> index da59e836a06e..a5ecb97b6f41 100644
> --- a/fs/ceph/file.c
> +++ b/fs/ceph/file.c
> @@ -757,6 +757,11 @@ int ceph_atomic_open(struct inode *dir, struct dentry *dentry,
> /* If it's not being looked up, it's negative */
> return -ENOENT;
> }
> + /*
> + * Do not truncate the file, since atomic_open is called before the
> + * permission check. The caller will do the truncation afterward.
> + */
> + flags &= ~O_TRUNC;
> retry:
> /* do the open */
> req = prepare_open_request(dir->i_sb, flags, mode);
> @@ -807,9 +812,7 @@ int ceph_atomic_open(struct inode *dir, struct dentry *dentry,
> }
>
> set_bit(CEPH_MDS_R_PARENT_LOCKED, &req->r_req_flags);
> - err = ceph_mdsc_do_request(mdsc,
> - (flags & (O_CREAT|O_TRUNC)) ? dir : NULL,
> - req);
> + err = ceph_mdsc_do_request(mdsc, (flags & O_CREAT) ? dir : NULL, req);
> if (err == -ENOENT) {
> dentry = ceph_handle_snapdir(req, dentry);
> if (IS_ERR(dentry)) {
> --
> 2.25.1
>
Merged into the testing branch. Thanks Weiwen!
-- Xiubo
prev parent reply other threads:[~2022-07-01 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 2:00 [PATCH] ceph: don't truncate file in atomic_open Hu Weiwen
2022-07-01 1:31 ` Xiubo Li [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=6f7d30bf-a83d-efe6-4cd0-53e4f56ef352@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sehuww@mail.scut.edu.cn \
/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