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 changes for 5.11
Date: Sat, 19 Dec 2020 22:11:27 +0100 [thread overview]
Message-ID: <20201219211127.287454-1-agruenba@redhat.com> (raw)
Hi Linus,
could you please pull the following gfs2 changes for 5.11?
Thanks a lot,
Andreas
The following changes since commit dd0ecf544125639e54056d851e4887dbb94b6d2f:
gfs2: Fix deadlock between gfs2_{create_inode,inode_lookup} and delete_work_func (2020-12-01 00:21:10 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-for-5.11
for you to fetch changes up to 6e5c4ea37a99e5b97aba227fc43f3682d4bc0496:
gfs2: in signal_our_withdraw wait for unfreeze of _this_ fs only (2020-12-03 17:04:41 +0100)
----------------------------------------------------------------
Changes in gfs2:
* Don't wait for unfreeze of the wrong filesystems.
* Remove an obsolete delete_work_func hack and an incorrect sb_start_write.
* Minor documentation updates and cosmetic care.
----------------------------------------------------------------
Andreas Gruenbacher (2):
gfs2: Make inode operations static
Revert "GFS2: Prevent delete work from occurring on glocks used for create"
Andrew Price (2):
Documentation: Update filesystems/gfs2.rst
MAINTAINERS: Add gfs2 bug tracker link
Bob Peterson (2):
gfs2: Remove sb_start_write from gfs2_statfs_sync
gfs2: in signal_our_withdraw wait for unfreeze of _this_ fs only
Tom Rix (1):
gfs2: remove trailing semicolons from macro definitions
Documentation/filesystems/gfs2.rst | 37 ++++++++++++++++++-------------------
MAINTAINERS | 2 +-
fs/gfs2/glock.c | 8 --------
fs/gfs2/incore.h | 1 -
fs/gfs2/inode.c | 16 ++++++++--------
fs/gfs2/inode.h | 3 ---
fs/gfs2/super.c | 2 --
fs/gfs2/util.c | 2 +-
fs/gfs2/util.h | 6 +++---
9 files changed, 31 insertions(+), 46 deletions(-)
next reply other threads:[~2020-12-19 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 21:11 Andreas Gruenbacher [this message]
2020-12-20 18:53 ` 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=20201219211127.287454-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®