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 5.7
Date: Tue, 12 May 2020 16:54:34 +0200 [thread overview]
Message-ID: <20200512145434.160164-1-agruenba@redhat.com> (raw)
Hi Linus,
could you please pull the following fixes for gfs2?
Thanks a lot,
Andreas
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.7-rc1.fixes
for you to fetch changes up to b14c94908b1b884276a6608dea3d0b1b510338b7:
Revert "gfs2: Don't demote a glock until its revokes are written" (2020-05-08 15:01:25 -0500)
----------------------------------------------------------------
Various gfs2 fixes
Fixes for bugs prior to v5.7-rc1:
- Fix random block reads when reading fragmented journals (v5.2).
- Fix a possible random memory access in gfs2_walk_metadata (v5.3).
Fixes for v5.7-rc1:
- Fix several overlooked gfs2_qa_get / gfs2_qa_put imbalances.
- Fix several bugs in the new filesystem withdraw logic.
----------------------------------------------------------------
Andreas Gruenbacher (3):
gfs2: Another gfs2_walk_metadata fix
gfs2: More gfs2_find_jhead fixes
gfs2: Grab glock reference sooner in gfs2_add_revoke
Bob Peterson (11):
gfs2: fix withdraw sequence deadlock
gfs2: Fix error exit in do_xmote
gfs2: Fix BUG during unmount after file system withdraw
gfs2: Fix use-after-free in gfs2_logd after withdraw
gfs2: Fix problems regarding gfs2_qa_get and _put
gfs2: Change BUG_ON to an assert_withdraw in gfs2_quota_change
gfs2: remove check for quotas on in gfs2_quota_check
gfs2: move privileged user check to gfs2_quota_lock_check
gfs2: don't call quota_unhold if quotas are not locked
gfs2: If go_sync returns error, withdraw but skip invalidate
Revert "gfs2: Don't demote a glock until its revokes are written"
fs/gfs2/bmap.c | 16 +++++++++-------
fs/gfs2/glock.c | 6 ++----
fs/gfs2/inode.c | 7 ++++---
fs/gfs2/log.c | 11 ++++++++---
fs/gfs2/lops.c | 19 ++++++++++++-------
fs/gfs2/meta_io.c | 2 +-
fs/gfs2/quota.c | 13 +++++--------
fs/gfs2/quota.h | 3 ++-
fs/gfs2/super.c | 1 -
fs/gfs2/util.c | 10 ++++++----
10 files changed, 49 insertions(+), 39 deletions(-)
next reply other threads:[~2020-05-12 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 14:54 Andreas Gruenbacher [this message]
2020-05-12 18: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=20200512145434.160164-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®