UBSAN: object-size-mismatch in wg_xmit
Jeffrey Walton
noloader at gmail.com
Mon Jan 11 17:35:19 UTC 2021
On Mon, Jan 11, 2021 at 12:20 PM Dmitry Vyukov <dvyukov at google.com> wrote:
> ...
> FTR, I've disabled the following UBSAN configs:
> UBSAN_MISC
> UBSAN_DIV_ZERO
> UBSAN_BOOL
> UBSAN_OBJECT_SIZE
> UBSAN_SIGNED_OVERFLOW
> UBSAN_UNSIGNED_OVERFLOW
> UBSAN_ENUM
> UBSAN_ALIGNMENT
> UBSAN_UNREACHABLE
>
> Only these are enabled now:
> UBSAN_BOUNDS
> UBSAN_SHIFT
>
> This is commit:
> https://github.com/google/syzkaller/commit/2c1f2513486f21d26b1942ce77ffc782677fbf4e
I think the commit cut too deep.
The overflows are important if folks are building with compilers other than GCC.
The aligned data accesses are important on platforms like MIPS64 and Sparc64.
Object size is important because it catches destination buffer overflows.
I don't know what's in miscellaneous. There may be something useful in there.
Jeff
More information about the WireGuard
mailing list