diff options
| author | Matti Vaittinen <matti.vaittinen@nsn.com> | 2011-11-14 00:15:14 +0000 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2011-11-14 14:35:33 -0500 |
| commit | 4a287eba2de395713d8b2b2aeaa69fa086832d34 (patch) | |
| tree | 96962825dab1262bc46c8d5cc067103faea1d9ea /net/ipv6/tcp_ipv6.c | |
| parent | d71314b4ac88637f9ac2770a9f635babdf6f2ff9 (diff) | |
| download | op-kernel-dev-4a287eba2de395713d8b2b2aeaa69fa086832d34.zip op-kernel-dev-4a287eba2de395713d8b2b2aeaa69fa086832d34.tar.gz | |
IPv6 routing, NLM_F_* flag support: REPLACE and EXCL flags support, warn about missing CREATE flag
The support for NLM_F_* flags at IPv6 routing requests.
If NLM_F_CREATE flag is not defined for RTM_NEWROUTE request,
warning is printed, but no error is returned. Instead new route is
added. Later NLM_F_CREATE may be required for
new route creation.
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 created against linux-3.2-rc1
Signed-off-by: Matti Vaittinen <Mazziesaccount@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv6/tcp_ipv6.c')
0 files changed, 0 insertions, 0 deletions
