marcan_42

166 ms·

1501.
by marcan_42 8y ago
Case in point: I tried to shrink an NTFS filesystem offline with ntfsresize (offline!) and this happened: https://marcan.st/2015/10/rescuing-a-broken-ntfs-filesystem/ This is a tool that is part of most Linux
1502.
by marcan_42 8y ago
Every 64-bit OS can guarantee SSE2 support, because it's baked into the x86-64 spec. Every single 64-bit Linux build can and does use SSE2 (unless someone explicitly turned that off for no reason). If there are performance difference
1503.
by marcan_42 9y ago
It does extend. It's just an XOR/parity trick. The last person shouts out the XOR of all the previous colors (if you prefer: whether the number of visible white hats is even or odd). From there, every other subsequent person knows
1504.
by marcan_42 9y ago
Sure. -fstack-check wasn't designed for stack clash protection. It's old and it makes little sense in context, but it works and it exists, which is why it's being used until proper Stack Clash prevention lands in GCC 8. I
1505.
by marcan_42 9y ago
Sure, but the thing is something would've already probed into the 4K guard page before you had a chance to probe past it. If your stack guard page is the next thing up on the stack and you call that vDSO function, then sure, it'
1506.
by marcan_42 9y ago
It isn't. -fstack-check consistently checks the stack at a 4K offset. It wasn't designed for Stack Clash protection, but in practice, it works as long as all the code was compiled with it (which on Gentoo Hardened, it would be,