sysfs: Add block and char subdirectories under /sys/dev#12813
Merged
copybara-service[bot] merged 1 commit intogoogle:masterfrom Apr 3, 2026
Merged
sysfs: Add block and char subdirectories under /sys/dev#12813copybara-service[bot] merged 1 commit intogoogle:masterfrom
copybara-service[bot] merged 1 commit intogoogle:masterfrom
Conversation
gVisor does not expose real block/char devices, the directories remain empty, but their existence is required for compatibility. Tools like lsblk expect /sys/dev/block/ to exist in order to enumerate block devices. Currently, gVisor's sysfs creates /sys/dev/ as an empty directory without the standard block/ and char/ children, causing lsblk to fail with ENOENT. Signed-off-by: Tan Yifeng <yiftan@tencent.com>
tanyifeng
force-pushed
the
add-dev-block-char
branch
from
7c0be65 to
7b59546
Compare
ayushr2
approved these changes
Apr 2, 2026
copybara-service Bot
pushed a commit
that referenced
this pull request
Apr 2, 2026
gVisor does not expose real block/char devices, the directories remain empty, but their existence is required for compatibility. Tools like lsblk expect /sys/dev/block/ to exist in order to enumerate block devices. Currently, gVisor's sysfs creates /sys/dev/ as an empty directory without the standard block/ and char/ children, causing lsblk to fail with ENOENT. FUTURE_COPYBARA_INTEGRATE_REVIEW=#12813 from tanyifeng:add-dev-block-char 7b59546 PiperOrigin-RevId: 893658362
copybara-service Bot
pushed a commit
that referenced
this pull request
Apr 3, 2026
gVisor does not expose real block/char devices, the directories remain empty, but their existence is required for compatibility. Tools like lsblk expect /sys/dev/block/ to exist in order to enumerate block devices. Currently, gVisor's sysfs creates /sys/dev/ as an empty directory without the standard block/ and char/ children, causing lsblk to fail with ENOENT. FUTURE_COPYBARA_INTEGRATE_REVIEW=#12813 from tanyifeng:add-dev-block-char 7b59546 PiperOrigin-RevId: 893658362
copybara-service Bot
pushed a commit
that referenced
this pull request
Apr 3, 2026
gVisor does not expose real block/char devices, the directories remain empty, but their existence is required for compatibility. Tools like lsblk expect /sys/dev/block/ to exist in order to enumerate block devices. Currently, gVisor's sysfs creates /sys/dev/ as an empty directory without the standard block/ and char/ children, causing lsblk to fail with ENOENT. FUTURE_COPYBARA_INTEGRATE_REVIEW=#12813 from tanyifeng:add-dev-block-char 7b59546 PiperOrigin-RevId: 893658362
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
2 participants
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.
gVisor does not expose real block/char devices, the directories remain empty, but their existence is required for compatibility.
Tools like lsblk expect /sys/dev/block/ to exist in order to enumerate block devices. Currently, gVisor's sysfs creates /sys/dev/ as an empty directory without the standard block/ and char/ children, causing lsblk to fail with ENOENT.