The kernel patch series removing IPV6=m is out! I am quite happy about it and I hope I did not mess up :)
A lot of people were CC'ed, sorry about the noise ^^
The kernel patch series removing IPV6=m is out! I am quite happy about it and I hope I did not mess up :)
A lot of people were CC'ed, sorry about the noise ^^
It seems I messed up. fs_initcall() is not good enough as under certain situations there might be a race condition when booting up.
Replacing it with device_initcall() seems good enough.
One thing I do not understand is why this doesn't happen on my environment but it does happen on virtme-ng..
@ffmancera doesnt 9pfs setups network early, before calling init, making it fail this way?
That would also depend on how you invoke virtme-ng, I'm just guessing here :)
@mpdesouza So in essence, this seems a race condition as after booting several times on my libvirt environment I managed to catch it.
I think it is related to addrconf checking on loopback or some other uninitialized device..
After looking at the code using device_initcall() makes more sense.
103 files changed, 310 insertions(+), 795 deletions(-)
@T_X AFAIU, openWRT is using CONFIG_IPV6=y by default since these three commits.
https://github.com/openwrt/openwrt/commit/0c8f0186d58468024db96a5ab0ca36a4d400d408
https://github.com/openwrt/openwrt/commit/836d462b10e82a3314e62bb5d15a1632e5786271
https://github.com/openwrt/openwrt/commit/33beafa8d88e51907acba6fdece5a35f509934df