From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/8] GFS2: Pre-pull patch posting (merge window)
Date: Mon, 3 Jul 2017 12:19:21 -0500 [thread overview]
Message-ID: <20170703171929.7866-1-rpeterso@redhat.com> (raw)
Hi,
We've got eight GFS2 patches for this merge window:
1. Andreas Gruenbacher has four patches related to cleaning up the GFS2
inode evict process. This is about half of his patches designed to
fix a long-standing GFS2 hang related to the inode shrinker.
(Shrinker calls gfs2 evict, evict calls DLM, DLM requires memory
and blocks on the shrinker.) These 4 patches have been well tested.
His second set of patches are still being tested, so I plan to hold
them until the next merge window, after we have more weeks of testing.
5. Arvind Yadav has a patch to add const to attribute_group structures.
6. I have a patch to detect directory entry inconsistencies and withdraw
the file system if any are found. Better that than silent corruption.
7. I have a patch to remove a vestigial variable from glock structures,
saving some slab space.
8. I have another patch to remove a vestigial variable from the GFS2
in-core superblock structure.
Regards,
Bob Peterson
---
Andreas Gruenbacher (4):
gfs2: Get rid of flush_delayed_work in gfs2_evict_inode
gfs2: Protect gl->gl_object by spin lock
gfs2: Clean up glock work enqueuing
gfs2: gfs2_create_inode: Keep glock across iput
Arvind Yadav (1):
GFS2: constify attribute_group structures.
Bob Peterson (3):
GFS2: Withdraw when directory entry inconsistencies are detected
GFS2: Remove gl_list from glock structure
GFS2: Eliminate vestigial sd_log_flush_wrapped
fs/gfs2/bmap.c | 2 +-
fs/gfs2/dir.c | 7 ++--
fs/gfs2/glock.c | 124 +++++++++++++++++++++++++++++++++----------------------
fs/gfs2/glock.h | 7 ++++
fs/gfs2/glops.c | 56 ++++++++++++++++++++-----
fs/gfs2/incore.h | 5 ++-
fs/gfs2/inode.c | 19 +++++----
fs/gfs2/log.c | 3 --
fs/gfs2/lops.c | 6 +--
fs/gfs2/main.c | 1 -
fs/gfs2/rgrp.c | 6 +--
fs/gfs2/super.c | 33 +++++++++------
fs/gfs2/sys.c | 4 +-
fs/gfs2/xattr.c | 4 +-
14 files changed, 175 insertions(+), 102 deletions(-)
--
2.9.4
next reply other threads:[~2017-07-03 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 17:19 Bob Peterson [this message]
2017-07-03 17:19 ` [Cluster-devel] [PATCH 1/8] GFS2: Withdraw when directory entry inconsistencies are detected Bob Peterson
2017-07-03 17:19 ` [Cluster-devel] [PATCH 2/8] GFS2: Remove gl_list from glock structure Bob Peterson
2017-07-03 17:19 ` [Cluster-devel] [PATCH 3/8] GFS2: Eliminate vestigial sd_log_flush_wrapped Bob Peterson
2017-07-03 17:19 ` [Cluster-devel] [PATCH 4/8] gfs2: Get rid of flush_delayed_work in gfs2_evict_inode Bob Peterson
2017-07-03 17:19 ` [Cluster-devel] [PATCH 5/8] gfs2: Protect gl->gl_object by spin lock Bob Peterson
2017-07-03 17:19 ` [Cluster-devel] [PATCH 6/8] gfs2: Clean up glock work enqueuing Bob Peterson
2017-07-03 17:19 ` [Cluster-devel] [PATCH 7/8] gfs2: gfs2_create_inode: Keep glock across iput Bob Peterson
2017-07-03 17:19 ` [Cluster-devel] [PATCH 8/8] GFS2: constify attribute_group structures Bob Peterson
-- strict thread matches above, loose matches on Subject: below --
2017-02-20 13:44 [Cluster-devel] [PATCH 0/8] GFS2: Pre-pull patch posting (merge window) 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=20170703171929.7866-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).