avoid plaintext rdma offload if encryption is required
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest3 patches 1 replyIn review
- v13 patches 2 repliesSuperseded
Changes in v2 from the cover letter
- Added missing Cc: list on commit 2/3
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | cifs: introduce cifs_io_parms in smb2_async_writev()fs/ | +39 | 0 replies | |
| 2/3 | cifs: split out smb3_use_rdma_offload() helperfs/ | +28 | 0 replies | |
| 3/3 | cifs: don't try to use rdma offload on encrypted connectionsfs/ | +4 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/3] avoid plaintext rdma offload if encryption is required
I think it is a security problem to send confidential data in plaintext over the wire, so we should avoid doing that even if rdma is in use.
We already have a similar check to prevent data integrity problems for rdma offload.
Modern Windows servers support signed and encrypted rdma offload, but we don't support this yet...
Changes v2:
- Added missing Cc: list on commit 2/3
Stefan Metzmacher (3):
cifs: introduce cifs_io_parms in smb2_async_writev()
cifs: split out smb3_use_rdma_offload() helper
cifs: don't try to use rdma offload on encrypted connections
fs/cifs/smb2pdu.c | 89 +++++++++++++++++++++++++++++++++++++---------- 1 file changed, 70 insertions(+), 19 deletions(-)
Signature · 1 line
2.34.1