From: Ulf Samuelsson <netdev@emagii•com>
To: Linux Netdev List <netdev@vger•kernel.org>
Subject: netlink NETLINK_ROUTE failure & Can the kernel really handle IPv6 properly
Date: Wed, 01 Oct 2014 22:28:46 +0200 [thread overview]
Message-ID: <542C63FE.9080807@emagii.com> (raw)
Trying to write a kernel module handing NETLINK_ROUTE messages for a
3.4.x kernel.
After building the module, it fails to load on my PowerPC P2020 target.
Reason is that the "netlink_kernel_create" fails.
---------------------------------------
struct *sock nls;
...
static int __init my_init (...)
{
...
nls = netlink_kernel_create( &init_net, NETLINK_ROUTE, 0, my_rcv,
NULL, THIS_MODULE);
if (!nls) {
return -ENOMEM;
}
...
}
----------------------------------------
netlick_kernel_create returns 0, so the kernel module fails.
Is there anything wrong wth the call to netlink_kernel_create ?
Goggling show that some code uses "__net_init".
Not sure what that means.
Other code uses a mutex, instead of NULL.
Does NETLINK_ROUTE require a mutex?
All ideas are welcome-
==============
BTW, the problem I am trying to solve is how to connect to an I/F with
an IPv6 link-local address.
An existing kernel module waits for a NETDEV_UP event, and then tries to
communicate
with the link-local address.
This will fail, because (according to a colleague) the I/F enters a
"tentative" state,
where it is trying to decide if it is unique or not.
It will remain in that state for 1-2 seconds, and only afterwards is the
link-local address
available for normal use.
The guys writing the module, claim that the kernel is using NETDEV_UP.
There is very little code in the kernel using NETLINK_ROUTE, even in
latest stable.
It is using NETDEV_UP.
If my colleague is right, the kernel really cannot handle IPv6
link-local addresses properly.
--
Best Regards
Ulf Samuelsson
next reply other threads:[~2014-10-01 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 20:28 Ulf Samuelsson [this message]
2014-10-01 21:30 ` netlink NETLINK_ROUTE failure & Can the kernel really handle IPv6 properly Hannes Frederic Sowa
2014-10-02 12:38 ` Ulf samuelsson
2014-10-02 15:44 ` Dan Williams
2014-10-03 5:59 ` Ulf Samuelsson
2014-10-03 7:59 ` Ulf Samuelsson
2014-10-03 18:49 ` David Miller
2014-10-06 11:25 ` Ulf Samuelsson
2014-10-06 3:35 ` Gao feng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=542C63FE.9080807@emagii.com \
--to=netdev@emagii$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox