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

2018-01-07 Thread Theodore Ts'o
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

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

2018-01-03 Thread Jan Kara
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 from ext4_iomap_begin() and implement do standard allocation retry

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

2017-12-21 Thread Ross Zwisler
On Thu, Dec 21, 2017 at 05:30:55PM +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

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

2017-12-21 Thread Jan Kara
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 from ext4_iomap_begin() and implement do standard allocation retry

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

2017-12-13 Thread Jan Kara
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 from ext4_iomap_begin() and implement do standard allocation retry