From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Austin Schuh <austin@peloton-tech.com>
Cc: linux-can@vger.kernel.org
Subject: Re: skbuff panic
Date: Sun, 06 Jul 2014 21:38:21 +0200 [thread overview]
Message-ID: <53B9A5AD.8050403@pengutronix.de> (raw)
In-Reply-To: <53B97598.50400@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
On 07/06/2014 06:13 PM, Oliver Hartkopp wrote:
> Answering myself:
>
> I tested the latest 3.16.0-rc3-00149-g034a0f6 with tst-packet.c and it works
> like charm. Receiving and sending with tst-packet is no problem.
> I was using the SJA1000 based EMS PCMCIA card in my laptop for this test.
>
> So I really wonder why (obviously) a CAN frame is processed by the PF_PACKET
> reception handler at the start of your system?!?
What about a dhcp client or the kernel's autoip functionality?
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-07-06 19:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 23:03 skbuff panic Austin Schuh
2014-07-03 23:18 ` Austin Schuh
2014-07-05 10:40 ` Oliver Hartkopp
2014-07-05 18:38 ` Austin Schuh
2014-07-05 19:21 ` Oliver Hartkopp
2014-07-06 5:07 ` Austin Schuh
2014-07-06 12:12 ` Oliver Hartkopp
2014-07-06 16:13 ` Oliver Hartkopp
2014-07-06 19:38 ` Marc Kleine-Budde [this message]
2014-07-07 4:11 ` Austin Schuh
2014-07-10 0:07 ` Austin Schuh
2014-07-10 17:37 ` Austin Schuh
2014-07-11 13:27 ` Oliver Hartkopp
2014-07-11 14:58 ` Austin Schuh
2014-07-11 17:48 ` Marc Kleine-Budde
2015-02-19 11:48 ` Daniel Steer
2015-02-23 12:55 ` Oliver Hartkopp
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=53B9A5AD.8050403@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=austin@peloton-tech.com \
--cc=linux-can@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.