mirror of https://lore.kernel.org/lkml/
 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 fixes for 5.10-rc5
Date: Wed,  2 Dec 2020 21:58:39 +0100	[thread overview]
Message-ID: <20201202205839.843476-1-agruenba@redhat.com> (raw)

Hi Linus,

please consider pulling the following additional gfs2 fixes.

Thanks,
Andreas

The following changes since commit 418baf2c28f3473039f2f7377760bd8f6897ae18:

  Linux 5.10-rc5 (2020-11-22 15:36:08 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v5.10-rc5-fixes

for you to fetch changes up to dd0ecf544125639e54056d851e4887dbb94b6d2f:

  gfs2: Fix deadlock between gfs2_{create_inode,inode_lookup} and delete_work_func (2020-12-01 00:21:10 +0100)

----------------------------------------------------------------
Various gfs2 fixes

----------------------------------------------------------------
Alexander Aring (2):
      gfs2: Fix deadlock dumping resource group glocks
      gfs2: set lockdep subclass for iopen glocks

Andreas Gruenbacher (2):
      gfs2: Upgrade shared glocks for atime updates
      gfs2: Fix deadlock between gfs2_{create_inode,inode_lookup} and delete_work_func

Bob Peterson (2):
      gfs2: check for empty rgrp tree in gfs2_ri_update
      gfs2: Don't freeze the file system during unmount

 fs/gfs2/glock.c  |  1 +
 fs/gfs2/glops.c  |  6 ++++--
 fs/gfs2/incore.h |  1 +
 fs/gfs2/inode.c  | 42 ++++++++++++++++++++++++++++++++----------
 fs/gfs2/rgrp.c   |  4 ++++
 5 files changed, 42 insertions(+), 12 deletions(-)


             reply	other threads:[~2020-12-02 21:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02 20:58 Andreas Gruenbacher [this message]
2020-12-03  1:57 ` 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=20201202205839.843476-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®