linux-kernel.vger.kernel.org archive mirror
 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.18-rc5
Date: Fri, 29 Apr 2022 18:26:32 +0200	[thread overview]
Message-ID: <20220429162632.29934-1-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit af2d861d4cd2a4da5137f795ee3509e6f944a25b:

  Linux 5.18-rc4 (2022-04-24 14:51:22 -0700)

are available in the Git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-5.18-rc5

for you to fetch changes up to 7acae6183cf37c48b8da48bbbdb78820fb3913f3:

  ceph: fix possible NULL pointer dereference for req->r_session (2022-04-25 10:45:50 +0200)

----------------------------------------------------------------
A fix for a NULL dereference that turns out to be easily triggerable
by fsync (marked for stable) and a false positive WARN and snap_rwsem
locking fixups.

----------------------------------------------------------------
Ilya Dryomov (1):
      libceph: disambiguate cluster/pool full log message

Niels Dossche (1):
      ceph: get snap_rwsem read lock in handle_cap_export for ceph_add_cap

Xiubo Li (2):
      ceph: remove incorrect session state check
      ceph: fix possible NULL pointer dereference for req->r_session

 fs/ceph/caps.c        | 7 +++++++
 fs/ceph/mds_client.c  | 6 ------
 net/ceph/osd_client.c | 6 +++++-
 3 files changed, 12 insertions(+), 7 deletions(-)

             reply	other threads:[~2022-04-29 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 16:26 Ilya Dryomov [this message]
2022-04-29 23:29 ` [GIT PULL] Ceph fixes for 5.18-rc5 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=20220429162632.29934-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;
as well as URLs for NNTP newsgroup(s).