All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvdimm@lists.01.org
Cc: virtio-fs@redhat.com, dgilbert@redhat.com, stefanha@redhat.com,
	miklos@szeredi.hu
Subject: [PATCH 14/19] fuse, dax: Take ->i_mmap_sem lock during dax page fault
Date: Wed, 21 Aug 2019 13:57:15 -0400	[thread overview]
Message-ID: <20190821175720.25901-15-vgoyal@redhat.com> (raw)
In-Reply-To: <20190821175720.25901-1-vgoyal@redhat.com>

We need some kind of locking mechanism here. Normal file systems like
ext4 and xfs seems to take their own semaphore to protect agains
truncate while fault is going on.

We have additional requirement to protect against fuse dax memory range
reclaim. When a range has been selected for reclaim, we need to make sure
no other read/write/fault can try to access that memory range while
reclaim is in progress. Once reclaim is complete, lock will be released
and read/write/fault will trigger allocation of fresh dax range.

Taking inode_lock() is not an option in fault path as lockdep complains
about circular dependencies. So define a new fuse_inode->i_mmap_sem.

Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
---
 fs/fuse/dir.c    |  2 ++
 fs/fuse/file.c   | 17 +++++++++++++----
 fs/fuse/fuse_i.h |  7 +++++++
 fs/fuse/inode.c  |  1 +
 4 files changed, 23 insertions(+), 4 deletions(-)

diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
index fd8636e67ae9..84c0b638affb 100644
--- a/fs/fuse/dir.c
+++ b/fs/fuse/dir.c
@@ -1559,8 +1559,10 @@ int fuse_do_setattr(struct dentry *dentry, struct iattr *attr,
 	 */
 	if ((is_truncate || !is_wb) &&
 	    S_ISREG(inode->i_mode) && oldsize != outarg.attr.size) {
+		down_write(&fi->i_mmap_sem);
 		truncate_pagecache(inode, outarg.attr.size);
 		invalidate_inode_pages2(inode->i_mapping);
+		up_write(&fi->i_mmap_sem);
 	}
 
 	clear_bit(FUSE_I_SIZE_UNSTABLE, &fi->state);
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index b8bcf49f007f..7b70b5ea7f94 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -2792,13 +2792,20 @@ static int __fuse_dax_fault(struct vm_fault *vmf, enum page_entry_size pe_size,
 	if (write)
 		sb_start_pagefault(sb);
 
-	/* TODO inode semaphore to protect faults vs truncate */
-
+	/*
+	 * We need to serialize against not only truncate but also against
+	 * fuse dax memory range reclaim. While a range is being reclaimed,
+	 * we do not want any read/write/mmap to make progress and try
+	 * to populate page cache or access memory we are trying to free.
+	 */
+	down_read(&get_fuse_inode(inode)->i_mmap_sem);
 	ret = dax_iomap_fault(vmf, pe_size, &pfn, NULL, &fuse_iomap_ops);
 
 	if (ret & VM_FAULT_NEEDDSYNC)
 		ret = dax_finish_sync_fault(vmf, pe_size, pfn);
 
+	up_read(&get_fuse_inode(inode)->i_mmap_sem);
+
 	if (write)
 		sb_end_pagefault(sb);
 
@@ -3767,9 +3774,11 @@ static long fuse_file_fallocate(struct file *file, int mode, loff_t offset,
 			file_update_time(file);
 	}
 
-	if (mode & FALLOC_FL_PUNCH_HOLE)
+	if (mode & FALLOC_FL_PUNCH_HOLE) {
+		down_write(&fi->i_mmap_sem);
 		truncate_pagecache_range(inode, offset, offset + length - 1);
-
+		up_write(&fi->i_mmap_sem);
+	}
 	fuse_invalidate_attr(inode);
 
 out:
diff --git a/fs/fuse/fuse_i.h b/fs/fuse/fuse_i.h
index 37b31c5435ff..125bb7123651 100644
--- a/fs/fuse/fuse_i.h
+++ b/fs/fuse/fuse_i.h
@@ -220,6 +220,13 @@ struct fuse_inode {
 	 */
 	struct rw_semaphore i_dmap_sem;
 
+	/**
+	 * Can't take inode lock in fault path (leads to circular dependency).
+	 * So take this in fuse dax fault path to make sure truncate and
+	 * punch hole etc. can't make progress in parallel.
+	 */
+	struct rw_semaphore i_mmap_sem;
+
 	/** Sorted rb tree of struct fuse_dax_mapping elements */
 	struct rb_root_cached dmap_tree;
 	unsigned long nr_dmaps;
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 7e0ed5f3f7e6..52135b4616d2 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -83,6 +83,7 @@ static struct inode *fuse_alloc_inode(struct super_block *sb)
 	fi->state = 0;
 	fi->nr_dmaps = 0;
 	mutex_init(&fi->mutex);
+	init_rwsem(&fi->i_mmap_sem);
 	init_rwsem(&fi->i_dmap_sem);
 	spin_lock_init(&fi->lock);
 	fi->forget = fuse_alloc_forget();
-- 
2.20.1

_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvdimm@lists.01.org
Cc: virtio-fs@redhat.com, vgoyal@redhat.com, miklos@szeredi.hu,
	stefanha@redhat.com, dgilbert@redhat.com
Subject: [PATCH 14/19] fuse, dax: Take ->i_mmap_sem lock during dax page fault
Date: Wed, 21 Aug 2019 13:57:15 -0400	[thread overview]
Message-ID: <20190821175720.25901-15-vgoyal@redhat.com> (raw)
In-Reply-To: <20190821175720.25901-1-vgoyal@redhat.com>

We need some kind of locking mechanism here. Normal file systems like
ext4 and xfs seems to take their own semaphore to protect agains
truncate while fault is going on.

We have additional requirement to protect against fuse dax memory range
reclaim. When a range has been selected for reclaim, we need to make sure
no other read/write/fault can try to access that memory range while
reclaim is in progress. Once reclaim is complete, lock will be released
and read/write/fault will trigger allocation of fresh dax range.

Taking inode_lock() is not an option in fault path as lockdep complains
about circular dependencies. So define a new fuse_inode->i_mmap_sem.

Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
---
 fs/fuse/dir.c    |  2 ++
 fs/fuse/file.c   | 17 +++++++++++++----
 fs/fuse/fuse_i.h |  7 +++++++
 fs/fuse/inode.c  |  1 +
 4 files changed, 23 insertions(+), 4 deletions(-)

diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
index fd8636e67ae9..84c0b638affb 100644
--- a/fs/fuse/dir.c
+++ b/fs/fuse/dir.c
@@ -1559,8 +1559,10 @@ int fuse_do_setattr(struct dentry *dentry, struct iattr *attr,
 	 */
 	if ((is_truncate || !is_wb) &&
 	    S_ISREG(inode->i_mode) && oldsize != outarg.attr.size) {
+		down_write(&fi->i_mmap_sem);
 		truncate_pagecache(inode, outarg.attr.size);
 		invalidate_inode_pages2(inode->i_mapping);
+		up_write(&fi->i_mmap_sem);
 	}
 
 	clear_bit(FUSE_I_SIZE_UNSTABLE, &fi->state);
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index b8bcf49f007f..7b70b5ea7f94 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -2792,13 +2792,20 @@ static int __fuse_dax_fault(struct vm_fault *vmf, enum page_entry_size pe_size,
 	if (write)
 		sb_start_pagefault(sb);
 
-	/* TODO inode semaphore to protect faults vs truncate */
-
+	/*
+	 * We need to serialize against not only truncate but also against
+	 * fuse dax memory range reclaim. While a range is being reclaimed,
+	 * we do not want any read/write/mmap to make progress and try
+	 * to populate page cache or access memory we are trying to free.
+	 */
+	down_read(&get_fuse_inode(inode)->i_mmap_sem);
 	ret = dax_iomap_fault(vmf, pe_size, &pfn, NULL, &fuse_iomap_ops);
 
 	if (ret & VM_FAULT_NEEDDSYNC)
 		ret = dax_finish_sync_fault(vmf, pe_size, pfn);
 
+	up_read(&get_fuse_inode(inode)->i_mmap_sem);
+
 	if (write)
 		sb_end_pagefault(sb);
 
@@ -3767,9 +3774,11 @@ static long fuse_file_fallocate(struct file *file, int mode, loff_t offset,
 			file_update_time(file);
 	}
 
-	if (mode & FALLOC_FL_PUNCH_HOLE)
+	if (mode & FALLOC_FL_PUNCH_HOLE) {
+		down_write(&fi->i_mmap_sem);
 		truncate_pagecache_range(inode, offset, offset + length - 1);
-
+		up_write(&fi->i_mmap_sem);
+	}
 	fuse_invalidate_attr(inode);
 
 out:
diff --git a/fs/fuse/fuse_i.h b/fs/fuse/fuse_i.h
index 37b31c5435ff..125bb7123651 100644
--- a/fs/fuse/fuse_i.h
+++ b/fs/fuse/fuse_i.h
@@ -220,6 +220,13 @@ struct fuse_inode {
 	 */
 	struct rw_semaphore i_dmap_sem;
 
+	/**
+	 * Can't take inode lock in fault path (leads to circular dependency).
+	 * So take this in fuse dax fault path to make sure truncate and
+	 * punch hole etc. can't make progress in parallel.
+	 */
+	struct rw_semaphore i_mmap_sem;
+
 	/** Sorted rb tree of struct fuse_dax_mapping elements */
 	struct rb_root_cached dmap_tree;
 	unsigned long nr_dmaps;
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 7e0ed5f3f7e6..52135b4616d2 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -83,6 +83,7 @@ static struct inode *fuse_alloc_inode(struct super_block *sb)
 	fi->state = 0;
 	fi->nr_dmaps = 0;
 	mutex_init(&fi->mutex);
+	init_rwsem(&fi->i_mmap_sem);
 	init_rwsem(&fi->i_dmap_sem);
 	spin_lock_init(&fi->lock);
 	fi->forget = fuse_alloc_forget();
-- 
2.20.1


WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-nvdimm@lists.01.org
Cc: virtio-fs@redhat.com, vgoyal@redhat.com, miklos@szeredi.hu
Subject: [Virtio-fs] [PATCH 14/19] fuse, dax: Take ->i_mmap_sem lock during dax page fault
Date: Wed, 21 Aug 2019 13:57:15 -0400	[thread overview]
Message-ID: <20190821175720.25901-15-vgoyal@redhat.com> (raw)
In-Reply-To: <20190821175720.25901-1-vgoyal@redhat.com>

We need some kind of locking mechanism here. Normal file systems like
ext4 and xfs seems to take their own semaphore to protect agains
truncate while fault is going on.

We have additional requirement to protect against fuse dax memory range
reclaim. When a range has been selected for reclaim, we need to make sure
no other read/write/fault can try to access that memory range while
reclaim is in progress. Once reclaim is complete, lock will be released
and read/write/fault will trigger allocation of fresh dax range.

Taking inode_lock() is not an option in fault path as lockdep complains
about circular dependencies. So define a new fuse_inode->i_mmap_sem.

Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
---
 fs/fuse/dir.c    |  2 ++
 fs/fuse/file.c   | 17 +++++++++++++----
 fs/fuse/fuse_i.h |  7 +++++++
 fs/fuse/inode.c  |  1 +
 4 files changed, 23 insertions(+), 4 deletions(-)

diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
index fd8636e67ae9..84c0b638affb 100644
--- a/fs/fuse/dir.c
+++ b/fs/fuse/dir.c
@@ -1559,8 +1559,10 @@ int fuse_do_setattr(struct dentry *dentry, struct iattr *attr,
 	 */
 	if ((is_truncate || !is_wb) &&
 	    S_ISREG(inode->i_mode) && oldsize != outarg.attr.size) {
+		down_write(&fi->i_mmap_sem);
 		truncate_pagecache(inode, outarg.attr.size);
 		invalidate_inode_pages2(inode->i_mapping);
+		up_write(&fi->i_mmap_sem);
 	}
 
 	clear_bit(FUSE_I_SIZE_UNSTABLE, &fi->state);
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index b8bcf49f007f..7b70b5ea7f94 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -2792,13 +2792,20 @@ static int __fuse_dax_fault(struct vm_fault *vmf, enum page_entry_size pe_size,
 	if (write)
 		sb_start_pagefault(sb);
 
-	/* TODO inode semaphore to protect faults vs truncate */
-
+	/*
+	 * We need to serialize against not only truncate but also against
+	 * fuse dax memory range reclaim. While a range is being reclaimed,
+	 * we do not want any read/write/mmap to make progress and try
+	 * to populate page cache or access memory we are trying to free.
+	 */
+	down_read(&get_fuse_inode(inode)->i_mmap_sem);
 	ret = dax_iomap_fault(vmf, pe_size, &pfn, NULL, &fuse_iomap_ops);
 
 	if (ret & VM_FAULT_NEEDDSYNC)
 		ret = dax_finish_sync_fault(vmf, pe_size, pfn);
 
+	up_read(&get_fuse_inode(inode)->i_mmap_sem);
+
 	if (write)
 		sb_end_pagefault(sb);
 
@@ -3767,9 +3774,11 @@ static long fuse_file_fallocate(struct file *file, int mode, loff_t offset,
 			file_update_time(file);
 	}
 
-	if (mode & FALLOC_FL_PUNCH_HOLE)
+	if (mode & FALLOC_FL_PUNCH_HOLE) {
+		down_write(&fi->i_mmap_sem);
 		truncate_pagecache_range(inode, offset, offset + length - 1);
-
+		up_write(&fi->i_mmap_sem);
+	}
 	fuse_invalidate_attr(inode);
 
 out:
diff --git a/fs/fuse/fuse_i.h b/fs/fuse/fuse_i.h
index 37b31c5435ff..125bb7123651 100644
--- a/fs/fuse/fuse_i.h
+++ b/fs/fuse/fuse_i.h
@@ -220,6 +220,13 @@ struct fuse_inode {
 	 */
 	struct rw_semaphore i_dmap_sem;
 
+	/**
+	 * Can't take inode lock in fault path (leads to circular dependency).
+	 * So take this in fuse dax fault path to make sure truncate and
+	 * punch hole etc. can't make progress in parallel.
+	 */
+	struct rw_semaphore i_mmap_sem;
+
 	/** Sorted rb tree of struct fuse_dax_mapping elements */
 	struct rb_root_cached dmap_tree;
 	unsigned long nr_dmaps;
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index 7e0ed5f3f7e6..52135b4616d2 100644
--- a/fs/fuse/inode.c
+++ b/fs/fuse/inode.c
@@ -83,6 +83,7 @@ static struct inode *fuse_alloc_inode(struct super_block *sb)
 	fi->state = 0;
 	fi->nr_dmaps = 0;
 	mutex_init(&fi->mutex);
+	init_rwsem(&fi->i_mmap_sem);
 	init_rwsem(&fi->i_dmap_sem);
 	spin_lock_init(&fi->lock);
 	fi->forget = fuse_alloc_forget();
-- 
2.20.1


  parent reply	other threads:[~2019-08-21 17:58 UTC|newest]

Thread overview: 231+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 17:57 [PATCH v3 00/19][RFC] virtio-fs: Enable DAX support Vivek Goyal
2019-08-21 17:57 ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57 ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 01/19] dax: remove block device dependencies Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-26 11:51   ` Christoph Hellwig
2019-08-26 11:51     ` [Virtio-fs] " Christoph Hellwig
2019-08-26 11:51     ` Christoph Hellwig
2019-08-27 16:38     ` Vivek Goyal
2019-08-27 16:38       ` [Virtio-fs] " Vivek Goyal
2019-08-27 16:38       ` Vivek Goyal
2019-08-28  6:58       ` Christoph Hellwig
2019-08-28  6:58         ` [Virtio-fs] " Christoph Hellwig
2019-08-28  6:58         ` Christoph Hellwig
2019-08-28 17:58         ` Vivek Goyal
2019-08-28 17:58           ` [Virtio-fs] " Vivek Goyal
2019-08-28 17:58           ` Vivek Goyal
2019-08-28 22:53           ` Dave Chinner
2019-08-28 22:53             ` [Virtio-fs] " Dave Chinner
2019-08-28 22:53             ` Dave Chinner
2019-08-29  0:04             ` Dan Williams
2019-08-29  0:04               ` [Virtio-fs] " Dan Williams
2019-08-29  0:04               ` Dan Williams
2019-08-29  9:32               ` Christoph Hellwig
2019-08-29  9:32                 ` [Virtio-fs] " Christoph Hellwig
2019-08-29  9:32                 ` Christoph Hellwig
2019-12-16 18:10               ` Vivek Goyal
2019-12-16 18:10                 ` [Virtio-fs] " Vivek Goyal
2019-12-16 18:10                 ` Vivek Goyal
2020-01-07 12:51                 ` Christoph Hellwig
2020-01-07 12:51                   ` [Virtio-fs] " Christoph Hellwig
2020-01-07 12:51                   ` Christoph Hellwig
2020-01-07 14:22                   ` Dan Williams
2020-01-07 14:22                     ` [Virtio-fs] " Dan Williams
2020-01-07 14:22                     ` Dan Williams
2020-01-07 17:07                     ` Darrick J. Wong
2020-01-07 17:07                       ` [Virtio-fs] " Darrick J. Wong
2020-01-07 17:07                       ` Darrick J. Wong
2020-01-07 17:29                       ` Dan Williams
2020-01-07 17:29                         ` [Virtio-fs] " Dan Williams
2020-01-07 17:29                         ` Dan Williams
2020-01-07 18:01                         ` Vivek Goyal
2020-01-07 18:01                           ` [Virtio-fs] " Vivek Goyal
2020-01-07 18:01                           ` Vivek Goyal
2020-01-07 18:07                           ` Dan Williams
2020-01-07 18:07                             ` [Virtio-fs] " Dan Williams
2020-01-07 18:07                             ` Dan Williams
2020-01-07 18:33                             ` Vivek Goyal
2020-01-07 18:33                               ` [Virtio-fs] " Vivek Goyal
2020-01-07 18:33                               ` Vivek Goyal
2020-01-07 18:49                               ` Dan Williams
2020-01-07 18:49                                 ` [Virtio-fs] " Dan Williams
2020-01-07 18:49                                 ` Dan Williams
2020-01-07 19:02                                 ` Darrick J. Wong
2020-01-07 19:02                                   ` [Virtio-fs] " Darrick J. Wong
2020-01-07 19:02                                   ` Darrick J. Wong
2020-01-07 19:46                                   ` Dan Williams
2020-01-07 19:46                                     ` [Virtio-fs] " Dan Williams
2020-01-07 19:46                                     ` Dan Williams
2020-01-07 23:38                                     ` Dan Williams
2020-01-07 23:38                                       ` [Virtio-fs] " Dan Williams
2020-01-07 23:38                                       ` Dan Williams
2020-01-09 11:24                                 ` Jan Kara
2020-01-09 11:24                                   ` [Virtio-fs] " Jan Kara
2020-01-09 11:24                                   ` Jan Kara
2020-01-09 20:03                                   ` Dan Williams
2020-01-09 20:03                                     ` [Virtio-fs] " Dan Williams
2020-01-09 20:03                                     ` Dan Williams
2020-01-10 12:36                                     ` Christoph Hellwig
2020-01-10 12:36                                       ` [Virtio-fs] " Christoph Hellwig
2020-01-10 12:36                                       ` Christoph Hellwig
2020-01-14 20:31                                     ` Vivek Goyal
2020-01-14 20:31                                       ` [Virtio-fs] " Vivek Goyal
2020-01-14 20:31                                       ` Vivek Goyal
2020-01-14 20:39                                       ` Dan Williams
2020-01-14 20:39                                         ` [Virtio-fs] " Dan Williams
2020-01-14 20:39                                         ` Dan Williams
2020-01-14 21:28                                         ` Vivek Goyal
2020-01-14 21:28                                           ` [Virtio-fs] " Vivek Goyal
2020-01-14 21:28                                           ` Vivek Goyal
2020-01-14 22:23                                           ` Dan Williams
2020-01-14 22:23                                             ` [Virtio-fs] " Dan Williams
2020-01-14 22:23                                             ` Dan Williams
2020-01-15 19:56                                             ` Vivek Goyal
2020-01-15 19:56                                               ` [Virtio-fs] " Vivek Goyal
2020-01-15 19:56                                               ` Vivek Goyal
2020-01-15 20:17                                               ` Dan Williams
2020-01-15 20:17                                                 ` [Virtio-fs] " Dan Williams
2020-01-15 20:17                                                 ` Dan Williams
2020-01-15 21:08                                                 ` Jeff Moyer
2020-01-15 21:08                                                   ` [Virtio-fs] " Jeff Moyer
2020-01-15 21:08                                                   ` Jeff Moyer
2020-01-16 18:09                                                   ` Dan Williams
2020-01-16 18:09                                                     ` [Virtio-fs] " Dan Williams
2020-01-16 18:09                                                     ` Dan Williams
2020-01-16 18:39                                                     ` Vivek Goyal
2020-01-16 18:39                                                       ` [Virtio-fs] " Vivek Goyal
2020-01-16 18:39                                                       ` Vivek Goyal
2020-01-16 19:09                                                       ` Dan Williams
2020-01-16 19:09                                                         ` [Virtio-fs] " Dan Williams
2020-01-16 19:09                                                         ` Dan Williams
2020-01-16 19:23                                                         ` Vivek Goyal
2020-01-16 19:23                                                           ` [Virtio-fs] " Vivek Goyal
2020-01-16 19:23                                                           ` Vivek Goyal
2020-02-11 17:33                                                     ` Vivek Goyal
2020-02-11 17:33                                                       ` [Virtio-fs] " Vivek Goyal
2020-02-11 17:33                                                       ` Vivek Goyal
2020-01-15  9:03                                           ` Jan Kara
2020-01-15  9:03                                             ` [Virtio-fs] " Jan Kara
2020-01-15  9:03                                             ` Jan Kara
2019-08-21 17:57 ` [PATCH 02/19] dax: Pass dax_dev to dax_writeback_mapping_range() Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-26 11:53   ` Christoph Hellwig
2019-08-26 11:53     ` [Virtio-fs] " Christoph Hellwig
2019-08-26 11:53     ` Christoph Hellwig
2019-08-26 20:33     ` Vivek Goyal
2019-08-26 20:33       ` [Virtio-fs] " Vivek Goyal
2019-08-26 20:33       ` Vivek Goyal
2019-08-26 20:58       ` Vivek Goyal
2019-08-26 20:58         ` [Virtio-fs] " Vivek Goyal
2019-08-26 20:58         ` Vivek Goyal
2019-08-26 21:33         ` Dan Williams
2019-08-26 21:33           ` [Virtio-fs] " Dan Williams
2019-08-26 21:33           ` Dan Williams
2019-08-28  6:58         ` Christoph Hellwig
2019-08-28  6:58           ` [Virtio-fs] " Christoph Hellwig
2019-08-28  6:58           ` Christoph Hellwig
2020-01-03 14:12         ` Vivek Goyal
2020-01-03 14:12           ` [Virtio-fs] " Vivek Goyal
2020-01-03 14:12           ` Vivek Goyal
2020-01-03 18:12           ` Dan Williams
2020-01-03 18:12             ` [Virtio-fs] " Dan Williams
2020-01-03 18:12             ` Dan Williams
2020-01-03 18:18             ` Dan Williams
2020-01-03 18:18               ` [Virtio-fs] " Dan Williams
2020-01-03 18:18               ` Dan Williams
2020-01-03 18:33               ` Vivek Goyal
2020-01-03 18:33                 ` [Virtio-fs] " Vivek Goyal
2020-01-03 18:33                 ` Vivek Goyal
2020-01-03 19:30                 ` Dan Williams
2020-01-03 19:30                   ` [Virtio-fs] " Dan Williams
2020-01-03 19:30                   ` Dan Williams
2020-01-03 18:43               ` Vivek Goyal
2020-01-03 18:43                 ` [Virtio-fs] " Vivek Goyal
2020-01-03 18:43                 ` Vivek Goyal
2019-08-27 13:45       ` Jan Kara
2019-08-27 13:45         ` [Virtio-fs] " Jan Kara
2019-08-27 13:45         ` Jan Kara
2019-08-21 17:57 ` [PATCH 03/19] virtio: Add get_shm_region method Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 04/19] virtio: Implement get_shm_region for PCI transport Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-26  1:43   ` [Virtio-fs] " piaojun
2019-08-26  1:43     ` piaojun
2019-08-26  1:43     ` piaojun
2019-08-26 13:06     ` Vivek Goyal
2019-08-26 13:06       ` Vivek Goyal
2019-08-26 13:06       ` Vivek Goyal
2019-08-27  9:41       ` piaojun
2019-08-27  9:41         ` piaojun
2019-08-27  9:41         ` piaojun
2019-08-27  8:34   ` Cornelia Huck
2019-08-27  8:34     ` [Virtio-fs] " Cornelia Huck
2019-08-27  8:34     ` Cornelia Huck
2019-08-27  8:46     ` Cornelia Huck
2019-08-27  8:46       ` [Virtio-fs] " Cornelia Huck
2019-08-27  8:46       ` Cornelia Huck
2019-08-27 11:53     ` Vivek Goyal
2019-08-27 11:53       ` [Virtio-fs] " Vivek Goyal
2019-08-27 11:53       ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 05/19] virtio: Implement get_shm_region for MMIO transport Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-27  8:39   ` Cornelia Huck
2019-08-27  8:39     ` [Virtio-fs] " Cornelia Huck
2019-08-27  8:39     ` Cornelia Huck
2019-08-27 11:54     ` Vivek Goyal
2019-08-27 11:54       ` [Virtio-fs] " Vivek Goyal
2019-08-27 11:54       ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 06/19] fuse, dax: add fuse_conn->dax_dev field Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 07/19] virtio_fs, dax: Set up virtio_fs dax_device Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 08/19] fuse: Keep a list of free dax memory ranges Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 09/19] fuse: implement FUSE_INIT map_alignment field Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 10/19] fuse: Introduce setupmapping/removemapping commands Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 11/19] fuse, dax: Implement dax read/write operations Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 19:49   ` Liu Bo
2019-08-21 19:49     ` [Virtio-fs] " Liu Bo
2019-08-21 19:49     ` Liu Bo
2019-08-22 12:59     ` Vivek Goyal
2019-08-22 12:59       ` [Virtio-fs] " Vivek Goyal
2019-08-22 12:59       ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 12/19] fuse, dax: add DAX mmap support Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 13/19] fuse: Define dax address space operations Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` Vivek Goyal [this message]
2019-08-21 17:57   ` [Virtio-fs] [PATCH 14/19] fuse, dax: Take ->i_mmap_sem lock during dax page fault Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 15/19] fuse: Maintain a list of busy elements Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 16/19] dax: Create a range version of dax_layout_busy_page() Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 17/19] fuse: Add logic to free up a memory range Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 18/19] fuse: Release file in process context Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal
2019-08-21 17:57 ` [PATCH 19/19] fuse: Take inode lock for dax inode truncation Vivek Goyal
2019-08-21 17:57   ` [Virtio-fs] " Vivek Goyal
2019-08-21 17:57   ` Vivek Goyal

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=20190821175720.25901-15-vgoyal@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=miklos@szeredi.hu \
    --cc=stefanha@redhat.com \
    --cc=virtio-fs@redhat.com \
    /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.