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 fix for 6.9
Date: Thu, 21 Mar 2024 17:42:03 +0100	[thread overview]
Message-ID: <cover.1711038961.git.dsterba@suse.com> (raw)

Hi,

please pull the following branch. It's fixing a problem found in 6.7
after adding the temp-fsid feature which changed device tracking in
memory and broke grub-probe. This is used on initrd-less systems. There
were several iterations of the fix and it took longer than expected.

The patch depends on VFS changes (bdev_handle) so it's based on merge of
last btrfs pull request.  We'll provide backport for stable trees.

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit 43a7548e28a6df12a6170421d9d016c576010baa:

  Merge tag 'for-6.9-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux (2024-03-12 12:28:34 -0700)

are available in the Git repository at:

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

for you to fetch changes up to d565fffa68560ac540bf3d62cc79719da50d5e7a:

  btrfs: do not skip re-registration for the mounted device (2024-03-18 19:16:50 +0100)

----------------------------------------------------------------
Anand Jain (1):
      btrfs: do not skip re-registration for the mounted device

 fs/btrfs/volumes.c | 58 +++++++++++++++++++++++++++++++++++++++++++-----------
 1 file changed, 47 insertions(+), 11 deletions(-)

             reply	other threads:[~2024-03-21 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 16:42 David Sterba [this message]
2024-03-21 17:34 ` [GIT PULL] Btrfs fix for 6.9 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.1711038961.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.