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] gfs fixes for 5.18-rc1
Date: Thu, 31 Mar 2022 22:11:49 +0200 [thread overview]
Message-ID: <20220331201149.566786-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 fixes for 5.18-rc1.
Thanks,
Andreas
The following changes since commit 754e0b0e35608ed5206d6a67a791563c631cec07:
Linux 5.17-rc4 (2022-02-13 12:13:30 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.17-rc4-fixes
for you to fetch changes up to 27ca8273fda398638ca994a207323a85b6d81190:
gfs2: Make sure FITRIM minlen is rounded up to fs block size (2022-03-31 20:35:38 +0200)
----------------------------------------------------------------
gfs2 fixes
* To avoid deadlocks, actively cancel dlm locking requests when we give
up on them. Further dlm operations on the same lock will return
-EBUSY until the cancel has been completed, so in that case, wait and
repeat. (This is rare.)
* Lock inversion fixes in gfs2_inode_lookup() and gfs2_create_inode().
* Some more fallout from the gfs2 mmap + page fault deadlock fixes
(merge c03098d4b9ad7).
* Various other minor bug fixes and cleanups.
----------------------------------------------------------------
Andreas Gruenbacher (12):
gfs2: gfs2_setattr_size error path fix
gfs2: Expect -EBUSY after canceling dlm locking requests
gfs2: cancel timed-out glock requests
gfs2: Switch lock order of inode and iopen glock
gfs2: Make use of list_is_first
gfs2: Initialize gh_error in gfs2_glock_nq
gfs2: Fix should_fault_in_pages() logic
gfs2: Disable page faults during lockless buffered reads
gfs2: Minor retry logic cleanup
gfs2: Fix gfs2_file_buffered_write endless loop workaround
gfs2: Remove dead code in gfs2_file_read_iter
gfs2: Make sure not to return short direct writes
Andrew Price (1):
gfs2: Make sure FITRIM minlen is rounded up to fs block size
Bob Peterson (2):
gfs2: assign rgrp glock before compute_bitstructs
gfs2: Remove return value for gfs2_indirect_init
fs/gfs2/bmap.c | 9 ++++----
fs/gfs2/file.c | 68 ++++++++++++++++++++++++++----------------------------
fs/gfs2/glock.c | 14 +++++++++--
fs/gfs2/inode.c | 51 ++++++++++++++++++++++------------------
fs/gfs2/lock_dlm.c | 15 +++++++++++-
fs/gfs2/rgrp.c | 19 ++++++++-------
fs/gfs2/rgrp.h | 2 +-
fs/gfs2/super.c | 2 +-
8 files changed, 104 insertions(+), 76 deletions(-)
next reply other threads:[~2022-03-31 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 20:11 Andreas Gruenbacher [this message]
2022-03-31 23:22 ` 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=20220331201149.566786-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®