Bug 1455596

Summary: RGW NFS: 2-byte overrun in state/incorrect alloc_state dispatch
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Matt Benjamin (redhat) <mbenjamin>
Component: RGWAssignee: Matt Benjamin (redhat) <mbenjamin>
Status: CLOSED ERRATA QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.2CC: cbodley, ceph-eng-bugs, hnallurv, kbader, mbenjamin, owasserm, sweil, tserlin
Target Milestone: rcKeywords: CodeChange
Target Release: 2.3   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: RHEL: nfs-ganesha-2.4.5-5.el7cp Ubuntu: nfs-ganesha_2.4.5-5redhat1xenial Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-19 13:33:40 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 Matt Benjamin (redhat) 2017-05-25 14:37:40 UTC 
Description of problem:
An incorrect allocation of object state tracking object in FSAL_RGW (nfs-ganesha RGW fs driver) leads to frequent, 2-byte overrun of the allocated object in several operations (e.g., rgw_setattr).

This may or may not be the root cause of a crash observed, once, in a heavy-mutation workload on a magna cluster.  It was obvserved trivially running RGW NFS under glibc AddressSanitizer.


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

How reproducible:
100%

Steps to Reproduce:
1. run RGW NFS with AddressSanitizer
2. run heavy-mutation Crefi workload, e.g.
 for i in {create,rename,chmod,chown,truncate}; do ./crefi.py --fop $i --multi -b 10 -d 50 -n 50 -t text --random --min=1k --max=10k /hello/nfs/; done

Actual results:
ASAN stop

Expected results:
no stop
Comment 9 errata-xmlrpc 2017-06-19 13:33:40 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, 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-2017:1497