Avoid int overflow after year 2038#270
Open
bmwiedemann wants to merge 1 commit into
Open
Conversation
So it can work until year 2106. See https://en.wikipedia.org/wiki/Year_2038_problem This patch was done while reviewing potential year-2038 issues in openSUSE. Signed-off-by: Bernhard M. Wiedemann <bwiedemann@suse.de>
mwilck
requested changes
Jun 5, 2026
mwilck
left a comment
Collaborator
There was a problem hiding this comment.
Good, but I'd appreciate a more verbose commit message. See comment.
| return 0; | ||
|
|
||
| mtime = sb[44]|(sb[45]|(sb[46]|sb[47]<<8)<<8)<<8; | ||
| mtime = sb[44]|(sb[45]|(sb[46]|(unsigned int)sb[47]<<8)<<8)<<8; |
Collaborator
There was a problem hiding this comment.
This needs more explanation in the commit message. AFAIU this is effective because it overrides the standard integral promotion in C, which counter-intuitively promotes unsigned char to int if, as usual, the size of the latter type is larger than the size of the former.
Collaborator
There was a problem hiding this comment.
Extending this with explanation from claude:
- sb is unsigned char[], so each element is unsigned char
- C's integer promotion rules promote unsigned char to int before any arithmetic
- All intermediate computations are therefore signed int
- For timestamps after 2038-01-19 03:14:07 UTC, sb[47] >= 0x80 (the MSB has its high bit set)
- Eventually this means a 1 is shifted into bit 31 of a signed int — this is undefined behavior in C (pre-C23), because left-shifting into the sign bit of a signed integer is UB
- On every real implementation, this produces a negative int
- When assigned to a 64-bit time_t (the type on all modern 64-bit Linux), the negative int is sign-extended to a negative time_t, representing a date before the Unix epoch — completely wrong
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Avoid int overflow after year 2038, so it can work until year 2106. Note: dates before 1970 will stop working.
See https://en.wikipedia.org/wiki/Year_2038_problem
This patch was done while reviewing potential year-2038 issues in openSUSE.