# VERIFICATION FOCAL
Validation performed on a 6-core VM with 8Gb or RAM. The following stress-ng
command was running throughout the test from the description:
# stress-ng --class memory --class vm --all 1 --timeout 96h
Afterwards, the udevadm test loop was executed as below:
# date; while
Thanks, Robie! Our users reported that issues usually appear within one
or two hours, but that's likely tied to machine-specific workloads.
I've been able to force this issue to occur in a VM when running the
test script from the description together with stress-ng memory/vm
stressors. The
Accepting, but in the Test Plan, please could you elaborate on how long
you need to typically wait to see the reproducer, so that a third party
will be able to verify if they are not affected? Eg. 1 minute, 1 hour, 1
day or 1 week? Then, during SRU verification, if we wait (say) double
that time,
We've had users report this bug under Focal, and the usbguard pkg there
does seem to be missing this fix. I've updated the bug with the SRU
template, and tested the patches (builds available at [0]). Users also
reported that this patched version resolved this issue, so I've pushed
it to the Focal
** Description changed:
- With 0.7.4+ds-1 from 19.10, usbguard may stop responding to events when
- recvmsg fails with ENOBUFS. To reproduce:
+ [Impact]
+ usbguard-daemon will no longer process device events until restarted
+
+ [Test Plan]
+ 1. Spin up a Focal VM with usbguard enabled
+ 2. Run
** Also affects: usbguard (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: usbguard (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: usbguard (Ubuntu Focal)
Status: New => In Progress
** Changed in: usbguard (Ubuntu Focal)
Assignee:
The issue is fixed in the current version now
https://launchpad.net/ubuntu/+source/usbguard/0.7.8+ds-1
** Changed in: usbguard (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FYI, upstream committed https://github.com/USBGuard/usbguard/pull/378 to
address this issue. It is essentially what I mentioned in the bug
description.
** Changed in: usbguard (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
** Changed in: usbguard
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855189
Title:
usbguard stops responding when recvmsg receives ENOBUFS
To manage notifications
FYI, IMHO, this bug needs to be fixed as part of the MIR process in bug
#1816548.
** Bug watch added: github.com/USBGuard/usbguard/issues #349
https://github.com/USBGuard/usbguard/issues/349
** Also affects: usbguard via
https://github.com/USBGuard/usbguard/issues/349
Importance:
10 matches
Mail list logo
