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.10-rc3
Date: Thu, 12 Nov 2020 23:23:46 +0100 [thread overview]
Message-ID: <20201112222346.2227664-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following additional gfs2 fixes on top of 5.10-rc3.
Thank you very much,
Andreas
The following changes since commit f8394f232b1eab649ce2df5c5f15b0e528c92091:
Linux 5.10-rc3 (2020-11-08 16:10:16 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.10-rc3-fixes
for you to fetch changes up to 4e79e3f08e576acd51dffb4520037188703238b3:
gfs2: Fix case in which ail writes are done to jdata holes (2020-11-12 18:55:20 +0100)
----------------------------------------------------------------
Fix jdata data corruption and glock reference leak
----------------------------------------------------------------
Bob Peterson (2):
Revert "gfs2: Ignore journal log writes for jdata holes"
gfs2: Fix case in which ail writes are done to jdata holes
Zhang Qilong (1):
gfs2: fix possible reference leak in gfs2_check_blk_type
fs/gfs2/aops.c | 2 +-
fs/gfs2/bmap.c | 8 ++------
fs/gfs2/log.c | 2 ++
fs/gfs2/rgrp.c | 10 +++++-----
4 files changed, 10 insertions(+), 12 deletions(-)
next reply other threads:[~2020-11-12 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 22:23 Andreas Gruenbacher [this message]
2020-11-13 0:44 ` [GIT PULL] GFS2 fixes for 5.10-rc3 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=20201112222346.2227664-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;
as well as URLs for NNTP newsgroup(s).