Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

executor: linux: Android and gVisor are unable to mount tmpfs with sandbox=none #4972

Open
ramosian-glider opened this issue Jul 3, 2024 · 1 comment
Open

executor: linux: Android and gVisor are unable to mount tmpfs with sandbox=none #4972

ramosian-glider opened this issue Jul 3, 2024 · 1 comment
Labels
bug

Comments

@ramosian-glider
Copy link
Member

#4959 broke program execution on Android:

SYZFAIL: mount(tmpfs) failed
 (errno 28: No space left on device)
loop exited with status 67

and gVisor:

SYZFAIL: mount(proc) failed
 (errno 14: Bad address)
loop exited with status 67
@ramosian-glider
Copy link
Member Author

CC @eprucka3 @avagin @kalder

ramosian-glider added a commit to ramosian-glider/syzkaller that referenced this issue Jul 3, 2024
@ramosian-glider
executor: linux: temporarily disable tmpfs mounting on Android
4638c9f 
Commit 3160a12 ("executor: linux: chroot into tmpfs with sandbox=none")
broke some Android instances, which fail to mount tmpfs.
Disable it for the time being.

Tracking bug: google#4972
@ramosian-glider ramosian-glider mentioned this issue Jul 3, 2024
Merged
ramosian-glider added a commit to ramosian-glider/syzkaller that referenced this issue Jul 3, 2024
@ramosian-glider
executor: linux: bump fs.mount-max to 100000
88217ac 
Android sets fs.mount-max to 100, making it impossible to create new chroots.
Relax the limit, setting it to a value used on desktops.

Tracking bug: google#4972
ramosian-glider added a commit to ramosian-glider/syzkaller that referenced this issue Jul 3, 2024
@ramosian-glider
executor: linux: bump fs.mount-max to 100000
bae52ca 
Android sets fs.mount-max to 100, making it impossible to create new chroots.
Relax the limit, setting it to a value used on desktops.

Tracking bug: google#4972
ramosian-glider added a commit to ramosian-glider/syzkaller that referenced this issue Jul 3, 2024
@ramosian-glider
executor: linux: bump fs.mount-max to 100000
b1f458d 
Android sets fs.mount-max to 100, making it impossible to create new chroots.
Relax the limit, setting it to a value used on desktops.

Tracking bug: google#4972
github-merge-queue bot pushed a commit that referenced this issue Jul 3, 2024
@ramosian-glider @dvyukov
executor: linux: bump fs.mount-max to 100000
409d975 
Android sets fs.mount-max to 100, making it impossible to create new chroots.
Relax the limit, setting it to a value used on desktops.

Tracking bug: #4972
avagin pushed a commit to avagin/syzkaller that referenced this issue Jul 4, 2024
@ramosian-glider @avagin
executor: linux: bump fs.mount-max to 100000
f9b68e1 
Android sets fs.mount-max to 100, making it impossible to create new chroots.
Relax the limit, setting it to a value used on desktops.

Tracking bug: google#4972
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ramosian-glider