On Wed, Jul 19, 2017 at 3:02 AM, Alexander Potapenko <glider@xxxxxxxxxx> wrote: > On Tue, Jul 18, 2017 at 4:55 PM, Alexander Potapenko <glider@xxxxxxxxxx> wrote: >> KMSAN reported use of uninitialized sctp_addr->v4.sin_addr.s_addr and >> sctp_addr->v6.sin6_scope_id in sctp_v6_cmp_addr() (see below). >> Make sure all fields of an IPv6 address are initialized, which >> guarantees that the IPv4 fields are also initialized. > I'm assuming here that the IPv4 address is known to overlap with the > IPv6 one and doesn't need separate initialization. > Ok, addr->v6.sin6_scope_id = 0 will fix the call trace you posted here. addr->v6.sin6_flowinfo = 0 is to fix uninitialized sctp_addr->v4.sin_addr.s_addr, I couldn't see how this happens, can you also post the call trace for v4.sin_addr.s_addr ? Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
