From: Li Wei <lw@cn.fujitsu.com>
To: Zhenwei Pi <p_ace@126.com>, <netdev@vger.kernel.org>
Subject: Re: patch for udp_sendmsg
Date: Mon, 20 Jul 2015 10:10:53 +0800 [thread overview]
Message-ID: <55AC58AD.1010703@cn.fujitsu.com> (raw)
In-Reply-To: <55ABB67E.8040100@126.com>
Hello,
Read "Documentation/SubmittingPatches" before sending out the
first patch.
On 07/19/2015 10:38 PM, Zhenwei Pi wrote:
> Dear Sirs,
>
> Commit : the max length of udp msg is (0xFFFF - sizeof(struct udphdr) - sizeof(struct iphdr). return -EMSGSIZE in udp_sendmsg.
> Patch : as the attached file
>
> ____________________________________________________________
> | IP header | UDP header | udp data ........ |
> |___________|______________|_________________________________|
> |--> Total Length : 0xffff <--|
>
>
> If length of "data" is between (0xFFFF - sizeof(struct udphdr) - sizeof(struct iphdr) and 0xFFFF, sendto will fail because of ip_make_skb.
> Should kernel return -EMSGSIZE as soon as possible ?
>
>
prev parent reply other threads:[~2015-07-20 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 14:38 patch for udp_sendmsg Zhenwei Pi
2015-07-20 2:10 ` Li Wei [this message]
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=55AC58AD.1010703@cn.fujitsu.com \
--to=lw@cn.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=p_ace@126.com \
/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;
as well as URLs for NNTP newsgroup(s).