lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 08 Nov 2010 10:51:57 +0300
From:	Michael Tokarev <mjt@....msk.ru>
To:	ranjith kumar <ranjithproxy@...il.com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: how to read one udp packet with more than one recvfrom() calls?

08.11.2010 10:08, ranjith kumar wrote:
> Hi,
> 
> I  have implemented client and server programs using udp
> protocol(files are attached).
> UDP packet size is 500bytes.
> 
> I want to read these 500bytes in two calls to recvfrom(). First time
> reading 100bytes and second time 400bytes.
> How to do this?

There's no way to do so.  According to the udp(7) manpage:

 All receive operations return only one packet.  When the packet is
 smaller than the passed buffer, only that much data is  returned; when
 it is bigger, the packet is truncated and the MSG_TRUNC flag is set.
 MSG_WAITALL is not supported.

This is intentional, because the kernel does not keep the received
packets, it either delivers them right to the application or drops
them.  There's no sophisticated queue/stream management like for tcp.

For current speeds, one wants to _reduce_ number of system calls
made, not to increase them as you're trying to do, in order to
process as many data in one go as possible.  This is why new
system calls like mrecvfrom are being proposed.

> When I tried to change the third argument of recvfrom(size_t len),
> from 500 to 100, first 100bytes are read correctly.
> But when I call recvfrom() second time with len=400, it is reading the
> first 400bytes of "next udp packet".
> Why? Isn't it possible to read one udp packet in two calls to
> recvfrom()/read()????

This is how UDP is designed to work, and how it works on other
operating systems too.

/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ