From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GIT PULL] gfs2 fixes
Date: Fri, 16 Dec 2022 15:33:17 +0100 [thread overview]
Message-ID: <20221216143317.668868-1-agruenba@redhat.com> (raw)
Hi Linus,
please consider pulling the following gfs2 fixes.
Thank you very much,
Andreas
The following changes since commit b7b275e60bcd5f89771e865a8239325f86d9927d:
Linux 6.1-rc7 (2022-11-27 13:31:48 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v6.1-rc7-fixes
for you to fetch changes up to 6b46a06100dd0e0ebe400573e94ccd09163bfd5b:
gfs2: Remove support for glock holder auto-demotion (2) (2022-12-15 12:41:22 +0100)
----------------------------------------------------------------
gfs2 fixes
- Revert a change to delete_work_func() that has gone wrong in commit
c412a97cf6c5 ("gfs2: Use TRY lock in gfs2_inode_lookup for UNLINKED
inodes").
- Avoid dequeuing GL_ASYNC glock holders twice by first checking if the
holder is still queued.
- gfs2: Always check the inode size of inline inodes when reading in
inodes to prevent corrupt filesystem images from causing weid errors.
- Properly handle a race between gfs2_create_inode() and
gfs2_inode_lookup() that causes insert_inode_locked4() to return
-EBUSY.
- Fix and clean up the interaction between gfs2_create_inode() and
gfs2_evict_inode() by completely handling the inode deallocation and
destruction in gfs2_evict_inode().
- Remove support for glock holder auto-demotion as we have no current
plans of using this feature again.
- And a few more minor cleanups and clarifications.
----------------------------------------------------------------
Andreas Gruenbacher (17):
gfs2: Add extra error check in alloc_dinode
gfs2: Get rid of ghs[] in gfs2_create_inode
gfs2: Clean up initialization of "ip" in gfs2_create_inode
gfs2: Fix and clean up create / evict interaction
gfs2: Handle -EBUSY result of insert_inode_locked4
gfs2: Cosmetic gfs2_dinode_{in,out} cleanup
gfs2: Always check inode size of inline inodes
gfs2: Make gfs2_glock_hold return its glock argument
gfs2: Avoid dequeuing GL_ASYNC glock holders twice
gfs2: Clean up after gfs2_create_inode rework
gfs2: Simply dequeue iopen glock in gfs2_evict_inode
gfs2: Uninline and improve glock_{set,clear}_object
gfs2: Add gfs2_inode_lookup comment
gfs2: Partially revert gfs2_inode_lookup change
gfs2: Minor gfs2_try_evict cleanup
gfs2: Remove support for glock holder auto-demotion
gfs2: Remove support for glock holder auto-demotion (2)
fs/gfs2/aops.c | 2 -
fs/gfs2/bmap.c | 3 -
fs/gfs2/file.c | 3 +-
fs/gfs2/glock.c | 269 ++++++++++++++++++++----------------------------------
fs/gfs2/glock.h | 65 +------------
fs/gfs2/glops.c | 44 +++++----
fs/gfs2/incore.h | 1 -
fs/gfs2/inode.c | 64 +++++++------
fs/gfs2/meta_io.c | 6 ++
fs/gfs2/super.c | 84 +++++++++--------
fs/gfs2/xattr.c | 26 +++---
11 files changed, 234 insertions(+), 333 deletions(-)
next reply other threads:[~2022-12-16 14:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 14:33 Andreas Gruenbacher [this message]
2022-12-17 14:28 ` [Cluster-devel] [GIT PULL] gfs2 fixes pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-09-05 16:12 Andreas Gruenbacher
2023-09-05 20:14 ` pr-tracker-bot
2023-08-08 12:53 Andreas Gruenbacher
2023-08-08 17:00 ` pr-tracker-bot
2023-07-04 12:51 Andreas Gruenbacher
2023-07-04 18:59 ` pr-tracker-bot
2023-02-22 12:01 Andreas Gruenbacher
2023-02-22 22:27 ` pr-tracker-bot
2022-10-09 10:45 Andreas Gruenbacher
2022-10-11 3:43 ` pr-tracker-bot
2022-08-05 20:12 Andreas Gruenbacher
2022-08-06 22:08 ` pr-tracker-bot
2022-05-24 19:41 Andreas Gruenbacher
2022-05-25 2:16 ` 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-02-11 17:05 Andreas Gruenbacher
2022-02-11 19:47 ` Linus Torvalds
2022-02-11 21:40 ` Andreas Gruenbacher
2022-02-11 20:05 ` 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=20221216143317.668868-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
/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).