netdev - Re: [Patch 4/5] Network Drop Monitor: Adding drop monitor implementation & Netlink protocol

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]

Message-Id: <20090610.010828.81117955.davem@davemloft.net>
Date:	Wed, 10 Jun 2009 01:08:28 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	kaber@...sh.net
Cc:	herbert@...dor.apana.org.au, nhorman@...driver.com,
	zbr@...emap.net, netdev@...r.kernel.org, kuznet@....inr.ac.ru,
	pekkas@...core.fi, jmorris@...ei.org, yoshfuji@...ux-ipv6.org
Subject: Re: [Patch 4/5] Network Drop Monitor: Adding drop monitor
 implementation & Netlink protocol

From: Patrick McHardy <kaber@...sh.net>
Date: Mon, 06 Apr 2009 15:21:45 +0200

> David Miller wrote:
>> We can start treating it like a real protocol, firmly define
>> the endianness of everything to kill all the over-the-wire
>> issues, etc. and deal with this 4-byte-align stuff as well.
> 
> We could add a setsockopt option for userspace to specify "version 2"
> operation. The netlink attributes helpers would need to be aware of
> the currently used protocol version and could transparently choose
> a different encoding (also taking care of endianess etc). For the
> case of one value per attribute this should be a straight-forward
> conversion. In case of structures that contain values with different
> endianness, we'll probably need to define a new encoding (ideally
> also one attribute per value) for version 2.

Ok.

> I'd also suggest to get rid of the 64k attribute and message size
> limit at the same time, this is making it quite hard to support
> transactional semantics for large updates (f.i. for nf_tables sets).

Another option is to support continuations of some sort.
--
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