From: Marcel Hellwig <mhellwig@mut-group.com>
To: 'Eric Dumazet' <eric.dumazet@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
"'davem@davemloft.net'" <davem@davemloft.net>,
"'kuznet@ms2.inr.ac.ru'" <kuznet@ms2.inr.ac.ru>,
"'yoshfuji@linux-ipv6.org'" <yoshfuji@linux-ipv6.org>,
"'andrew@lunn.ch'" <andrew@lunn.ch>
Cc: "'netdev@vger.kernel.org'" <netdev@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"Matthias Wystrik" <mwystrik@mut-group.com>
Subject: AW: AW: AW: PROBLEM: Kernel Oops in UDP stack
Date: Thu, 2 Aug 2018 11:02:39 +0000 [thread overview]
Message-ID: <c54e9eee0add4f04b0ce61a1ae2c3f04@ZCOM03.mut-group.com> (raw)
In-Reply-To: <1ae1b19241734bfaacff082d241932f9@ZCOM03.mut-group.com>
Hi everyone,
I did three things that evening.
* I created a small dts file, so I could boot a 3.5.7 kernel.
* Ported the pskb_expand_head from 3.5.7 to 3.4.113
* Ported the whole skbuf.{c,h} file from 3.5.7 to 3.4.113
Sadly enough the second and third one panicked as well, but interestingly not the first one (3.5.7 with a simple dts file). Now the question is: Is something changed outside of the skbuf (maybe in udp.{c,h}?) or is it because the dts uses a different approach of talking to the MAC of the lpc3250?
I may try a more recent kernel with a dts file (maybe a 4.x.x one), but I think that will be impossible to backport a patch for our 2.6 kernel :(
If anybody has any more ideas about why the dts kernel does not panic, you're very welcome.
Mit freundlichen Grüßen / With kind regards
Marcel Hellwig
B. Sc. Informatik
Entwickler
m-u-t GmbH
Am Marienhof 2
22880 Wedel
Germany
Phone: +49 4103 9308 - 474
Fax: +49 4103 9308 - 99
mhellwig@mut-group.com
www.mut-group.com
Geschäftsführer (Managing Director): Fabian Peters
Amtsgericht Pinneberg (Commercial Register No.): HRB 10304 PI
USt-IdNr. (VAT-No.): DE228275390
WEEE-Reg-Nr.: DE 72271808
next prev parent reply other threads:[~2018-08-02 11:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 15:06 Marcel Hellwig
2018-07-31 15:59 ` Eric Dumazet
2018-08-01 5:55 ` AW: " Marcel Hellwig
2018-08-01 10:20 ` Eric Dumazet
2018-08-01 10:35 ` AW: " Marcel Hellwig
2018-08-01 10:44 ` Paolo Abeni
2018-08-01 10:49 ` Eric Dumazet
2018-08-01 11:25 ` Eric Dumazet
2018-08-01 11:31 ` AW: " Marcel Hellwig
2018-08-01 13:27 ` Marcel Hellwig
2018-08-02 11:02 ` Marcel Hellwig [this message]
2018-08-02 13:05 ` Eric Dumazet
2018-08-02 9:17 ` David Laight
2018-08-02 13:13 ` Eric Dumazet
2018-08-02 13:18 ` David Laight
2018-08-02 13:57 ` AW: " Marcel Hellwig
2018-08-02 15:07 ` Eric Dumazet
2018-08-03 8:24 ` AW: " Marcel Hellwig
2018-08-07 13:42 ` Marcel Hellwig
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=c54e9eee0add4f04b0ce61a1ae2c3f04@ZCOM03.mut-group.com \
--to=mhellwig@mut-group.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mwystrik@mut-group.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshfuji@linux-ipv6.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
Powered by JetHome