vfs: skip write tracking for special files on open - #13149
Merged
copybara-service[bot] merged 1 commit intoAug 5, 2026
Conversation
shayonj
force-pushed
the
fix-special-file-rofs
branch
from
July 16, 2026 11:22
1b1760c to
7d4179f
Compare
Contributor
Author
|
👋🏾 @nixprime - curious if you had any feedback 🙏🏾 |
Collaborator
|
Need a Googler to pull this in. |
milantracy
approved these changes
Jul 23, 2026
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 23, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 7d4179f PiperOrigin-RevId: 952841897
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 23, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 7d4179f PiperOrigin-RevId: 952841897
Collaborator
|
there are some test failures at https://buildkite.com/gvisor/pipeline/builds/44757 do you want to take a look? |
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. Mark the remaining FileDescriptions backed by special-file inodes. Also skip overlay copy-up for writable opens of special files; Linux overlayfs applies the same special_file() exception before deciding whether copy-up is required. Add regression coverage for character devices and FIFOs through read-only bind mounts.
shayonj
force-pushed
the
fix-special-file-rofs
branch
from
July 28, 2026 10:48
7d4179f to
87673b0
Compare
Contributor
Author
|
thank you! just pushed the fix |
milantracy
approved these changes
Jul 28, 2026
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 952841897
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 952841897
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 952841897
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 952841897
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 952841897
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 952841897
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 952841897
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 952841897
copybara-service Bot
pushed a commit
that referenced
this pull request
Jul 28, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 952841897
Collaborator
|
I made a tiny patch to your PR that fixes some test failure i see internally you can see the diff as follows,
|
Contributor
Author
|
Thanks for catching this. I missed that my special file shortcut bypassed the existing check for lower layer files that aren't be copied up. For future - do you know why it didn't fail in the CI on this branch? |
Collaborator
|
the CI on buildkite doens't have any test coverage for the edge cases. I created #13998, PRs are welcome if you are interesetd |
copybara-service Bot
pushed a commit
that referenced
this pull request
Aug 5, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 959292441
copybara-service Bot
pushed a commit
that referenced
this pull request
Aug 5, 2026
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc. This adds an `IsSpecialFile` option on `FileDescription`, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate. Fixes: #13148 FUTURE_COPYBARA_INTEGRATE_REVIEW=#13149 from shayonj:fix-special-file-rofs 87673b0 PiperOrigin-RevId: 959292441
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linux skips the mount-level write check when opening a character device, block device, FIFO, or socket, so write-opening /dev/null on a read-only bind mount succeeds. gVisor was running that check unconditionally and returning EROFS, which breaks buildah's mount-bind-then-RO-remount hardening pattern when used under runsc.
This adds an
IsSpecialFileoption onFileDescription, paired across the open and close paths so the writer counter stays balanced, and set it on every open path that backs a special-file inode. The socket and host-imported FDs live on internal disconnected mounts that are never remounted RO, so flagging them is a no-op today and exists for parity with the kernel's predicate.Fixes: #13148