On Tue, Nov 05, 2013 at 08:03:33PM +0100, Max Reitz wrote:
error_setg_errno() may overwrite errno; therefore, its value should be
read before calling that function and not afterwards.
Signed-off-by: Max Reitz mre...@redhat.com
---
block.c | 2 +-
1 file changed, 1 insertion(+), 1
On Tue, Nov 05, 2013 at 12:26:41PM -0700, Eric Blake wrote:
On 11/05/2013 12:03 PM, Max Reitz wrote:
error_setg_errno() may overwrite errno; therefore, its value should be
read before calling that function and not afterwards.
Signed-off-by: Max Reitz mre...@redhat.com
---
block.c |
error_setg_errno() may overwrite errno; therefore, its value should be
read before calling that function and not afterwards.
Signed-off-by: Max Reitz mre...@redhat.com
---
block.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block.c b/block.c
index 58efb5b..0e96a22 100644
On 11/05/2013 12:03 PM, Max Reitz wrote:
error_setg_errno() may overwrite errno; therefore, its value should be
read before calling that function and not afterwards.
Signed-off-by: Max Reitz mre...@redhat.com
---
block.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by:
Le Tuesday 05 Nov 2013 à 20:03:33 (+0100), Max Reitz a écrit :
error_setg_errno() may overwrite errno; therefore, its value should be
read before calling that function and not afterwards.
Signed-off-by: Max Reitz mre...@redhat.com
---
block.c | 2 +-
1 file changed, 1 insertion(+), 1
