Bug 479374 - statd fails to create SM_DIR
Summary: statd fails to create SM_DIR
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: nfs-utils
Version: 5.2
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Martin Jenner
URL: https://bug.oraclecorp.com/pls/bug/we...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-09 05:55 UTC by Wengang Wang
Modified: 2011-10-13 06:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-17 19:31:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
patch which fixes the bug (466 bytes, patch)
2009-01-09 05:55 UTC, Wengang Wang
no flags Details | Diff

Description Wengang Wang 2009-01-09 05:55:02 UTC
Created attachment 328520 [details]
patch which fixes the bug

service nfslock start may fail when /var/lib/nfs/statd/sm doesn't exist.
that's because of opendir() against /var/lib/nfs/statd/sm fails. root reason is the directory is not created if it doesn't exist.
this problem exist in both RHEL5 and RHEL4

according code in shuffle_dirs(), since st is not initailized, whether
the SM_DIR is created depends on the thread stack of rpc.statd.
the fix is to insert a memset() before calling stat().

attached patch(based on nfs-utils 1.0.9) fixes this problem.
please include this patch for next release.

Comment 2 Karel Volný 2009-03-20 11:03:51 UTC
Can anyone please add info how this bug can be reproduced? - I was unable to do so, in all my tries the directory got re-created on nfslock startup ...

Comment 4 RHEL Program Management 2009-04-29 20:25:27 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 5 Wengang Wang 2009-05-19 02:25:17 UTC
please include it in the next release.
the same fix for EL4 is already included, see https://bugzilla.redhat.com/show_bug.cgi?id=479376


Note You need to log in before you can comment on or make changes to this bug.