Bug 1743235

Summary:	journalctl dumps core when stack limit is reduced to 256 KB
Product:	Red Hat Enterprise Linux 8	Reporter:	Renaud Métrich <rmetrich>
Component:	systemd	Assignee:	Jan Synacek <jsynacek>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	low	Docs Contact:
Priority:	low
Version:	8.2	CC:	dvolkov, jsynacek, systemd-maint-list
Target Milestone:	rc
Target Release:	8.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	systemd-239-19.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 16:45:02 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:

Description Renaud Métrich 2019-08-19 12:28:52 UTC

This bug was initially created as a copy of Bug #1743230

I am copying this bug because: it also applies to RHEL8



Description of problem:

When reducing the stack limit for the user executing journalctl to 256KB, journalctl command dumps core:

$ ulimit -s 256
$ journalctl
Segmentation fault

This also affects RHEL8


Version-Release number of selected component (if applicable):

systemd-219, systemd-239 and upstream


How reproducible:

Always


Steps to Reproduce:
1. Create a user

# useradd user

2. Switch to user and set limit

# su - user
$ ulimit -s 256

3. Execute journalctl command

$ journalctl


Actual results:

Segmentation fault


Expected results:

"
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
No journal files were opened due to insufficient permissions.
"

Comment 1 Renaud Métrich 2019-09-16 10:20:23 UTC

Merged Upstream: https://github.com/systemd/systemd/commit/f5e0b942af1e86993c21f4e5c84342bb10403dac

Comment 2 Jan Synacek 2019-09-18 08:38:36 UTC

https://github.com/systemd-rhel/rhel-8/pull/23

Comment 6 errata-xmlrpc 2020-04-28 16:45:02 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-2020:1794