[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALx6S35TJ44b1UM=OqqwfDMFrXFjDJj==shW6Z_8zM3VH9v6WA@mail.gmail.com>
Date: Mon, 12 Mar 2018 14:25:41 -0700
From: Tom Herbert <tom@...bertland.com>
To: Eric Biggers <ebiggers3@...il.com>
Cc: Tom Herbert <tom@...ntonium.net>,
"David S. Miller" <davem@...emloft.net>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH net] kcm: lock lower socket in kcm_attach
On Mon, Mar 12, 2018 at 2:09 PM, Eric Biggers <ebiggers3@...il.com> wrote:
> On Mon, Mar 12, 2018 at 02:04:12PM -0700, Tom Herbert wrote:
>> Need to lock lower socket in order to provide mutual exclusion
>> with kcm_unattach.
>>
>> Fixes: ab7ac4eb9832e32a09f4e804 ("kcm: Kernel Connection Multiplexor module")
>> Signed-off-by: Tom Herbert <tom@...ntonium.net>
>> ---
>
> Is this fixing the syzbot-reported bug "KASAN: use-after-free Read in
> get_work_pool"? If so, please add:
>
> Reported-by: syzbot+ea75c0ffcd353d32515f064aaebefc5279e6161e@...kaller.appspotmail.com
Yeah, I was looking for a "reported by". I didn't see it in the email
from syzbot. Where is this found?
Thanks,
Tom
Powered by blists - more mailing lists