From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
smfrench@gmail.com, hyc.lee@gmail.com, senozhatsky@chromium.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 3/4] ksmbd: increment reference count of parent fp
Date: Tue, 1 Mar 2022 13:21:55 +0900 [thread overview]
Message-ID: <Yh2fY6F8n/8KvMEH@google.com> (raw)
In-Reply-To: <20220228234833.10434-3-linkinjeon@kernel.org>
On (22/03/01 08:48), Namjae Jeon wrote:
> diff --git a/fs/ksmbd/smb2pdu.c b/fs/ksmbd/smb2pdu.c
> index 3151ab7d7410..03c3733e54e4 100644
> --- a/fs/ksmbd/smb2pdu.c
> +++ b/fs/ksmbd/smb2pdu.c
> @@ -5764,8 +5764,10 @@ static int set_rename_info(struct ksmbd_work *work, struct ksmbd_file *fp,
> if (parent_fp) {
> if (parent_fp->daccess & FILE_DELETE_LE) {
> pr_err("parent dir is opened with delete access\n");
> + ksmbd_fd_put(work, parent_fp);
> return -ESHARE;
> }
> + ksmbd_fd_put(work, parent_fp);
> }
And also in ksmbd_validate_entry_in_use()?
> next:
> return smb2_rename(work, fp, user_ns, rename_info,
> diff --git a/fs/ksmbd/vfs_cache.c b/fs/ksmbd/vfs_cache.c
> index 0974d2e972b9..c4d59d2735f0 100644
> --- a/fs/ksmbd/vfs_cache.c
> +++ b/fs/ksmbd/vfs_cache.c
> @@ -496,6 +496,7 @@ struct ksmbd_file *ksmbd_lookup_fd_inode(struct inode *inode)
> list_for_each_entry(lfp, &ci->m_fp_list, node) {
> if (inode == file_inode(lfp->filp)) {
> atomic_dec(&ci->m_count);
> + lfp = ksmbd_fp_get(lfp);
> read_unlock(&ci->m_lock);
> return lfp;
> }
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-03-01 4:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 23:48 [PATCH 1/4] ksmbd: remove internal.h include Namjae Jeon
2022-02-28 23:48 ` [PATCH 2/4] ksmbd: remove filename in ksmbd_file Namjae Jeon
2022-03-01 4:14 ` Sergey Senozhatsky
2022-03-01 8:34 ` Namjae Jeon
2022-03-01 11:21 ` Sergey Senozhatsky
2022-02-28 23:48 ` [PATCH 3/4] ksmbd: increment reference count of parent fp Namjae Jeon
2022-03-01 4:21 ` Sergey Senozhatsky [this message]
2022-03-01 8:40 ` Namjae Jeon
2022-02-28 23:48 ` [PATCH v3 4/4] ksmbd: fix racy issue from using ->d_parent and ->d_name Namjae Jeon
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=Yh2fY6F8n/8KvMEH@google.com \
--to=senozhatsky@chromium.org \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=smfrench@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