Red Hat Bugzilla – Bug 229349
[GFS2] NFS fix - gfs2_drevalidate panic
Last modified: 2007-11-30 17:07:42 EST
Description of problem:
Glock assertion failure found in '07 NFS connectathon. One of the NFSDs was
doing a "readdirplus" procedure call. It passed the logic into gfs2_readdir
where the call obtained its directory inode glock. It then subsequently
tried to construct the filehandle based on the contents of the directory
lising that invoked lookup and comes down to gfs2_drevalidate(). It hit
the assertion failure while trying obtain the inode glock again.
Version-Release number of selected component (if applicable):
Each time and every time
Steps to Reproduce:
* Run cthon04 test suite
Patch had submitted to cluster-devel and has been in Linux tree since
sometime after Feb. 12.
In Steve's git on: 02/06/07.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Devel ACK for 5.1 - Would like to get the patch incorporated into an early 5.1
cycle kernel build.
This request was evaluated by Red Hat Kernel Team for inclusion in a Red
Hat Enterprise Linux maintenance release, and has moved to bugzilla
Confirmed the fix is in, and I hit what looked like this panic with the GA
kernel just by having a nfs exported gfs2 mounted using nfsv3 and trying to do
an ls of the directory.
nfs3 mounts when the system hosting the gfs2 fs is running the -45 kernel seems
to work fine.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.