RTEMS | cpukit/libio: error ENAMETOOLONG when a path compenent is larger than NAME_MAX (!1095)

[Prashant Rahul (@prashantrahul141)]

Prashant Rahul commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1095#note_144854


Are you reffering to the link in [cpukit/libcsupport/src/link.c](https://gitlab.rtems.org/rtems/rtos/rtems/-/blob/main/cpukit/libcsupport/src/link.c)? It uses `rtems_filesystem_eval_path_start` to evaluate path, which internally calls `rtems_filesystem_eval_path_start_with_root_and_current` which then calls `rtems_filesystem_eval_path_continue` where I have added the check, so link shouldnt have this problem, no?

There exists a test case for this in [testsuites/fstests/fsrenamelongname/test.c](https://gitlab.rtems.org/rtems/rtos/rtems/-/blob/main/testsuites/fstests/fsrenamelongname/test.c), should I add more tests for this case in others too? because it is kind of redundant since all the filesystem path evaluation uses the same 2 functions where I have added the length check.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1095#note_144854
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260309/a7aac239/attachment.htm>