Bug 1466700
Summary: | [Ganesha] : Ganesha crashed while running dbench during handle_digest | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ambarish <asoman> |
Component: | nfs-ganesha | Assignee: | Kaleb KEITHLEY <kkeithle> |
Status: | CLOSED WONTFIX | QA Contact: | Ambarish <asoman> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.3 | CC: | amukherj, asoman, bturner, dang, ffilz, jthottan, kkeithle, mbenjamin, rcyriac, rhinduja, rhs-bugs, skoduri, storage-qa-internal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-10 07:08: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
Ambarish
2017-06-30 09:38:28 UTC
So, I've looked this over, and have a few comments. 1. The core is inconsistent some way. The line it supposedly crashed on is not a statement that can cause a SEGFAULT in C (the line is if (!fh_desc) ) This means something's wrong. The debuginfo matches the binaries, so the only thing I can think of is that the binary doesn't match the core. But the binary is 8 days old. I also checked the one other thread doing anything, and it's source doesn't line up either (it's supposedly stopped on a brace) 2. The memory in both functions is all valid. It can all be read. This means, to me, that (1) is causing the location of the crash to be mis-reported, and it's actually crashing somewhere else. Since this is reproducible, can it be reproduced again with a new set of core files? Hopefully they'll match up better. For that core, I get this: warning: exec file is newer than core file. And there's no backtrace. Presumably the change to 2.4.4-8 broke the backtrace. Can you put the correct binaries back? That might fix the core. If not, you'll have to reproduce again. Note to self: This looks like maybe the subhandle was released while the entry was valid. Should not happen in >=2.5, due to chunked readdir. |