Reliability #22

orbisvicis opened this Issue Dec 13, 2012 · 1 comment


None yet
2 participants

I need to reptyr badblocks in non-destructive read-write mode after the X server locked up. However I feel this is especially representative of any critical I/O based applications.

I am probably being paranoid, and I've already tested reptyr/badblocks in a virtual machine, and everything appeared fine. But I would probably never notice a single scrambled bad block.

So my question is this: Theoretically, is it possible/plausible for reptyr to scramble the FDs, accidentally write junk to a bad sector, or any other nightmare, that would compromise the reliability of critical applications.


nelhage commented Dec 13, 2012

reptyr does attach to the process via ptrace and perform operations in the process' address space, so it is theoretically possible for a bug somewhere to cause memory corruption. That said, I've written it with some care to minimize such risks, and never observed that sort of bug.

I do recommend testing reptyr on a dry-run against any super-critical processes, but if that works, I would be pretty confident that it will fail safely, if it does, rather than by silently corrupting data.

@nelhage nelhage closed this Dec 13, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment