3 ms·
Hah. Binary patching is a neat hack, but my first thought would've been to make a loopbackable filesystem in a file that explicitly didn't have that many inodes
by mst 6y ago
Hah. Binary patching is a neat hack, but my first thought would've been to make a loopbackable filesystem in a file that explicitly didn't have that many inodes.
Mostly on grounds that if one binary had that problem, maybe another one would, and I would really rather not go through the same process twice ;)
- nneonneo 6y agoThe nice thing about OP's solution is that they produced a new binary that's runnable on any system - in particular, it sounded like they had a whole research team who probably needed to run the software. I suppose you could give them an "installer" of sorts that would simply mount the appropriate filesystem and put everything there, but the OP's solution seems decently elegant all things considered :)
- mst 6y agoYeah. It's a question of axes: "runnable on any system" versus "robust against any program with that bug". Trade-offs all the way down, as usual, and "neat hack" was meant positively, mine's just a different neat hack with different advantages and failure modes :D
- noobermin 6y agoHow about something like a vm