From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, bono@onlinehome.de
Subject: Re: [Bugme-new] [Bug 16603] New: send of data > 4 GB fails on 64 bit systems
Date: Mon, 27 Sep 2010 21:07:11 -0700 (PDT) [thread overview]
Message-ID: <20100927.210711.189689133.davem@davemloft.net> (raw)
In-Reply-To: <20100927205624.1564649e.akpm@linux-foundation.org>
From: Andrew Morton <akpm@linux-foundation.org>
Date: Mon, 27 Sep 2010 20:56:24 -0700
> A blanket suckyfix might be, at the syscall level:
>
> if (size > 4g) {
> do_it_in_4g_hunks();
> do_the_last_bit();
> }
>
> unless that would break some networking syscall->framesize guarantees
> or something?
There is not a single length passed in, but a vector of them, that's
what the iovec conveys.
Even if you could, socket send calls have atomicity guarentees. For a
datagram socket, for example, a single send call corresponds to one
packet on the network.
BTW, this aspect of datagram sockets is a part of the reason we don't
see many reports about this stuff. :-) Only stream protocols can
really take such enormous lengths, and the most popular (TCP) does
much of the iovec handling by hand.
We just need to fix our junk, and the {min,max}_t(size_t, ...) change
I suggested is likely the easiest path.
prev parent reply other threads:[~2010-09-28 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16603-10286@https.bugzilla.kernel.org/>
2010-09-27 23:15 ` [Bugme-new] [Bug 16603] New: send of data > 4 GB fails on 64 bit systems Andrew Morton
2010-09-28 2:41 ` David Miller
2010-09-28 3:24 ` David Miller
2010-09-28 3:56 ` Andrew Morton
2010-09-28 4:07 ` David Miller [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=20100927.210711.189689133.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=bono@onlinehome.de \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.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 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).