locking updates
From: Manfred Spraul <hidden>
Date: 2000-01-20 14:09:05
From: Manfred Spraul <hidden>
Date: 2000-01-20 14:09:05
I noticed a few locking problems/improvements in the ppc code: * arch/ppc/kernel/syscalls.c: - printk() is SMP safe, the lock_kernel() calls around printk() are superflous. - the complete sysv ipc code is smp safe. - sys_uname(): you should acquire the uts_sem semaphore before accessing the members of system_utsname [applies to both 2.2 and 2.3]. * arch/ppc/kernel/signal.c: - do_exit(SIGSEGV) doesn't need lock_kernel(). It's always interesting to compare 2 architectures: I also spotted a bug in the i386 code ;) -- Manfred ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/