public inbox for linux-kernel@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.6-rc6
Date: Wed, 11 Oct 2023 11:51:10 +0200	[thread overview]
Message-ID: <cover.1697017675.git.dsterba@suse.com> (raw)

Hi,

a revert of recent mount option parsing fix, this breaks mounts with
security options. The second patch is the flexible array annotation.

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit e36f94914021e58ee88a8856c7fdf35adf9c7ee1:

  btrfs: error out when reallocating block for defrag using a stale transaction (2023-10-04 01:04:33 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 75f5f60bf7ee075ed4a29637ce390898b4c36811:

  btrfs: add __counted_by for struct btrfs_delayed_item and use struct_size() (2023-10-11 11:37:19 +0200)

----------------------------------------------------------------
David Sterba (1):
      Revert "btrfs: reject unknown mount options early"

Gustavo A. R. Silva (1):
      btrfs: add __counted_by for struct btrfs_delayed_item and use struct_size()

 fs/btrfs/delayed-inode.c | 2 +-
 fs/btrfs/delayed-inode.h | 2 +-
 fs/btrfs/super.c         | 4 ----
 3 files changed, 2 insertions(+), 6 deletions(-)

             reply	other threads:[~2023-10-11  9:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11  9:51 David Sterba [this message]
2023-10-11 21:58 ` [GIT PULL] Btrfs fixes for 6.6-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.1697017675.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