From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 0/6] Refactor gfs2_evict_inode (V2)
Date: Wed, 16 Sep 2020 10:00:14 -0500 [thread overview]
Message-ID: <20200916150020.36582-1-rpeterso@redhat.com> (raw)
Function gfs2_evict_inode is very large and messy. This patch set is an
attempt to simplify the function and make it more understandable. This
will make it easier to maintain.
This is the second version of this patch set, and it implements the suggestions
Andreas made.
It also now adds a patch to fix a bug in which unmount causes a kernel panic
when system inode glocks still have pages in memory.
Bob Peterson (6):
gfs2: switch variable error to ret in gfs2_evict_inode
gfs2: factor evict_deleted_inode out of gfs2_evict_inode
gfs2: further simplify gfs2_evict_inode with new func
evict_should_delete
gfs2: factor out evict code related to dinodes we are not deleting
gfs2: simplify the logic in gfs2_evict_inode
gfs2: special evict process for system inodes
fs/gfs2/ops_fstype.c | 15 ++-
fs/gfs2/super.c | 244 ++++++++++++++++++++++++++++---------------
2 files changed, 170 insertions(+), 89 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-16 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 15:00 Bob Peterson [this message]
2020-09-16 15:00 ` [Cluster-devel] [GFS2 PATCH 1/6] gfs2: switch variable error to ret in gfs2_evict_inode Bob Peterson
2020-09-16 15:00 ` [Cluster-devel] [GFS2 PATCH 2/6] gfs2: factor evict_deleted_inode out of gfs2_evict_inode Bob Peterson
2020-09-16 15:00 ` [Cluster-devel] [GFS2 PATCH 3/6] gfs2: further simplify gfs2_evict_inode with new func evict_should_delete Bob Peterson
2020-09-16 15:00 ` [Cluster-devel] [GFS2 PATCH 4/6] gfs2: factor out evict code related to dinodes we are not deleting Bob Peterson
2020-09-16 15:00 ` [Cluster-devel] [GFS2 PATCH 5/6] gfs2: simplify the logic in gfs2_evict_inode Bob Peterson
2020-09-16 15:00 ` [Cluster-devel] [GFS2 PATCH 6/6] gfs2: special evict process for system inodes Bob Peterson
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=20200916150020.36582-1-rpeterso@redhat.com \
--to=rpeterso@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).