From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] gfs2 changes for 7.1
Date: Tue, 14 Apr 2026 14:19:07 +0200 [thread overview]
Message-ID: <20260414121908.887366-1-agruenba@redhat.com> (raw)
Dear Linus,
please consider pulling the following gfs2 changes for 7.1.
Thanks,
Andreas
The following changes since commit 7141433fbed290f4dd42008d3102db2363275035:
Merge tag 'gfs2-for-7.0' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2026-02-09 16:29:57 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-for-7.1
for you to fetch changes up to 74b4dbb946060a3233604d91859a9abd3708141d:
gfs2: prevent NULL pointer dereference during unmount (2026-04-07 22:20:00 +0200)
----------------------------------------------------------------
gfs2 changes
- Fix possible data loss during inode evict.
- Fix a race during bufdata allocation.
- More careful cleaning up during a withdraw.
- Prevent excessive log flushing under memory pressure.
- Various other minor fixes and cleanups.
----------------------------------------------------------------
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(-)
next reply other threads:[~2026-04-14 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 12:19 Andreas Gruenbacher [this message]
2026-04-16 2:54 ` [GIT PULL] gfs2 changes for 7.1 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=20260414121908.887366-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=gfs2@lists.linux.dev \
--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