From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] GFS2 changes for the 5.6 merge window
Date: Fri, 31 Jan 2020 16:48:23 +0100 [thread overview]
Message-ID: <20200131154823.30363-1-agruenba@redhat.com> (raw)
Hi Linus,
could you please pull the following changes for gfs2?
In addition, please expect to see another pull request from Bob Peterson
about his gfs2 recovery patch queue shortly.
Thanks a lot,
Andreas
The following changes since commit 887352fb5ffd593d28f77059c09dabb47c5b86e9:
Merge branch 'for-linus' from git://git.kernel.dk/linux-block (2019-12-10 11:02:38 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-for-5.6
for you to fetch changes up to a31b4ec539e966515f1f97f4000d0e2a399930ce:
Revert "gfs2: eliminate tr_num_revoke_rm" (2020-01-28 15:04:53 +0100)
----------------------------------------------------------------
Changes in gfs2:
- Fix some corner cases on filesystems with a block size < page size.
- Fix a corner case that could expose incorrect access times over nfs.
- Revert an otherwise sensible revoke accounting cleanup that causes
assertion failures. The revoke accounting is whacky and needs to be
fixed properly before we can add back this cleanup.
- Various other minor cleanups.
----------------------------------------------------------------
Alex Shi (2):
fs/gfs2: remove unused IS_DINODE and IS_LEAF macros
gfs2: remove unused LBIT macros
Andreas Gruenbacher (4):
gfs2: Another gfs2_find_jhead fix
gfs2: Avoid access time thrashing in gfs2_inode_lookup
gfs2: Fix incorrect variable name
gfs2: Remove GFS2_MIN_LVB_SIZE define
Bob Peterson (3):
gfs2: eliminate ssize parameter from gfs2_struct2blk
gfs2: minor cleanup: remove unneeded variable ret in gfs2_jdata_writepage
Revert "gfs2: eliminate tr_num_revoke_rm"
fs/gfs2/aops.c | 4 +--
fs/gfs2/dir.c | 3 ---
fs/gfs2/glock.c | 2 +-
fs/gfs2/glops.c | 2 +-
fs/gfs2/incore.h | 6 ++---
fs/gfs2/inode.c | 10 ++++----
fs/gfs2/log.c | 21 +++++++---------
fs/gfs2/log.h | 4 +--
fs/gfs2/lops.c | 70 +++++++++++++++++++++++++++++++++-------------------
fs/gfs2/ops_fstype.c | 2 ++
fs/gfs2/rgrp.c | 10 --------
fs/gfs2/trans.c | 9 +++----
12 files changed, 73 insertions(+), 70 deletions(-)
next reply other threads:[~2020-01-31 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 15:48 Andreas Gruenbacher [this message]
2020-01-31 21:10 ` 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=20200131154823.30363-1-agruenba@redhat.com \
--to=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®