From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/9] GFS2: Pre-pull patch posting (merge window)
Date: Fri, 20 May 2016 11:22:18 -0500 [thread overview]
Message-ID: <1463761347-19864-1-git-send-email-rpeterso@redhat.com> (raw)
Hi,
We've got nine patches this time:
- Abhi Das has two patches that fix a GFS2 splice issue (and an adjustment).
- Ben Marzinski has a patch which allows the proper unmount of a GFS2
file system after hitting a withdraw error.
- I have a patch to fix a problem where GFS2 would dereference an error
value, plus three cosmetic / refactoring patches.
- Daniel DeFreez has a patch to fix two glock reference count problems,
where GFS2 was not properly "uninitializing" its glock holder on error
paths.
- Denys Vlasenko has a patch to change a function to not be inlined,
thus reducing the memory footprint of the GFS2 module.
Regards,
Bob Peterson
---
Abhi Das (2):
gfs2: Use gfs2 wrapper to sync inode before calling
generic_file_splice_read()
gfs2: use inode_lock/unlock instead of accessing i_mutex directly
Benjamin Marzinski (1):
GFS2: ignore unlock failures after withdraw
Bob Peterson (4):
GFS2: Get rid of dead code in inode_go_demote_ok
GFS2: Don't dereference inode in gfs2_inode_lookup until it's valid
GFS2: Remove allocation parms from gfs2_rbm_find
GFS2: Refactor gfs2_remove_from_journal
Daniel DeFreez (1):
GFS2: Add calls to gfs2_holder_uninit in two error handlers
Denys Vlasenko (1):
GFS2: fs/gfs2/glock.c: Deinline do_error, save 1856 bytes
fs/gfs2/aops.c | 5 +++--
fs/gfs2/file.c | 31 ++++++++++++++++++++++++++++---
fs/gfs2/glock.c | 11 +++++++++--
fs/gfs2/glops.c | 7 -------
fs/gfs2/inode.c | 6 +++---
fs/gfs2/meta_io.c | 7 ++++---
fs/gfs2/meta_io.h | 8 ++++++--
fs/gfs2/rgrp.c | 16 ++++++----------
fs/gfs2/util.c | 1 +
9 files changed, 60 insertions(+), 32 deletions(-)
--
2.5.5
next reply other threads:[~2016-05-20 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 16:22 Bob Peterson [this message]
2016-05-20 16:22 ` [Cluster-devel] [PATCH 1/9] GFS2: ignore unlock failures after withdraw Bob Peterson
2016-05-20 16:22 ` [Cluster-devel] [PATCH 2/9] GFS2: Get rid of dead code in inode_go_demote_ok Bob Peterson
2016-05-20 16:22 ` [Cluster-devel] [PATCH 3/9] gfs2: Use gfs2 wrapper to sync inode before calling generic_file_splice_read() Bob Peterson
2016-05-20 16:22 ` [Cluster-devel] [PATCH 4/9] GFS2: fs/gfs2/glock.c: Deinline do_error, save 1856 bytes Bob Peterson
2016-05-20 16:22 ` [Cluster-devel] [PATCH 5/9] GFS2: Don't dereference inode in gfs2_inode_lookup until it's valid Bob Peterson
2016-05-20 16:22 ` [Cluster-devel] [PATCH 6/9] GFS2: Add calls to gfs2_holder_uninit in two error handlers Bob Peterson
2016-05-20 16:22 ` [Cluster-devel] [PATCH 7/9] gfs2: use inode_lock/unlock instead of accessing i_mutex directly Bob Peterson
2016-05-20 16:22 ` [Cluster-devel] [PATCH 8/9] GFS2: Remove allocation parms from gfs2_rbm_find Bob Peterson
2016-05-20 16:22 ` [Cluster-devel] [PATCH 9/9] GFS2: Refactor gfs2_remove_from_journal Bob Peterson
-- strict thread matches above, loose matches on Subject: below --
2018-06-04 16:29 [Cluster-devel] [PATCH 0/9] GFS2: Pre-pull patch posting (merge window) Bob Peterson
2018-04-02 15:44 Bob Peterson
2017-05-03 13:45 Bob Peterson
2015-04-13 15:10 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=1463761347-19864-1-git-send-email-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).