Automatically applying components based on crash stacktrace and information from OWNERS files.
If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/e3140a8f27345d395ea75fe619d730951a438e89 (Run SQLite DBFuzz2 on ClusterFuzz to fuzz for data corruption).
If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Richard and Dan, could you please let me know the URL of the check-in that fixed this?
dbfuzz2 test case attached. Stack trace below.
../../third_party/sqlite/amalgamation/sqlite3.c:72450:11: runtime error: signed integer overflow: 2097151999 - -513466266 cannot be represented in type 'int'
#0 0x55d6219a762d in checkList third_party/sqlite/amalgamation/sqlite3.c:72450:11
#1 0x55d6219895fb in sqlite3BtreeIntegrityCheck third_party/sqlite/amalgamation/sqlite3.c:72860:3
#2 0x55d62197119f in sqlite3VdbeExec third_party/sqlite/amalgamation/sqlite3.c:88953:7
#3 0x55d621935751 in sqlite3Step third_party/sqlite/amalgamation/sqlite3.c:81427:10
#4 0x55d62193004a in sqlite3_step third_party/sqlite/amalgamation/sqlite3.c:81490:16
#5 0x55d62193a7a2 in sqlite3_exec third_party/sqlite/amalgamation/sqlite3.c:118075:12
#6 0x55d621846d98 in LLVMFuzzerTestOneInput third_party/sqlite/src/test/dbfuzz2.c:95:5
Thank you very much for the quick response, Richard! I am backporting this.
I just looked this up in N2176 [1] (the last C17 draft), and unsigned->signed conversion is implementation-defined -- S 6.3.1.3. I suspect this means we'll get a UBSan warning for the if on line 9428.
ClusterFuzz testcase 5398973764075520 is verified as fixed, so closing issue as verified.
If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Comment 1 by ClusterFuzz
, Dec 9Labels: Test-Predator-Auto-Components