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.15-rc6
Date: Fri,  7 Mar 2025 20:58:03 +0100	[thread overview]
Message-ID: <cover.1741370327.git.dsterba@suse.com> (raw)

Hi,

please pull a few more fixes for btrfs, thanks.

- fix leaked extent map after error when reading chunks

- replace use of deprecated strncpy

- in zoned mode, fixed range when ulocking extent range, causing a hang

----------------------------------------------------------------
The following changes since commit efa11fd269c139e29b71ec21bc9c9c0063fde40d:

  btrfs: fix data overwriting bug during buffered write when block size < page size (2025-02-21 09:32:24 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 35d99c68af40a8ca175babc5a89ef7e2226fb3ca:

  btrfs: fix a leaked chunk map issue in read_one_chunk() (2025-03-06 14:40:09 +0100)

----------------------------------------------------------------
Haoxiang Li (1):
      btrfs: fix a leaked chunk map issue in read_one_chunk()

Naohiro Aota (1):
      btrfs: zoned: fix extent range end unlock in cow_file_range()

Thorsten Blum (1):
      btrfs: replace deprecated strncpy() with strscpy()

 fs/btrfs/inode.c   | 9 +++++++--
 fs/btrfs/sysfs.c   | 4 ++--
 fs/btrfs/volumes.c | 1 +
 3 files changed, 10 insertions(+), 4 deletions(-)

             reply	other threads:[~2025-03-07 19:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 19:58 David Sterba [this message]
2025-03-07 22:30 ` [GIT PULL] Btrfs fixes for 6.15-rc6 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2025-05-06 14:06 David Sterba
2025-05-06 16:38 ` 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.1741370327.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.