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, 11 Feb 2022 18:05:22 +0100 [thread overview]
Message-ID: <20220211170522.348999-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following two gfs2 fixes for 5.17-rc4.
Thanks,
Andreas
The following changes since commit 74382e277ae97b4bcfac6f8b61df7a500d392500:
gfs2: dump inode object for iopen glocks (2022-01-11 16:52:44 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.16-rc3-fixes2
for you to fetch changes up to d3add1a9519dcacd6e644ecac741c56cf18b67f5:
gfs2: Fix gfs2_release for non-writers regression (2022-02-11 17:44:42 +0100)
----------------------------------------------------------------
gfs2 fixes:
* Revert debug commit that causes unexpected data corruption.
* Fix muti-block reservation regression.
----------------------------------------------------------------
Andreas Gruenbacher (1):
Revert "gfs2: check context in gfs2_glock_put"
Bob Peterson (1):
gfs2: Fix gfs2_release for non-writers regression
fs/gfs2/file.c | 7 ++++---
fs/gfs2/glock.c | 3 ---
2 files changed, 4 insertions(+), 6 deletions(-)
next reply other threads:[~2022-02-11 17:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 17:05 Andreas Gruenbacher [this message]
2022-02-11 19:47 ` Linus Torvalds
2022-02-11 21:40 ` Andreas Gruenbacher
2022-02-11 20:05 ` 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-05-24 19:41 Andreas Gruenbacher
2022-05-25 2:16 ` pr-tracker-bot
2022-08-05 20:12 Andreas Gruenbacher
2022-08-06 22:08 ` pr-tracker-bot
2022-10-09 10:45 Andreas Gruenbacher
2022-10-11 3:43 ` pr-tracker-bot
2022-12-16 14:33 Andreas Gruenbacher
2022-12-17 14:28 ` pr-tracker-bot
2023-02-22 12:01 Andreas Gruenbacher
2023-02-22 22:27 ` pr-tracker-bot
2023-07-04 12:51 Andreas Gruenbacher
2023-07-04 18:59 ` pr-tracker-bot
2023-08-08 12:53 Andreas Gruenbacher
2023-09-05 16:12 Andreas Gruenbacher
2023-09-05 20:14 ` pr-tracker-bot
2023-09-18 14:34 Andreas Gruenbacher
2023-09-18 20:20 ` pr-tracker-bot
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
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=20220211170522.348999-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®