Bug 2178798 - vlock 100% CPU when console or terminal is closed abruptly
Summary: vlock 100% CPU when console or terminal is closed abruptly
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kbd
Version: 8.10
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Vitezslav Crhonek
QA Contact: Evgeny Fedin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-15 18:26 UTC by Timothy Mullican
Modified: 2023-06-29 15:22 UTC (History)
3 users (show)

Fixed In Version: kbd-2.0.4-11.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
kbd-1.15.5-vlock-stdin-closed-inf-loop.patch (632 bytes, patch)
2023-03-15 18:26 UTC, Timothy Mullican
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-151990 0 None None None 2023-03-15 18:28:59 UTC

Description Timothy Mullican 2023-03-15 18:26:53 UTC
Created attachment 1951091 [details]
kbd-1.15.5-vlock-stdin-closed-inf-loop.patch

Description of problem:
vlock causes 100% CPU usage when console or terminal is closed abruptly. It looks like there was a patch (kbd-1.15.5-vlock-stdin-closed-inf-loop.patch) as part of kbd-1.15.5-16.el7_9.x86_64.rpm, but this was not applied to newer versions of the package.

Version-Release number of selected component (if applicable):
kbd-2.0.4-10.el8.x86_64.rpm

How reproducible:
See bug# 1486233

Steps to Reproduce:
start vlock and kill TTY session.

Actual results:
100% CPU usage

Expected results:
vlock to cancel lock after TTY is absent. not cause 100% cpu usage.

Additional info:

Comment 1 Timothy Mullican 2023-03-15 18:34:36 UTC
There is also a commit for KBD v2.0.90 (https://git.kernel.org/pub/scm/linux/kernel/git/legion/kbd.git/commit/?id=afb661b80441b6e3fa8cfa3b69f50e4805ebf8be) "Fix infinite loop of vlock if locked VC is closed", but the RHEL 8 KBD RPM uses v2.0.4.

Comment 2 Vitezslav Crhonek 2023-03-20 08:26:15 UTC
Thank you, reproduced.


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