From: 배석진 <soukjin.bae@samsung.com>
To: Eric Dumazet <eric.dumazet@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE:(2) (2) (2) (2) [Kernel][NET] Bug report on packet defragmenting
Date: Fri, 09 Nov 2018 09:42:16 +0900 [thread overview]
Message-ID: <1181390155.1787604.1541724136242.JavaMail.jboss@ep1ml102> (raw)
In-Reply-To: <dce9a158-8e7b-1381-c7ff-b590771f95fb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
>Thanks for testing.
>
>This is not a pristine net-next tree, this dump seems unrelated to the patch ?
yes, looks like that.
but only when using your patch, panic came. even right after packet recieving..
without that, there's no problem except defrag issue. it's odd.. :p
I couldn't more debugging since have other problems.
[-- Attachment #2: rcptInfo.txt --]
[-- Type: application/octet-stream, Size: 1090 bytes --]
=================================================================================================================================
Subject : Re: (2) (2) (2) [Kernel][NET] Bug report on packet defragmenting
From : Eric Dumazet eric.dumazet@gmail.com
Sent Date : 2018-11-09 00:12 GMT+9
=================================================================================================================================
Name Type Job Title Dept. Company
=================================================================================================================================
배석진 TO Staff Engineer System개발2그룹(무선) 삼성전자
eric.dumazet@gmail.com TO
netdev@vger.kernel.org TO
=================================================================================================================================
next prev parent reply other threads:[~2018-11-09 10:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p4>
2018-11-08 1:29 ` [Kernel][NET] Bug report on packet defragmenting 배석진
2018-11-08 1:43 ` Eric Dumazet
[not found] ` <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p5>
2018-11-08 2:05 ` 배석진
2018-11-08 3:24 ` (2) " Eric Dumazet
2018-11-08 3:56 ` Eric Dumazet
[not found] ` <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p6>
2018-11-08 4:10 ` 배석진
2018-11-08 4:26 ` (2) " Eric Dumazet
2018-11-08 6:13 ` Eric Dumazet
[not found] ` <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p2>
2018-11-08 7:58 ` 배석진
2018-11-08 15:12 ` (2) " Eric Dumazet
[not found] ` <CGME20181108012927epcms1p47f719c1908da64a378690362901644ee@epcms1p1>
2018-11-09 0:42 ` 배석진 [this message]
2018-11-09 1:58 ` (2) " Eric Dumazet
2018-11-09 2:24 ` 배석진
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=1181390155.1787604.1541724136242.JavaMail.jboss@ep1ml102 \
--to=soukjin.bae@samsung.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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.