From: Manfred Spraul <manfreds@colorfullife.com>
To: linuxppc-dev@lists.linuxppc.org, cort@ppc.kernel.org
Subject: locking updates
Date: Thu, 20 Jan 2000 15:09:05 +0100 [thread overview]
Message-ID: <38871701.291C923B@colorfullife.com> (raw)
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/
reply other threads:[~2000-01-20 14:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38871701.291C923B@colorfullife.com \
--to=manfreds@colorfullife.com \
--cc=cort@ppc.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).