55 Commits

Author	SHA1	Message	Date
JF Bastien	30bf96bfe7	Use common parse routine to read alignment values from bitcode ... While fuzzing LLVM bitcode files, I discovered that (1) the bitcode reader doesn't check that alignments are no larger than 2**29; (2) downstream code doesn't check the range; and (3) for values out of range, corresponding large memory requests (based on alignment size) will fail. This code fixes the bitcode reader to check for valid alignments, fixing this problem. This CL fixes alignment value on global variables, functions, and instructions: alloca, load, load atomic, store, store atomic. Patch by Karl Schimpf (kschimpf@google.com). llvm-svn: 230180	2015-02-22 19:32:03 +00:00
Filipe Cabecinhas	ecf8f7f49b	[Bitcode reader] Fix a few assertions when reading invalid files ... Summary: When creating {insert,extract}value instructions from a BitcodeReader, we weren't verifying the fields were valid. Bugs found with afl-fuzz Reviewers: rafael Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D7325 llvm-svn: 229345	2015-02-16 00:03:11 +00:00
Filipe Cabecinhas	fcd044b692	Check bit widths before trying to get a type. ... Added a test case for it. Also added run lines for the test case in r227566. Bugs found with afl-fuzz llvm-svn: 227589	2015-01-30 18:13:50 +00:00
Filipe Cabecinhas	de968ecb05	[Bitcode] Diagnose errors instead of asserting from bad input ... Eventually we can make some of these pass the error along to the caller. Reports a fatal error if: We find an invalid abbrev record We try to get an invalid abbrev number We can't fill the current word due to an EOF Fixed an invalid bitcode test to check for output with FileCheck Bugs found with afl-fuzz llvm-svn: 226986	2015-01-24 04:15:05 +00:00
Filipe Cabecinhas	3ca723c9e5	Use report_fatal_error instead of llvm_unreachable, so we don't crash on user input ... llvm-svn: 226248	2015-01-16 04:54:12 +00:00