Bug 2218620 - glibc: segmentation fault with char array of large sizes [NEEDINFO]
Summary: glibc: segmentation fault with char array of large sizes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: glibc
Version: 8.8
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: glibc team
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-29 17:00 UTC by Tim Zielke
Modified: 2023-07-14 13:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-14 13:29:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:
fweimer: needinfo? (cww)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-161195 0 None None None 2023-06-29 17:01:32 UTC

Description Tim Zielke 2023-06-29 17:00:28 UTC
Description of problem:

I had a C executable that was using a char array of a size around 104857600. For example,

#define BUFFERMAX 104857600
   char     buffer[BUFFERMAX+1];   /* message buffer                */

The C executable ran fine on RHEL 7 Linux x86_64 machines. However, when we ported over to a RHEL 8 server, the program would just throw a "segmentation fault" when you tried to execute it. I recompiled the program with a lower value for the BUFFERMAX (i.e. 4194304), and now it runs fine on RHEL 8. I am fine with this workaround, but wanted to report the potential bug here for RHEL 8.

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

Issue happened on the following:

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.8
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.8"
Red Hat Enterprise Linux release 8.8 (Ootpa)


How reproducible:

Write a C program that has char array of around 104857600. See if it can run on both RHEL 7 and RHEL 8.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Carlos O'Donell 2023-06-30 13:24:46 UTC
If you are a Red Hat customer with an active subscription, please visit the Red Hat Customer Portal [1] for assistance with your issue.

[1] http://access.redhat.com/

Comment 5 Carlos O'Donell 2023-07-14 13:29:19 UTC
I'm marking this CLOSED/NOTABUG because there doesn't seem to be any direct issue with glibc, but rather a `ulimit -d` issue.

If you are a Red Hat customer with an active subscription, please reach out to your support representative.


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