From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GIT PULL] gfs2 fixes for 5.15
Date: Mon, 30 Aug 2021 23:10:33 +0200 [thread overview]
Message-ID: <20210830211033.1825127-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 fixes for 5.15, which are all
unrelated to the deadlock avoidance patch queue we've been discussing.
Thanks,
Andreas
The following changes since commit 2734d6c1b1a089fb593ef6a23d4b70903526fe0c:
Linux 5.14-rc2 (2021-07-18 14:13:49 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.14-rc2-fixes
for you to fetch changes up to 08d736667185dca2751cf47eabb0830cecdeb160:
gfs2: Remove redundant check from gfs2_glock_dq (2021-08-20 09:03:46 -0500)
----------------------------------------------------------------
Changes in gfs2:
* Various withdraw related fixes (freeze glock recursion, thread
initialization / destruction order, journal recovery, glock cleanup,
withdraw under journal lock).
* Some error message improvements.
* Various minor cleanups.
----------------------------------------------------------------
Bob Peterson (14):
gfs2: Fix glock recursion in freeze_go_xmote_bh
gfs2: be more verbose replaying invalid rgrp blocks
gfs2: trivial clean up of gfs2_ail_error
gfs2: tiny cleanup in gfs2_log_reserve
gfs2: init system threads before freeze lock
gfs2: Don't release and reacquire local statfs bh
gfs2: Make recovery error more readable
gfs2: Eliminate vestigial HIF_FIRST
gfs2: nit: gfs2_drop_inode shouldn't return bool
gfs2: Mark journal inodes as "don't cache"
gfs2: don't stop reads while withdraw in progress
gfs2: Don't call dlm after protocol is unmounted
gfs2: Delay withdraw from atomic context
gfs2: Remove redundant check from gfs2_glock_dq
Colin Ian King (1):
gfs2: Fix memory leak of object lsi on error return path
fs/gfs2/aops.c | 9 +----
fs/gfs2/glock.c | 13 +++----
fs/gfs2/glops.c | 27 +++++++------
fs/gfs2/incore.h | 2 +-
fs/gfs2/lock_dlm.c | 5 +++
fs/gfs2/log.c | 2 +-
fs/gfs2/lops.c | 44 +++++++++++++--------
fs/gfs2/meta_io.c | 7 ++--
fs/gfs2/ops_fstype.c | 53 +++++++++++++++++++++++++
fs/gfs2/super.c | 107 +++++++++------------------------------------------
fs/gfs2/super.h | 3 +-
fs/gfs2/util.c | 3 +-
fs/gfs2/util.h | 5 +++
13 files changed, 139 insertions(+), 141 deletions(-)
next reply other threads:[~2021-08-30 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 21:10 Andreas Gruenbacher [this message]
2021-08-31 18:19 ` [Cluster-devel] [GIT PULL] gfs2 fixes for 5.15 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=20210830211033.1825127-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 NNTP newsgroup(s).