CEPH-Devel 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 6.6-rc6
Date: Fri, 13 Oct 2023 17:35:42 +0200	[thread overview]
Message-ID: <20231013153544.463041-1-idryomov@gmail.com> (raw)

Hi Linus,

The following changes since commit 94f6f0550c625fab1f373bb86a6669b45e9748b3:

  Linux 6.6-rc5 (2023-10-08 13:49:43 -0700)

are available in the Git repository at:

  https://github.com/ceph/ceph-client.git tags/ceph-for-6.6-rc6

for you to fetch changes up to 07bb00ef00ace88dd6f695fadbba76565756e55c:

  ceph: fix type promotion bug on 32bit systems (2023-10-09 13:35:24 +0200)

----------------------------------------------------------------
Fixes for an overreaching WARN_ON, two error paths and a switch to
kernel_connect() which recently grown protection against someone using
BPF to rewrite the address.  All but one marked for stable.

----------------------------------------------------------------
Dan Carpenter (1):
      ceph: fix type promotion bug on 32bit systems

Jordan Rife (1):
      libceph: use kernel_connect()

Luis Henriques (1):
      ceph: remove unnecessary IS_ERR() check in ceph_fname_to_usr()

Xiubo Li (1):
      ceph: fix incorrect revoked caps assert in ceph_fill_file_size()

 fs/ceph/crypto.c     | 2 +-
 fs/ceph/file.c       | 2 +-
 fs/ceph/inode.c      | 4 +---
 net/ceph/messenger.c | 4 ++--
 4 files changed, 5 insertions(+), 7 deletions(-)

             reply	other threads:[~2023-10-13 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 15:35 Ilya Dryomov [this message]
2023-10-13 19:06 ` [GIT PULL] Ceph fixes for 6.6-rc6 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=20231013153544.463041-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 read-only IMAP folder(s) and NNTP newsgroup(s).