[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <18341daf5b2c458db8e30299d6cddafc@ZCOM03.mut-group.com>
Date: Thu, 2 Aug 2018 13:57:19 +0000
From: Marcel Hellwig <mhellwig@...-group.com>
To: 'Eric Dumazet' <eric.dumazet@...il.com>,
David Laight <David.Laight@...LAB.COM>,
"'davem@...emloft.net'" <davem@...emloft.net>,
"'kuznet@....inr.ac.ru'" <kuznet@....inr.ac.ru>,
"'yoshfuji@...ux-ipv6.org'" <yoshfuji@...ux-ipv6.org>,
"'andrew@...n.ch'" <andrew@...n.ch>
CC: "'netdev@...r.kernel.org'" <netdev@...r.kernel.org>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
"Matthias Wystrik" <mwystrik@...-group.com>
Subject: AW: AW: PROBLEM: Kernel Oops in UDP stack
>> There are actually 2 faults, difficult to quickly sort out the merged tracebacks.
>> You are also running a rather old kernel: Linux version 3.4.113.
>>
>> It may well be that whichever ethernet driver generated the misaligned
>> frame has since been fixed.
>
>A misalign frame driver problem would have faulted earlier in IP stack, much before we perform the copy to user space in udp_recvmsg()
>
JFYI: we are talking about the lpc_eth driver[0] #57c10b6 , which is not the newest, but all newer did not fix a major problem (at least the commit messages are not screaming: WARNING, UNALIGNED MEMORY!). Is there a diagram/document how a ip packet travels down the code? From the MAC/phy driver to udp_recvmsg? It's not that obvious for me, but maybe it is something I can work with.
[0]: https://elixir.bootlin.com/linux/v3.4.113/source/drivers/net/ethernet/nxp/lpc_eth.c
Regards,
Marcel
Powered by blists - more mailing lists