x86: correctly wire up the newuname system call
PATCH 1/1 x86: correctly wire up the newuname system call
Before commit e28cbf22933d0c0ccaf3c4c27a1a263b41f73859 64-bit x86 had a private implementation of sys_uname which was just called sys_uname, which other architectures used for the old uname. Due to some merge issues with the uname refactoring patches we ended up calling the old uname version for both the old and new system call slots, which lead to the domainname filed never be set which caused failures with libnss_nis.
arch/x86/ia32/ia32entry.S +1 -1
@@ -626,7 +626,7 @@ ia32_sys_call_table: .quad stub32_sigreturn .quad stub32_clone /* 120 */ .quad sys_setdomainname - .quad sys_uname + .quad sys_newuname .quad sys_modify_ldt .quad compat_sys_adjtimex .quad sys32_mprotect /* 125 */
Quoted 6 lines · Christoph Hellwig
Before commit
e28cbf22933d0c0ccaf3c4c27a1a263b41f7385964-bit x86 had a private implementation ofsys_unamewhich was just calledsys_uname, which other architectures used for the old uname. Due to some merge issues with the uname refactoring patches we ended up calling the old uname version for both the old and new system call slots, which lead to the domainname filed never be set which caused failures with
^^^^^ field.
Quoted 10 lines
libnss_nis.Reported-by Andy Isaacson <[email protected]>Signed-off-by Christoph Hellwig <[email protected]>Index:
linux-2.6/arch/x86/ia32/ia32entry.S
===================================================================
arch/x86/ia32/ia32entry.S ia32_sys_call_table: · line 629
Quoted 5 lines
arch/x86/ia32/ia32entry.S +1
-1@@ -626,7 +626,7 @@ ia32_sys_call_table: .quad stub32_sigreturn .quad stub32_clone /* 120 */ .quad sys_setdomainname - .quad sys_uname + .quad sys_newuname
Yes, that's the same patch I arrived at and fixes the issue for me.
Thanks,
-andy