From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Pull request (merge window)
Date: Wed, 5 Jul 2017 09:08:40 -0400 (EDT) [thread overview]
Message-ID: <768389219.28737308.1499260120885.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <2018468119.28735933.1499259957760.JavaMail.zimbra@redhat.com>
Hi Linus,
Please consider pulling the following changes for the GFS2 file system.
Regards,
Bob Peterson
----------------------------------------------------------------
The following changes since commit 3ef2bc099d1cce09e2844467e2ced98e1a44609d:
Merge tag 'devicetree-for-4.12' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux (2017-05-05 19:33:07 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-4.13.fixes
for you to fetch changes up to 29695254ec51506d97b2a90ac27baabb438c70dd:
GFS2: constify attribute_group structures. (2017-07-05 07:21:14 -0500)
----------------------------------------------------------------
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.
The first patch eliminates the flush_delayed_work, which can block.
2. Andreas's second patch protects setting of gl_object for rgrps with
a spin_lock to prevent proven races.
3. His third patch introduces a centralized mechanism for queueing glock
work with better reference counting, to prevent more races.
4. His fourth patch retains a reference to inode glocks when an error
occurs while creating an inode. This keeps the subsequent evict from
needing to reacquire the glock, which might call into DLM and block
in low memory conditions.
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.
----------------------------------------------------------------
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(-)
next parent reply other threads:[~2017-07-05 13:08 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2018468119.28735933.1499259957760.JavaMail.zimbra@redhat.com>
2017-07-05 13:08 ` Bob Peterson [this message]
[not found] <2063498114.10752149.1552067836491.JavaMail.zimbra@redhat.com>
2019-03-08 17:58 ` [Cluster-devel] GFS2: Pull request (merge window) Bob Peterson
[not found] <180051537.56890898.1545229879645.JavaMail.zimbra@redhat.com>
2018-12-19 14:31 ` Bob Peterson
[not found] <1929897739.23623737.1540322729596.JavaMail.zimbra@redhat.com>
2018-10-23 19:26 ` Bob Peterson
2018-10-24 16:35 ` Linus Torvalds
2018-10-24 16:41 ` Bob Peterson
[not found] <1772901878.39899227.1528134744434.JavaMail.zimbra@redhat.com>
2018-06-04 17:53 ` Bob Peterson
[not found] <242799785.15741010.1522776740239.JavaMail.zimbra@redhat.com>
2018-04-03 17:32 ` Bob Peterson
[not found] <2035999397.5567269.1517410350526.JavaMail.zimbra@redhat.com>
2018-01-31 14:54 ` Bob Peterson
[not found] <800692691.31850756.1510678641181.JavaMail.zimbra@redhat.com>
2017-11-14 16:57 ` Bob Peterson
2017-11-14 17:17 ` Bob Peterson
[not found] <1332965725.6958432.1504544624096.JavaMail.zimbra@redhat.com>
2017-09-04 17:05 ` Bob Peterson
[not found] <909713995.4565875.1494016018520.JavaMail.zimbra@redhat.com>
2017-05-05 20:28 ` Bob Peterson
2017-05-05 21:07 ` Linus Torvalds
[not found] <1526627784.3659456.1493822813354.JavaMail.zimbra@redhat.com>
2017-05-03 16:41 ` Bob Peterson
[not found] <468087826.25173671.1487684421990.JavaMail.zimbra@redhat.com>
2017-02-21 13:41 ` Bob Peterson
[not found] <1872743029.687446.1475513532790.JavaMail.zimbra@redhat.com>
2016-10-03 16:52 ` Bob Peterson
[not found] <404724578.17300814.1469208769730.JavaMail.zimbra@redhat.com>
2016-07-22 17:33 ` Bob Peterson
[not found] <2074855986.8621406.1463772170266.JavaMail.zimbra@redhat.com>
2016-05-20 19:23 ` Bob Peterson
[not found] <2094757318.39162844.1458219077321.JavaMail.zimbra@redhat.com>
2016-03-17 12:51 ` Bob Peterson
[not found] <1243871936.8427302.1452623511952.JavaMail.zimbra@redhat.com>
2016-01-12 18:34 ` Bob Peterson
[not found] <337313427.7367463.1447086799887.JavaMail.zimbra@redhat.com>
2015-11-09 16:45 ` Bob Peterson
[not found] <987432592.26261269.1441889826020.JavaMail.zimbra@redhat.com>
2015-09-10 13:19 ` Bob Peterson
[not found] <1946368926.25134466.1435330524247.JavaMail.zimbra@redhat.com>
2015-06-26 14:56 ` Bob Peterson
[not found] <1305736412.15685734.1429033600005.JavaMail.zimbra@redhat.com>
2015-04-14 17:47 ` Bob Peterson
2015-04-14 23:16 ` Linus Torvalds
2015-04-15 7:34 ` Steven Whitehouse
2015-04-14 23:19 ` Linus Torvalds
2015-04-15 12:09 ` Bob Peterson
2015-02-10 11:04 Steven Whitehouse
-- strict thread matches above, loose matches on Subject: below --
2014-12-08 18:26 Steven Whitehouse
2014-10-08 19:25 Steven Whitehouse
2014-06-04 9:33 Steven Whitehouse
2014-04-01 23:15 Steven Whitehouse
2014-04-04 21:52 ` Linus Torvalds
2014-04-07 9:31 ` Steven Whitehouse
2014-01-20 19:15 Steven Whitehouse
2013-11-05 15:39 Steven Whitehouse
2013-09-09 9:22 Steven Whitehouse
2013-07-01 15:20 Steven Whitehouse
2013-04-29 11:08 Steven Whitehouse
2013-02-19 16:38 Steven Whitehouse
2012-12-11 10:39 Steven Whitehouse
2012-09-13 13:42 [Cluster-devel] GFS2: Pull request (fixes) Steven Whitehouse
2012-10-01 9:09 ` [Cluster-devel] GFS2: Pull request (merge window) Steven Whitehouse
2012-07-23 14:59 Steven Whitehouse
2012-08-03 1:22 ` Linus Torvalds
2012-08-03 10:18 ` Steven Whitehouse
2012-08-03 16:16 ` Linus Torvalds
2012-05-21 8:17 Steven Whitehouse
2012-03-20 16:10 Steven Whitehouse
2012-01-06 12:09 Steven Whitehouse
2011-10-25 8:41 Steven Whitehouse
2011-07-22 12:08 Steven Whitehouse
2011-05-20 8:14 Steven Whitehouse
2011-03-16 13:55 Steven Whitehouse
2011-01-05 10:22 Steven Whitehouse
2010-10-21 9:43 Steven Whitehouse
2010-08-03 9:06 Steven Whitehouse
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=768389219.28737308.1499260120885.JavaMail.zimbra@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).