From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ebiederm@xmission.com, ying.huang@intel.com, pavel@ucw.cz,
nigel@nigel.suspend2.net, rjw@sisk.pl, vgoyal@redhat.com,
mingo@elte.hu, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org
Subject: Re: [PATCH] kexec jump: fix compiling warning on xchg(&kexec_lock, 0) in kernel_kexec()
Date: Wed, 13 Aug 2008 13:25:35 -0700 [thread overview]
Message-ID: <20080813132535.6cd4bab6.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0808131310450.3462@nehalem.linux-foundation.org>
On Wed, 13 Aug 2008 13:13:13 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > Used a bitop to preserve the runtime checking in there. spin_unlock()
> > doesn't return the previous lockedness.
>
> Umm. spin_unlock does a lot more when you have lock debugging on, and
> doesn't do useless crap when it isn't.
>
> > A bitop seems a better fit to me. We never spin on that lock (it
> > always uses test_and_set), so why use a "spin"lock?
>
> ..because an atomic bitop is not the same as a lock.
>
> The memory ordering guarantees are different. Yes, they are sufficient,
> but that's because we've had to make them so to account for CRAP CODE that
> uses bit operations as if they were locks.
>
> Don't continue that. It's WRONG.
#2:
(The xchg(kexec_crash_image) stuff is still in there)
--- a/kernel/kexec.c~kexec-use-a-bitop-for-locking-rather-than-xchg
+++ a/kernel/kexec.c
@@ -924,19 +924,14 @@ static int kimage_load_segment(struct ki
*/
struct kimage *kexec_image;
struct kimage *kexec_crash_image;
-/*
- * A home grown binary mutex.
- * Nothing can wait so this mutex is safe to use
- * in interrupt context :)
- */
-static int kexec_lock;
+
+static DEFINE_SPINLOCK(kexec_lock);
asmlinkage long sys_kexec_load(unsigned long entry, unsigned long nr_segments,
struct kexec_segment __user *segments,
unsigned long flags)
{
struct kimage **dest_image, *image;
- int locked;
int result;
/* We only trust the superuser with rebooting the system. */
@@ -972,8 +967,7 @@ asmlinkage long sys_kexec_load(unsigned
*
* KISS: always take the mutex.
*/
- locked = xchg(&kexec_lock, 1);
- if (locked)
+ if (!spin_trylock(&kexec_lock))
return -EBUSY;
dest_image = &kexec_image;
@@ -1015,8 +1009,7 @@ asmlinkage long sys_kexec_load(unsigned
image = xchg(dest_image, image);
out:
- locked = xchg(&kexec_lock, 0); /* Release the mutex */
- BUG_ON(!locked);
+ spin_unlock(&kexec_lock);
kimage_free(image);
return result;
@@ -1063,9 +1056,6 @@ asmlinkage long compat_sys_kexec_load(un
void crash_kexec(struct pt_regs *regs)
{
- int locked;
-
-
/* Take the kexec_lock here to prevent sys_kexec_load
* running on one cpu from replacing the crash kernel
* we are using after a panic on a different cpu.
@@ -1074,8 +1064,7 @@ void crash_kexec(struct pt_regs *regs)
* of memory the xchg(&kexec_crash_image) would be
* sufficient. But since I reuse the memory...
*/
- locked = xchg(&kexec_lock, 1);
- if (!locked) {
+ if (spin_trylock(&kexec_lock)) {
if (kexec_crash_image) {
struct pt_regs fixed_regs;
crash_setup_regs(&fixed_regs, regs);
@@ -1083,8 +1072,7 @@ void crash_kexec(struct pt_regs *regs)
machine_crash_shutdown(&fixed_regs);
machine_kexec(kexec_crash_image);
}
- locked = xchg(&kexec_lock, 0);
- BUG_ON(!locked);
+ spin_unlock(&kexec_lock);
}
}
@@ -1434,7 +1422,7 @@ int kernel_kexec(void)
{
int error = 0;
- if (xchg(&kexec_lock, 1))
+ if (!spin_trylock(&kexec_lock))
return -EBUSY;
if (!kexec_image) {
error = -EINVAL;
@@ -1498,8 +1486,6 @@ int kernel_kexec(void)
#endif
Unlock:
- if (!xchg(&kexec_lock, 0))
- BUG();
-
+ spin_unlock(&kexec_lock);
return error;
}
_
next prev parent reply other threads:[~2008-08-13 20:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 9:12 [PATCH] kexec jump: fix compiling warning on xchg(&kexec_lock, 0) in kernel_kexec() Huang Ying
2008-08-13 9:27 ` Andrew Morton
2008-08-13 17:01 ` Linus Torvalds
2008-08-13 17:25 ` Andrew Morton
2008-08-13 17:59 ` Ingo Molnar
2008-08-13 16:57 ` Linus Torvalds
2008-08-13 18:12 ` Eric W. Biederman
2008-08-13 18:31 ` Vivek Goyal
2008-08-13 19:44 ` Andrew Morton
2008-08-13 19:50 ` Linus Torvalds
2008-08-13 20:07 ` Andrew Morton
2008-08-13 20:13 ` Linus Torvalds
2008-08-13 20:25 ` Andrew Morton [this message]
2008-08-13 20:31 ` Linus Torvalds
2008-08-13 20:41 ` Andrew Morton
2008-08-13 21:21 ` Vivek Goyal
2008-08-13 22:17 ` Linus Torvalds
2008-08-13 20:15 ` Trond Myklebust
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=20080813132535.6cd4bab6.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.com \
--cc=ying.huang@intel.com \
/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