From: David Laight <David.Laight@ACULAB.COM>
To: 'Eric Dumazet' <eric.dumazet@gmail.com>,
'Marcel Hellwig' <mhellwig@mut-group.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: RE: AW: PROBLEM: Kernel Oops in UDP stack
Date: Thu, 2 Aug 2018 13:18:57 +0000 [thread overview]
Message-ID: <b124d0aedf7c41fba86c59efe4c957a2@AcuMS.aculab.com> (raw)
In-Reply-To: <405319c1-2fa0-e1b5-7173-b19d9769d98a@gmail.com>
From: Eric Dumazet
> Sent: 02 August 2018 14:13
>
> A misalign frame driver problem would have faulted earlier in IP stack,
> much before we perform the copy to user space in udp_recvmsg()
And my mailer failed to thread all the later responses :-(
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2018-08-02 13:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 15:06 PROBLEM: Kernel Oops in UDP stack 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
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 [this message]
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=b124d0aedf7c41fba86c59efe4c957a2@AcuMS.aculab.com \
--to=david.laight@aculab.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=mhellwig@mut-group.com \
--cc=mwystrik@mut-group.com \
--cc=netdev@vger.kernel.org \
--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 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.