linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: caiqian@redhat.com
Cc: torvalds@linux-foundation.org, linux-next@vger.kernel.org,
	kexec <kexec@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kdump regression compared to v2.6.35
Date: Tue, 31 Aug 2010 11:22:40 +0200	[thread overview]
Message-ID: <4C7CC9E0.20501@kernel.org> (raw)
In-Reply-To: <2044609874.1606211283216015254.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>

Hello,

Thanks for verifyiing.  Can you please apply this patch on top and
check that those debug messages go away?

Thanks.

diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index c8183b2..7855429 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue.c
@@ -196,7 +196,7 @@ typedef cpumask_var_t mayday_mask_t;
 	cpumask_test_and_set_cpu((cpu), (mask))
 #define mayday_clear_cpu(cpu, mask)		cpumask_clear_cpu((cpu), (mask))
 #define for_each_mayday_cpu(cpu, mask)		for_each_cpu((cpu), (mask))
-#define alloc_mayday_mask(maskp, gfp)		alloc_cpumask_var((maskp), (gfp))
+#define alloc_mayday_mask(maskp, gfp)		zalloc_cpumask_var((maskp), (gfp))
 #define free_mayday_mask(mask)			free_cpumask_var((mask))
 #else
 typedef unsigned long mayday_mask_t;

  reply	other threads:[~2010-08-31  9:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <71887879.1606161283215975799.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-31  0:53 ` kdump regression compared to v2.6.35 caiqian
2010-08-31  9:22   ` Tejun Heo [this message]
     [not found] <373987879.1541191283181021800.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-30 15:10 ` caiqian
2010-08-30 16:38   ` Tejun Heo
2010-08-30 17:31     ` Tejun Heo
     [not found] <123671462.1479561283081998014.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-29 11:41 ` caiqian
2010-08-29 11:56   ` CAI Qian
2010-08-29 11:52     ` Tejun Heo
2010-08-29 12:03       ` CAI Qian
2010-08-29 12:36         ` Tejun Heo
2010-08-30  3:42           ` CAI Qian
2010-08-30  8:29             ` Tejun Heo
2010-08-30 10:24               ` CAI Qian
2010-08-30 12:50                 ` Tejun Heo
2010-08-30 14:02                   ` CAI Qian
2010-08-30 14:21                     ` Tejun Heo
2010-08-30 14:47                       ` CAI Qian
2010-08-30 14:51                         ` CAI Qian
2010-08-30 14:55                           ` Tejun Heo
     [not found] <2142316909.1477341283065016062.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-29  7:01 ` caiqian
2010-08-29  8:57   ` Tejun Heo
2010-08-29 11:24     ` CAI Qian
2010-08-29 11:21       ` Tejun Heo
     [not found] <229468156.1475641283020469212.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-28 18:36 ` caiqian
     [not found] <2082161789.1474781283008521258.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-28 15:19 ` caiqian
2010-08-27 12:35 CAI Qian

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=4C7CC9E0.20501@kernel.org \
    --to=tj@kernel.org \
    --cc=caiqian@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).