Skip to contentSkip to conversation

Fix FATAL ERROR when FS_specific attribute is missing or empty in VFS config (#8)

nfs-ganesha Boaz Harrosh 1 participant 1 message Jan 24, 2013 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): nfs-ganesha/nfs-ganesha/pull/[email protected]

#1 lore raw

I have a fix for this in my tree, for next push

Quoted 3 lines · amitd

This happened in Release build due to uninitialized variable ret in fs_specific_has()

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------!

---

Quoted 26 lines

You can merge this Pull Request by running

git pull https://github.com/amitd/nfs-ganesha fix_fs_specific_has

Or view, comment on, or merge it at:

https://github.com/nfs-ganesha/nfs-ganesha/pull/8

Commit Summary

* In fs_specific_has(), properly initialize ret

File Changes

* *M* src/FSAL/FSAL_VFS/export.c (3)

Patch Links:

* https://github.com/nfs-ganesha/nfs-ganesha/pull/8.patch
* https://github.com/nfs-ganesha/nfs-ganesha/pull/8.diff