In the "obscure driver problems" department

[jiml8]

I don't think this post belongs in this forum but I am not sure where to put it so I am putting it here. Move as you see fit.

This one has actually been biting me hard, since I have been doing a lot of work with the synclink_gt.c driver and have been encountering problems with the race condition described here - and have been actively hunting for the problem.

http://lwn.net/Articles/578773/
https://lkml.org/lkml/2014/1/2/122

I have no idea how long it will take for these patches to be picked up in the kernel tree, but I'm posting this on the off-chance that Mageia would want to patch the driver as indicated.

I have patched it, and am currently testing (though we have built our own distro tailored for our embedded needs so this is not testing on Mageia).

[merlin]

I suspect Mageia uses a mainline kernel stable branch in https://git.kernel.org/cgit/linux/kerne ... table.git/ such as linux-3.10-y and then applies Mageia specific kernel commits on top.

Therefore, I recommend you try to get kernel patches into the upstream kernel.org kernel git repos via the appropriate kernel maintainers and kernel mailing lists. If the fix goes onto the stable branch say linux-3.10-y then Mageia would pick it up in due course.

I think Mageia has a kernel team. Check on the Mageia website to see whether they have a bugzilla bug report system and raise a bug report for kernel patches.

[doktor5000]

I think Mageia has a kernel team. Check on the Mageia website to see whether they have a bugzilla bug report system and raise a bug report for kernel patches.

Well, there's no team, only one person. And yes, best report it via bugzilla, as usually most developers don't read forums.
https://wiki.mageia.org/en/How_to_report_a_bug_properly