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 for v5.16-rc4
Date: Sat, 4 Dec 2021 11:24:46 +0100 [thread overview]
Message-ID: <20211204102446.19275-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 fixes for 5.16-rc4.
Thanks,
Andreas
The following changes since commit 42eb8fdac2fc5d62392dcfcf0253753e821a97b0:
Merge tag 'gfs2-v5.16-rc2-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2021-11-17 15:55:07 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.16-rc4-fixes
for you to fetch changes up to 3d36e57ff768dbb919c06ffedec4bfe4587c6254:
gfs2: gfs2_create_inode rework (2021-12-02 12:41:10 +0100)
----------------------------------------------------------------
Fixes in gfs2:
* Since commit 486408d690e1 ("gfs2: Cancel remote delete work
asynchronously"), inode create and lookup-by-number can overlap more
easily and we can end up with temporary duplicate inodes. Fix the
code to prevent that.
* Fix a BUG demoting weak glock holders from a remote node.
----------------------------------------------------------------
Andreas Gruenbacher (4):
gfs2: Fix remote demote of weak glock holders
gfs2: gfs2_inode_lookup cleanup
gfs2: gfs2_inode_lookup rework
gfs2: gfs2_create_inode rework
fs/gfs2/glock.c | 10 ++++--
fs/gfs2/inode.c | 109 +++++++++++++++++++++++---------------------------------
2 files changed, 52 insertions(+), 67 deletions(-)
next reply other threads:[~2021-12-04 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 10:24 Andreas Gruenbacher [this message]
2021-12-04 16:55 ` 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=20211204102446.19275-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®