summaryrefslogtreecommitdiffhomepage
path: root/pkg/sentry/kernel
AgeCommit message (Collapse)Author
2019-08-20Merge cf8a689b (automated)gVisor bot
2019-08-19Merge 67d7864f (automated)gVisor bot
2019-08-16Merge f7114e0a (automated)gVisor bot
2019-08-16Merge 4bab7d7f (automated)gVisor bot
2019-08-15Merge ef045b91 (automated)gVisor bot
2019-08-14Merge d81d94ac (automated)gVisor bot
2019-08-14Merge 69d1414a (automated)gVisor bot
2019-08-14Merge cee044c2 (automated)gVisor bot
2019-08-13Merge 0e907c42 (automated)gVisor bot
2019-08-13Merge c386f046 (automated)gVisor bot
2019-08-13Merge 99bf75a6 (automated)gVisor bot
2019-08-13Merge 8d97b22a (automated)gVisor bot
2019-08-13Merge 691c2f81 (automated)gVisor bot
2019-08-12Merge eac690e3 (automated)gVisor bot
2019-08-10Merge af90e686 (automated)gVisor bot
2019-08-09Merge f2762e8c (automated)gVisor bot
2019-08-09Merge 69030811 (automated)gVisor bot
2019-08-08Merge 7bfad8eb (automated)gVisor bot
2019-08-08Merge 13a98df4 (automated)gVisor bot
2019-08-08netstack: Don't start endpoint goroutines too soon on restore.Rahat Mahmood
Endpoint protocol goroutines were previously started as part of loading the endpoint. This is potentially too soon, as resources used by these goroutine may not have been loaded. Protocol goroutines may perform meaningful work as soon as they're started (ex: incoming connect) which can cause them to indirectly access resources that haven't been loaded yet. This CL defers resuming all protocol goroutines until the end of restore. PiperOrigin-RevId: 262409429
2019-08-08Merge 2e45d169 (automated)gVisor bot
2019-08-08Merge 08cd5e1d (automated)gVisor bot
2019-08-08Merge 40d6d8c1 (automated)gVisor bot
2019-08-07Merge 1c9781a4 (automated)gVisor bot
2019-08-07Merge 79cc4397 (automated)gVisor bot
2019-08-07Merge e70eafc9 (automated)gVisor bot
2019-08-06Merge dfbc0b0a (automated)gVisor bot
2019-08-06Merge 704f9610 (automated)gVisor bot
2019-08-05Merge 23e74043 (automated)gVisor bot
2019-08-02Merge 960a5e55 (automated)gVisor bot
2019-08-02Merge b6a5b950 (automated)gVisor bot
2019-08-02Job control: controlling TTYs and foreground process groups.Kevin Krakauer
(Don't worry, this is mostly tests.) Implemented the following ioctls: - TIOCSCTTY - set controlling TTY - TIOCNOTTY - remove controlling tty, maybe signal some other processes - TIOCGPGRP - get foreground process group. Also enables tcgetpgrp(). - TIOCSPGRP - set foreground process group. Also enabled tcsetpgrp(). Next steps are to actually turn terminal-generated control characters (e.g. C^c) into signals to the proper process groups, and to send SIGTTOU and SIGTTIN when appropriate. PiperOrigin-RevId: 261387276
2019-08-02Merge b461be88 (automated)gVisor bot
2019-08-02Merge 2906dffc (automated)gVisor bot
2019-08-02Merge aaaefdf9 (automated)gVisor bot
2019-08-02Remove kernel.mounts.Nicolas Lacasse
We can get the mount namespace from the CreateProcessArgs in all cases where we need it. This also gets rid of kernel.Destroy method, since the only thing it was doing was DecRefing the mounts. Removing the need to call kernel.SetRootMountNamespace also allowed for some more simplifications in the container fs setup code. PiperOrigin-RevId: 261357060
2019-08-02Merge 3eff0531 (automated)gVisor bot
2019-08-01Merge bad43772 (automated)gVisor bot
2019-08-01Merge f2b25aea (automated)gVisor bot
2019-08-01Merge 0a246fab (automated)gVisor bot
2019-07-31Merge cf2b2d97 (automated)gVisor bot
2019-07-31Initialize kernel.unimplementedSyscallEmitter with a sync.Once.Nicolas Lacasse
This is initialized lazily on the first unimplemented syscall. Without the sync.Once, this is racy. PiperOrigin-RevId: 260971758
2019-07-30Merge 7369c63e (automated)gVisor bot
2019-07-30Merge 93b0917d (automated)gVisor bot
2019-07-30Merge e511c0e0 (automated)gVisor bot
2019-07-30Add feature to launch Sentry from an open host FD.Zach Koopmans
Adds feature to launch from an open host FD instead of a binary_path. The FD should point to a valid executable and most likely be statically compiled. If the executable is not statically compiled, the loader will search along the interpreter paths, which must be able to be resolved in the Sandbox's file system or start will fail. PiperOrigin-RevId: 260756825
2019-07-30Merge 1decf764 (automated)gVisor bot
2019-07-30Merge 8da9f8a1 (automated)gVisor bot
2019-07-30Merge ddf25e33 (automated)gVisor bot
2019-07-30Merge b765eb45 (automated)gVisor bot