Bug 1492664 - kernel: Soft lockup in warn_alloc
Summary: kernel: Soft lockup in warn_alloc
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1492665
Blocks: 1492671
TreeView+ depends on / blocked
 
Reported: 2017-09-18 12:25 UTC by Adam Mariš
Modified: 2019-09-29 14:22 UTC (History)
49 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-03 00:36:17 UTC
Embargoed:


Attachments (Terms of Use)

Description Adam Mariš 2017-09-18 12:25:32 UTC
A soft lockup caused by running uncontrolled concurrent warn_alloc() calls when running LTP memcg_stress test was found.

Bug report:

https://www.spinics.net/lists/linux-mm/msg128248.html

Comment 1 Adam Mariš 2017-09-18 12:26:32 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1492665]

Comment 2 Wade Mealing 2017-10-03 00:35:52 UTC
Soft lockup during stress testing is very common.

This would fall under DOS at best, I'm not convinced that we should chase up all softlockups to their security case as these can be very, very common on misconfigured systems, or people misconfiguring during benchmarking / overloading.

I'd say we'd get 5-10 of these a week in support and I wouldn't have the bandwidth to chase them down.  In this case it seems the cgroup operations are being abused.

Comment 3 Tetsuo Handa 2017-11-16 05:39:08 UTC
This problem not only allows a local unprivileged user to intentionally lockup
the system but also allows some non stress test workload to by chance lockup.

This problem was addressed upstream as
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=400e22499dd92613821374c8c6c88c7225359980 .

Please be sure to backport to RHEL8 if using 4.9+ kernel.


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