From: Dave Chinner <david@fromorbit.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: ntfs3@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Jiaji Qin <jjtan24@m.fudan.edu.cn>,
Kun Hu <huk23@m.fudan.edu.cn>
Subject: Re: [PATCH] fs/ntfs3: Update inode->i_mapping->a_ops on compression state change
Date: Fri, 24 Jan 2025 07:24:45 +1100 [thread overview]
Message-ID: <Z5KljQpaTp9ZlJxj@dread.disaster.area> (raw)
In-Reply-To: <20250123135335.15060-1-almaz.alexandrovich@paragon-software.com>
On Thu, Jan 23, 2025 at 04:53:35PM +0300, Konstantin Komarov wrote:
> Update inode->i_mapping->a_ops when the compression state changes to
> ensure correct address space operations.
> Clear ATTR_FLAG_SPARSED/FILE_ATTRIBUTE_SPARSE_FILE when enabling
> compression to prevent flag conflicts.
>
> Fixes: 6b39bfaeec44 ("fs/ntfs3: Add support for the compression attribute")
> Reported-by: Kun Hu <huk23@m.fudan.edu.cn>, Jiaji Qin <jjtan24@m.fudan.edu.cn>
> Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
> ---
> fs/ntfs3/attrib.c | 1 +
> fs/ntfs3/file.c | 2 ++
> fs/ntfs3/frecord.c | 6 ++++--
> 3 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ntfs3/attrib.c b/fs/ntfs3/attrib.c
> index af94e3737470..d2410ab6c7bf 100644
> --- a/fs/ntfs3/attrib.c
> +++ b/fs/ntfs3/attrib.c
> @@ -2666,6 +2666,7 @@ int attr_set_compress(struct ntfs_inode *ni, bool compr)
>
> /* Update data attribute flags. */
> if (compr) {
> + attr->flags &= ATTR_FLAG_SPARSED;
> attr->flags |= ATTR_FLAG_COMPRESSED;
> attr->nres.c_unit = NTFS_LZNT_CUNIT;
> } else {
> diff --git a/fs/ntfs3/file.c b/fs/ntfs3/file.c
> index 3f96a11804c9..e8f452f47cd5 100644
> --- a/fs/ntfs3/file.c
> +++ b/fs/ntfs3/file.c
> @@ -105,6 +105,8 @@ int ntfs_fileattr_set(struct mnt_idmap *idmap, struct dentry *dentry,
> int err = ni_set_compress(inode, flags & FS_COMPR_FL);
> if (err)
> return err;
> + inode->i_mapping->a_ops =
> + (flags & FS_COMPR_FL) ? &ntfs_aops_cmpr : &ntfs_aops;
It is not safe to change a_ops dynamically like this.
There can be other operations running concurrently using the
existing aops, and some functionality (e.g. the page fault paths)
have dependencies between aops methods and swapping the aops between
those operations can cause all sorts of problem (including crashing
the kernel).
This is the reason why we cannot turn functionality like FSDAX on
and off via fileattr_set() methods setting/clearing inode flags.
The inode has to transition out of cache and be re-instantiated to
change the inode aops methods safely...
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2025-01-23 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 13:53 Konstantin Komarov
2025-01-23 20:24 ` Dave Chinner [this message]
2025-01-28 6:07 ` Christoph Hellwig
2025-01-31 13:18 ` [PATCH v2] fs/ntfs3: Update inode->i_mapping->a_ops on compression state Konstantin Komarov
2025-02-14 2:38 ` Kun Hu
2025-02-18 5:31 ` Kun Hu
2025-02-18 6:15 ` Dave Chinner
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=Z5KljQpaTp9ZlJxj@dread.disaster.area \
--to=david@fromorbit.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=huk23@m.fudan.edu.cn \
--cc=jjtan24@m.fudan.edu.cn \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
/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
all inboxes | Powered by JetHome®