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 6.4-rc1
Date: Thu,  4 May 2023 20:28:10 +0200	[thread overview]
Message-ID: <20230504182810.165185-1-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit 457391b0380335d5e9a5babdec90ac53928b23b4:

  Linux 6.3 (2023-04-23 12:02:52 -0700)

are available in the Git repository at:

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

for you to fetch changes up to db2993a423e3fd0e4878f4d3ac66fe717f5f072e:

  ceph: reorder fields in 'struct ceph_snapid_map' (2023-04-30 12:37:28 +0200)

----------------------------------------------------------------
A few filesystem improvements, with a rather nasty use-after-free fix
from Xiubo intended for stable.

----------------------------------------------------------------
Christophe JAILLET (1):
      ceph: reorder fields in 'struct ceph_snapid_map'

Xiubo Li (4):
      ceph: do not print the whole xattr value if it's too long
      ceph: implement writeback livelock avoidance using page tagging
      ceph: fix potential use-after-free bug when trimming caps
      ceph: pass ino# instead of old_dentry if it's disconnected

 fs/ceph/addr.c       | 11 +++++++-
 fs/ceph/caps.c       |  2 +-
 fs/ceph/debugfs.c    | 18 ++++++++----
 fs/ceph/dir.c        | 13 +++++++--
 fs/ceph/mds_client.c | 78 ++++++++++++++++++++++++++++++++++------------------
 fs/ceph/mds_client.h |  5 ++--
 fs/ceph/super.h      |  2 ++
 fs/ceph/xattr.c      | 20 +++++++++-----
 8 files changed, 102 insertions(+), 47 deletions(-)

             reply	other threads:[~2023-05-04 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 18:28 Ilya Dryomov [this message]
2023-05-04 21:50 ` 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=20230504182810.165185-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®