* locking updates
@ 2000-01-20 14:09 Manfred Spraul
0 siblings, 0 replies; only message in thread
From: Manfred Spraul @ 2000-01-20 14:09 UTC (permalink / raw)
To: linuxppc-dev, cort
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/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2000-01-20 14:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-01-20 14:09 locking updates Manfred Spraul
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).