My initial conclusion about go-udev being the culprit was premature, the
socket closing & quit channel code looks fine after all, the problem
lies somewhere else and may be something in the go runtime stack and
it's very unclear for the time being.
** Changed in: snapd (Ubuntu)
Importance:
The bug may occur regardless of experimental hotplug flag, and may
prevent clean shutdown of snapd - of course only if there is udev
netlink activity, therefore setting to critical.
** Changed in: snapd
Importance: High => Critical
** Changed in: snapd (Ubuntu)
Importance: Medium =>
** Changed in: snapd (Ubuntu)
Status: New => In Progress
** Changed in: snapd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824162
Title:
I think the bug is in the go-udev package (upstream). The Monitor()
function returns a 'quit' channel that the caller uses to stop
processing. Monitor() runs a backgroud goroutine that monitors/reads
from netlink socket and stops if quit channel is written to. I think the
problem is that the quit
** Changed in: snapd
Assignee: (unassigned) => Paweł Stołowski (stolowski)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824162
Title:
It looks like an udev/netlink related panic in snapd
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => High
--
You received this bug notification because you are a member of
