gfs2 filesystem and dlm development
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruenba@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
	gfs2@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] gfs2 changes for 6.14
Date: Mon, 20 Jan 2025 15:13:43 +0100	[thread overview]
Message-ID: <20250120141344.2017385-1-agruenba@redhat.com> (raw)

Dear Linus,

please consider pulling the following gfs2 changes.

Thanks,
Andreas

The following changes since commit ff2a7a064a69069554564f52b6a84fc8a8c7d688:

  Merge tag 'gfs2-for-6.13' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 (2024-11-26 12:34:50 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 7c9d9223802fbed4dee1ae301661bf346964c9d2:

  gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag (2025-01-14 18:54:08 +0100)

----------------------------------------------------------------
gfs2 changes

- In the quota code, to avoid spurious audit messages, don't call
  capable() when quotas are off.

- When changing the 'j' flag of an inode, truncate the inode address
  space to avoid mixing "buffer head" and "iomap" pages.

----------------------------------------------------------------
Andreas Gruenbacher (1):
      gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag

Christian Göttsche (1):
      gfs2: reorder capability check last

 fs/gfs2/file.c  | 1 +
 fs/gfs2/quota.h | 4 ++--
 2 files changed, 3 insertions(+), 2 deletions(-)


             reply	other threads:[~2025-01-20 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 14:13 Andreas Gruenbacher [this message]
2025-01-20 22:30 ` [GIT PULL] gfs2 changes for 6.14 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=20250120141344.2017385-1-agruenba@redhat.com \
    --to=agruenba@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --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