Bug 1699264

Summary:	Free output is wrong
Product:	Red Hat Enterprise Linux 7	Reporter:	Josef Ridky <jridky>
Component:	procps-ng	Assignee:	Jan Rybar <jrybar>
Status:	CLOSED ERRATA	QA Contact:	Karel Volný <kvolny>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	kvolny
Target Milestone:	rc	Keywords:	EasyFix, Patch, Upstream
Target Release:	7.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	procps-ng-3.3.10-26.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-06 13:03:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1250060

Description Josef Ridky 2019-04-12 09:27:59 UTC

Description of problem:

Output of free utility for Memory used is wrong.
Now, the value is decreased by integer from /proc/meminfo -> Slab, but based on upstream version, it should be decreased only by integer from /proc/meminfo -> SReclaimable.

Version-Release number of selected component (if applicable):
procps-ng-3.3.10-23.el7

How reproducible:
$ free 

Actual results:
Mem used is computed without SUnreclaim.

Expected results:
Mem used should contain value from SUnreclaim

Additional info:
This bug is blocking #1250060 (net-snmp)

Comment 1 Jan Rybar 2019-04-12 11:20:57 UTC

Unreclaimable slabs shouldn't be counted in available memory.
Josef, thanks for the catch!

Upstream fix:
https://gitlab.com/procps-ng/procps/commit/05d751c4f076a2f0118b914c5e51cfbb4762ad8e

Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799716

Comment 6 errata-xmlrpc 2019-08-06 13:03:38 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:2189