Re: [PATCH 2/4] btrfs: Communicate back ENOMEM when it occurs

2017-03-29 Thread Anand Jain
On 03/28/2017 11:38 PM, David Sterba wrote: On Mon, Mar 13, 2017 at 03:42:12PM +0800, Anand Jain wrote: The only error that write dev flush (send) will fail is due to the ENOMEM then, as its not a device specific error and rather a system wide issue, we should rather stop further iterations an

Re: [PATCH 2/4] btrfs: Communicate back ENOMEM when it occurs

2017-03-28 Thread David Sterba
On Mon, Mar 13, 2017 at 03:42:12PM +0800, Anand Jain wrote: > The only error that write dev flush (send) will fail is due > to the ENOMEM then, as its not a device specific error and > rather a system wide issue, we should rather stop further > iterations and perpetuate the -ENOMEM error to the cal

Re: [PATCH 2/4] btrfs: Communicate back ENOMEM when it occurs

2017-03-14 Thread Qu Wenruo
At 03/13/2017 03:42 PM, Anand Jain wrote: The only error that write dev flush (send) will fail is due to the ENOMEM then, as its not a device specific error and rather a system wide issue, we should rather stop further iterations and perpetuate the -ENOMEM error to the caller. Signed-off-by: A

[PATCH 2/4] btrfs: Communicate back ENOMEM when it occurs

2017-03-13 Thread Anand Jain
The only error that write dev flush (send) will fail is due to the ENOMEM then, as its not a device specific error and rather a system wide issue, we should rather stop further iterations and perpetuate the -ENOMEM error to the caller. Signed-off-by: Anand Jain --- fs/btrfs/disk-io.c | 2 +- 1 f