Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rules/sdk: intelligently flag overflowing uint*->uint* + int*->int* conversions #58

Merged
merged 1 commit into from
Oct 14, 2022

Conversation

odeke-em
Copy link
Collaborator

Retrieve the underlying types to perform smarter conversions. More importantly, this change intelligently flags overflowing conversions for homogenous signedness aka:

  • int* -> int*
  • uint* -> uint*

whereby for each same signedness, just check widths where:

  • 64-bit machines: uint64 == uint > uint32 > uint16 > uint8
    int64 == int > int32 > int16 > int8

  • 32-bit machines: uint64 > uint == uint32 > uint16 > uint8
    int64 > int == int32 > int16 > int8

and this change only flags the offending non-fitting conversions. For an exhibit, this code

package inttests

type in = int
type uin = uint

func it() {
	_ = uint64(uint32(0))
	_ = uint(uint32(0))
	_ = uint(uint16(0))
	_ = uint(uint8(0))
	_ = uint(uint64(0))
	_ = uint32(uint64(0))
	_ = uint16(uint64(0))
	_ = uint8(uint64(0))
	_ = uint8(uint(0))
	_ = uint8(uint32(0))
	_ = uint8(uint64(0))
	_ = int(uint(0))
	_ = in(uint(0))
	_ = uin(uint(0))
	_ = uin(uint32(0))
}
  • Previously:
  • Could not catch the aliased int with overflowing potential from uint
  • Falsely flagged all the rest as overflowing so 12 issues
  • Currently:
  • Catches the aliased int with overflowing potential from uint
  • Only flags the actually overflowing conversions so only 8 issues

Fixes #56
Fixes #57

@odeke-em
Copy link
Collaborator Author

Just a kind FYI to @elias-orijtech @kirbyquerby @willpoint @ebuchman @tac0turtle @jhusdero and this change will cut down massively on false positives

…onversions

Retrieve the underlying types to perform smarter conversions.
More importantly, this change intelligently flags overflowing
conversions for homogenous signedness aka:
* int* -> int*
* uint* -> uint*

whereby for each same signedness, just check widths where:
+ 64-bit machines:
uint64 == uint > uint32 > uint16 > uint8
int64  == int  > int32  > int16  > int8

+ 32-bit machines:
uint64 > uint == uint32 > uint16 > uint8
int64  > int  == int32  > int16  > int8

and this change only flags the offending non-fitting conversions.
For an exhibit, this code
```go
package inttests

type in = int
type uin = uint

func it() {
	_ = uint64(uint32(0))
	_ = uint(uint32(0))
	_ = uint(uint16(0))
	_ = uint(uint8(0))
	_ = uint(uint64(0))
	_ = uint32(uint64(0))
	_ = uint16(uint64(0))
	_ = uint8(uint64(0))
	_ = uint8(uint(0))
	_ = uint8(uint32(0))
	_ = uint8(uint64(0))
	_ = int(uint(0))
	_ = in(uint(0))
	_ = uin(uint(0))
	_ = uin(uint32(0))
}
```

* Previously:
+ Could not catch the aliased int with overflowing potential from uint
+ Falsely flagged all the rest as overflowing so 12 issues

* Currently:
+ Catches the aliased int with overflowing potential from uint
+ Only flags the actually overflowing conversions so only 8 issues

Fixes #56
Fixes #57
@odeke-em odeke-em force-pushed the rules-sdk-consider-uint+-int+-conversions branch from e5034d7 to 9592313 Compare October 14, 2022 00:04
@odeke-em odeke-em merged commit 9592313 into master Oct 14, 2022
@odeke-em odeke-em deleted the rules-sdk-consider-uint+-int+-conversions branch October 14, 2022 00:07
@odeke-em
Copy link
Collaborator Author

Confirmed that this change reduces the reports in cosmos-sdk from 1,045 down to 837, it eliminated a bunch of false positives!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant