From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: YUAN Jia <Jia.Yuan@alcatel-sbell.com.cn>
Cc: "'linux-sctp@vger.kernel.org'" <linux-sctp@vger.kernel.org>,
'network dev' <netdev@vger.kernel.org>
Subject: Re: A PMTU auto-discovery error for large SCTP packets
Date: Sun, 29 Jan 2017 14:39:43 +0000 [thread overview]
Message-ID: <20170129143943.GL3781@localhost.localdomain> (raw)
In-Reply-To: <07B7943445653648AD9B4DBB916BB48F1C265220@cnshjmbx01>
On Wed, Jan 25, 2017 at 06:40:10AM +0000, YUAN Jia wrote:
...
> I think that ‘sctp_manip_pkt’ should also behave like this. Isn’t it?
I believe so, yes.
Will you send a patch?
Btw, your host did have a MTU bigger than 1500, right? I'm just curious
on why such big packet was generated in the first place.
Marcelo
WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: YUAN Jia <Jia.Yuan@alcatel-sbell.com.cn>
Cc: "'linux-sctp@vger.kernel.org'" <linux-sctp@vger.kernel.org>,
"'network dev'" <netdev@vger.kernel.org>
Subject: Re: A PMTU auto-discovery error for large SCTP packets
Date: Sun, 29 Jan 2017 12:39:43 -0200 [thread overview]
Message-ID: <20170129143943.GL3781@localhost.localdomain> (raw)
In-Reply-To: <07B7943445653648AD9B4DBB916BB48F1C265220@cnshjmbx01>
On Wed, Jan 25, 2017 at 06:40:10AM +0000, YUAN Jia wrote:
...
> I think that ‘sctp_manip_pkt’ should also behave like this. Isn’t it?
I believe so, yes.
Will you send a patch?
Btw, your host did have a MTU bigger than 1500, right? I'm just curious
on why such big packet was generated in the first place.
Marcelo
next prev parent reply other threads:[~2017-01-29 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 6:40 A PMTU auto-discovery error for large SCTP packets YUAN Jia
2017-01-29 14:39 ` Marcelo Ricardo Leitner [this message]
2017-01-29 14:39 ` Marcelo Ricardo Leitner
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=20170129143943.GL3781@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=Jia.Yuan@alcatel-sbell.com.cn \
--cc=linux-sctp@vger.kernel.org \
--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.