Coverity: suppress IDL-generated code false positives via project-level filter

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      What

      Add a Coverity analysis filter in the `MongoDB master` project configuration that excludes files matching `*_gen.cpp` from the `DEADCODE` and `CONSTANT_EXPRESSION_RESULT` checkers. Verify the four findings in `repl_set_config_gen.cpp` (lines 954, 970) no longer appear after the next scan. Document the filter in the Coverity triage runbook.

      Resolves: SERVER-119563, SERVER-119568, SERVER-119569, SERVER-119571

      Why

      `repl_set_config_gen.cpp` is machine-generated by the IDL compiler and is not hand-maintained. The IDL compiler emits exhaustive branches covering every enum value; Coverity's data-flow analysis sees the restricted value range and flags the remaining branches as dead code. There is no real defect. A project-level filter is the correct fix — editing the generated file is futile since it is overwritten on every IDL change, and the same class of finding will recur for every IDL schema that gets updated.

            Assignee:
            Unassigned
            Reporter:
            Denis Trailin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: