From: Stefan Metzmacher <metze@samba.org>
To: Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>
Cc: Steve French <smfrench@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Shyam Prasad N <nspmangalore@gmail.com>,
Rohith Surabattula <rohiths.msft@gmail.com>,
Tom Talpey <tom@talpey.com>, Matthew Wilcox <willy@infradead.org>,
Jeff Layton <jlayton@kernel.org>,
linux-cifs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Long Li <longli@microsoft.com>,
Namjae Jeon <linkinjeon@kernel.org>
Subject: Re: [PATCH 11/12] cifs: Fix problem with encrypted RDMA data read
Date: Wed, 1 Feb 2023 15:00:55 +0100 [thread overview]
Message-ID: <4d3e67b1-478e-a10e-4f37-ff284183a988@samba.org> (raw)
In-Reply-To: <Y9pq+YUf/iFE8JUC@infradead.org>
Am 01.02.23 um 14:36 schrieb Christoph Hellwig:
> On Tue, Jan 31, 2023 at 06:28:54PM +0000, David Howells wrote:
>> When the cifs client is talking to the ksmbd server by RDMA and the ksmbd
>> server has "smb3 encryption = yes" in its config file, the normal PDU
>> stream is encrypted, but the directly-delivered data isn't in the stream
>> (and isn't encrypted), but is rather delivered by DDP/RDMA packets (at
>> least with IWarp).
>
> This really needs to be split into a separate backportable fix series.
> And it seems like Stefan has just send such a series.
My changes are triggered by this commit...
Now I'm looking more closely as I didn't understand it...
next prev parent reply other threads:[~2023-02-01 14:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 18:28 [PATCH 00/12] smb3: Use iov_iters down to the network transport and fix DIO page pinning David Howells
2023-01-31 18:28 ` [PATCH 01/12] netfs: Add a function to extract a UBUF or IOVEC into a BVEC iterator David Howells
2023-01-31 18:28 ` [PATCH 02/12] netfs: Add a function to extract an iterator into a scatterlist David Howells
2023-01-31 18:28 ` [PATCH 03/12] cifs: Implement splice_read to pass down ITER_BVEC not ITER_PIPE David Howells
2023-02-01 13:35 ` Christoph Hellwig
2023-01-31 18:28 ` [PATCH 04/12] cifs: Add a function to build an RDMA SGE list from an iterator David Howells
2023-01-31 18:28 ` [PATCH 05/12] cifs: Add a function to Hash the contents of " David Howells
2023-02-01 8:52 ` Herbert Xu
2023-02-01 14:36 ` David Howells
2023-02-02 0:55 ` Herbert Xu
2023-02-03 21:00 ` David Howells
2023-01-31 18:28 ` [PATCH 06/12] cifs: Add some helper functions David Howells
2023-01-31 18:28 ` [PATCH 07/12] cifs: Add a function to read into an iter from a socket David Howells
2023-01-31 18:28 ` [PATCH 09/12] cifs: Build the RDMA SGE list directly from an iterator David Howells
2023-01-31 18:28 ` [PATCH 10/12] cifs: Remove unused code David Howells
2023-01-31 18:28 ` [PATCH 11/12] cifs: Fix problem with encrypted RDMA data read David Howells
2023-02-01 13:36 ` Christoph Hellwig
2023-02-01 14:00 ` Stefan Metzmacher [this message]
2023-02-01 14:05 ` Stefan Metzmacher
2023-02-01 14:52 ` Stefan Metzmacher
2023-01-31 18:28 ` [PATCH 12/12] cifs: DIO to/from KVEC-type iterators should now work David Howells
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=4d3e67b1-478e-a10e-4f37-ff284183a988@samba.org \
--to=metze@samba.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jlayton@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=nspmangalore@gmail.com \
--cc=rohiths.msft@gmail.com \
--cc=smfrench@gmail.com \
--cc=tom@talpey.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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