From: Eric Biggers <ebiggers@kernel.org>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: viro@zeniv.linux.org.uk, jaegeuk@kernel.org, tytso@mit.edu,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, amir73il@gmail.com
Subject: Re: [PATCH v3 06/10] libfs: Add helper to choose dentry operations at mount
Date: Wed, 24 Jan 2024 19:13:48 -0800 [thread overview]
Message-ID: <20240125031348.GD52073@sol.localdomain> (raw)
In-Reply-To: <20240119184742.31088-7-krisman@suse.de>
On Fri, Jan 19, 2024 at 03:47:38PM -0300, Gabriel Krisman Bertazi wrote:
> +/**
> + * generic_set_sb_d_ops - helper for choosing the set of
> + * filesystem-wide dentry operations for the enabled features
> + * @sb: superblock to be configured
> + *
> + * Filesystems supporting casefolding and/or fscrypt can call this
> + * helper at mount-time to configure sb->s_d_root to best set of dentry
s_d_op, not s_d_root.
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Gabriel Krisman Bertazi <krisman@suse.de>
Cc: tytso@mit.edu, amir73il@gmail.com,
linux-f2fs-devel@lists.sourceforge.net, viro@zeniv.linux.org.uk,
linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
linux-ext4@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v3 06/10] libfs: Add helper to choose dentry operations at mount
Date: Wed, 24 Jan 2024 19:13:48 -0800 [thread overview]
Message-ID: <20240125031348.GD52073@sol.localdomain> (raw)
In-Reply-To: <20240119184742.31088-7-krisman@suse.de>
On Fri, Jan 19, 2024 at 03:47:38PM -0300, Gabriel Krisman Bertazi wrote:
> +/**
> + * generic_set_sb_d_ops - helper for choosing the set of
> + * filesystem-wide dentry operations for the enabled features
> + * @sb: superblock to be configured
> + *
> + * Filesystems supporting casefolding and/or fscrypt can call this
> + * helper at mount-time to configure sb->s_d_root to best set of dentry
s_d_op, not s_d_root.
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-01-25 3:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 18:47 [PATCH v3 00/10] Set casefold/fscrypt dentry operations through sb->s_d_op Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [PATCH v3 01/10] ovl: Reject mounting case-insensitive filesystems Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-25 2:51 ` Eric Biggers
2024-01-25 2:51 ` [f2fs-dev] " Eric Biggers
2024-01-25 16:55 ` Gabriel Krisman Bertazi
2024-01-25 16:55 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-27 7:08 ` Eric Biggers
2024-01-27 7:08 ` [f2fs-dev] " Eric Biggers
2024-01-19 18:47 ` [PATCH v3 02/10] fscrypt: Share code between functions that prepare lookup Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-25 3:05 ` Eric Biggers
2024-01-25 3:05 ` [f2fs-dev] " Eric Biggers
2024-01-25 20:18 ` Gabriel Krisman Bertazi
2024-01-25 20:18 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [PATCH v3 03/10] fscrypt: Drop d_revalidate for valid dentries during lookup Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [PATCH v3 04/10] fscrypt: Drop d_revalidate once the key is added Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-25 3:12 ` Eric Biggers
2024-01-25 3:12 ` [f2fs-dev] " Eric Biggers
2024-01-25 20:20 ` Gabriel Krisman Bertazi
2024-01-25 20:20 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-27 7:17 ` Eric Biggers
2024-01-27 7:17 ` [f2fs-dev] " Eric Biggers
2024-01-29 19:34 ` Gabriel Krisman Bertazi
2024-01-29 19:34 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [PATCH v3 05/10] libfs: Merge encrypted_ci_dentry_ops and ci_dentry_ops Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [PATCH v3 06/10] libfs: Add helper to choose dentry operations at mount Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-25 3:13 ` Eric Biggers [this message]
2024-01-25 3:13 ` Eric Biggers
2024-01-19 18:47 ` [PATCH v3 07/10] ext4: Configure dentry operations at dentry-creation time Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [PATCH v3 08/10] f2fs: " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [PATCH v3 09/10] ubifs: " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
2024-01-19 18:47 ` [PATCH v3 10/10] libfs: Drop generic_set_encrypted_ci_d_ops Gabriel Krisman Bertazi
2024-01-19 18:47 ` [f2fs-dev] " Gabriel Krisman Bertazi
-- strict thread matches above, loose matches on Subject: below --
2024-01-11 22:58 [PATCH v3 00/10] Set casefold/fscrypt dentry operations through sb->s_d_op Gabriel Krisman Bertazi
2024-01-11 22:58 ` [PATCH v3 06/10] libfs: Add helper to choose dentry operations at mount Gabriel Krisman Bertazi
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=20240125031348.GD52073@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=amir73il@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=krisman@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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.