google/gvisor

Failed to stop overwriting a running binary

Open

#1,005 opened on Oct 14, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (1,061 forks)batch import
area: compatibilityarea: filesystemgood first issuepriority: p2type: bug

Repository metrics

Stars
 (12,713 stars)
PR merge metrics
 (Avg merge 4d 22h) (184 merged PRs in 30d)

Description

runsc result:

$ stress -c 1 &
$ which stress
/usr/bin/stress
$ cp /bin/ls /usr/bin/stress
[1]+  Bus error               stress -c 1

Expected result in vanilla Linux:

$ stress -c 1 &
$ which stress
/usr/bin/stress
$ cp /bin/ls /usr/bin/stress
cp: cannot create regular file '/usr/bin/stress': Text file busy

Contributor guide

Research direction
Investigate how gVisor's virtual filesystem handles overwriting a running binary and why it does not produce 'Text file busy'. Compare with Linux kernel behavior.
Tech stack
go
Domain
backendoperating systems
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
LinuxgVisor
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40