Changeset 1d66629 in rtems
- Timestamp:
- 10/24/02 18:54:07 (21 years ago)
- Branches:
- 4.10, 4.11, 4.8, 4.9, 5, master
- Children:
- 38ad1630
- Parents:
- bf61751c
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
cpukit/libcsupport/src/eval.c
rbf61751c r1d66629 61 61 if ( (result == 0) && follow_link ) { 62 62 63 if ( !pathloc->ops->node_type_h ) 63 if ( !pathloc->ops->node_type_h ){ 64 rtems_filesystem_freenode( pathloc ); 64 65 rtems_set_errno_and_return_minus_one( ENOTSUP ); 66 } 65 67 66 68 type = (*pathloc->ops->node_type_h)( pathloc ); … … 69 71 ( type == RTEMS_FILESYSTEM_SYM_LINK ) ) { 70 72 71 if ( !pathloc->ops->eval_link_h ) 73 if ( !pathloc->ops->eval_link_h ){ 74 rtems_filesystem_freenode( pathloc ); 72 75 rtems_set_errno_and_return_minus_one( ENOTSUP ); 76 } 73 77 74 result = (*pathloc->ops->eval_link_h)( pathloc, flags ); 78 /* what to do with the valid node pathloc points to 79 * if eval_link_h fails? 80 * Let the FS implementation deal with this case. It 81 * should probably free pathloc in either case: 82 * - if the link evaluation fails, it must free the 83 * original (valid) pathloc because we are going 84 * to return -1 and hence the FS generics won't 85 * cleanup pathloc. 86 * - if the link evaluation is successful, the updated 87 * pathloc will be passed up (and eventually released). 88 * Hence, the (valid) originial node that we submit to 89 * eval_link_h() should be released by the handler. 90 */ 91 92 result = (*pathloc->ops->eval_link_h)( pathloc, flags ); 75 93 76 94 }
Note: See TracChangeset
for help on using the changeset viewer.