kmsg log is full of these entries: "netlink: 12 bytes leftover after parsing attributes"

[rivalcomp]

Dear Devs,

I like using qBittorrent because it's much more faster than Transmission and it has proxy support. But I have a problem with it: since I switched to qBittorrent the kmsg log is full of these entries:

[170078.110594] netlink: 12 bytes leftover after parsing attributes.
[170078.110604] netlink: 12 bytes leftover after parsing attributes.
[170078.110754] netlink: 12 bytes leftover after parsing attributes.
[170078.110794] netlink: 12 bytes leftover after parsing attributes.
[170078.115672] netlink: 12 bytes leftover after parsing attributes.
[170078.115683] netlink: 12 bytes leftover after parsing attributes.
[170078.115869] netlink: 12 bytes leftover after parsing attributes.
[170078.115919] netlink: 12 bytes leftover after parsing attributes.
[170078.117402] netlink: 12 bytes leftover after parsing attributes.
[170078.117419] netlink: 12 bytes leftover after parsing attributes.
[170078.117588] netlink: 12 bytes leftover after parsing attributes.
[170078.117637] netlink: 12 bytes leftover after parsing attributes.
[170087.915229] netlink: 12 bytes leftover after parsing attributes.
[170087.915243] netlink: 12 bytes leftover after parsing attributes.
[170087.915446] netlink: 12 bytes leftover after parsing attributes.
[170087.915508] netlink: 12 bytes leftover after parsing attributes.
[170087.915771] netlink: 12 bytes leftover after parsing attributes.

It grows by 1-2 lines (entries) per second. When I stop qBittorrent these entries stop to grow. When these kernel messages are growing, the system calls dd regularily to dump these messages to the kmsg log (I can see this activity in iotop). Disks are clicking all the time. After stopping qBittorrent, everything is back to normal. Please try to solve or help me to find solution to this problem. Google is not my friend this time. Tried to file this issue to the QNAP forum a few weeks ago but nobody cares about it. Thanks.

It's an issue since I use qBittorrent so it's version independent from my view, but actually I'm using the most recent 4.3.0.

qBittorrent version and Operating System

SW: qBittorrent 4.3.0
OS: Linux 3.4.6 #1 SMP Tue Oct 6 06:14:39 CST 2020 x86_64 GNU/Linux
HW: QNAP TS-469L; 4x4TB RAID5, 3GB RAM, firmware version 4.3.4.1368 (2020/07/03)

Steps to reproduce

Nothing, just running qBittorrent server.

[FranciscoPombal]

Where did you download qBittorrent from? Did you compile it yourself? If so, how? And what are the versions of the libraries used (most importantly, libtorrent)?

[NotTsunami]

I suspect it has to do with the ancient Linux kernel used. Netlink communicates between user-space and kernel. A library used for qBit or even your OS might be expecting logic from a newer kernel. It appears 3.4.6 is the latest kernel version officially supported for that hardware though, unfortunately.

[FranciscoPombal]

@NotTsunami

I suspect it has to do with the ancient Linux kernel used. Netlink communicates between user-space and kernel. A library used for qBit or even your OS might be expecting logic from a newer kernel. It appears 3.4.6 is the latest kernel version officially supported for that hardware though, unfortunately.

Wow, 3.4.6, I had not noticed that. This is certainly a possibility. Any idea how one could go about verifying your hypothesis?

[rivalcomp]

Where did you download qBittorrent from? Did you compile it yourself? If so, how? And what are the versions of the libraries used (most importantly, libtorrent)?

It is installed from Qnapclub Repo: https://www.qnapclub.eu/en/qpkg/358
As I can see it's a static build so I don't have libtorrent installed. But at this moment I can see a new version (4.3.1) so I'm going to do a test with this new build and I will report.

Edit: it's the same with version 4.3.1 as well...

[luzpaz]

Closing as version is obsolete and no follow-ups.

[rivalcomp]

Just for a remark: qBittorrent v4.5.5 also has this issue.
Not a big deal. Kmsg log grows to huge after while and I clean it up with an automated script.
As it seems, this NAS dies in the future with this issue. :)
This thread can remain closed of course. Thanks.