Returned mail: Data format error

This Message was undeliverable due to the following reason: Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely

Re: [PATCH v4 17/18] mm, fs, dax: dax_flush_dma, handle dma vs block-map-change collisions

On Thu, Jan 4, 2018 at 3:12 AM, Jan Kara wrote: > On Sat 23-12-17 16:57:31, Dan Williams wrote: >> +static struct page *dma_busy_page(void *entry) >> +{ >> + unsigned long pfn, end_pfn; >> + >> + for_each_entry_pfn(entry, pfn, end_pfn) { >> + struct page *page =

Re: [PATCH 2/2] ext4: Fix ENOSPC handling in DAX page fault handler

On Wed, Jan 03, 2018 at 11:08:44AM +0100, Jan Kara wrote: > When allocation of underlying block for a page fault fails, we fail the > fault with SIGBUS. However we may well hit ENOSPC just due to lots of > free blocks being held by the running / committing transaction. So > propagate the error

Re: [PATCH 1/2] dax: Pass detailed error code from dax_iomap_fault()

On Wed, Jan 03, 2018 at 11:08:43AM +0100, Jan Kara wrote: > Ext4 needs to pass through error from its iomap handler to the page > fault handler so that it can properly detect ENOSPC and force > transaction commit and retry the fault (and block allocation). Add > argument to dax_iomap_fault() for

Re: [PATCH v6 0/2] dax, dm: stop requiring dax for device-mapper

On Thu, Jan 4, 2018 at 10:12 AM, Mike Snitzer wrote: > On Wed, Nov 29 2017 at 1:59pm -0500, > Dan Williams wrote: > >> Changes since v5 [1]: >> * Make DAX_DRIVER select DAX to simplify the Kconfig dependencies >> (Michael) >> * Rebase on 4.15-rc1