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 changes for the 5.6 merge window (2)
Date: Fri,  7 Feb 2020 12:50:39 +0100	[thread overview]
Message-ID: <20200207115039.48920-1-agruenba@redhat.com> (raw)

Hi Linus,

could you please pull the following additional changes for gfs2?

Thanks a lot,
Andreas

The following changes since commit a62aa6f7f50a9a0af5e07d98774f8a7b439d390f:

  Merge tag 'gfs2-for-5.6' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2020-01-31 13:07:16 -0800)

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-2

for you to fetch changes up to 6e5e41e2dc4e4413296d5a4af54ac92d7cd52317:

  gfs2: fix O_SYNC write handling (2020-02-06 18:49:41 +0100)

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

- Fix a bug in Abhi Das's journal head lookup improvements that can cause a
  valid journal to be rejected.
- Fix an O_SYNC write handling bug reported by Christoph Hellwig.

----------------------------------------------------------------
Abhi Das (1):
      gfs2: fix gfs2_find_jhead that returns uninitialized jhead with seq 0

Andreas Gruenbacher (1):
      gfs2: fix O_SYNC write handling

Christoph Hellwig (1):
      gfs2: move setting current->backing_dev_info

 fs/gfs2/file.c | 72 +++++++++++++++++++++++++---------------------------------
 fs/gfs2/lops.c |  2 +-
 2 files changed, 32 insertions(+), 42 deletions(-)


             reply	other threads:[~2020-02-07 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 11:50 Andreas Gruenbacher [this message]
2020-02-08  2: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=20200207115039.48920-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®