From: David Sterba <dsterba@suse.cz>
To: torvalds@linux-foundation.org
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.18-rc6
Date: Mon, 2 May 2022 18:47:39 +0200 [thread overview]
Message-ID: <cover.1651509134.git.dsterba@suse.com> (raw)
Hi,
a few more fixes mostly around how some file attributes could be set.
Please pull, thanks.
- fix handling of compression property
- don't allow setting it on anything else than regular file or
directory
- do not allow setting it on nodatacow files via properties
- improved error handling when setting xattr
- make sure symlinks are always properly logged
----------------------------------------------------------------
The following changes since commit 5f0addf7b89085f8e0a2593faa419d6111612b9b:
btrfs: zoned: use dedicated lock for data relocation (2022-04-21 16:06:24 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.18-rc5-tag
for you to fetch changes up to 4b73c55fdebd8939f0f6000921075f7f6fa41397:
btrfs: skip compression property for anything other than files and dirs (2022-04-27 22:20:21 +0200)
----------------------------------------------------------------
Chung-Chiang Cheng (2):
btrfs: export a helper for compression hard check
btrfs: do not allow compression on nodatacow files
Filipe Manana (3):
btrfs: always log symlinks in full mode
btrfs: do not BUG_ON() on failure to update inode when setting xattr
btrfs: skip compression property for anything other than files and dirs
fs/btrfs/btrfs_inode.h | 11 ++++++++++
fs/btrfs/inode.c | 15 ++-----------
fs/btrfs/props.c | 59 +++++++++++++++++++++++++++++++++++++++++++++-----
fs/btrfs/props.h | 4 +++-
fs/btrfs/tree-log.c | 14 +++++++++++-
fs/btrfs/xattr.c | 11 +++++++---
6 files changed, 91 insertions(+), 23 deletions(-)
next reply other threads:[~2022-05-02 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 16:47 David Sterba [this message]
2022-05-02 19:03 ` [GIT PULL] Btrfs fixes for 5.18-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.1651509134.git.dsterba@suse.com \
--to=dsterba@suse.cz \
--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).