Abhishekmishra2808 opened a new pull request, #18872:
URL: https://github.com/apache/nuttx/pull/18872

   Add a new CONFIG_FS_PERMISSION Kconfig symbol to group the configuration 
options required for future filesystem permission support.
   
   When enabled, this symbol selects:
   
   * CONFIG_SCHED_USER_IDENTITY
   * CONFIG_PSEUDOFS_ATTRIBUTES
   
   These provide the existing infrastructure for task credentials (uid/gid) and 
pseudo-filesystem inode ownership/mode metadata.
   
   The symbol defaults to n to preserve current behavior for existing 
configurations.
   
   No runtime permission enforcement is introduced by this commit. Only Kconfig 
integration is added.
   
   Part of GSoC https://github.com/apache/nuttx/issues/18458
   
   *Note: Please adhere to [Contributing 
Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).*
   
   ## Summary
   
   *Update this section with information on why change is necessary,
    what it exactly does and how, if new feature shows up, provide
    references (dependencies, similar problems and solutions), etc.*
   
   ## Impact
   
   *Update this section, where applicable, on how change affects users,
    build process, hardware, documentation, security, compatibility, etc.*
   
   ## Testing
   
   Build Succesful
   <img width="944" height="467" alt="WhatsApp Image 2026-05-12 at 8 21 08 PM" 
src="https://github.com/user-attachments/assets/85dc1e5b-36dd-4889-9590-c1ef8317861e";
 />
   
   ostest 
   <img width="940" height="420" alt="WhatsApp Image 2026-05-12 at 9 26 43 PM" 
src="https://github.com/user-attachments/assets/5918ea31-d60e-4340-a44c-6a30ffa04450";
 />
   
   ls -l (permission bits)
   <img width="258" height="157" alt="WhatsApp Image 2026-05-12 at 10 42 59 PM" 
src="https://github.com/user-attachments/assets/5218261c-b7a0-4b03-a0da-5f1a9ba9611f";
 />
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to