mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Ceph fixes for 5.17-rc3
Date: Fri,  4 Feb 2022 14:15:18 +0100	[thread overview]
Message-ID: <20220204131518.13859-1-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit 26291c54e111ff6ba87a164d85d4a4e134b7315c:

  Linux 5.17-rc2 (2022-01-30 15:37:07 +0200)

are available in the Git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-5.17-rc3

for you to fetch changes up to 038b8d1d1ab1cce11a158d30bf080ff41a2cfd15:

  libceph: optionally use bounce buffer on recv path in crc mode (2022-02-02 18:50:36 +0100)

----------------------------------------------------------------
A patch to make it possible to disable zero copy path in the messenger
to avoid checksum or authentication tag mismatches and ensuing session
resets in case the destination buffer isn't guaranteed to be stable.

----------------------------------------------------------------
Ilya Dryomov (2):
      libceph: make recv path in secure mode work the same as send path
      libceph: optionally use bounce buffer on recv path in crc mode

 include/linux/ceph/libceph.h   |   1 +
 include/linux/ceph/messenger.h |   5 +
 net/ceph/ceph_common.c         |   7 ++
 net/ceph/messenger.c           |   4 +
 net/ceph/messenger_v1.c        |  54 ++++++++-
 net/ceph/messenger_v2.c        | 250 ++++++++++++++++++++++++++++++-----------
 6 files changed, 251 insertions(+), 70 deletions(-)

             reply	other threads:[~2022-02-04 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 13:15 Ilya Dryomov [this message]
2022-02-04 17:58 ` pr-tracker-bot

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=20220204131518.13859-1-idryomov@gmail.com \
    --to=idryomov@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®