From: akpm@linux-foundation.org
To: v.mayatskih@gmail.com, amwang@redhat.com, nhorman@tuxdriver.com,
mm-commits@vger.kernel.org
Subject: [merged] kexec-fix-oops-in-crash_kernel_shrink.patch removed from -mm tree
Date: Wed, 12 May 2010 10:58:23 -0400 [thread overview]
Message-ID: <201005121759.o4CHxpXn011535@imap1.linux-foundation.org> (raw)
The patch titled
kexec: fix OOPS in crash_kernel_shrink
has been removed from the -mm tree. Its filename was
kexec-fix-oops-in-crash_kernel_shrink.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: kexec: fix OOPS in crash_kernel_shrink
From: Vitaly Mayatskikh <v.mayatskih@gmail.com>
Two "echo 0 > /sys/kernel/kexec_crash_size" OOPSes kernel. Also content
of this file is invalid after first shrink to zero: it shows 1 instead of
0.
This scenario is unlikely to happen often (root privs, valid crashkernel=
in cmdline, dump-capture kernel not loaded), I hit it only by chance.
This patch fixes it.
Signed-off-by: Vitaly Mayatskikh <v.mayatskih@gmail.com>
Cc: Cong Wang <amwang@redhat.com>
Cc: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/kexec.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff -puN kernel/kexec.c~kexec-fix-oops-in-crash_kernel_shrink kernel/kexec.c
--- a/kernel/kexec.c~kexec-fix-oops-in-crash_kernel_shrink
+++ a/kernel/kexec.c
@@ -1134,11 +1134,9 @@ int crash_shrink_memory(unsigned long ne
free_reserved_phys_range(end, crashk_res.end);
- if (start == end) {
- crashk_res.end = end;
+ if (start == end)
release_resource(&crashk_res);
- } else
- crashk_res.end = end - 1;
+ crashk_res.end = end - 1;
unlock:
mutex_unlock(&kexec_mutex);
_
Patches currently in -mm which might be from v.mayatskih@gmail.com are
origin.patch
reply other threads:[~2010-05-12 18:00 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=201005121759.o4CHxpXn011535@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=v.mayatskih@gmail.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