linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 5.8
Date: Mon,  8 Jun 2020 18:32:50 +0200	[thread overview]
Message-ID: <20200608163250.550547-1-agruenba@redhat.com> (raw)

Hi Linus,

please consider pulling the following gfs2 changes for 5.8.

Thanks a lot,
Andreas

The following changes since commit 3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162:

  Linux 5.7 (2020-05-31 16:49:15 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-for-5.8

for you to fetch changes up to 300e549b6e53025ea69550f009451f7a13bfc3eb:

  Merge branch 'gfs2-iopen' into for-next (2020-06-05 21:25:36 +0200)

----------------------------------------------------------------
Changes in gfs2:

- An iopen glock locking scheme rework that speeds up deletes of
  inodes accessed from multiple nodes.
- Various bug fixes and debugging improvements.
- Convert gfs2-glocks.txt to ReST.

----------------------------------------------------------------
Andreas Gruenbacher (10):
      gfs2: Keep track of deleted inode generations in LVBs
      gfs2: Turn gl_delete into a delayed work
      gfs2: Give up the iopen glock on contention
      gfs2: Try harder to delete inodes locally
      gfs2: Minor gfs2_lookup_by_inum cleanup
      gfs2: Move inode generation number check into gfs2_inode_lookup
      gfs2: Check inode generation number in delete_work_func
      gfs2: Wake up when setting GLF_DEMOTE
      gfs2: Smarter iopen glock waiting
      Merge branch 'gfs2-iopen' into for-next

Bob Peterson (10):
      gfs2: Don't ignore inode write errors during inode_go_sync
      gfs2: Allow lock_nolock mount to specify jid=X
      gfs2: Only do glock put in gfs2_create_inode for free inodes
      gfs2: print mapping->nrpages in glock dump for address space glocks
      gfs2: introduce new gfs2_glock_assert_withdraw
      gfs2: instrumentation wrt log_flush stuck
      gfs2: Allow ASPACE glocks to also have an lvb
      gfs2: initialize transaction tr_ailX_lists earlier
      gfs2: new slab for transactions
      gfs2: fix use-after-free on transaction ail lists

Mauro Carvalho Chehab (1):
      docs: filesystems: convert gfs2-glocks.txt to ReST

 .../{gfs2-glocks.txt => gfs2-glocks.rst}           | 149 ++++++++-------
 Documentation/filesystems/index.rst                |   1 +
 MAINTAINERS                                        |   2 +-
 fs/gfs2/export.c                                   |   4 +-
 fs/gfs2/glock.c                                    | 208 ++++++++++++++++++---
 fs/gfs2/glock.h                                    |  16 ++
 fs/gfs2/glops.c                                    |  21 ++-
 fs/gfs2/incore.h                                   |   9 +-
 fs/gfs2/inode.c                                    |  47 +++--
 fs/gfs2/inode.h                                    |   2 +-
 fs/gfs2/log.c                                      |  56 ++++--
 fs/gfs2/main.c                                     |   9 +
 fs/gfs2/ops_fstype.c                               |   2 +-
 fs/gfs2/rgrp.c                                     |   2 +-
 fs/gfs2/super.c                                    |  72 ++++++-
 fs/gfs2/trans.c                                    |  21 ++-
 fs/gfs2/trans.h                                    |   1 +
 fs/gfs2/util.c                                     |   1 +
 fs/gfs2/util.h                                     |   1 +
 include/uapi/linux/gfs2_ondisk.h                   |   6 +
 20 files changed, 489 insertions(+), 141 deletions(-)
 rename Documentation/filesystems/{gfs2-glocks.txt => gfs2-glocks.rst} (63%)


             reply	other threads:[~2020-06-08 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 16:32 Andreas Gruenbacher [this message]
2020-06-08 20:05 ` [GIT PULL] GFS2 changes for 5.8 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=20200608163250.550547-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;
as well as URLs for NNTP newsgroup(s).