From: Sasha Levin <redacted>
Date: Sun, 13 Jul 2014 17:50:53 -0400

While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel with the KASAN patchset, I've stumbled on the following spew:

 ...

It's similar to another variation:

 ...

I've tried debugging it, but I don't see a code path that could lead to that.

Both of these cases involve working with pointers declared with
DECLARE_SOCKADDR, maybe that somehow confuses ASAN code generation?