Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2161133

Summary: whatis command causes crash to coredump
Product: Red Hat Enterprise Linux 8 Reporter: Frank Sorenson <fsorenso>
Component: crashAssignee: lijiang
Status: CLOSED ERRATA QA Contact: xiaoying yan <yiyan>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.5CC: jieli, lijiang, xiawu
Target Milestone: rcKeywords: Patch, Triaged
Target Release: 8.9Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: crash-7.3.2-6.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-14 15:31:46 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 Frank Sorenson 2023-01-16 04:49:25 UTC
Description of problem:

The 'whatis' command causes crash to coredump

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

crash-7.3.2-4.el8.x86_64


How reproducible:

  very easy


Steps to Reproduce:

use 'whatis', or type the name of some struct:

for example:
  crash> whatis dentry
or
  crash> kernfs_node
or:
  crash> dentry


Actual results:

  crash> kernfs_node
  *** stack smashing detected ***: <unknown> terminated
  Aborted (core dumped)


Expected results:

no coredump, crash shows 


Additional info:
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007f4fb5ea9cf5 in __GI_abort () at abort.c:79
#2  0x00007f4fb5f02c17 in __libc_message (action=<optimized out>, fmt=fmt@entry=0x7f4fb600f4fa "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:181
#3  0x00007f4fb5f95b65 in __GI___fortify_fail_abort (need_backtrace=need_backtrace@entry=false, msg=msg@entry=0x7f4fb600f4d8 "stack smashing detected") at fortify_fail.c:28
#4  0x00007f4fb5f95b18 in __stack_chk_fail () at stack_chk_fail.c:29
#5  0x0000555c7402bb0c in value_rtti_type (v=0x555c7a588f60, full=0x1, top=0x555c76a0f0c0, using_enc=0x7ffe5b5c8d46) at cp-abi.c:122
#6  0x0000555c7400370f in whatis_exp (exp=0x555c7bcfc6c0 "P\307\317{\\U", show=1) at typeprint.c:453
#7  0x0000555c74019dbd in execute_command (p=<optimized out>, from_tty=1) at top.c:484
#8  0x0000555c73f29528 in gdb_command_funnel (req=req@entry=0x555c7485db20 <shared_bufs>) at symtab.c:5184
#9  0x0000555c73d76627 in gdb_interface (req=req@entry=0x555c7485db20 <shared_bufs>) at gdb_interface.c:397
#10 0x0000555c73d76de6 in gdb_pass_through (cmd=cmd@entry=0x7ffe5b5c8d40 "ptype dentry", fptr=fptr@entry=0x555c7b6e05c0, flags=flags@entry=0) at gdb_interface.c:332
#11 0x0000555c73daee81 in whatis_datatype (st=0x555c74608a67 <program_context+231> "dentry", flags=<optimized out>, flags@entry=2048, ofp=0x555c7b6e05c0) at symbols.c:7836
#12 0x0000555c73dbb934 in do_datatype_declaration (dm=dm@entry=0x7ffe5b5caee0, flags=2048) at symbols.c:6842
#13 0x0000555c73dbd95a in cmd_whatis () at symbols.c:7235
#14 0x0000555c73cd27bd in exec_command () at main.c:892
#15 0x0000555c73cd2a0a in main_loop () at main.c:839
#16 0x0000555c73f587f7 in captured_command_loop (data=data@entry=0x0) at main.c:258
#17 0x0000555c73f5726a in catch_errors (func=func@entry=0x555c73f587e0 <captured_command_loop at main.c:253>, func_args=func_args@entry=0x0, 
    errstring=errstring@entry=0x555c741c5eb9 "", mask=mask@entry=6) at exceptions.c:557
#18 0x0000555c73f59946 in captured_main (data=data@entry=0x7ffe5b5cbec0) at main.c:1064
#19 0x0000555c73f5726a in catch_errors (func=func@entry=0x555c73f58b10 <captured_main at main.c:302>, func_args=func_args@entry=0x7ffe5b5cbec0, 
    errstring=errstring@entry=0x555c741c5eb9 "", mask=mask@entry=6) at exceptions.c:557
#20 0x0000555c73f59cc4 in gdb_main (args=0x7ffe5b5cbec0) at main.c:1079
#21 gdb_main_entry (argc=<optimized out>, argv=<optimized out>) at main.c:1099
#22 0x0000555c73cd0e94 in main (argc=3, argv=0x7ffe5b5cc048) at main.c:720

Comment 22 errata-xmlrpc 2023-11-14 15:31:46 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 (crash bug fix and enhancement update), 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-2023:6947