error

2016-07-27 Thread Returned mail
Message could not be delivered ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm

[GIT PULL] libnvdimm for 4.8

2016-07-27 Thread Williams, Dan J
Hi Linus, please pull from:   git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm tags/libnvdimm-for-4.8 ...to receive the libnvdimm update for 4.8. This has been in -next with the following reported conflicts: 1/ The __pmem address space has been removed.  New usages of __pmem came in

[BUG] kernel NULL pointer dereference observed during pmem btt switch test

2016-07-27 Thread Yi Zhang
Hello everyone Could you help check this issue, thanks. Steps I used: 1. Reserve 4*8G of memory for pmem by add kernel parameter "memmap=8G!4G memmap=8G!12G memmap=8G!20G memmap=8G!28G" 2. Execute below script #!/bin/bash pmem_btt_switch() { sector_size_list="512 520 528 4096 4104 4160 4

[ndctl PATCH v2] ndctl: print 'size' when creating/listing BTT namespaces

2016-07-27 Thread Vishal Verma
Print the usable size of a BTT namespace after removing driver overhead in the json for listing/creating a BTT namespace. This makes it consistent with other flavors of namespaces (dax, pfn). Cc: Dan Williams Reported-by: Linda Knippers Signed-off-by: Vishal Verma --- v2: - For a create-namesp

[PATCH v2] nvdimm, btt: add a size attribute for BTTs

2016-07-27 Thread Vishal Verma
To be consistent with other namespaces, expose a 'size' attribute for BTT devices also. Cc: Dan Williams Reported-by: Linda Knippers Signed-off-by: Vishal Verma --- v2: - Use the correct locking in size_show (Dan) - Use a typecast for 64b multiplication drivers/nvdimm/btt.c | 1 + driv

Re: Subtle races between DAX mmap fault and write path

2016-07-27 Thread Dave Chinner
On Wed, Jul 27, 2016 at 03:10:39PM -0600, Ross Zwisler wrote: > On Wed, Jul 27, 2016 at 02:07:45PM +0200, Jan Kara wrote: > > Hi, > > > > when testing my latest changes to DXA fault handling code I have hit the > > following interesting race between the fault and write path (I'll show > > function

Re: Subtle races between DAX mmap fault and write path

2016-07-27 Thread Dan Williams
[ Adding Eric ] On Wed, Jul 27, 2016 at 5:07 AM, Jan Kara wrote: > Hi, > > when testing my latest changes to DXA fault handling code I have hit the > following interesting race between the fault and write path (I'll show > function names for ext4 but xfs has the same issue AFAICT). > > We have a

Re: Subtle races between DAX mmap fault and write path

2016-07-27 Thread Ross Zwisler
On Wed, Jul 27, 2016 at 02:07:45PM +0200, Jan Kara wrote: > Hi, > > when testing my latest changes to DXA fault handling code I have hit the > following interesting race between the fault and write path (I'll show > function names for ext4 but xfs has the same issue AFAICT). > > We have a file 'f

Re: HPE SMART data retreival

2016-07-27 Thread Linda Knippers
Hi Johannes, I hope Dan and Jerry also reply but I have recently started looking at this too and have some comments below. On 7/27/2016 6:35 AM, Johannes Thumshirn wrote: > Hi Dan and Jerry, > > I'm currently looking into SMART data retrieval on HPE NVDIMMs. > > After the first obstacle (like g

Subtle races between DAX mmap fault and write path

2016-07-27 Thread Jan Kara
Hi, when testing my latest changes to DXA fault handling code I have hit the following interesting race between the fault and write path (I'll show function names for ext4 but xfs has the same issue AFAICT). We have a file 'f' which has a hole at offset 0. Process 0

HPE SMART data retreival

2016-07-27 Thread Johannes Thumshirn
Hi Dan and Jerry, I'm currently looking into SMART data retrieval on HPE NVDIMMs. After the first obstacle (like getting cat /sys/class/nd/ndctl0/device/nmem0/commands reutrn smart so ndctl will issue the ioctl) I ran into a rather nasty problem. According to [1] HPEDIMMs need the input buffer sp