netdev - Re: [PATCH 1/2] improve netem reorder flexibility

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091221095407.5430a630@nehalam>
Date:	Mon, 21 Dec 2009 09:54:07 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	David Miller <davem@...emloft.net>
Cc:	christian.samsel@...h-aachen.de, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] improve netem reorder flexibility

On Fri, 18 Dec 2009 19:59:07 -0800 (PST)
David Miller <davem@...emloft.net> wrote:

> From: Christian Samsel <christian.samsel@...h-aachen.de>
> Date: Fri, 18 Dec 2009 19:01:28 +0100
> 
> > Am Freitag, 18. Dezember 2009 18:32:40 schrieb Stephen Hemminger:  
> >> On Fri, 18 Dec 2009 14:18:37 +0100
> >> 
> >> Christian Samsel <christian.samsel@...h-aachen.de> wrote:  
> >> > This patch adds a new feature to netem: The newly introduced parameter
> >> > reorderdelay TIME is the time a reordered packet is delayed. It can be
> >> > used in a combination with delay TIME to enable netem to produce late
> >> > packets, which is not possible in the standard netem / iproute2. In the
> >> > standard version reordered packets are always sent immediately and
> >> > therefore are always early packets.  
> >> 
> >> I like the idea but is it binary compatible with older kernels/ older
> >>  iproute2 utilities?
> >>   
> > Thats a good point. I will test it. So far i think it should work.  
> 
> It won't work.
> 
> If you change the size of the tc_netem_qopt, older kernels will
> reject because the size is different from what the kernel expects.
> 
> So newer iproute2 will not work with older kernels.
> 
> You can't change these structures, add new netlink attributes
> to pass the new data instead.

The netem logic for parsing attributes is different from others for
historical reasons.  Looking at parse_attr():

If qopt is larger than expected, then the extra data is interpreted as
the following nested attribute.

If qopt is smaller than expected, then it returns -EINVAL.

Note: in early versions of netem development, the parsing was different,
and it was possible to grow the structure, but the attribute parsing got
changed and is now more restrictive.  BUT that is okay, since the correct
way to add options to netlink API's is to add new attributes, not extend
size of structures.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html