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] [day] [month] [year] [list]

Date:	Wed, 10 Jun 2009 12:35:08 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	David Miller <davem@...emloft.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

David Miller wrote:
> From: Patrick McHardy <kaber@...sh.net>
> Date: Mon, 06 Apr 2009 15:21:45 +0200
> 
>> 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.

Yes, something like NLM_F_MULTI to accumulate multiple messages might
help. I'm not sure yet whether this can be used to make the entire
operation atomic since the individual attributes still can't span more
than one skb, but it looks worth a try.
--
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