On Fri, Mar 10, 2017 at 7:01 AM, Paul Moore wrote:
> On Thu, Mar 9, 2017 at 2:12 AM, David Miller wrote:
>> From: Alexander Potapenko
>> Date: Mon, 6 Mar 2017 19:46:14 +0100
>>
>>> KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
>>> uninitialized memory in selinux_socke
On Thu, Mar 9, 2017 at 2:12 AM, David Miller wrote:
> From: Alexander Potapenko
> Date: Mon, 6 Mar 2017 19:46:14 +0100
>
>> KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
>> uninitialized memory in selinux_socket_bind():
> ...
>> (the line numbers are relative to 4.8-r
From: Alexander Potapenko
Date: Mon, 6 Mar 2017 19:46:14 +0100
> KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
> uninitialized memory in selinux_socket_bind():
...
> (the line numbers are relative to 4.8-rc6, but the bug persists upstream)
>
> , when I run the follow
On Mon, 2017-03-06 at 19:46 +0100, Alexander Potapenko wrote:
> KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
> uninitialized memory in selinux_socket_bind():
>
...
> Signed-off-by: Alexander Potapenko
> ---
> Changes since v1:
> - fixed patch description
> - fixed ad
KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of
uninitialized memory in selinux_socket_bind():
==
BUG: KMSAN: use of unitialized memory
inter: 0
CPU: 3 PID: 1074 Comm: packet2 Tainted: GB 4.8.0-r