cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GIT PULL] gfs2 fix
Date: Tue,  6 Jun 2023 14:48:00 +0200	[thread overview]
Message-ID: <20230606124800.1151665-1-agruenba@redhat.com> (raw)

Hi Linus,

please consider pulling the following fix.

Thanks,
Andreas

The following changes since commit 48b1320a674e1ff5de2fad8606bee38f724594dc:

  Merge tag 'for-6.4-rc4-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux (2023-05-30 17:23:50 -0400)

are available in the Git repository at:

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

for you to fetch changes up to fa58cc888d67e640e354d8b3ceef877ea167b0cf:

  gfs2: Don't get stuck writing page onto itself under direct I/O (2023-06-01 14:55:43 +0200)

----------------------------------------------------------------
gfs2 fix

- Don't get stuck writing page onto itself under direct I/O.

----------------------------------------------------------------
Andreas Gruenbacher (1):
      gfs2: Don't get stuck writing page onto itself under direct I/O

 fs/gfs2/file.c | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

             reply	other threads:[~2023-06-06 12:48 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06 12:48 Andreas Gruenbacher [this message]
2023-06-06 12:55 ` [Cluster-devel] [GIT PULL] gfs2 fix Linus Torvalds
2023-06-06 13:32   ` Andreas Gruenbacher
2023-06-06 13:22 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-04-26 14:54 Andreas Gruenbacher
2022-04-26 18:31 ` Linus Torvalds
2022-04-26 21:27   ` Andreas Gruenbacher
2022-04-26 23:33     ` Linus Torvalds
2022-04-27 12:29       ` Andreas Gruenbacher
2022-04-27 17:13         ` Linus Torvalds
2022-04-27 19:41           ` Andreas Gruenbacher
2022-04-27 20:25             ` Linus Torvalds
2022-04-27 21:26               ` Andreas Gruenbacher
2022-04-27 22:20                 ` Linus Torvalds
2022-04-28  0:00                   ` Linus Torvalds
2022-04-28 13:26                     ` Andreas Gruenbacher
2022-04-28 17:09                       ` Linus Torvalds
2022-04-28 17:17                         ` Linus Torvalds
2022-04-28 17:21                           ` Andreas Gruenbacher
2022-04-28 17:38                         ` Andreas Gruenbacher
2022-05-02 18:31                           ` Linus Torvalds
2022-05-02 18:58                             ` Linus Torvalds
2022-05-02 20:24                               ` Andreas Gruenbacher
2022-05-03  8:56                             ` Andreas Gruenbacher
2022-05-03 13:30                               ` Andreas Gruenbacher
2022-05-03 16:19                               ` Linus Torvalds
2022-05-03 16:41                                 ` Andreas Gruenbacher
2022-05-03 16:50                                   ` Linus Torvalds
2022-05-03 21:35                               ` Andreas Gruenbacher
2022-05-03 22:41                                 ` Linus Torvalds
2022-05-04 17:52                                   ` Andreas Gruenbacher
2022-04-28 18:16                       ` pr-tracker-bot
2022-04-26 19:07 ` 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=20230606124800.1151665-1-agruenba@redhat.com \
    --to=agruenba@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 read-only IMAP folder(s) and NNTP newsgroup(s).