You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(tldr: See 2 images, also attached IOS crash
report).
issue:
mounting tmpfs results in write only mode. (touch returns file name is too long within tmpfs).
Unmounting tmpfs will 100% result in a crash of the app.
abi level rm on a filedesc in tmpfs will crash the app. busybox rm will just report permission issue.(perhaps due to first checking permission before abi)?
basically tmpfs is unsuable.
IOS crash returns "Address Size Fault" .
Theories:
its the 'mount' syscall ( or 'mprotect' or suid bits called within mount param )
its the inode offsets of 32 bit (ISH-AOK) address, differing from the IOS kernel (64 bit) address.
It is due to the differing IOS and "linux"/ISH kernel paramaters of mount.
Executables safely alloc and free avail mem, so it must be mount paramaters.
it is due to the libmusl or busybox mount implimentation/param(related to suid bits).
Proposal:
making a block device driver in /dev/ to mount the tmpfs with mount params preset.
make every filedesc in tmpfs a buffered fifo.
Significance:
tmpfs will make some use cases 60-80% faster. (apt, fzf,tmux,etc...).
Maybe more rootfs distros can start init (related to tmpfs in fstab).
Let me know what you think and if you have any insight/leads to where to start to fix this issue.
Thank you,
ADDITION:
Another solution is to use mmap and specify a valid address(size and location) paramaters manually at the ISH-AOK Kernel when mount is invoked.
The text was updated successfully, but these errors were encountered:
(tldr: See 2 images, also attached IOS crash
report).
issue:
mounting tmpfs results in write only mode. (touch returns file name is too long within tmpfs).
Unmounting tmpfs will 100% result in a crash of the app.
abi level rm on a filedesc in tmpfs will crash the app. busybox rm will just report permission issue.(perhaps due to first checking permission before abi)?
basically tmpfs is unsuable.
IOS crash returns "Address Size Fault" .
Theories:
its the 'mount' syscall ( or 'mprotect' or suid bits called within mount param )
its the inode offsets of 32 bit (ISH-AOK) address, differing from the IOS kernel (64 bit) address.
It is due to the differing IOS and "linux"/ISH kernel paramaters of mount.
Executables safely alloc and free avail mem, so it must be mount paramaters.
it is due to the libmusl or busybox mount implimentation/param(related to suid bits).
Proposal:
Significance:
tmpfs will make some use cases 60-80% faster. (apt, fzf,tmux,etc...).
Maybe more rootfs distros can start init (related to tmpfs in fstab).
Let me know what you think and if you have any insight/leads to where to start to fix this issue.
Thank you,
ADDITION:
Another solution is to use mmap and specify a valid address(size and location) paramaters manually at the ISH-AOK Kernel when mount is invoked.
The text was updated successfully, but these errors were encountered: