netdev - Re: [PATCH] IPv6 - support for NLM_F_* flags at IPv6 routing requests

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: <20111102.032816.595045810281014355.davem@davemloft.net>
Date:	Wed, 02 Nov 2011 03:28:16 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	matti.vaittinen@....com
Cc:	netdev@...r.kernel.org, shemminger@...tta.com
Subject: Re: [PATCH] IPv6 - support for NLM_F_* flags at IPv6 routing
 requests

From: Matti Vaittinen <matti.vaittinen@....com>
Date: Wed, 02 Nov 2011 09:09:51 +0200

> On Tue, 2011-11-01 at 16:27 +0200, Matti Vaittinen wrote:
>> Hi dee Ho again.
>> 
>> Here's the support for NLM_F_* flags at IPv6 routing requests once again.
>> 
>> This time if no NLM_F_CREATE flag is not defined for RTM_NEWROUTE request,
>> warning is printed, but no error is returned. Instead new route is added.
>> 
>> Exception is when NLM_F_REPLACE flag is given without NLM_F_CREATE, and
>> no matching route is found. In this case it should be safe to assume
>> that the request issuer is familiar with NLM_F_* flags, and does really
>> not want route to be created.
>> 
>> Specifying NLM_F_REPLACE flag will now make the kernel to search for
>> matching route, and replace it with new one. If no route is found and
>> NLM_F_CREATE is specified as well, then new route is created.
>> 
>> Also, specifying NLM_F_EXCL will yield returning of error if matching route 
>> is found.
>> 
>> Patch is created against linux-3.1-rc4
>> 
> 
> New patch where the definition of new error is removed as Stephen suggested.
> 
> Signed-off-by: Matti Vaittinen <Mazziesaccount@...il.com>

Please do not submit new versions of patches in this way by replying
and quoting your original commit log message.  That makes for lots
of work for me.

Instead, submit a fresh new full patch posting and prefix your subject
with something like "[PATCH v2]" to indicate it's a new version.
--
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