Skip to content

meta-nilrt: worldwritable permissions#965

Draft
Nasrulla-NI wants to merge 1 commit intoni:nilrt/master/nextfrom
Nasrulla-NI:worldwritable
Draft

meta-nilrt: worldwritable permissions#965
Nasrulla-NI wants to merge 1 commit intoni:nilrt/master/nextfrom
Nasrulla-NI:worldwritable

Conversation

@Nasrulla-NI
Copy link
Copy Markdown

@Nasrulla-NI Nasrulla-NI commented Mar 9, 2026

Summary of Changes

Currently NILRT will automatically mount block and TTY devices as world-writable and should be updated to no longer do this.
We should try to avoid just changing the permissions and should instead have some way to toggle the world-writable permissions back on if needed. Hence to do this - /etc/natinst/share/ni-rt.ini - worldwritable.enabled="true" or worldwritable.enabled="false" is appended as per information provided from hardware config team/

  • Controls whether VFAT/TTY mounts are world-writable.
  • 0 = default restrictive (fmask=0002,dmask=0002)
  • 1 = world-writable (fmask=0000,dmask=0000)
  • Reads /** /etc/natinst/share/ni-rt.ini - worldwritable.enabled="true" or worldwritable.enabled="false" **

Justification

Please refer below feature
https://dev.azure.com/ni/DevCentral/_workitems/edit/3470239

Testing

VFAT and TTY:
- worldwritable.enabled="false"
worldwritable enabled_false

worldwritable.enabled="true"
worldwritable enabled_true

  • I have built the core package feed with this PR in place. (bitbake packagefeed-ni-core)

Procedure

@Nasrulla-NI Nasrulla-NI force-pushed the worldwritable branch 2 times, most recently from b979e99 to 4b7192e Compare March 9, 2026 09:39
Signed-off-by: Nasrulla Shariff <nasrulla.shariff@emerson.com>

revert changes in target_common.ini

changes updated w.r.t Hardware Config
Copy link
Copy Markdown
Contributor

@amstewart amstewart left a comment

Choose a reason for hiding this comment

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

We should try to avoid just changing the permissions and should instead have some way to toggle the world-writable permissions back on if needed.

Why? Because of VISA? VISA has to run as a user that isn't root or a member of the dialout group?

@Nasrulla-NI
Copy link
Copy Markdown
Author

We should try to avoid just changing the permissions and should instead have some way to toggle the world-writable permissions back on if needed.

Why? Because of VISA? VISA has to run as a user that isn't root or a member of the dialout group?

Thanks for the comment. Indeed, the change was aimed at supporting VISA, since it often runs as a non‑root user without dialout membership and needs access to these device nodes. So, added a config/feature flag so the relaxed permissions are enabled only when needed. This will be controlled from front end Hwconfig.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants