From: Chris Metcalf <cmetcalf@ezchip.com>
To: lkp@lists.01.org
Subject: Re: [watchdog] 952c8813073: BUG: unable to handle kernel NULL pointer dereference at (null)
Date: Sat, 09 May 2015 10:34:19 -0400 [thread overview]
Message-ID: <554E1AEB.3090707@ezchip.com> (raw)
In-Reply-To: <20150509125054.GD22912@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
On 5/9/2015 8:50 AM, Fengguang Wu wrote:
> Hi Chris,
>
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 952c8813073ed240a610f8b44ecea9bdd60b62b4 ("watchdog: add watchdog_cpumask sysctl to assist nohz")
>
>
> [...]
> [ 0.079378] BUG: unable to handle kernel NULL pointer dereference at (null)
This bug was fixed by John Hubbard here:
http://permalink.gmane.org/gmane.linux.kernel.next/35308
I ack'ed it on May 6 but I think it hasn't made it from Andrew's tree to linux-next yet.
Thanks!
--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
WARNING: multiple messages have this Message-ID (diff)
From: Chris Metcalf <cmetcalf@ezchip.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
LKML <linux-kernel@vger.kernel.org>, <lkp@01.org>
Subject: Re: [watchdog] 952c8813073: BUG: unable to handle kernel NULL pointer dereference at (null)
Date: Sat, 9 May 2015 10:34:19 -0400 [thread overview]
Message-ID: <554E1AEB.3090707@ezchip.com> (raw)
In-Reply-To: <20150509125054.GD22912@wfg-t540p.sh.intel.com>
On 5/9/2015 8:50 AM, Fengguang Wu wrote:
> Hi Chris,
>
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 952c8813073ed240a610f8b44ecea9bdd60b62b4 ("watchdog: add watchdog_cpumask sysctl to assist nohz")
>
>
> [...]
> [ 0.079378] BUG: unable to handle kernel NULL pointer dereference at (null)
This bug was fixed by John Hubbard here:
http://permalink.gmane.org/gmane.linux.kernel.next/35308
I ack'ed it on May 6 but I think it hasn't made it from Andrew's tree to linux-next yet.
Thanks!
--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
next prev parent reply other threads:[~2015-05-09 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-09 12:50 [watchdog] 952c8813073: BUG: unable to handle kernel NULL pointer dereference at (null) Fengguang Wu
2015-05-09 12:50 ` Fengguang Wu
2015-05-09 14:34 ` Chris Metcalf [this message]
2015-05-09 14:34 ` Chris Metcalf
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=554E1AEB.3090707@ezchip.com \
--to=cmetcalf@ezchip.com \
--cc=lkp@lists.01.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 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.