Bug 1743230

Summary: journalctl dumps core when stack limit is reduced to 256 KB
Product: Red Hat Enterprise Linux 7 Reporter: Renaud Métrich <rmetrich>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Frantisek Sumsal <fsumsal>
Severity: low Docs Contact:
Priority: low    
Version: 7.6CC: dvolkov, jsynacek, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-219-72.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-31 20:02:28 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:23:08 UTC
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 8 Lukáš Nykrýn 2019-10-21 14:18:17 UTC
fix merged to github master branch -> https://github.com/systemd-rhel/rhel-7/pull/43 -> post

Comment 9 Lukáš Nykrýn 2019-10-21 14:21:51 UTC
fix merged to github master branch -> https://github.com/systemd-rhel/rhel-8/pull/23 -> post

Comment 15 errata-xmlrpc 2020-03-31 20:02:28 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/RHBA-2020:1117