From: Su Yue <l@damenly.org>
To: Su Yue <glass.su@suse.com>
Cc: gfs2@lists.linux.dev, agruenba@redhat.com, willy@infradead.org
Subject: Re: [PATCH 0/2] GFS2: Fix wrong call of new trans for jdata
Date: Mon, 09 Jun 2025 08:20:51 +0800 [thread overview]
Message-ID: <zfehydcs.fsf@damenly.org> (raw)
In-Reply-To: <20250606094756.95958-1-glass.su@suse.com> (Su Yue's message of "Fri, 6 Jun 2025 17:47:54 +0800")
On Fri 06 Jun 2025 at 17:47, Su Yue <glass.su@suse.com> wrote:
> Patch 1 is trivial.
> Please see commit message of patch 2/2.
>
Please ignore the patchset. The issue was fixed by
commit 5a90f8d49922 ("gfs2: Don't start unnecessary transactions
during log flush").
--
Su
> Su Yue (2):
> gfs2: rename gfs2_write_jdata_folio to
> gfs2_write_jdata_full_folio
> gfs2: do not call gfs2_jdata_writepages for jdata
>
> fs/gfs2/aops.c | 46
> +++++++++++++++++++++++++++++++++++++++++++---
> fs/gfs2/aops.h | 1 +
> fs/gfs2/log.c | 6 +++++-
> 3 files changed, 49 insertions(+), 4 deletions(-)
prev parent reply other threads:[~2025-06-09 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 9:47 [PATCH 0/2] GFS2: Fix wrong call of new trans for jdata Su Yue
2025-06-06 9:47 ` [PATCH 1/2] gfs2: rename gfs2_write_jdata_folio to gfs2_write_jdata_full_folio Su Yue
2025-06-06 9:47 ` [PATCH 2/2] gfs2: do not call gfs2_jdata_writepages for jdata Su Yue
2025-06-06 12:27 ` Matthew Wilcox
2025-06-09 0:18 ` Su Yue
2025-06-09 0:20 ` Su Yue [this message]
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=zfehydcs.fsf@damenly.org \
--to=l@damenly.org \
--cc=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=glass.su@suse.com \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.