From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: Xiubo Li <xiubli@redhat.com>,
"idryomov@gmail.com" <idryomov@gmail.com>,
"cfsworks@gmail.com" <cfsworks@gmail.com>
Cc: Milind Changire <mchangir@redhat.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"brauner@kernel.org" <brauner@kernel.org>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 4/6] ceph: Split out page-array discarding to a function
Date: Thu, 8 Jan 2026 20:11:28 +0000 [thread overview]
Message-ID: <5ccf108f4d05b89c9939fa4dc0a0410f5ad7b887.camel@ibm.com> (raw)
In-Reply-To: <20260107210139.40554-5-CFSworks@gmail.com>
On Wed, 2026-01-07 at 13:01 -0800, Sam Edwards wrote:
> Discarding a page array (i.e. after failure to submit it) is a little
> complex:
> - Every folio in the batch needs to be redirtied and unlocked.
> - Some folios are bounce pages created for fscrypt; the underlying
> plaintext folios also need to be redirtied and unlocked.
> - The array itself can come either from the mempool or general kalloc,
> so different free functions need to be used depending on which.
>
> Although currently only ceph_submit_write() does this, this logic is
> complex enough to warrant its own function. Move it to a new
> ceph_discard_page_array() function that is called by ceph_submit_write()
> instead.
>
> Suggested-by: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
> Signed-off-by: Sam Edwards <CFSworks@gmail.com>
> ---
> fs/ceph/addr.c | 67 ++++++++++++++++++++++++++++----------------------
> 1 file changed, 38 insertions(+), 29 deletions(-)
>
> diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
> index 467aa7242b49..3becb13a09fe 100644
> --- a/fs/ceph/addr.c
> +++ b/fs/ceph/addr.c
> @@ -1222,6 +1222,43 @@ void ceph_allocate_page_array(struct address_space *mapping,
> ceph_wbc->len = 0;
> }
>
> +static inline
> +void ceph_discard_page_array(struct writeback_control *wbc,
> + struct ceph_writeback_ctl *ceph_wbc)
> +{
> + int i;
> + struct page *page;
> +
> + for (i = 0; i < folio_batch_count(&ceph_wbc->fbatch); i++) {
> + struct folio *folio = ceph_wbc->fbatch.folios[i];
> +
> + if (!folio)
> + continue;
> +
> + page = &folio->page;
> + redirty_page_for_writepage(wbc, page);
> + unlock_page(page);
> + }
> +
> + for (i = 0; i < ceph_wbc->locked_pages; i++) {
> + page = ceph_fscrypt_pagecache_page(ceph_wbc->pages[i]);
> +
> + if (!page)
> + continue;
> +
> + redirty_page_for_writepage(wbc, page);
> + unlock_page(page);
> + }
> +
> + if (ceph_wbc->from_pool) {
> + mempool_free(ceph_wbc->pages, ceph_wb_pagevec_pool);
> + ceph_wbc->from_pool = false;
> + } else
> + kfree(ceph_wbc->pages);
> + ceph_wbc->pages = NULL;
> + ceph_wbc->locked_pages = 0;
> +}
> +
> static inline
> bool is_folio_index_contiguous(const struct ceph_writeback_ctl *ceph_wbc,
> const struct folio *folio)
> @@ -1445,35 +1482,7 @@ int ceph_submit_write(struct address_space *mapping,
> BUG_ON(len < ceph_fscrypt_page_offset(page) + thp_size(page) - offset);
>
> if (!ceph_inc_osd_stopping_blocker(fsc->mdsc)) {
> - for (i = 0; i < folio_batch_count(&ceph_wbc->fbatch); i++) {
> - struct folio *folio = ceph_wbc->fbatch.folios[i];
> -
> - if (!folio)
> - continue;
> -
> - page = &folio->page;
> - redirty_page_for_writepage(wbc, page);
> - unlock_page(page);
> - }
> -
> - for (i = 0; i < ceph_wbc->locked_pages; i++) {
> - page = ceph_fscrypt_pagecache_page(ceph_wbc->pages[i]);
> -
> - if (!page)
> - continue;
> -
> - redirty_page_for_writepage(wbc, page);
> - unlock_page(page);
> - }
> -
> - if (ceph_wbc->from_pool) {
> - mempool_free(ceph_wbc->pages, ceph_wb_pagevec_pool);
> - ceph_wbc->from_pool = false;
> - } else
> - kfree(ceph_wbc->pages);
> - ceph_wbc->pages = NULL;
> - ceph_wbc->locked_pages = 0;
> -
> + ceph_discard_page_array(wbc, ceph_wbc);
> ceph_osdc_put_request(req);
> return -EIO;
> }
This patch makes sense to me. Looks good.
Reviewed-by: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
Thanks,
Slava.
next prev parent reply other threads:[~2026-01-08 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 21:01 [PATCH v2 0/6] ceph: CephFS writeback correctness and performance fixes Sam Edwards
2026-01-07 21:01 ` [PATCH v2 1/6] ceph: Do not propagate page array emplacement errors as batch errors Sam Edwards
2026-01-08 20:05 ` Viacheslav Dubeyko
2026-01-07 21:01 ` [PATCH v2 2/6] ceph: Remove error return from ceph_process_folio_batch() Sam Edwards
2026-01-08 20:08 ` Viacheslav Dubeyko
2026-01-09 0:29 ` Sam Edwards
2026-01-07 21:01 ` [PATCH v2 3/6] ceph: Free page array when ceph_submit_write fails Sam Edwards
2026-01-07 21:01 ` [PATCH v2 4/6] ceph: Split out page-array discarding to a function Sam Edwards
2026-01-08 20:11 ` Viacheslav Dubeyko [this message]
2026-01-07 21:01 ` [PATCH v2 5/6] ceph: Assert writeback loop invariants Sam Edwards
2026-01-08 20:12 ` Viacheslav Dubeyko
2026-01-07 21:01 ` [PATCH v2 6/6] ceph: Fix write storm on fscrypted files Sam Edwards
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=5ccf108f4d05b89c9939fa4dc0a0410f5ad7b887.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=brauner@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=cfsworks@gmail.com \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchangir@redhat.com \
--cc=xiubli@redhat.com \
/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®