From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>, Jet Chen <jet.chen@intel.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
linux-crypto@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, linux-can@vger.kernel.org,
netfilter-devel@vger.kernel.org, netfilter@vger.kernel.org
Subject: Re: [net] BUG: unable to handle kernel NULL pointer dereference at 000000000000022f
Date: Tue, 13 May 2014 09:43:54 +0200 [thread overview]
Message-ID: <5371CD3A.9020500@pengutronix.de> (raw)
In-Reply-To: <5371AA32.6070407@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On 05/13/2014 07:14 AM, Oliver Hartkopp wrote:
> Hello Jet,
>
> this is likely not CAN related, as
>
> # CONFIG_CAN is not set
>
> and all the CAN changes introduced by Marc's merge are not even compiled in
> your setup.
>
> So I assume the issue somewhere in the netlink or ipv6 stuff (see commit at
> the end.
Yes, I my merge is probably broken. That was an attempt to merge net
into net-next, but I'm going to ask David Miller to do so. As I'm going
to rebase this branch onto David's net-next (after the net merge), we
can ignore this for now.
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]
next prev parent reply other threads:[~2014-05-13 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 2:52 [net] BUG: unable to handle kernel NULL pointer dereference at 000000000000022f Jet Chen
2014-05-13 5:14 ` Oliver Hartkopp
2014-05-13 7:43 ` Marc Kleine-Budde [this message]
2014-05-13 7:51 ` Marc Kleine-Budde
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=5371CD3A.9020500@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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.