public inbox for linux-btrfs@vger.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.2-rc5, part 2
Date: Fri, 20 Jan 2023 18:09:36 +0100	[thread overview]
Message-ID: <cover.1674232757.git.dsterba@suse.com> (raw)

Hi,

there are two more fixes and an update that's not a fix but replaces use
of write_one_page which is going to be removed (similar updates to other
filesystems go via other trees).

Please pull, thanks.

- fix potential out-of-bounds access to leaf data when seeking in an
  inline file

- fix potential crash in quota when rescan races with disable

- reimplement super block signature scratching by marking page/folio
  dirty and syncing block device, allow removing write_one_page

----------------------------------------------------------------
The following changes since commit 09e44868f1e03c7825ca4283256abedc95e249a3:

  btrfs: do not abort transaction on failure to update log root (2023-01-12 15:43:31 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.2-rc4-tag

for you to fetch changes up to b7adbf9ada3513d2092362c8eac5cddc5b651f5c:

  btrfs: fix race between quota rescan and disable leading to NULL pointer deref (2023-01-16 19:46:54 +0100)

----------------------------------------------------------------
Christoph Hellwig (2):
      btrfs: factor out scratching of one regular super block
      btrfs: stop using write_one_page in btrfs_scratch_superblock

Filipe Manana (2):
      btrfs: fix invalid leaf access due to inline extent during lseek
      btrfs: fix race between quota rescan and disable leading to NULL pointer deref

 fs/btrfs/file.c    | 13 ++++++++++---
 fs/btrfs/qgroup.c  | 25 +++++++++++++++++--------
 fs/btrfs/volumes.c | 50 +++++++++++++++++++++++++-------------------------
 3 files changed, 52 insertions(+), 36 deletions(-)

             reply	other threads:[~2023-01-20 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 17:09 David Sterba [this message]
2023-01-20 20:06 ` [GIT PULL] Btrfs fixes for 6.2-rc5, part 2 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.1674232757.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