All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.14-rc3
Date: Thu, 13 Feb 2025 21:02:41 +0100	[thread overview]
Message-ID: <cover.1739475780.git.dsterba@suse.com> (raw)

Hi,

please pull, a few more btrfs fixes. Thanks.

- fix stale page cache after race between readahead and direct IO write

- fix hole expansion when writing at an offset beyond EOF, the range
  will not be zeroed

- use proper way to calculate offsets in folio ranges

----------------------------------------------------------------
The following changes since commit fdef89ce6fada462aef9cb90a140c93c8c209f0f:

  btrfs: avoid starting new transaction when cleaning qgroup during subvolume drop (2025-01-23 22:34:17 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.14-rc2-tag

for you to fetch changes up to da2dccd7451de62b175fb8f0808d644959e964c7:

  btrfs: fix hole expansion when writing at an offset beyond EOF (2025-02-11 23:09:03 +0100)

----------------------------------------------------------------
Filipe Manana (2):
      btrfs: fix stale page cache after race between readahead and direct IO write
      btrfs: fix hole expansion when writing at an offset beyond EOF

Matthew Wilcox (Oracle) (1):
      btrfs: fix two misuses of folio_shift()

 fs/btrfs/extent_io.c | 29 ++++++++++++++++++++---------
 fs/btrfs/file.c      |  4 +---
 2 files changed, 21 insertions(+), 12 deletions(-)

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13 20:02 David Sterba [this message]
2025-02-13 20:28 ` [GIT PULL] Btrfs fixes for 6.14-rc3 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=cover.1739475780.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.