From: John Groves <John@groves.net>
To: Christian Brauner <brauner@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.cz>, Matthew Wilcox <willy@infradead.org>,
linux-cxl@vger.kernel.org, linux-fsdevel@vger.kernel.org,
nvdimm@lists.linux.dev, John Groves <jgroves@micron.com>,
john@jagalactic.com, Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
dave.hansen@linux.intel.com, gregory.price@memverge.com,
Randy Dunlap <rdunlap@infradead.org>,
Jerome Glisse <jglisse@google.com>,
Aravind Ramesh <arramesh@micron.com>,
Ajay Joshi <ajayjoshi@micron.com>,
Eishan Mirakhur <emirakhur@micron.com>,
Ravi Shankar <venkataravis@micron.com>,
Srinivasulu Thanneeru <sthanneeru@micron.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
Chandan Babu R <chandanbabu@kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
"Darrick J . Wong" <djwong@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>,
Steve French <stfrench@microsoft.com>,
Nathan Lynch <nathanl@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Thomas Zimmermann <tzimmermann@suse.de>,
Julien Panis <jpanis@baylibre.com>,
Stanislav Fomichev <sdf@google.com>,
Dongsheng Yang <dongsheng.yang@easystack.cn>
Subject: Re: [RFC PATCH v2 08/12] famfs: module operations & fs_context
Date: Thu, 2 May 2024 10:51:39 -0500 [thread overview]
Message-ID: <hrboank5xdhpr6jj4x5pd4trmsnehbo2yrvi57aed736pakz2w@eldaewzyg2jv> (raw)
In-Reply-To: <20240430-badeverbot-paletten-05442cfbbdf0@brauner>
On 24/04/30 01:01PM, Christian Brauner wrote:
> On Mon, Apr 29, 2024 at 12:04:24PM -0500, John Groves wrote:
> > Start building up from the famfs module operations. This commit
> > includes the following:
> >
> > * Register as a file system
> > * Parse mount parameters
> > * Allocate or find (and initialize) a superblock via famfs_get_tree()
> > * Lookup the host dax device, and bail if it's in use (or not dax)
> > * Register as the holder of the dax device if it's available
> > * Add Kconfig and Makefile misc to build famfs
> > * Add FAMFS_SUPER_MAGIC to include/uapi/linux/magic.h
> > * Add export of fs/namei.c:may_open_dev(), which famfs needs to call
> > * Update MAINTAINERS file for the fs/famfs/ path
> >
> > The following exports had to happen to enable famfs:
> >
> > * This uses the new fs/super.c:kill_char_super() - the other kill*super
> > helpers were not quite right.
> > * This uses the dev_dax_iomap export of dax_dev_get()
> >
> > This commit builds but is otherwise too incomplete to run
> >
> > Signed-off-by: John Groves <john@groves.net>
> > ---
> > MAINTAINERS | 1 +
> > fs/Kconfig | 2 +
> > fs/Makefile | 1 +
> > fs/famfs/Kconfig | 10 ++
> > fs/famfs/Makefile | 5 +
> > fs/famfs/famfs_inode.c | 345 +++++++++++++++++++++++++++++++++++++
> > fs/famfs/famfs_internal.h | 36 ++++
> > fs/namei.c | 1 +
> > include/uapi/linux/magic.h | 1 +
> > 9 files changed, 402 insertions(+)
> > create mode 100644 fs/famfs/Kconfig
> > create mode 100644 fs/famfs/Makefile
> > create mode 100644 fs/famfs/famfs_inode.c
> > create mode 100644 fs/famfs/famfs_internal.h
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 3f2d847dcf01..365d678e2f40 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -8188,6 +8188,7 @@ L: linux-cxl@vger.kernel.org
> > L: linux-fsdevel@vger.kernel.org
> > S: Supported
> > F: Documentation/filesystems/famfs.rst
> > +F: fs/famfs
> >
> > FANOTIFY
> > M: Jan Kara <jack@suse.cz>
> > diff --git a/fs/Kconfig b/fs/Kconfig
> > index a46b0cbc4d8f..53b4629e92a0 100644
> > --- a/fs/Kconfig
> > +++ b/fs/Kconfig
> > @@ -140,6 +140,8 @@ source "fs/autofs/Kconfig"
> > source "fs/fuse/Kconfig"
> > source "fs/overlayfs/Kconfig"
> >
> > +source "fs/famfs/Kconfig"
> > +
> > menu "Caches"
> >
> > source "fs/netfs/Kconfig"
> > diff --git a/fs/Makefile b/fs/Makefile
> > index 6ecc9b0a53f2..3393f399a9e9 100644
> > --- a/fs/Makefile
> > +++ b/fs/Makefile
> > @@ -129,3 +129,4 @@ obj-$(CONFIG_EFIVAR_FS) += efivarfs/
> > obj-$(CONFIG_EROFS_FS) += erofs/
> > obj-$(CONFIG_VBOXSF_FS) += vboxsf/
> > obj-$(CONFIG_ZONEFS_FS) += zonefs/
> > +obj-$(CONFIG_FAMFS) += famfs/
> > diff --git a/fs/famfs/Kconfig b/fs/famfs/Kconfig
> > new file mode 100644
> > index 000000000000..edb8980820f7
> > --- /dev/null
> > +++ b/fs/famfs/Kconfig
> > @@ -0,0 +1,10 @@
> > +
> > +
> > +config FAMFS
> > + tristate "famfs: shared memory file system"
> > + depends on DEV_DAX && FS_DAX && DEV_DAX_IOMAP
> > + help
> > + Support for the famfs file system. Famfs is a dax file system that
> > + can support scale-out shared access to fabric-attached memory
> > + (e.g. CXL shared memory). Famfs is not a general purpose file system;
> > + it is an enabler for data sets in shared memory.
> > diff --git a/fs/famfs/Makefile b/fs/famfs/Makefile
> > new file mode 100644
> > index 000000000000..62230bcd6793
> > --- /dev/null
> > +++ b/fs/famfs/Makefile
> > @@ -0,0 +1,5 @@
> > +# SPDX-License-Identifier: GPL-2.0
> > +
> > +obj-$(CONFIG_FAMFS) += famfs.o
> > +
> > +famfs-y := famfs_inode.o
> > diff --git a/fs/famfs/famfs_inode.c b/fs/famfs/famfs_inode.c
> > new file mode 100644
> > index 000000000000..61306240fc0b
> > --- /dev/null
> > +++ b/fs/famfs/famfs_inode.c
> > @@ -0,0 +1,345 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * famfs - dax file system for shared fabric-attached memory
> > + *
> > + * Copyright 2023-2024 Micron Technology, inc
> > + *
> > + * This file system, originally based on ramfs the dax support from xfs,
> > + * is intended to allow multiple host systems to mount a common file system
> > + * view of dax files that map to shared memory.
> > + */
> > +
> > +#include <linux/fs.h>
> > +#include <linux/time.h>
> > +#include <linux/init.h>
> > +#include <linux/string.h>
> > +#include <linux/parser.h>
> > +#include <linux/magic.h>
> > +#include <linux/slab.h>
> > +#include <linux/fs_context.h>
> > +#include <linux/fs_parser.h>
> > +#include <linux/dax.h>
> > +#include <linux/hugetlb.h>
> > +#include <linux/iomap.h>
> > +#include <linux/path.h>
> > +#include <linux/namei.h>
> > +
> > +#include "famfs_internal.h"
> > +
> > +#define FAMFS_DEFAULT_MODE 0755
> > +
> > +static struct inode *famfs_get_inode(struct super_block *sb,
> > + const struct inode *dir,
> > + umode_t mode, dev_t dev)
> > +{
> > + struct inode *inode = new_inode(sb);
> > + struct timespec64 tv;
> > +
> > + if (!inode)
> > + return NULL;
> > +
> > + inode->i_ino = get_next_ino();
> > + inode_init_owner(&nop_mnt_idmap, inode, dir, mode);
> > + inode->i_mapping->a_ops = &ram_aops;
> > + mapping_set_gfp_mask(inode->i_mapping, GFP_HIGHUSER);
> > + mapping_set_unevictable(inode->i_mapping);
> > + tv = inode_set_ctime_current(inode);
> > + inode_set_mtime_to_ts(inode, tv);
> > + inode_set_atime_to_ts(inode, tv);
> > +
> > + switch (mode & S_IFMT) {
> > + default:
> > + init_special_inode(inode, mode, dev);
> > + break;
> > + case S_IFREG:
> > + inode->i_op = NULL /* famfs_file_inode_operations */;
> > + inode->i_fop = NULL /* &famfs_file_operations */;
> > + break;
> > + case S_IFDIR:
> > + inode->i_op = NULL /* famfs_dir_inode_operations */;
> > + inode->i_fop = &simple_dir_operations;
> > +
> > + /* Directory inodes start off with i_nlink == 2 (for ".") */
> > + inc_nlink(inode);
> > + break;
> > + case S_IFLNK:
> > + inode->i_op = &page_symlink_inode_operations;
> > + inode_nohighmem(inode);
> > + break;
> > + }
> > + return inode;
> > +}
> > +
> > +/*
> > + * famfs dax_operations (for char dax)
> > + */
> > +static int
> > +famfs_dax_notify_failure(struct dax_device *dax_dev, u64 offset,
> > + u64 len, int mf_flags)
> > +{
> > + struct super_block *sb = dax_holder(dax_dev);
> > + struct famfs_fs_info *fsi = sb->s_fs_info;
> > +
> > + pr_err("%s: rootdev=%s offset=%lld len=%llu flags=%x\n", __func__,
> > + fsi->rootdev, offset, len, mf_flags);
> > +
> > + return 0;
> > +}
> > +
> > +static const struct dax_holder_operations famfs_dax_holder_ops = {
> > + .notify_failure = famfs_dax_notify_failure,
> > +};
> > +
> > +/*****************************************************************************
> > + * fs_context_operations
> > + */
> > +
> > +static int
> > +famfs_fill_super(struct super_block *sb, struct fs_context *fc)
> > +{
> > + int rc = 0;
> > +
> > + sb->s_maxbytes = MAX_LFS_FILESIZE;
> > + sb->s_blocksize = PAGE_SIZE;
> > + sb->s_blocksize_bits = PAGE_SHIFT;
> > + sb->s_magic = FAMFS_SUPER_MAGIC;
> > + sb->s_op = NULL /* famfs_super_ops */;
> > + sb->s_time_gran = 1;
> > +
> > + return rc;
> > +}
> > +
> > +static int
> > +lookup_daxdev(const char *pathname, dev_t *devno)
> > +{
> > + struct inode *inode;
> > + struct path path;
> > + int err;
> > +
> > + if (!pathname || !*pathname)
> > + return -EINVAL;
> > +
> > + err = kern_path(pathname, LOOKUP_FOLLOW, &path);
> > + if (err)
> > + return err;
> > +
> > + inode = d_backing_inode(path.dentry);
> > + if (!S_ISCHR(inode->i_mode)) {
> > + err = -EINVAL;
> > + goto out_path_put;
> > + }
> > +
> > + if (!may_open_dev(&path)) { /* had to export this */
> > + err = -EACCES;
> > + goto out_path_put;
> > + }
> > +
> > + /* if it's dax, i_rdev is struct dax_device */
> > + *devno = inode->i_rdev;
> > +
> > +out_path_put:
> > + path_put(&path);
> > + return err;
> > +}
> > +
> > +static int
> > +famfs_get_tree(struct fs_context *fc)
> > +{
> > + struct famfs_fs_info *fsi = fc->s_fs_info;
> > + struct dax_device *dax_devp;
> > + struct super_block *sb;
> > + struct inode *inode;
> > + dev_t daxdevno;
> > + int err;
> > +
> > + /* TODO: clean up chatty messages */
> > +
> > + err = lookup_daxdev(fc->source, &daxdevno);
> > + if (err)
> > + return err;
> > +
> > + fsi->daxdevno = daxdevno;
> > +
> > + /* This will set sb->s_dev=daxdevno */
> > + sb = sget_dev(fc, daxdevno);
>
> This will open the dax device as a block device. However, nothing in
> your ->kill_sb method or kill_char_super() closes it again. So you're
> leaking block device references and leaving unitialized memory around as
> you've claimed that device but never ended your claim.
My uptake is admittedly a bit slow with the superblock handling code; I'm
still working to get my head around it. Thank you for your help and
patience on this.
By "This will open the dax device as a block device", are you referring to
the call from sget_fc() to get_filesystem() - which then does a
__module_get(fs->owner)? That's the only thing I see that one might refer
to as "open" - and I do see [I think] that the famfs code is not doing a
module_put. Or maybe I'm missing something else...
Looking at xfs as an example, bdev_file_open_by_path() is called from
xfs_fill_super(), which is called back from get_tree_bdev() after the
superblock is found or allocated.
In famfs, I'm not currently using a get_tree helper because there doesn't
appear to be one that's quite right for a character-backed FS (?). The
call in famfs that I think is most analogous to bdev_file_open_by_path()
is dax_dev_get(), which is called after we've found or allocated a
superblock via sget_dev()->sget_fc().
Using sget_dev() looked ok to me, but it does put a devdax (char device)
dev_t in superblock->s_dev - which may be a bit squirrely because it's
usually a block dev_t. But I don't see s_dev being used except in the
setup_bdev_super() path, which famfs is not using.
So if there is an open that I'm not closing, I'm not seeing it yet (other
than the apparent missing module_put()). Can you elaborate a bit?
>
> > + if (IS_ERR(sb)) {
> > + pr_err("%s: sget_dev error\n", __func__);
> > + return PTR_ERR(sb);
> > + }
> > +
> > + if (sb->s_root) {
> > + pr_info("%s: found a matching suerblock for %s\n",
> > + __func__, fc->source);
> > +
> > + /* We don't expect to find a match by dev_t; if we do, it must
> > + * already be mounted, so we bail
> > + */
> > + err = -EBUSY;
> > + goto deactivate_out;
> > + } else {
> > + pr_info("%s: initializing new superblock for %s\n",
> > + __func__, fc->source);
> > + err = famfs_fill_super(sb, fc);
> > + if (err)
> > + goto deactivate_out;
> > + }
> > +
> > + /* This will fail if it's not a dax device */
> > + dax_devp = dax_dev_get(daxdevno);
> > + if (!dax_devp) {
> > + pr_warn("%s: device %s not found or not dax\n",
> > + __func__, fc->source);
> > + err = -ENODEV;
> > + goto deactivate_out;
> > + }
> > +
> > + err = fs_dax_get(dax_devp, sb, &famfs_dax_holder_ops);
> > + if (err) {
> > + pr_err("%s: fs_dax_get(%lld) failed\n", __func__, (u64)daxdevno);
> > + err = -EBUSY;
> > + goto deactivate_out;
> > + }
> > + fsi->dax_devp = dax_devp;
> > +
> > + inode = famfs_get_inode(sb, NULL, S_IFDIR | fsi->mount_opts.mode, 0);
> > + sb->s_root = d_make_root(inode);
> > + if (!sb->s_root) {
> > + pr_err("%s: d_make_root() failed\n", __func__);
> > + err = -ENOMEM;
> > + fs_put_dax(fsi->dax_devp, sb);
> > + goto deactivate_out;
> > + }
> > +
> > + sb->s_flags |= SB_ACTIVE;
> > +
> > + WARN_ON(fc->root);
> > + fc->root = dget(sb->s_root);
> > + return err;
> > +
> > +deactivate_out:
> > + pr_debug("%s: deactivating sb=%llx\n", __func__, (u64)sb);
> > + deactivate_locked_super(sb);
> > + return err;
> > +}
> > +
> > +/*****************************************************************************/
> > +
> > +enum famfs_param {
> > + Opt_mode,
> > + Opt_dax,
> > +};
> > +
> > +const struct fs_parameter_spec famfs_fs_parameters[] = {
> > + fsparam_u32oct("mode", Opt_mode),
> > + fsparam_string("dax", Opt_dax),
> > + {}
> > +};
> > +
> > +static int famfs_parse_param(struct fs_context *fc, struct fs_parameter *param)
> > +{
> > + struct famfs_fs_info *fsi = fc->s_fs_info;
> > + struct fs_parse_result result;
> > + int opt;
> > +
> > + opt = fs_parse(fc, famfs_fs_parameters, param, &result);
> > + if (opt == -ENOPARAM) {
> > + opt = vfs_parse_fs_param_source(fc, param);
> > + if (opt != -ENOPARAM)
> > + return opt;
>
> This shouldn't be needed. The VFS will handle all that for you.
>
> > +
> > + return 0;
> > + }
> > + if (opt < 0)
> > + return opt;
> > +
> > + switch (opt) {
> > + case Opt_mode:
> > + fsi->mount_opts.mode = result.uint_32 & S_IALLUGO;
> > + break;
> > + case Opt_dax:
> > + if (strcmp(param->string, "always"))
> > + pr_notice("%s: invalid dax mode %s\n",
> > + __func__, param->string);
> > + break;
> > + }
> > +
> > + return 0;
> > +}
> > +
> > +static void famfs_free_fc(struct fs_context *fc)
> > +{
> > + struct famfs_fs_info *fsi = fc->s_fs_info;
> > +
> > + if (fsi && fsi->rootdev)
> > + kfree(fsi->rootdev);
>
> Dead code since rootdev is unused an unset?
Good catch, thank you. rootdev was used in v1 but not in v2.
>
> > +
> > + kfree(fsi);
> > +}
> > +
> > +static const struct fs_context_operations famfs_context_ops = {
> > + .free = famfs_free_fc,
> > + .parse_param = famfs_parse_param,
> > + .get_tree = famfs_get_tree,
> > +};
> > +
> > +static int famfs_init_fs_context(struct fs_context *fc)
> > +{
> > + struct famfs_fs_info *fsi;
> > +
> > + fsi = kzalloc(sizeof(*fsi), GFP_KERNEL);
> > + if (!fsi)
> > + return -ENOMEM;
> > +
> > + fsi->mount_opts.mode = FAMFS_DEFAULT_MODE;
> > + fc->s_fs_info = fsi;
> > + fc->ops = &famfs_context_ops;
> > + return 0;
> > +}
> > +
> > +static void famfs_kill_sb(struct super_block *sb)
> > +{
> > + struct famfs_fs_info *fsi = sb->s_fs_info;
> > +
> > + if (fsi->dax_devp)
> > + fs_put_dax(fsi->dax_devp, sb);
> > + if (fsi && fsi->rootdev)
> > + kfree(fsi->rootdev);
> > + kfree(fsi);
> > + sb->s_fs_info = NULL;
> > +
> > + kill_char_super(sb); /* new */
> > +}
>
> Can likely just be
>
> static void famfs_kill_sb(struct super_block *sb)
> {
> struct famfs_fs_info *fsi = sb->s_fs_info;
>
> generic_shutdown_super(sb);
>
> if (sb->s_bdev_file)
> bdev_fput(sb->s_bdev_file);
>
> if (fsi->dax_devp)
> fs_put_dax(fsi->dax_devp, sb);
>
> kfree(fsi);
> }
>
> and then you don't need any custom helpers at all.
Thanks; will give this a try
>
> > +
> > +#define MODULE_NAME "famfs"
> > +static struct file_system_type famfs_fs_type = {
> > + .name = MODULE_NAME,
> > + .init_fs_context = famfs_init_fs_context,
> > + .parameters = famfs_fs_parameters,
> > + .kill_sb = famfs_kill_sb,
> > + .fs_flags = FS_USERNS_MOUNT,
>
> Sorry, no. This should not be mountable by unprivileged users and
> containers if it's using a real device and especially not since it's not
> even a mature filesystem.
I'm a derp. That should be:
.fs_flags = FS_REQUIRES_DEV;
Right?
<snip>
Thank you for your help!
John
next prev parent reply other threads:[~2024-05-02 15:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 17:04 [RFC PATCH v2 00/12] Introduce the famfs shared-memory file system John Groves
2024-04-29 17:04 ` [RFC PATCH v2 01/12] famfs: Introduce famfs documentation John Groves
2024-04-30 6:46 ` Bagas Sanjaya
2024-04-29 17:04 ` [RFC PATCH v2 02/12] dev_dax_iomap: Move dax_pgoff_to_phys() from device.c to bus.c John Groves
2024-04-29 17:04 ` [RFC PATCH v2 03/12] dev_dax_iomap: Add fs_dax_get() func to prepare dax for fs-dax usage John Groves
2024-04-29 17:04 ` [RFC PATCH v2 04/12] dev_dax_iomap: Save the kva from memremap John Groves
2024-04-29 17:04 ` [RFC PATCH v2 05/12] dev_dax_iomap: Add dax_operations for use by fs-dax on devdax John Groves
2024-04-29 17:04 ` [RFC PATCH v2 06/12] dev_dax_iomap: export dax_dev_get() John Groves
2024-04-29 17:04 ` [RFC PATCH v2 07/12] famfs prep: Add fs/super.c:kill_char_super() John Groves
2024-05-02 18:17 ` Al Viro
2024-05-02 22:25 ` John Groves
2024-05-03 9:04 ` Christian Brauner
2024-05-03 15:38 ` John Groves
2024-04-29 17:04 ` [RFC PATCH v2 08/12] famfs: module operations & fs_context John Groves
2024-04-30 11:01 ` Christian Brauner
2024-05-02 15:51 ` John Groves [this message]
2024-05-03 14:15 ` John Groves
2024-05-02 18:23 ` Al Viro
2024-05-02 21:50 ` John Groves
2024-04-29 17:04 ` [RFC PATCH v2 09/12] famfs: Introduce inode_operations and super_operations John Groves
2024-04-29 17:04 ` [RFC PATCH v2 10/12] famfs: Introduce file_operations read/write John Groves
2024-05-02 18:29 ` Al Viro
2024-05-02 21:51 ` John Groves
2024-04-29 17:04 ` [RFC PATCH v2 11/12] famfs: Introduce mmap and VM fault handling John Groves
2024-04-29 17:04 ` [RFC PATCH v2 12/12] famfs: famfs_ioctl and core file-to-memory mapping logic & iomap_ops John Groves
2024-04-29 18:32 ` [RFC PATCH v2 00/12] Introduce the famfs shared-memory file system Matthew Wilcox
2024-04-29 23:08 ` Kent Overstreet
2024-04-30 2:24 ` John Groves
2024-04-30 3:11 ` Kent Overstreet
2024-05-01 2:09 ` John Groves
2024-04-30 2:11 ` John Groves
2024-04-30 21:01 ` Matthew Wilcox
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=hrboank5xdhpr6jj4x5pd4trmsnehbo2yrvi57aed736pakz2w@eldaewzyg2jv \
--to=john@groves.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=ajayjoshi@micron.com \
--cc=amir73il@gmail.com \
--cc=arramesh@micron.com \
--cc=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=chandanbabu@kernel.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=dongsheng.yang@easystack.cn \
--cc=emirakhur@micron.com \
--cc=gregory.price@memverge.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jglisse@google.com \
--cc=jgroves@micron.com \
--cc=john@jagalactic.com \
--cc=jpanis@baylibre.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nathanl@linux.ibm.com \
--cc=nvdimm@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=sdf@google.com \
--cc=stfrench@microsoft.com \
--cc=sthanneeru@micron.com \
--cc=tzimmermann@suse.de \
--cc=venkataravis@micron.com \
--cc=viro@zeniv.linux.org.uk \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.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 read-only IMAP folder(s) and NNTP newsgroup(s).