RTEMS | msdos: update inode during rename (!80)

[Loris Nardo (@loris.nardo)]

Loris Nardo commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/80#note_108760


For our use case #2169 is not important, even if it is not aligned with POSIX it still is a well defined behavior, it is just the reason why the test fails.

I've pushed a new commit where I've made some changes to the fstests, there are still two testcases missing both inside fsrenamelimits:
- One is related to `ENAMETOOLONG` which on some filesystem (RFS for instance) fails
- The other is related to `LINK_MAX` which fails on some filesystem
Should I make two separate tests?
Regarding the expected failures of the test cases I've placed the `set-test-state` inside `spec/build/bsps/tst.yml` is it the correct place?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/80#note_108760
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/20240706/2eaa04fb/attachment.htm>