[all-commits] [llvm/llvm-project] cc945e: [MachO] Loosen boundary check for reading export t...

[Cyndy Ishida via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: cc945e41a7788327d0e8ba0ea6dc3571d7efa04f
      https://github.com/llvm/llvm-project/commit/cc945e41a7788327d0e8ba0ea6dc3571d7efa04f
  Author: Cyndy Ishida <cyndy_ishida at apple.com>
  Date:   2024-07-09 (Tue, 09 Jul 2024)

  Changed paths:
    M llvm/lib/Object/MachOObjectFile.cpp
    R llvm/test/tools/llvm-objdump/MachO/Inputs/macho-inconsistent-export
    M llvm/test/tools/llvm-objdump/MachO/bad-trie.test
    A llvm/test/tools/llvm-objdump/MachO/export-trie-boundary.test

  Log Message:
  -----------
  [MachO] Loosen boundary check for reading export trie nodes (#96705)

The design of the export trie in macho's is that each node has a
variable length payload. When reading nodes, it should be an error if
reading the uleb128 puts you beyond the stated node size but not when
the stated size goes beyond the known part that was read.

resolves: rdar://130310832

This was primarily authored by Nick Kledzik, I added/cleaned up the test
cases.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications