linux-btrfs.vger.kernel.org archive mirror
 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.9-rc6
Date: Wed, 24 Apr 2024 12:01:52 +0200	[thread overview]
Message-ID: <cover.1713884233.git.dsterba@suse.com> (raw)

Hi,

please pull a few more fixes, thanks.

- fix information leak by the buffer returned from LOGICAL_INO ioctl

- fix flipped condition in scrub when tracking sectors in zoned mode

- fix calculation when dropping extent range

- reinstate fallback to write uncompressed data in case of fragmented
  space that could not store the entire compressed chunk

- minor fix to message formatting style to make it conforming to the
  commonly used style

----------------------------------------------------------------
The following changes since commit 1db7959aacd905e6487d0478ac01d89f86eb1e51:

  btrfs: do not wait for short bulk allocation (2024-04-09 23:20:32 +0200)

are available in the Git repository at:

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

for you to fetch changes up to fe1c6c7acce10baf9521d6dccc17268d91ee2305:

  btrfs: fix wrong block_start calculation for btrfs_drop_extent_map_range() (2024-04-18 18:18:50 +0200)

----------------------------------------------------------------
David Sterba (1):
      btrfs: remove colon from messages with state

Johannes Thumshirn (1):
      btrfs: fix information leak in btrfs_ioctl_logical_to_ino()

Naohiro Aota (1):
      btrfs: scrub: run relocation repair when/only needed

Qu Wenruo (1):
      btrfs: fix wrong block_start calculation for btrfs_drop_extent_map_range()

Sweet Tea Dorminy (1):
      btrfs: fallback if compressed IO fails for ENOSPC

 fs/btrfs/backref.c                | 12 +++---------
 fs/btrfs/extent_map.c             |  2 +-
 fs/btrfs/inode.c                  | 13 ++++++-------
 fs/btrfs/messages.c               |  2 +-
 fs/btrfs/scrub.c                  | 18 +++++++++---------
 fs/btrfs/tests/extent-map-tests.c |  5 +++++
 6 files changed, 25 insertions(+), 27 deletions(-)

             reply	other threads:[~2024-04-24 10:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 10:01 David Sterba [this message]
2024-04-24 16:30 ` [GIT PULL] Btrfs fixes for 6.9-rc6 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.1713884233.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 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 NNTP newsgroup(s).