diff options
| author | Tom Smeding <tom@tomsmeding.com> | 2022-09-08 10:28:49 +0200 |
|---|---|---|
| committer | Tom Smeding <tom@tomsmeding.com> | 2022-09-08 10:28:49 +0200 |
| commit | f4288dd09a9be0dad2cf955695d66d1b37c107d2 (patch) | |
| tree | 4b2c73f5586e966fa3516b68c4826d67e2c90a45 | |
| parent | b6f41cc07d366ee50ace720d3426656aba7daa2b (diff) | |
bugs/efault: Add reproducer link
| -rw-r--r-- | bugs/efault.html | 3 | ||||
| -rw-r--r-- | bugs/efault.md | 1 |
2 files changed, 3 insertions, 1 deletions
diff --git a/bugs/efault.html b/bugs/efault.html index 06be3c1..d00a51c 100644 --- a/bugs/efault.html +++ b/bugs/efault.html @@ -1,6 +1,7 @@ <h2>The impossible EFAULT</h2> <p>I have written a program; suppose it's called <code>worker</code>. -(While the program is written in Haskell, I don't think that's particularly relevant to this post.)</p> +(While the program is written in Haskell, I don't think that's particularly relevant to this post.) +(EDIT: Reproducer can be found <a href="https://git.tomsmeding.com/snap-efault/tree/">here</a>.)</p> <p>When run, <code>worker</code> starts a bunch of copies of a script. Under normal circumstances this script sets up a container using Linux cgroups and Linux user namespaces, but none of that is relevant because the strange behaviour in question occurs just fine without all of that -- in fact, we'll let it start the following script, say <code>./sleep.sh</code>:</p> <pre><code class="language-bash">#!/bin/bash diff --git a/bugs/efault.md b/bugs/efault.md index c9a539d..c66a6e1 100644 --- a/bugs/efault.md +++ b/bugs/efault.md @@ -2,6 +2,7 @@ I have written a program; suppose it's called `worker`. (While the program is written in Haskell, I don't think that's particularly relevant to this post.) +(EDIT: Reproducer can be found [here](https://git.tomsmeding.com/snap-efault/tree/).) When run, `worker` starts a bunch of copies of a script. Under normal circumstances this script sets up a container using Linux cgroups and Linux user namespaces, but none of that is relevant because the strange behaviour in question occurs just fine without all of that -- in fact, we'll let it start the following script, say `./sleep.sh`: |