From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GIT PULL] gfs2 fixes for 6.4
Date: Tue, 25 Apr 2023 15:50:44 +0200 [thread overview]
Message-ID: <20230425135044.1100895-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 fixes.
Thanks a lot,
Andreas
The following changes since commit 1e760fa3596e8c7f08412712c168288b79670d78:
Merge tag 'gfs2-v6.3-rc3-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2023-03-23 15:25:49 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v6.3-rc3-fixes
for you to fetch changes up to 644f6bf762fa903f64c59c2ec0f4d0d753527053:
gfs2: gfs2_ail_empty_gl no log flush on error (2023-04-25 11:07:16 +0200)
----------------------------------------------------------------
gfs2 fixes
- Fix revoke processing at unmount and on read-only remount.
- Refuse reading in inodes with an impossible indirect block height.
- Various minor cleanups.
----------------------------------------------------------------
Andreas Gruenbacher (1):
gfs2: Fix inode height consistency check
Andrew Price (3):
gfs2: Remove duplicate i_nlink check from gfs2_link()
gfs2: Remove ghs[] from gfs2_link
gfs2: Remove ghs[] from gfs2_unlink
Bob Peterson (6):
gfs2: Eliminate gfs2_trim_blocks
gfs2: Use gfs2_holder_initialized for jindex
gfs2: return errors from gfs2_ail_empty_gl
gfs2: Perform second log flush in gfs2_make_fs_ro
gfs2: Issue message when revokes cannot be written
gfs2: gfs2_ail_empty_gl no log flush on error
Markus Elfring (1):
gfs2: Move variable assignment behind a null pointer check in inode_go_dump
fs/gfs2/bmap.c | 8 --------
fs/gfs2/bmap.h | 1 -
fs/gfs2/glops.c | 23 +++++++++++++++--------
fs/gfs2/inode.c | 47 ++++++++++++++++++++++-------------------------
fs/gfs2/ops_fstype.c | 9 +++------
fs/gfs2/super.c | 9 +++++++++
6 files changed, 49 insertions(+), 48 deletions(-)
next reply other threads:[~2023-04-25 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 13:50 Andreas Gruenbacher [this message]
2023-04-26 17:06 ` [Cluster-devel] [GIT PULL] gfs2 fixes for 6.4 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=20230425135044.1100895-1-agruenba@redhat.com \
--to=agruenba@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).