[CRIU] [PATCH 2/2] static/file_fown: don't use the explicit value of the macro O_LARGEFILE

Alexander Kartashov alekskartashov at parallels.com
Mon Jan 28 03:22:34 EST 2013


This patch makes the test static/file_fown pass on ARM.
The problem is that the ARM EABI uses the value of O_LARGEFILE
different from one used in x86-64 ABI.

Signed-off-by: Alexander Kartashov <alekskartashov at parallels.com>
---
 test/zdtm/live/static/file_fown.c |    5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/test/zdtm/live/static/file_fown.c b/test/zdtm/live/static/file_fown.c
index 4756fa9..9e1704d 100644
--- a/test/zdtm/live/static/file_fown.c
+++ b/test/zdtm/live/static/file_fown.c
@@ -14,6 +14,7 @@
 #include <sys/socket.h>
 
 #include "zdtmtst.h"
+#include "asm/fcntl.h"
 
 #ifndef F_SETSIG
 #define F_SETSIG	10	/* for sockets. */
@@ -47,8 +48,8 @@ static void fill_pipe_params(struct params *p, int *pipes)
 	 * pipes are created with pipe() and have no O_LARGEFILE
 	 * set.
 	 */
-	p->pipe_flags[0] &= ~00100000;
-	p->pipe_flags[1] &= ~00100000;
+	p->pipe_flags[0] &= ~O_LARGEFILE;
+	p->pipe_flags[1] &= ~O_LARGEFILE;
 
 	test_msg("pipe_flags0 %08o\n", p->pipe_flags[0]);
 	test_msg("pipe_flags1 %08o\n", p->pipe_flags[1]);
-- 
1.7.10.4



More information about the CRIU mailing list