Re: [PATCH 3/3] vfio: disable filesystem-dax page pinning

Hi Dan, On 02/04/18 15:05 -0800, Dan Williams wrote: > Filesystem-DAX is incompatible with 'longterm' page pinning. Without > page cache indirection a DAX mapping maps filesystem blocks directly. > This means that the filesystem must not modify a file's block map while > any page in a mapping is

[GIT PULL] libnvdimm for 4.16

Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-4.16 ...to receive the libnvdimm update for 4.16. All of these commits have shipped in -next and have received build verification notices from 0day. There is one small merge conflict

Re: [PATCH 3/3] vfio: disable filesystem-dax page pinning

On Mon, Feb 5, 2018 at 1:44 PM, Alex Williamson wrote: > On Sun, 04 Feb 2018 15:05:30 -0800 > Dan Williams wrote: > >> Filesystem-DAX is incompatible with 'longterm' page pinning. Without >> page cache indirection a DAX mapping maps

Re: [PATCH 3/3] vfio: disable filesystem-dax page pinning

On Sun, 04 Feb 2018 15:05:30 -0800 Dan Williams wrote: > Filesystem-DAX is incompatible with 'longterm' page pinning. Without > page cache indirection a DAX mapping maps filesystem blocks directly. > This means that the filesystem must not modify a file's block map

Re: [PATCH] libnvdimm: remove redundant assignment to pointer 'dev'

On Mon, Feb 05, 2018 at 10:44:07AM -0800, Dan Williams wrote: > On Mon, Feb 5, 2018 at 10:20 AM, Ross Zwisler > wrote: > > On Mon, Feb 05, 2018 at 02:08:52PM +, Colin King wrote: > >> From: Colin Ian King > >> > >> Pointer dev is being

Re: [PATCH] libnvdimm: remove redundant assignment to pointer 'dev'

On 05/02/18 18:44, Dan Williams wrote: > On Mon, Feb 5, 2018 at 10:20 AM, Ross Zwisler > wrote: >> On Mon, Feb 05, 2018 at 02:08:52PM +, Colin King wrote: >>> From: Colin Ian King >>> >>> Pointer dev is being assigned a value that is

Re: [PATCH] libnvdimm: remove redundant assignment to pointer 'dev'

On Mon, Feb 5, 2018 at 10:20 AM, Ross Zwisler wrote: > On Mon, Feb 05, 2018 at 02:08:52PM +, Colin King wrote: >> From: Colin Ian King >> >> Pointer dev is being assigned a value that is never read, it is being >> re-assigned the same

Re: [PATCH] libnvdimm: remove redundant assignment to pointer 'dev'

On Mon, Feb 05, 2018 at 02:08:52PM +, Colin King wrote: > From: Colin Ian King > > Pointer dev is being assigned a value that is never read, it is being > re-assigned the same value later on, hence the initialization is redundant > and can be removed. > > Cleans up

Re: nvml/pmdk libvmmaloc segmentation fault when exit

Hi, Xiong, p...@googlegroups.com is the mailing list for nvml discussion. -Jeff Xiong Zhou writes: > Hi, > > This happens when testing nvml or pmdk libvmmalloc library: > + dmesg > [12890.676033] traps: test_libvmmallo[15789] general protection > ip:7f3f01481a31

[PATCH] libnvdimm: remove redundant assignment to pointer 'dev'

From: Colin Ian King Pointer dev is being assigned a value that is never read, it is being re-assigned the same value later on, hence the initialization is redundant and can be removed. Cleans up clang warning: drivers/nvdimm/pfn_devs.c:307:17: warning: Value stored to

nvml/pmdk libvmmaloc segmentation fault when exit

Hi, This happens when testing nvml or pmdk libvmmalloc library: + dmesg [12890.676033] traps: test_libvmmallo[15789] general protection ip:7f3f01481a31 sp:7ffd85f4b7a0 error:0 in libvmmalloc.so.1.0.0[7f3f0146d000+3e000] gdb output: Program received signal SIGSEGV, Segmentation fault.