Bug 1992331 - [GSS] [rhel8] SIGSEGV crash after upgrade to RHGS 3.5.4
Summary: [GSS] [rhel8] SIGSEGV crash after upgrade to RHGS 3.5.4
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: nfs-ganesha
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 3.5.z Batch Update 7
Assignee: Kaleb KEITHLEY
QA Contact: Sri Vignesh Selvan
URL:
Whiteboard: 3.5.5
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-10 21:42 UTC by Kaleb KEITHLEY
Modified: 2024-12-20 20:39 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, when a program tried to dereference a null pointer an uncommon condition occurred. It received multiple lock requests where some requests were blocked as the client info from the NLM subsys that required building a lease_id was not present. With this update, the client information from the NLM subsys is provided when possible.
Clone Of: 1959129
: 1995674 (view as bug list)
Environment:
Last Closed: 2021-10-05 07:57:33 UTC
Embargoed:
bcotton: needinfo+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:3727 0 None None None 2021-10-05 07:57:47 UTC

Comment 13 Kaleb KEITHLEY 2021-08-30 12:16:44 UTC 
revised doc text looks fine.
Comment 16 errata-xmlrpc 2021-10-05 07:57:33 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 (nfs-ganesha bug fix 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-2021:3727
Comment 17 Ben Cotton 2022-02-14 21:36:55 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 18 Ben Cotton 2022-02-14 21:40:47 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 19 Ben Cotton 2022-02-14 21:41:28 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 20 Ben Cotton 2022-02-14 21:43:44 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 21 Ben Cotton 2022-02-14 21:45:04 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 22 Ben Cotton 2022-02-14 21:48:10 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 23 Ben Cotton 2022-02-14 21:49:08 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 24 Ben Cotton 2022-02-14 21:51:30 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 25 Ben Cotton 2022-02-14 21:52:16 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 26 Ben Cotton 2022-02-14 22:00:06 UTC 
We have reached the 'Change complete (Testable) deadline in the Fedora Linux 36 release schedule. At this time, all Changes should be complete enough to be testable. Indicate this by setting this tracking bug to MODIFIED. If the code for this Change is fully complete, you can set the status to ON_QA. The next milestone is the Change complete (100% complete) deadline on 2022-02-22
Comment 27 Ben Cotton 2022-02-14 22:01:46 UTC 
Sorry for the noise, I meant to be testing this against the staging server but forgot to update. Please ignore me.
Note You need to log in before you can comment on or make changes to this bug.