lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <1508883801.17367965.1554358418550.JavaMail.zimbra@redhat.com> Date: Thu, 4 Apr 2019 02:13:38 -0400 (EDT) From: Pankaj Gupta <pagupta@...hat.com> To: "Darrick J. Wong" <darrick.wong@...cle.com> Cc: Dave Chinner <david@...morbit.com>, linux-nvdimm@...ts.01.org, linux-kernel@...r.kernel.org, virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-acpi@...r.kernel.org, qemu-devel@...gnu.org, linux-ext4@...r.kernel.org, linux-xfs@...r.kernel.org, dan j williams <dan.j.williams@...el.com>, zwisler@...nel.org, vishal l verma <vishal.l.verma@...el.com>, dave jiang <dave.jiang@...el.com>, mst@...hat.com, jasowang@...hat.com, willy@...radead.org, rjw@...ysocki.net, hch@...radead.org, lenb@...nel.org, jack@...e.cz, tytso@....edu, adilger kernel <adilger.kernel@...ger.ca>, lcapitulino@...hat.com, kwolf@...hat.com, imammedo@...hat.com, jmoyer@...hat.com, nilal@...hat.com, riel@...riel.com, stefanha@...hat.com, aarcange@...hat.com, david@...hat.com, cohuck@...hat.com, xiaoguangrong eric <xiaoguangrong.eric@...il.com> Subject: Re: [PATCH v4 5/5] xfs: disable map_sync for async flush > > On Thu, Apr 04, 2019 at 09:09:12AM +1100, Dave Chinner wrote: > > On Wed, Apr 03, 2019 at 04:10:18PM +0530, Pankaj Gupta wrote: > > > Virtio pmem provides asynchronous host page cache flush > > > mechanism. we don't support 'MAP_SYNC' with virtio pmem > > > and xfs. > > > > > > Signed-off-by: Pankaj Gupta <pagupta@...hat.com> > > > --- > > > fs/xfs/xfs_file.c | 8 ++++++++ > > > 1 file changed, 8 insertions(+) > > > > > > diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c > > > index 1f2e2845eb76..dced2eb8c91a 100644 > > > --- a/fs/xfs/xfs_file.c > > > +++ b/fs/xfs/xfs_file.c > > > @@ -1203,6 +1203,14 @@ xfs_file_mmap( > > > if (!IS_DAX(file_inode(filp)) && (vma->vm_flags & VM_SYNC)) > > > return -EOPNOTSUPP; > > > > > > + /* We don't support synchronous mappings with DAX files if > > > + * dax_device is not synchronous. > > > + */ > > > + if (IS_DAX(file_inode(filp)) && !dax_synchronous( > > > + xfs_find_daxdev_for_inode(file_inode(filp))) && > > > + (vma->vm_flags & VM_SYNC)) > > > + return -EOPNOTSUPP; > > > + > > > file_accessed(filp); > > > vma->vm_ops = &xfs_file_vm_ops; > > > if (IS_DAX(file_inode(filp))) > > > > All this ad hoc IS_DAX conditional logic is getting pretty nasty. > > > > xfs_file_mmap( > > .... > > { > > struct inode *inode = file_inode(filp); > > > > if (vma->vm_flags & VM_SYNC) { > > if (!IS_DAX(inode)) > > return -EOPNOTSUPP; > > if (!dax_synchronous(xfs_find_daxdev_for_inode(inode)) > > return -EOPNOTSUPP; > > } > > > > file_accessed(filp); > > vma->vm_ops = &xfs_file_vm_ops; > > if (IS_DAX(inode)) > > vma->vm_flags |= VM_HUGEPAGE; > > return 0; > > } > > > > > > Even better, factor out all the "MAP_SYNC supported" checks into a > > helper so that the filesystem code just doesn't have to care about > > the details of checking for DAX+MAP_SYNC support.... > > Seconded, since ext4 has nearly the same flag validation logic. Agree. Thanks, Pankaj > > --D > > > > > Cheers, > > > > Dave. > > -- > > Dave Chinner > > david@...morbit.com >
Powered by blists - more mailing lists