File: MsanParamUnpoison.cpp

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
file content (28 lines) | stat: -rw-r--r-- 1,055 bytes parent folder | download | duplicates (32)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
// See https://llvm.org/LICENSE.txt for license information.
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception

// Triggers the bug described here:
// https://github.com/google/oss-fuzz/issues/2369#issuecomment-490240627
//
// In a nutshell, MSan's parameter shadow does not get unpoisoned before calls
// to LLVMFuzzerTestOneInput.  This test case causes the parameter shadow to be
// poisoned by the call to foo(), which will trigger an MSan false positive on
// the Size == 0 check if the parameter shadow is still poisoned.
#include <cstdint>
#include <cstdio>
#include <cstdlib>
#include <cstring>

volatile int zero = 0;
__attribute__((noinline)) int foo(int arg1, int arg2) { return zero; }

extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t Size) {
  if (Size == 0)
    return 0;

  // Pass uninitialized values to foo().  Since foo doesn't do anything with
  // them, MSan should not report an error here.
  int a, b;
  return foo(a, b);
}