Linux sandbox: ignore ENODEV when making the filesystem read-only. #16172
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.
The code remounting existing mounts as read-only already ignores various
errors, such as
EINVAL
,ESTALE
etc.Unfortunately, it doesn't ignore
ENODEV
, which can occur in case ofautofs
/automount
failure.Currently, having a single broken automount on the host can cause all
sandboxes to fail with the following error:
So simply also add
ENODEV
to the list of errors ignored.