From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] vfs ceph
Date: Sat, 22 Mar 2025 11:16:33 +0100 [thread overview]
Message-ID: <20250322-vfs-ceph-81a373556110@brauner> (raw)
Hey Linus,
/* Summary */
This contains the work to remove access to page->index from ceph and
fixes the test failure observed for ceph with generic/421 by refactoring
ceph_writepages_start().
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-6)
Debian clang version 16.0.6 (27+b1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.15-rc1.ceph
for you to fetch changes up to 59b59a943177e1a96d645a63d1ad824644fa848a:
fscrypt: Change fscrypt_encrypt_pagecache_blocks() to take a folio (2025-03-05 12:57:15 +0100)
Please consider pulling these changes from the signed vfs-6.15-rc1.ceph tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.15-rc1.ceph
----------------------------------------------------------------
Christian Brauner (2):
Merge patch series "ceph: fix generic/421 test failure"
Merge patch series "Remove accesses to page->index from ceph"
Matthew Wilcox (Oracle) (12):
ceph: Remove ceph_writepage()
ceph: Use a folio in ceph_page_mkwrite()
ceph: Convert ceph_find_incompatible() to take a folio
ceph: Convert ceph_readdir_cache_control to store a folio
ceph: Convert writepage_nounlock() to write_folio_nounlock()
ceph: Convert ceph_check_page_before_write() to use a folio
ceph: Remove uses of page from ceph_process_folio_batch()
ceph: Convert ceph_move_dirty_page_in_page_array() to move_dirty_folio_in_page_array()
ceph: Pass a folio to ceph_allocate_page_array()
fs: Remove page_mkwrite_check_truncate()
ceph: Fix error handling in fill_readdir_cache()
fscrypt: Change fscrypt_encrypt_pagecache_blocks() to take a folio
Viacheslav Dubeyko (4):
ceph: extend ceph_writeback_ctl for ceph_writepages_start() refactoring
ceph: introduce ceph_process_folio_batch() method
ceph: introduce ceph_submit_write() method
ceph: fix generic/421 test failure
fs/ceph/addr.c | 1259 +++++++++++++++++++++++++++++------------------
fs/ceph/dir.c | 15 +-
fs/ceph/inode.c | 31 +-
fs/ceph/mds_client.c | 2 +
fs/ceph/mds_client.h | 3 +
fs/ceph/super.c | 11 +
fs/ceph/super.h | 2 +-
fs/crypto/crypto.c | 22 +-
fs/ext4/page-io.c | 2 +-
fs/f2fs/data.c | 2 +-
include/linux/fscrypt.h | 12 +-
include/linux/pagemap.h | 28 --
12 files changed, 848 insertions(+), 541 deletions(-)
next reply other threads:[~2025-03-22 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 10:16 Christian Brauner [this message]
2025-03-24 21:01 ` 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=20250322-vfs-ceph-81a373556110@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@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®