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.
Created attachment 995330[details]
Full Backtrace
Description of problem:
The following segfault happen in rpc.gssd when Red Hat Storage
server (aka the ganesha server)
#0 memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:2588
#0 0x00007fb790aba8e3 in memmove (__len=103, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string3.h:57
#2 xdrmem_putbytes (xdrs=0x7fff5aa23880, addr=<optimized out>, len=103) at xdr_mem.c:145
#3 0x00007fb790ab9fda in gssrpc_xdr_opaque (xdrs=0x7fff5aa23880, cp=<optimized out>, cnt=<optimized out>)
at xdr.c:414
The full back trace is attached.
Version-Release number of selected component (if applicable):
gssproxy-0.3.0-10.el7
How reproducible:
100%
Steps to Reproduce:
1. start rpc.gssd with a valid keytab
2. mount the Red Hat storage server.
3.
Additional info:
The problem occurs because the rhel7 client is trying to
set up a GSS context with the server. Security is not
enabled on the server so the request is failed with
an AUTH_ERROR error.
to get the attached back trace I did the following:
Restart rpc.gssd
systemctl restart rpc-gssd
Attached to the runnning process
gdb -p $(pidof rpc.gssd)
Set the following gdb things
set follow-fork-mode child # gdb will follow the forked child
handle SIG37 nostop # gdb will ignore SIG 37
c # continue
In another window
mount ganesha-server:/export /mnt
Created attachment 995848[details]
Fix for the double-free bug
Steve,
the attached patch is a more complete version of the scratch build you tested today, and it is the one sent upstream.
For reference.
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://rhn.redhat.com/errata/RHBA-2015-2298.html
Created attachment 995330 [details] Full Backtrace Description of problem: The following segfault happen in rpc.gssd when Red Hat Storage server (aka the ganesha server) #0 memmove_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:2588 #0 0x00007fb790aba8e3 in memmove (__len=103, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string3.h:57 #2 xdrmem_putbytes (xdrs=0x7fff5aa23880, addr=<optimized out>, len=103) at xdr_mem.c:145 #3 0x00007fb790ab9fda in gssrpc_xdr_opaque (xdrs=0x7fff5aa23880, cp=<optimized out>, cnt=<optimized out>) at xdr.c:414 The full back trace is attached. Version-Release number of selected component (if applicable): gssproxy-0.3.0-10.el7 How reproducible: 100% Steps to Reproduce: 1. start rpc.gssd with a valid keytab 2. mount the Red Hat storage server. 3. Additional info: The problem occurs because the rhel7 client is trying to set up a GSS context with the server. Security is not enabled on the server so the request is failed with an AUTH_ERROR error.