From: Andreas Gruenbacher <agruenba@redhat.com>
To: gfs2@lists.linux.dev
Cc: Andreas Gruenbacher <agruenba@redhat.com>
Subject: [PATCH 00/18] gfs2 patches on for-next
Date: Mon, 13 Apr 2026 16:51:53 +0200 [thread overview]
Message-ID: <20260413145211.881752-1-agruenba@redhat.com> (raw)
Hello,
we currently have the following patches on for-next, to be submitted for
upstream inclusion in the current merge window. These mainly address
the following problems:
* When inodes got evicted, changes in the page cache were sometimes
discarded instead of being written back do disk (as exhibited by
xfstest generic/211).
* Systems under heavy memory pressure were issuing too many log flushes,
leading to a degradation in performance.
* An occasional leak of bufdata objects.
* Some minor improvements to the handling of withdraws.
Thanks,
Andreas
Andreas Gruenbacher (18):
gfs2: Call unlock_new_inode before d_instantiate
gfs2: Remove unnecessary check in gfs2_evict_inode
gfs2: Avoid unnecessary transactions in evict_linked_inode
gfs2: minor evict_[un]linked_inode cleanup
gfs2: Fix data loss during inode evict
gfs2: less aggressive low-memory log flushing
gfs2: Get rid of gfs2_log_[un]lock helpers
gfs2: Move gfs2_remove_from_journal to log.c
gfs2: Remove trans_drain code duplication
gfs2: bufdata allocation race
gfs2: drain ail under sd_log_flush_lock
gfs2: fix address space truncation during withdraw
gfs2: add some missing log locking
gfs2: gfs2_log_flush withdraw fixes
gfs2: inode directory consistency checks
gfs2: wait for withdraw earlier during unmount
gfs2: hide error messages after withdraw
gfs2: prevent NULL pointer dereference during unmount
fs/gfs2/aops.c | 15 +++---
fs/gfs2/bmap.c | 2 +-
fs/gfs2/glops.c | 13 +++--
fs/gfs2/inode.c | 3 +-
fs/gfs2/log.c | 127 +++++++++++++++++++++++++++++++++-------------
fs/gfs2/log.h | 26 +---------
fs/gfs2/lops.c | 16 +++---
fs/gfs2/meta_io.c | 43 ++--------------
fs/gfs2/meta_io.h | 1 -
fs/gfs2/rgrp.c | 2 +-
fs/gfs2/super.c | 111 +++++++++++++++++++++++++++++++---------
fs/gfs2/trans.c | 45 ++++++++--------
fs/gfs2/util.c | 3 +-
13 files changed, 237 insertions(+), 170 deletions(-)
--
2.53.0
next reply other threads:[~2026-04-13 14:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 14:51 Andreas Gruenbacher [this message]
2026-04-13 14:51 ` [PATCH 01/18] gfs2: Call unlock_new_inode before d_instantiate Andreas Gruenbacher
2026-04-13 14:51 ` [PATCH 02/18] gfs2: Remove unnecessary check in gfs2_evict_inode Andreas Gruenbacher
2026-04-13 14:51 ` [PATCH 03/18] gfs2: Avoid unnecessary transactions in evict_linked_inode Andreas Gruenbacher
2026-04-13 14:51 ` [PATCH 04/18] gfs2: minor evict_[un]linked_inode cleanup Andreas Gruenbacher
2026-04-13 14:51 ` [PATCH 05/18] gfs2: Fix data loss during inode evict Andreas Gruenbacher
2026-04-13 14:51 ` [PATCH 06/18] gfs2: less aggressive low-memory log flushing Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 07/18] gfs2: Get rid of gfs2_log_[un]lock helpers Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 08/18] gfs2: Move gfs2_remove_from_journal to log.c Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 09/18] gfs2: Remove trans_drain code duplication Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 10/18] gfs2: bufdata allocation race Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 11/18] gfs2: drain ail under sd_log_flush_lock Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 12/18] gfs2: fix address space truncation during withdraw Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 13/18] gfs2: add some missing log locking Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 14/18] gfs2: gfs2_log_flush withdraw fixes Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 15/18] gfs2: inode directory consistency checks Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 16/18] gfs2: wait for withdraw earlier during unmount Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 17/18] gfs2: hide error messages after withdraw Andreas Gruenbacher
2026-04-13 14:52 ` [PATCH 18/18] gfs2: prevent NULL pointer dereference during unmount Andreas Gruenbacher
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=20260413145211.881752-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
/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