diff options
author | Mark Fasheh <mark.fasheh@oracle.com> | 2007-11-07 16:35:14 -0800 |
---|---|---|
committer | Mark Fasheh <mark.fasheh@oracle.com> | 2007-11-27 16:47:02 -0800 |
commit | bccb9dad8949cd0df1d3d2188a1fdb4b1936d537 (patch) | |
tree | 93301cb788cdda02acf46f0222e09ed4be504207 /fs/ocfs2/aops.c | |
parent | 5a58c3ef22d6e5b84ff651a7d27ae2cbea9f9870 (diff) | |
download | kernel_samsung_aries-bccb9dad8949cd0df1d3d2188a1fdb4b1936d537.zip kernel_samsung_aries-bccb9dad8949cd0df1d3d2188a1fdb4b1936d537.tar.gz kernel_samsung_aries-bccb9dad8949cd0df1d3d2188a1fdb4b1936d537.tar.bz2 |
ocfs2: Remove bug statement in ocfs2_dentry_iput()
The existing bug statement didn't take into account unhashed dentries which
might not have a cluster lock on them. This could happen if a node exporting
the file system via NFS is rebooted, re-exported to nfs clients and then
unmounted. It's fine in this case to not have a dentry cluster lock.
Just remove the bug statement and replace it with an error print, which
does the proper checks. Though we want to know if something has happened
which might have prevented a cluster lock from being created, it's
definitely not necessary to panic the machine for this.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
Diffstat (limited to 'fs/ocfs2/aops.c')
0 files changed, 0 insertions, 0 deletions