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 updates for 7.1-rc1
Date: Fri, 24 Apr 2026 19:53:19 +0200	[thread overview]
Message-ID: <20260424175320.279295-1-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit 028ef9c96e96197026887c0f092424679298aae8:

  Linux 7.0 (2026-04-12 13:48:06 -0700)

are available in the Git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-7.1-rc1

for you to fetch changes up to b1137e0b3d4bad1cad73fa9bac763c74ddd1813d:

  ceph: add subvolume metrics collection and reporting (2026-04-22 01:40:23 +0200)

----------------------------------------------------------------
We have a series from Alex which extends CephFS client metrics with
support for per-subvolume data I/O performance and latency tracking
(metadata operations aren't included) and a good variety of fixes and
cleanups across RBD and CephFS.

----------------------------------------------------------------
Alex Markuze (3):
      ceph: handle InodeStat v8 versioned field in reply parsing
      ceph: parse subvolume_id from InodeStat v9 and store in inode
      ceph: add subvolume metrics collection and reporting

Dawei Feng (1):
      rbd: fix null-ptr-deref when device_add_disk() fails

Eric Biggers (1):
      libceph: Remove obsolete session key alignment logic

Max Kellermann (2):
      ceph: only d_add() negative dentries when they are unhashed
      ceph: clear s_cap_reconnect when ceph_pagelist_encode_32() fails

Raphael Zimmer (2):
      libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply()
      libceph: Fix slab-out-of-bounds access in auth message processing

Sam Edwards (1):
      ceph: fix num_ops off-by-one when crypto allocation fails

Viacheslav Dubeyko (1):
      crush: cleanup in crush_do_rule() method

kexinsun (1):
      libceph: update outdated comment in ceph_sock_write_space()

 drivers/block/rbd.c         |   6 +-
 fs/ceph/Makefile            |   2 +-
 fs/ceph/addr.c              |  18 ++
 fs/ceph/debugfs.c           | 157 +++++++++++++++++
 fs/ceph/dir.c               |   6 +-
 fs/ceph/file.c              |  68 +++++++-
 fs/ceph/inode.c             |  41 +++++
 fs/ceph/mds_client.c        |  98 +++++++++--
 fs/ceph/mds_client.h        |  14 +-
 fs/ceph/metric.c            | 183 ++++++++++++++++++-
 fs/ceph/metric.h            |  39 ++++-
 fs/ceph/subvolume_metrics.c | 416 ++++++++++++++++++++++++++++++++++++++++++++
 fs/ceph/subvolume_metrics.h |  97 +++++++++++
 fs/ceph/super.c             |   8 +
 fs/ceph/super.h             |  11 ++
 net/ceph/auth.c             |   4 +-
 net/ceph/crush/mapper.c     |   7 +-
 net/ceph/messenger.c        |   4 +-
 net/ceph/messenger_v2.c     |  13 +-
 net/ceph/mon_client.c       |   2 +
 20 files changed, 1144 insertions(+), 50 deletions(-)
 create mode 100644 fs/ceph/subvolume_metrics.c
 create mode 100644 fs/ceph/subvolume_metrics.h

             reply	other threads:[~2026-04-24 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24 17:53 Ilya Dryomov [this message]
2026-04-24 20:51 ` 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=20260424175320.279295-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®