cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: [Cluster-devel] [GIT PULL] gfs2 fixes
Date: Tue,  8 Aug 2023 14:53:15 +0200	[thread overview]
Message-ID: <20230808125315.1727575-1-agruenba@redhat.com> (raw)

Hi Linus,

please consider pulling the following two gfs2 fixes.

Thanks,
Andreas

The following changes since commit 94c76955e86a5a4f16a1d690b66dcc268c156e6a:

  Merge tag 'gfs2-v6.4-rc5-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2023-07-04 11:45:16 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git tags/gfs2-v6.4-fixes

for you to fetch changes up to 0be8432166a61abc537e1247e530f4b85970b56b:

  gfs2: Don't use filemap_splice_read (2023-08-07 18:42:04 +0200)

----------------------------------------------------------------
gfs2 fixes

- Fix a freeze consistency check in gfs2_trans_add_meta().

- Don't use filemap_splice_read as it can cause deadlocks on gfs2.

----------------------------------------------------------------
Andreas Gruenbacher (1):
      gfs2: Fix freeze consistency check in gfs2_trans_add_meta

Bob Peterson (1):
      gfs2: Don't use filemap_splice_read

 fs/gfs2/file.c  |  4 ++--
 fs/gfs2/trans.c | 14 ++++++++++----
 2 files changed, 12 insertions(+), 6 deletions(-)


             reply	other threads:[~2023-08-08 12:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08 12:53 Andreas Gruenbacher [this message]
2023-08-08 17:00 ` [Cluster-devel] [GIT PULL] gfs2 fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-09-05 16:12 Andreas Gruenbacher
2023-09-05 20:14 ` pr-tracker-bot
2023-07-04 12:51 Andreas Gruenbacher
2023-07-04 18:59 ` pr-tracker-bot
2023-02-22 12:01 Andreas Gruenbacher
2023-02-22 22:27 ` pr-tracker-bot
2022-12-16 14:33 Andreas Gruenbacher
2022-12-17 14:28 ` pr-tracker-bot
2022-10-09 10:45 Andreas Gruenbacher
2022-10-11  3:43 ` pr-tracker-bot
2022-08-05 20:12 Andreas Gruenbacher
2022-08-06 22:08 ` pr-tracker-bot
2022-05-24 19:41 Andreas Gruenbacher
2022-05-25  2:16 ` pr-tracker-bot
2022-05-13 21:07 Andreas Gruenbacher
2022-05-13 21:35 ` Linus Torvalds
2022-05-13 21:38 ` pr-tracker-bot
2022-02-11 17:05 Andreas Gruenbacher
2022-02-11 19:47 ` Linus Torvalds
2022-02-11 21:40   ` Andreas Gruenbacher
2022-02-11 20:05 ` 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=20230808125315.1727575-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).