Re: [PATCH v4 5/6] util: give a specific error message when O_DIRECT doesn't work

2020-09-02 Thread Daniel P . Berrangé
On Wed, Aug 26, 2020 at 01:19:53PM +0200, Markus Armbruster wrote: > Now back to my dislike of the #ifdeffery I voiced in reply to PATCH 2. > > Code now: > > #ifdef O_CLOEXEC > flags |= O_CLOEXEC; > #endif /* O_CLOEXEC */ > > ret = open(name, flags, mode); > >

Re: [PATCH v4 5/6] util: give a specific error message when O_DIRECT doesn't work

2020-08-26 Thread Markus Armbruster
Daniel P. Berrangé writes: > On Tue, Aug 25, 2020 at 05:19:53PM +0200, Markus Armbruster wrote: >> Daniel P. Berrangé writes: >> >> > A common error scenario is to tell QEMU to use O_DIRECT in combination >> > with a filesystem that doesn't support it. To aid users to diagnosing >> > their

Re: [PATCH v4 5/6] util: give a specific error message when O_DIRECT doesn't work

2020-08-25 Thread Daniel P . Berrangé
On Tue, Aug 25, 2020 at 05:19:53PM +0200, Markus Armbruster wrote: > Daniel P. Berrangé writes: > > > A common error scenario is to tell QEMU to use O_DIRECT in combination > > with a filesystem that doesn't support it. To aid users to diagnosing > > their mistake we want to provide a clear

Re: [PATCH v4 5/6] util: give a specific error message when O_DIRECT doesn't work

2020-08-25 Thread Markus Armbruster
Daniel P. Berrangé writes: > A common error scenario is to tell QEMU to use O_DIRECT in combination > with a filesystem that doesn't support it. To aid users to diagnosing > their mistake we want to provide a clear error message when this happens. > > Reviewed-by: Eric Blake > Signed-off-by:

[PATCH v4 5/6] util: give a specific error message when O_DIRECT doesn't work

2020-08-21 Thread Daniel P . Berrangé
A common error scenario is to tell QEMU to use O_DIRECT in combination with a filesystem that doesn't support it. To aid users to diagnosing their mistake we want to provide a clear error message when this happens. Reviewed-by: Eric Blake Signed-off-by: Daniel P. Berrangé --- util/osdep.c | 13