From 455e900d6c8aa4a6ebca2f94f6c4954cde65dbab Mon Sep 17 00:00:00 2001 From: Derrick Brashear Date: Fri, 4 Nov 2011 11:43:01 -0400 Subject: [PATCH] ukernel: handle pioctl errors properly in ktc the straight return from call_syscall isn't what we want. munge so e.g. EDOM handling for ktc_GetToken does the right thing. Reviewed-on: http://gerrit.openafs.org/5807 Reviewed-by: Derrick Brashear Tested-by: BuildBot (cherry picked from commit b06c700ee40ca70ef08259af819e2a6084137457) Change-Id: I8929615940cb4f025bdd04139399f0ceb82955c9 Reviewed-on: http://gerrit.openafs.org/6084 Tested-by: BuildBot Reviewed-by: Derrick Brashear --- src/auth/ktc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/auth/ktc.c b/src/auth/ktc.c index 7f72e0617..832ddd67a 100644 --- a/src/auth/ktc.c +++ b/src/auth/ktc.c @@ -134,7 +134,7 @@ static void ktc_LocalCell(void); #ifdef AFS_DUX40_ENV #define PIOCTL afs_pioctl #elif defined(UKERNEL) -#define PIOCTL(A,B,C,D) call_syscall(AFSCALL_PIOCTL,A,B,C,D) +#define PIOCTL(A,B,C,D) (errno = (call_syscall(AFSCALL_PIOCTL,A,B,C,D)), errno?-1:0) #else #define PIOCTL pioctl #endif -- 2.39.5