From: Vivek Goyal <vgoyal@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: nigel@nigel.suspend2.net, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, rjw@sisk.pl, ebiederm@xmission.com,
pavel@ucw.cz, ying.huang@intel.com, mingo@elte.hu,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] kexec jump: fix compiling warning on xchg(&kexec_lock, 0) in kernel_kexec()
Date: Wed, 13 Aug 2008 17:21:47 -0400 [thread overview]
Message-ID: <20080813212147.GF20974@redhat.com> (raw)
In-Reply-To: <20080813134118.e1ab1292.akpm@linux-foundation.org>
On Wed, Aug 13, 2008 at 01:41:18PM -0700, Andrew Morton wrote:
> On Wed, 13 Aug 2008 13:31:24 -0700 (PDT)
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> > On Wed, 13 Aug 2008, Andrew Morton wrote:
> > >
> > > #2:
> >
> > I thought you said there were things that want to sleep in the region?
>
> be reasonable - that was over five minutes ago.
>
> --- a/kernel/kexec.c~kexec-use-a-bitop-for-locking-rather-than-xchg
> +++ a/kernel/kexec.c
> @@ -12,7 +12,7 @@
> #include <linux/slab.h>
> #include <linux/fs.h>
> #include <linux/kexec.h>
> -#include <linux/spinlock.h>
> +#include <linux/mutex.h>
> #include <linux/list.h>
> #include <linux/highmem.h>
> #include <linux/syscalls.h>
> @@ -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_MUTEX(kexec_mutex);
>
> 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 (!mutex_trylock(&kexec_mutex))
> 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);
> + mutex_unlock(&kexec_mutex);
> kimage_free(image);
>
> return result;
> @@ -1063,10 +1056,7 @@ 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
> + /* Take the kexec_mutex 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 (mutex_trylock(&kexec_mutex)) {
> 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);
> + mutex_unlock(&kexec_mutex);
> }
> }
>
> @@ -1434,7 +1422,7 @@ int kernel_kexec(void)
> {
> int error = 0;
>
> - if (xchg(&kexec_lock, 1))
> + if (!mutex_trylock(&kexec_mutex))
> return -EBUSY;
> if (!kexec_image) {
> error = -EINVAL;
> @@ -1498,8 +1486,6 @@ int kernel_kexec(void)
> #endif
>
> Unlock:
> - if (!xchg(&kexec_lock, 0))
> - BUG();
> -
> + mutex_unlock(&kexec_mutex);
> return error;
> }
I tested kexec and kudmp on 2.6.27-rc3 with this patch. Works for me on a
32 bit machine.
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
ebiederm@xmission.com, ying.huang@intel.com, pavel@ucw.cz,
nigel@nigel.suspend2.net, rjw@sisk.pl, 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 17:21:47 -0400 [thread overview]
Message-ID: <20080813212147.GF20974@redhat.com> (raw)
In-Reply-To: <20080813134118.e1ab1292.akpm@linux-foundation.org>
On Wed, Aug 13, 2008 at 01:41:18PM -0700, Andrew Morton wrote:
> On Wed, 13 Aug 2008 13:31:24 -0700 (PDT)
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> > On Wed, 13 Aug 2008, Andrew Morton wrote:
> > >
> > > #2:
> >
> > I thought you said there were things that want to sleep in the region?
>
> be reasonable - that was over five minutes ago.
>
> --- a/kernel/kexec.c~kexec-use-a-bitop-for-locking-rather-than-xchg
> +++ a/kernel/kexec.c
> @@ -12,7 +12,7 @@
> #include <linux/slab.h>
> #include <linux/fs.h>
> #include <linux/kexec.h>
> -#include <linux/spinlock.h>
> +#include <linux/mutex.h>
> #include <linux/list.h>
> #include <linux/highmem.h>
> #include <linux/syscalls.h>
> @@ -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_MUTEX(kexec_mutex);
>
> 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 (!mutex_trylock(&kexec_mutex))
> 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);
> + mutex_unlock(&kexec_mutex);
> kimage_free(image);
>
> return result;
> @@ -1063,10 +1056,7 @@ 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
> + /* Take the kexec_mutex 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 (mutex_trylock(&kexec_mutex)) {
> 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);
> + mutex_unlock(&kexec_mutex);
> }
> }
>
> @@ -1434,7 +1422,7 @@ int kernel_kexec(void)
> {
> int error = 0;
>
> - if (xchg(&kexec_lock, 1))
> + if (!mutex_trylock(&kexec_mutex))
> return -EBUSY;
> if (!kexec_image) {
> error = -EINVAL;
> @@ -1498,8 +1486,6 @@ int kernel_kexec(void)
> #endif
>
> Unlock:
> - if (!xchg(&kexec_lock, 0))
> - BUG();
> -
> + mutex_unlock(&kexec_mutex);
> return error;
> }
I tested kexec and kudmp on 2.6.27-rc3 with this patch. Works for me on a
32 bit machine.
Thanks
Vivek
next prev parent reply other threads:[~2008-08-13 21:22 UTC|newest]
Thread overview: 36+ 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:12 ` Huang Ying
2008-08-13 9:27 ` Andrew Morton
2008-08-13 9:27 ` Andrew Morton
2008-08-13 17:01 ` Linus Torvalds
2008-08-13 17:01 ` Linus Torvalds
2008-08-13 17:25 ` Andrew Morton
2008-08-13 17:25 ` Andrew Morton
2008-08-13 17:59 ` Ingo Molnar
2008-08-13 17:59 ` Ingo Molnar
2008-08-13 16:57 ` Linus Torvalds
2008-08-13 16:57 ` Linus Torvalds
2008-08-13 18:12 ` Eric W. Biederman
2008-08-13 18:12 ` Eric W. Biederman
2008-08-13 18:31 ` Vivek Goyal
2008-08-13 18:31 ` Vivek Goyal
2008-08-13 19:44 ` Andrew Morton
2008-08-13 19:44 ` Andrew Morton
2008-08-13 19:50 ` Linus Torvalds
2008-08-13 19:50 ` Linus Torvalds
2008-08-13 20:07 ` Andrew Morton
2008-08-13 20:07 ` Andrew Morton
2008-08-13 20:13 ` Linus Torvalds
2008-08-13 20:13 ` Linus Torvalds
2008-08-13 20:25 ` Andrew Morton
2008-08-13 20:25 ` Andrew Morton
2008-08-13 20:31 ` Linus Torvalds
2008-08-13 20:31 ` Linus Torvalds
2008-08-13 20:41 ` Andrew Morton
2008-08-13 20:41 ` Andrew Morton
2008-08-13 21:21 ` Vivek Goyal [this message]
2008-08-13 21:21 ` Vivek Goyal
2008-08-13 22:17 ` Linus Torvalds
2008-08-13 22:17 ` Linus Torvalds
2008-08-13 20:15 ` Trond Myklebust
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=20080813212147.GF20974@redhat.com \
--to=vgoyal@redhat.com \
--cc=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.