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

Tue Mar 10 04:40:35 UTC 2026

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

I understand what youre saying, but doesnt every function that has to do any operation to any file or directory has to go through rtems' file system api? There are exactly two ways you can take to evaulate path, `rtems_filesystem_eval_path_continue` and `rtems_filesystem_eval_path_recursive` and I have implemented the length check in both of them.

And I agree with adding tests for the case of `ENAMETOOLONG` in other functions as well

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1095#note_144934
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/20260310/1f04d4f4/attachment-0001.htm>