RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2122599 - podman kill may deadlock
Summary: podman kill may deadlock
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Tom Sweeney
QA Contact: Alex Jia
URL:
Whiteboard:
Depends On:
Blocks: 2124716 2125647
TreeView+ depends on / blocked
 
Reported: 2022-08-30 11:22 UTC by Valentin Rothberg
Modified: 2023-03-24 07:47 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2124716 2125647 (view as bug list)
Environment:
Last Closed: 2023-03-24 07:47:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-132724 0 None None None 2022-08-30 11:47:59 UTC

Description Valentin Rothberg 2022-08-30 11:22:26 UTC 
Description of problem:

`podman kill` (Podman v4.2 only) can deadlock on low-performance machines or machines under extremely high load as reported upstream.

[1] https://github.com/containers/podman/issues/15492

Version-Release number of selected component (if applicable):
Podman v4.2.x

How reproducible:

I never managed to reproduce, neither did upstream CI or gating tests.  According to upstream report [1] it's easy to reproduce low-performance ARM machines.

Steps to Reproduce:
Kill a running container via `podman kill`.

Actual results:
Deadlock.

Expected results:
Container gets killed.

Additional info:
An upstream fix has already been merged: https://github.com/containers/podman/pull/15494
The fix is trivial as it's merely removing a number of lines.
Comment 1 Tom Sweeney 2022-09-06 22:00:13 UTC 
Can I get a dev and qa ack for zero day purposes please?
Comment 3 Tom Sweeney 2022-09-09 00:21:51 UTC 
@ypu can I get a qa ack on this please?
Comment 5 Alex Jia 2023-03-24 07:47:31 UTC 
This bug has been verified on podman-4.4.1-8.module+el8.8.0+18438+15d3aa65.
Note You need to log in before you can comment on or make changes to this bug.