Skip to content

Conversation

@ycsin
Copy link
Member

@ycsin ycsin commented Nov 16, 2024

Update the notes for POSIX_FILE_SYSTEM_R, looks like I missed the v4 release

@zephyrbot zephyrbot added Release Notes To be mentioned in the release notes area: POSIX POSIX API Library labels Nov 16, 2024
Add section for POSIX_FILE_SYSTEM_R which contains only `readdir_r()`.

Signed-off-by: Yong Cong Sin <[email protected]>
@ycsin ycsin force-pushed the pr/posix-readdir_r branch from afe04b6 to eacdd8f Compare November 16, 2024 05:48
@kartben
Copy link
Contributor

kartben commented Nov 16, 2024

Ya unfortunately it's too late. You may maybe submit a PR against the branch but I never remember if it's something we do or if submissions have to be handled as backports

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is maybe Ok for a backport PR to v4.0.

However, looking into things a bit deeper, getpwnam_r(), getpwuid_r(), getgrgid_r(), and getgrnam_r() belong to a separate Option Group -
POSIX_SYSTEM_DATABASE_R. And the non-reentrant versions of these belong to the POSIX_SYSTEM_DATABASE Option Group, and _POSIX_THREAD_SAFE_FUNCTIONS is more of an Option / Feature Test Macro.

So really what we need here is a new Kconfig.system_database file with two new Kconfig options (same as the option group names).

_POSIX_THREAD_SAFE_FUNCTIONS should probably be a hidden Kconfig option that depends on other Kconfig values being enabled. Namely, CONFIG_POSIX_SYSTEM_DATABASE_R, CONFIG_POSIX_C_LANG_SUPPORT_R, CONFIG_POSIX_FILE_LOCKING, CONFIG_POSIX_FILE_SYSTEM_R.

And then of course modify the docs

https://pubs.opengroup.org/onlinepubs/9799919799/xrat/V4_subprofiles.html

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of the above should be in a separate PR.

@dkalowsk dkalowsk added this to the v4.1.0 milestone Nov 16, 2024
@dkalowsk
Copy link
Contributor

Very much missed the release. Happy to add to the 4.0.1 backport list though!

@mmahadevan108
Copy link
Contributor

@ycsin . Do you think you can move the changes from the 4.0 release notes to 4.1 release notes?

@ycsin
Copy link
Member Author

ycsin commented Nov 19, 2024

@ycsin . Do you think you can move the changes from the 4.0 release notes to 4.1 release notes?

Should we? The changes were introduced in 4.0, not 4.1.

@ycsin ycsin force-pushed the pr/posix-readdir_r branch from eacdd8f to 352f9e6 Compare November 19, 2024 03:18
@ycsin ycsin changed the title doc: posix: update for POSIX_FILE_SYSTEM_R doc: posix: option_groups: add section for POSIX_FILE_SYSTEM_R Nov 19, 2024
@ycsin ycsin changed the title doc: posix: option_groups: add section for POSIX_FILE_SYSTEM_R doc: posix: update for POSIX_FILE_SYSTEM_R Nov 19, 2024
Mention the `_POSIX_THREAD_SAFE_FUNCTIONS` functions implemented in
zephyrproject-rtos#74394.

Signed-off-by: Yong Cong Sin <[email protected]>
@kartben
Copy link
Contributor

kartben commented Nov 19, 2024

@ycsin . Do you think you can move the changes from the 4.0 release notes to 4.1 release notes?

Should we? The changes were introduced in 4.0, not 4.1.

Yes but it's already been released, so by definition there's no way the release notes can be updated after the fact. They're already there and won't change: https://docs.zephyrproject.org/4.0.0/releases/release-notes-4.0.html
Updating the document in main would not be a good solution as we don't want to have discrepancies with the published release notes from the previous link (and released artifacts on GitHub)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See previous comment

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#76401 hmm...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, we discussed setting up some kind of CI check to catch these.

@ycsin ycsin closed this Nov 19, 2024
@ycsin
Copy link
Member Author

ycsin commented Nov 19, 2024

I think I confused GitHub to the point that it won't reflect the changes of the PR branch anymore, recreated a PR without changes to the 4.0 release notes #81553

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: POSIX POSIX API Library Release Notes To be mentioned in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants