Warning at kernel/softirq.c:161

Hi folks,

A test vm was sitting idle overnight, and just after midnight it threw this warning:

 ------------[ cut here ]------------
 WARNING: CPU: 3 PID: 14397 at kernel/softirq.c:161 __local_bh_enable_ip+0x76/0xa0
 Modules linked in:
 CPU: 3 PID: 14397 Comm: pmlogger Not tainted 4.9.0-rc1-dgc+ #1006
 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Debian-1.8.2-1 04/01/2014
  ffffc9000a407ba0 ffffffff81822120 0000000000000000 0000000000000000
  ffffc9000a407be0 ffffffff810b69fb 000000a133ac6b00 0000000000000201
  00000000ffffffff ffffffff8257eec0 ffff88013892a400 ffff88013a0c1c00
 Call Trace:
  [<ffffffff81822120>] dump_stack+0x63/0x83
  [<ffffffff810b69fb>] __warn+0xcb/0xf0
  [<ffffffff810b6aed>] warn_slowpath_null+0x1d/0x20
  [<ffffffff810bc296>] __local_bh_enable_ip+0x76/0xa0
  [<ffffffff81c8e92e>] _raw_spin_unlock_bh+0x1e/0x20
  [<ffffffff81b61372>] peernet2id+0x42/0x50
  [<ffffffff81b95a57>] netlink_broadcast_filtered+0x217/0x3b0
  [<ffffffff81b95c0d>] netlink_broadcast+0x1d/0x20
  [<ffffffff811537d7>] audit_log_end+0x177/0x1a0
  [<ffffffff817b02d0>] ? securityfs_remove+0x90/0x90
  [<ffffffff817cb506>] common_lsm_audit+0x216/0x650
  [<ffffffff817b0ebb>] ? avc_update_node+0x1bb/0x300
  [<ffffffff817b11ba>] slow_avc_audit+0x5a/0x70
  [<ffffffff817b1988>] avc_has_perm+0x188/0x1b0
  [<ffffffff812022a7>] ? __vfs_write+0xc7/0x140
  [<ffffffff817b32da>] current_has_perm+0x5a/0x70
  [<ffffffff817b33c3>] selinux_task_setpgid+0x13/0x20
  [<ffffffff817aeacb>] security_task_setpgid+0x3b/0x50
  [<ffffffff810caa85>] SyS_setpgid+0x165/0x1c0
  [<ffffffff81002b97>] do_syscall_64+0x67/0x180
  [<ffffffff81c8edab>] entry_SYSCALL64_slow_path+0x25/0x25
 ---[ end trace 6c6281fed3717798 ]---

No idea what caused it, VM has 4p, 4GB RAM, and using virtio for the network devices. never seen it before, no idea if it is reproducable as my test vms don't tend to sit idle for 5 hours like this one did before tripping this.

Cheers,

Dave.

Dave Chinner
[email protected]

Hi,

We are discussing a fix:
https://patchwork.ozlabs.org/patch/684753/

Thanks.