The original message was received at Thu, 12 Oct 2017 12:25:23 +0800
from lists.01.org [187.53.147.89]
- The following addresses had permanent fatal errors -
- Transcript of session follows -
while talking to lists.01.org.:
>>> MAIL From:"Bounced mail"
<<< 501 "Bounced mail" .
On Wed, Oct 11, 2017 at 7:17 PM, Dan Williams wrote:
> On Wed, Oct 11, 2017 at 6:28 PM, Dan Williams
> wrote:
>> On Wed, Oct 11, 2017 at 6:21 PM, Al Viro wrote:
>>> On Wed, Oct 11, 2017 at 05:47:18PM -0700, Dan Williams wrote:
The MAP_DIRECT mechanism for mmap intends to use a file lease t
On Wed, Oct 11, 2017 at 6:28 PM, Dan Williams wrote:
> On Wed, Oct 11, 2017 at 6:21 PM, Al Viro wrote:
>> On Wed, Oct 11, 2017 at 05:47:18PM -0700, Dan Williams wrote:
>>> The MAP_DIRECT mechanism for mmap intends to use a file lease to prevent
>>> block map changes while the file is mapped. It r
On Wed, Oct 11, 2017 at 6:21 PM, Al Viro wrote:
> On Wed, Oct 11, 2017 at 05:47:18PM -0700, Dan Williams wrote:
>> The MAP_DIRECT mechanism for mmap intends to use a file lease to prevent
>> block map changes while the file is mapped. It requires the fd to setup
>> an fasync_struct for signalling
On Wed, Oct 11, 2017 at 05:47:18PM -0700, Dan Williams wrote:
> The MAP_DIRECT mechanism for mmap intends to use a file lease to prevent
> block map changes while the file is mapped. It requires the fd to setup
> an fasync_struct for signalling lease break events to the lease holder.
*UGH*
That l
In preparation for using FL_LAYOUT leases to allow coordination between
the kernel and processes doing userspace flushes / RDMA with DAX
mappings, add this helper that can be used to start the lease break
process in contexts where we can not sleep waiting for the lease break
timeout.
This is targe
MAP_DIRECT is an mmap(2) flag with the following semantics:
MAP_DIRECT
When specified with MAP_SHARED_VALIDATE, sets up a file lease with the
same lifetime as the mapping. Unlike a typical F_RDLCK lease this lease
is broken when a "lease breaker" attempts to write(2), change the block
ma
The MAP_DIRECT mechanism for mmap intends to use a file lease to prevent
block map changes while the file is mapped. It requires the fd to setup
an fasync_struct for signalling lease break events to the lease holder.
Cc: Jan Kara
Cc: Jeff Moyer
Cc: Christoph Hellwig
Cc: Dave Chinner
Cc: "Darri
The mmap(2) syscall suffers from the ABI anti-pattern of not validating
unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a
mechanism to define new behavior that is known to fail on older kernels
without the support. Define a new MAP_SHARED_VALIDATE flag pattern that
is guaranteed
Move xfs_break_layouts() to its own compilation unit so that it can be
used for both pnfs layouts and MAP_DIRECT mappings.
Cc: Jan Kara
Cc: Jeff Moyer
Cc: Christoph Hellwig
Cc: Dave Chinner
Cc: "Darrick J. Wong"
Cc: Ross Zwisler
Signed-off-by: Dan Williams
---
fs/xfs/Kconfig |4 ++
Changes since v8 [1]:
* Move MAP_SHARED_VALIDATE definition next to MAP_SHARED in all arch
headers (Jan)
* Include xfs_layout.h directly in all the files that call
xfs_break_layouts() (Dave)
* Clarify / add more comments to the MAP_DIRECT checks at fault time
(Dave)
* Rename iomap_can_allo
Introduce a set of helper apis for filesystems to establish FL_LAYOUT
leases to protect against writes and block map updates while a
MAP_DIRECT mapping is established. While the lease protects against the
syscall write path and fallocate it does not protect against allocating
write-faults, so this
On Wed, Oct 11, 2017 at 09:54:15PM +0800, Xiong Zhou wrote:
> On Mon, Sep 25, 2017 at 10:49:03AM +0200, Carlos Maiolino wrote:
> > On Mon, Sep 25, 2017 at 01:40:06AM +, Xiong Zhou wrote:
> > > Hi,
> > >
> > > ffsb test won't exit like this on Linus tree 4.14-rc1+.
> > > Latest commit cd4175b11
On Wed, Oct 11, 2017 at 11:51 AM, Pankaj Gupta wrote:
> We are sharing the prototype version of 'fake DAX' flushing
> interface for the initial feedback. This is still work in progress
> and not yet ready for merging.
>
> Protoype right now just implements basic functionality without advanced
> fe
We are sharing the prototype version of 'fake DAX' flushing
interface for the initial feedback. This is still work in progress
and not yet ready for merging.
Protoype right now just implements basic functionality without advanced
features with two major parts:
- Qemu virtio-pmem device
It expos
On Wed, Oct 11, 2017 at 10:57 AM, Dave Jiang wrote:
> NVDIMM DSM interface v1.6 added additional smart health fields. Updating the
> smart payload data structure accordingly.
I'll also add a note when I merge this that the only reason we are
maintaining this structure in the kernel is in case we
NVDIMM DSM interface v1.6 added additional smart health fields. Updating the
smart payload data structure accordingly.
Signed-off-by: Dave Jiang
---
include/uapi/linux/ndctl.h |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/include/uapi/linux/ndctl.h b/include/uapi/li
On Wed, Oct 11, 2017 at 9:24 AM, Ross Zwisler
wrote:
> Hey Dan,
>
> I was getting the ndctl unit tests working again in my setup today, and on the
> first run of ndctl's "make check" hit a deadlock. This seems to be very easy
> to reproduce, all you have to do is specify a number of jobs to make
Hey Dan,
I was getting the ndctl unit tests working again in my setup today, and on the
first run of ndctl's "make check" hit a deadlock. This seems to be very easy
to reproduce, all you have to do is specify a number of jobs to make that is
larger than 1 (which I was accidentally doing via an al
On Wed, Oct 11, 2017 at 4:54 AM, Joerg Roedel wrote:
> On Tue, Oct 10, 2017 at 07:50:12AM -0700, Dan Williams wrote:
>> +static void ib_umem_lease_break(void *__umem)
>> +{
>> + struct ib_umem *umem = umem;
>> + struct ib_device *idev = umem->context->device;
>> + struct device *dev =
On Tue, Oct 10, 2017 at 01:31:44PM -0700, Linus Torvalds wrote:
> On Tue, Oct 10, 2017 at 12:44 PM, Andrew Morton
> wrote:
> >
> > This is all pretty mature code (isn't it?). Any idea why this bug
> > popped up now?
I have no idea why it's suddenly popped up. It looks like it should
be a bohrbu
On Wed, Oct 11, 2017 at 12:43 AM, Jan Kara wrote:
> On Tue 10-10-17 07:49:01, Dan Williams wrote:
>> The mmap(2) syscall suffers from the ABI anti-pattern of not validating
>> unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a
>> mechanism to define new behavior that is known to
On Wed, Oct 11, 2017 at 6:54 AM, Xiong Zhou wrote:
> On Mon, Sep 25, 2017 at 10:49:03AM +0200, Carlos Maiolino wrote:
>> On Mon, Sep 25, 2017 at 01:40:06AM +, Xiong Zhou wrote:
>> > Hi,
>> >
>> > ffsb test won't exit like this on Linus tree 4.14-rc1+.
>> > Latest commit cd4175b11685
>>
>> Can
On Tue, Oct 10, 2017 at 07:50:12AM -0700, Dan Williams wrote:
> +static void ib_umem_lease_break(void *__umem)
> +{
> + struct ib_umem *umem = umem;
> + struct ib_device *idev = umem->context->device;
> + struct device *dev = idev->dma_device;
> + struct scatterlist *sgl = umem->sg_
Ö£ºlinux-nvdimm@lists.01.org
Ïêϸ ¿Î³Ìʱ¼ä ¼°±¨ÃûÐÅÏ¢ Çë²éÔĸ½¼þ
___
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
On Tue 10-10-17 07:49:01, Dan Williams wrote:
> The mmap(2) syscall suffers from the ABI anti-pattern of not validating
> unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a
> mechanism to define new behavior that is known to fail on older kernels
> without the support. Define a n
26 matches
Mail list logo