From: Hyunchul Lee <hyc.lee@gmail.com>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: linux-cifs <linux-cifs@vger.kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steve French <smfrench@gmail.com>
Subject: Re: [PATCH v2] ksmbd: smbd: fix missing client's memory region invalidation
Date: Wed, 12 Jan 2022 09:09:05 +0900 [thread overview]
Message-ID: <CANFS6bahayu7kq6aq3SUcGSKhingopEhdSTZ4M+-MMf=EhGzSw@mail.gmail.com> (raw)
In-Reply-To: <CAKYAXd-a=8eAE023ECCoBKPD3L+q=Jb=Sem17VSVcheeryt9Dw@mail.gmail.com>
2022년 1월 11일 (화) 오후 10:21, Namjae Jeon <linkinjeon@kernel.org>님이 작성:
>
> 2022-01-11 20:57 GMT+09:00, Hyunchul Lee <hyc.lee@gmail.com>:
> > if the Channel of a SMB2 WRITE request is
> > SMB2_CHANNEL_RDMA_V1_INVALIDTE, a client
> > does not invalidate its memory regions but
> > ksmbd must do it by sending a SMB2 WRITE response
> > with IB_WR_SEND_WITH_INV.
> >
> > But if errors occur while processing a SMB2
> > READ/WRITE request, ksmbd sends a response
> > with IB_WR_SEND. So a client could use memory
> > regions already in use.
> >
> > Signed-off-by: Hyunchul Lee <hyc.lee@gmail.com>
> > ---
> > changes from v1:
> > - factor out setting a remote key to a helper functions.
> Can we make it as one helper function if desc, Channel,
> ChannelInfoOffset, ChannelInfoLength are given as arguments?
>
Okay, I will change it.
> >
> > fs/ksmbd/smb2pdu.c | 58 +++++++++++++++++++++++++++++++++++-----------
> > 1 file changed, 44 insertions(+), 14 deletions(-)
> >
> > diff --git a/fs/ksmbd/smb2pdu.c b/fs/ksmbd/smb2pdu.c
> > index ced8f949a4d6..b87969576642 100644
> > --- a/fs/ksmbd/smb2pdu.c
> > +++ b/fs/ksmbd/smb2pdu.c
> > @@ -6124,13 +6124,11 @@ static noinline int smb2_read_pipe(struct ksmbd_work
> > *work)
> > return err;
> > }
> >
> > -static ssize_t smb2_read_rdma_channel(struct ksmbd_work *work,
> > - struct smb2_read_req *req, void *data_buf,
> > - size_t length)
> > +static int smb2_set_remote_key_for_rdma_read(struct ksmbd_work *work,
> > + struct smb2_read_req *req)
> Can we make it as one helper function if desc, Channel,
> ChannelInfoOffset, ChannelInfoLength are given as arguments? i.e.
> smb2_set_remote_key_for_rdma().
>
> > {
> > struct smb2_buffer_desc_v1 *desc =
> > (struct smb2_buffer_desc_v1 *)&req->Buffer[0];
> > - int err;
> >
> > if (work->conn->dialect == SMB30_PROT_ID &&
> > req->Channel != SMB2_CHANNEL_RDMA_V1)
> > @@ -6143,6 +6141,16 @@ static ssize_t smb2_read_rdma_channel(struct
> > ksmbd_work *work,
> > work->need_invalidate_rkey =
> > (req->Channel == SMB2_CHANNEL_RDMA_V1_INVALIDATE);
> > work->remote_key = le32_to_cpu(desc->token);
> > + return 0;
> > +}
> > +
> > +static ssize_t smb2_read_rdma_channel(struct ksmbd_work *work,
> > + struct smb2_read_req *req, void *data_buf,
> > + size_t length)
> > +{
> > + struct smb2_buffer_desc_v1 *desc =
> > + (struct smb2_buffer_desc_v1 *)&req->Buffer[0];
> > + int err;
> >
> > err = ksmbd_conn_rdma_write(work->conn, data_buf, length,
> > le32_to_cpu(desc->token),
> > @@ -6179,6 +6187,13 @@ int smb2_read(struct ksmbd_work *work)
> > return smb2_read_pipe(work);
> > }
> >
> > + if (req->Channel == SMB2_CHANNEL_RDMA_V1_INVALIDATE ||
> > + req->Channel == SMB2_CHANNEL_RDMA_V1) {
> > + err = smb2_set_remote_key_for_rdma_read(work, req);
> > + if (err)
> > + goto out;
> > + }
> > +
> > fp = ksmbd_lookup_fd_slow(work, le64_to_cpu(req->VolatileFileId),
> > le64_to_cpu(req->PersistentFileId));
> > if (!fp) {
> > @@ -6352,17 +6367,11 @@ static noinline int smb2_write_pipe(struct
> > ksmbd_work *work)
> > return err;
> > }
> >
> > -static ssize_t smb2_write_rdma_channel(struct ksmbd_work *work,
> > - struct smb2_write_req *req,
> > - struct ksmbd_file *fp,
> > - loff_t offset, size_t length, bool sync)
> > +static int smb2_set_remote_key_for_rdma_write(struct ksmbd_work *work,
> > + struct smb2_write_req *req)
> > {
> > - struct smb2_buffer_desc_v1 *desc;
> > - char *data_buf;
> > - int ret;
> > - ssize_t nbytes;
> > -
> > - desc = (struct smb2_buffer_desc_v1 *)&req->Buffer[0];
> > + struct smb2_buffer_desc_v1 *desc =
> > + (struct smb2_buffer_desc_v1 *)&req->Buffer[0];
> >
> > if (work->conn->dialect == SMB30_PROT_ID &&
> > req->Channel != SMB2_CHANNEL_RDMA_V1)
> > @@ -6378,6 +6387,20 @@ static ssize_t smb2_write_rdma_channel(struct
> > ksmbd_work *work,
> > work->need_invalidate_rkey =
> > (req->Channel == SMB2_CHANNEL_RDMA_V1_INVALIDATE);
> > work->remote_key = le32_to_cpu(desc->token);
> > + return 0;
> > +}
> > +
> > +static ssize_t smb2_write_rdma_channel(struct ksmbd_work *work,
> > + struct smb2_write_req *req,
> > + struct ksmbd_file *fp,
> > + loff_t offset, size_t length, bool sync)
> > +{
> > + struct smb2_buffer_desc_v1 *desc;
> > + char *data_buf;
> > + int ret;
> > + ssize_t nbytes;
> > +
> > + desc = (struct smb2_buffer_desc_v1 *)&req->Buffer[0];
> >
> > data_buf = kvmalloc(length, GFP_KERNEL | __GFP_ZERO);
> > if (!data_buf)
> > @@ -6425,6 +6448,13 @@ int smb2_write(struct ksmbd_work *work)
> > return smb2_write_pipe(work);
> > }
> >
> > + if (req->Channel == SMB2_CHANNEL_RDMA_V1 ||
> > + req->Channel == SMB2_CHANNEL_RDMA_V1_INVALIDATE) {
> > + err = smb2_set_remote_key_for_rdma_write(work, req);
> > + if (err)
> > + goto out;
> > + }
> > +
> > if (!test_tree_conn_flag(work->tcon, KSMBD_TREE_CONN_FLAG_WRITABLE)) {
> > ksmbd_debug(SMB, "User does not have write permission\n");
> > err = -EACCES;
> > --
> > 2.25.1
> >
> >
--
Thanks,
Hyunchul
prev parent reply other threads:[~2022-01-12 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 11:57 [PATCH v2] ksmbd: smbd: fix missing client's memory region invalidation Hyunchul Lee
2022-01-11 13:21 ` Namjae Jeon
2022-01-12 0:09 ` Hyunchul Lee [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='CANFS6bahayu7kq6aq3SUcGSKhingopEhdSTZ4M+-MMf=EhGzSw@mail.gmail.com' \
--to=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=senozhatsky@chromium.org \
--cc=smfrench@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).