-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
stat,seccomp: fix 32-bit overflow on stat quantities
On most i686 distributions, glibc implements stat() for programs compiled without -D_FILE_OFFSET_BITS=64 by calling the corresponding stat64 system call, and if any of the 64-bit quantities in the statbuf are larger than 2^32-1, the glibc wrapper pretends the file does not exist by returning ENOENT. This flag mitigates the issue by pulling the rug under glibc and rewriting the quantities to stay within bounds. For timestamps, a fixed date within range is used. For inode numbers, the value is rewritten in a way that keeps the (device, inode) pair unique.
- Loading branch information
Showing
7 changed files
with
326 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.