From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] gfs2 fixes
Date: Fri, 5 Aug 2022 22:12:48 +0200 [thread overview]
Message-ID: <20220805201248.123846-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 fixes.
Thank you very much,
Andreas
The following changes since commit 03c765b0e3b4cb5063276b086c76f7a612856a9a:
Linux 5.19-rc4 (2022-06-26 14:22:10 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.19-rc4-fixes
for you to fetch changes up to 446279168e030fd0ed68e2bba336bef8bb3da352:
Merge part of branch 'for-next.instantiate' into for-next (2022-08-05 18:37:03 +0200)
----------------------------------------------------------------
gfs2 fixes
- Instantiate glocks ouside of the glock state engine, in the contect of
the process taking the glock. This moves unnecessary complexity out
of the core glock code. Clean up the instantiate logic to be more
sensible.
- In gfs2_glock_async_wait(), cancel pending locking request upon
failure. Make sure all glocks are left in a consistent state.
- Various other minor cleanups and fixes.
----------------------------------------------------------------
Andreas Gruenbacher (9):
gfs2: Minor gfs2_glock_nq_m cleanup
gfs2: Fix up gfs2_glock_async_wait
gfs2: Instantiate glocks ouside of glock state engine
gfs2: Revert 'Fix "truncate in progress" hang'
gfs2: Add new go_held glock operation
gfs2: Make go_instantiate take a glock
gfs2: Use better variable name
gfs2: List traversal in do_promote is safe
Merge part of branch 'for-next.instantiate' into for-next
Bob Peterson (2):
gfs2: Rewrap overlong comment in do_promote
gfs2: do_promote glock holder stealing fix
Minghao Chi (1):
gfs2: Remove redundant NULL check before kfree
Zhang Jiaming (1):
gfs2: Fix spelling mistake in comment
fs/gfs2/dir.c | 2 +-
fs/gfs2/file.c | 3 +-
fs/gfs2/glock.c | 200 ++++++++++++++++++++-------------------------------
fs/gfs2/glock.h | 2 +-
fs/gfs2/glops.c | 31 ++++----
fs/gfs2/incore.h | 6 +-
fs/gfs2/lock_dlm.c | 2 +-
fs/gfs2/main.c | 1 -
fs/gfs2/ops_fstype.c | 2 -
fs/gfs2/quota.c | 28 +-------
fs/gfs2/rgrp.c | 12 ++--
fs/gfs2/rgrp.h | 5 +-
fs/gfs2/super.c | 2 +-
fs/gfs2/xattr.c | 2 +-
14 files changed, 111 insertions(+), 187 deletions(-)
next reply other threads:[~2022-08-05 20:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 20:12 Andreas Gruenbacher [this message]
2022-08-06 22:08 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-11-07 14:21 Andreas Gruenbacher
2023-11-07 20:30 ` Linus Torvalds
2023-11-07 22:18 ` Andreas Grünbacher
2023-11-08 0:04 ` Linus Torvalds
2023-11-07 20:34 ` pr-tracker-bot
2023-09-18 14:34 Andreas Gruenbacher
2023-09-18 20:20 ` pr-tracker-bot
2023-09-05 16:12 Andreas Gruenbacher
2023-09-05 20:14 ` pr-tracker-bot
2023-08-08 12:53 Andreas Gruenbacher
2023-07-04 12:51 Andreas Gruenbacher
2023-07-04 18:59 ` pr-tracker-bot
2023-02-22 12:01 Andreas Gruenbacher
2023-02-22 22:27 ` pr-tracker-bot
2022-12-16 14:33 Andreas Gruenbacher
2022-12-17 14:28 ` pr-tracker-bot
2022-10-09 10:45 Andreas Gruenbacher
2022-10-11 3:43 ` pr-tracker-bot
2022-05-24 19:41 Andreas Gruenbacher
2022-05-25 2:16 ` pr-tracker-bot
2022-05-13 21:07 Andreas Gruenbacher
2022-05-13 21:35 ` Linus Torvalds
2022-05-13 21:38 ` pr-tracker-bot
2022-02-11 17:05 Andreas Gruenbacher
2022-02-11 19:47 ` Linus Torvalds
2022-02-11 21:40 ` Andreas Gruenbacher
2022-02-11 20:05 ` 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=20220805201248.123846-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--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
all inboxes | Powered by JetHome®