Bug 198271 - BUG warnings in dmesg log - avahi-daemon
Summary: BUG warnings in dmesg log - avahi-daemon
Status: RESOLVED CODE_FIX
Alias: None
Product: Networking
Classification: Unclassified
Component: IPV6 (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Hideaki YOSHIFUJI
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-26 01:42 UTC by Chris Rankin
Modified: 2018-01-21 13:52 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.14.9
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg output containing multiple BUG warnings. (17.09 KB, application/x-xz)
2017-12-26 01:42 UTC, Chris Rankin
Details
dmesg with commit 9704f81 reverted (14.56 KB, application/x-xz)
2017-12-26 09:50 UTC, Chris Rankin
Details
Patch to suppress the warnings (987 bytes, patch)
2017-12-26 18:15 UTC, Jindrich Makovicka
Details | Diff

Description Chris Rankin 2017-12-26 01:42:19 UTC
Created attachment 273309 [details]
dmesg output containing multiple BUG warnings.

Just booted 4.14.9 and seen lots of BUG warnings in the log. The dmesg output is attached. It looks like avahi-daemon is doing strange things with IPv6, possibly related to netfilter.
Comment 1 Chris Rankin 2017-12-26 09:48:39 UTC
On 26 December 2017 at 06:21, Willy Tarreau <w@1wt.eu> wrote:
> Hi Chris,
>
> On Tue, Dec 26, 2017 at 01:49:59AM +0000, Chris Rankin wrote:
> (...)
>> [   35.100181] Call Trace:
>> [   35.102709]  dump_stack+0x46/0x59
>> [   35.106095]  check_preemption_disabled+0xca/0xda
>> [   35.110786]  ip6_pol_route+0x46b/0x509 [ipv6]
> (...)
>
> One patch touched this area between 4.14.8 and 4.14.9, you may try
> to revert it to see if it fixes the issue :
>
>     9704f81 ("ipv6: grab rt->rt6i_ref before allocating pcpu rt")

Reverting this patch seems to have fixed the problem.
Comment 2 Chris Rankin 2017-12-26 09:50:10 UTC
Created attachment 273315 [details]
dmesg with commit 9704f81 reverted
Comment 3 Jindrich Makovicka 2017-12-26 18:15:44 UTC
Created attachment 273319 [details]
Patch to suppress the warnings

This patch avoids the warnings, although I am not sure if it does not just sweep an actual bug under the rug.
Comment 4 Chris Rankin 2018-01-21 13:52:10 UTC
Problem fixed by reverting commit #9704f81.

Note You need to log in before you can comment on or make changes to this bug.