[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACT4Y+ZMbLyxvOAz-rXfxkZOdqDAnLWNbg-K8n93k2JYUtdOYQ@mail.gmail.com>
Date: Mon, 19 Mar 2018 09:47:26 +0300
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Sowmini Varadhan <sowmini.varadhan@...cle.com>
Cc: syzbot <syzbot+80c06fb3aabfa386bc06@...kaller.appspotmail.com>,
David Miller <davem@...emloft.net>,
LKML <linux-kernel@...r.kernel.org>, linux-rdma@...r.kernel.org,
netdev <netdev@...r.kernel.org>, rds-devel@....oracle.com,
Santosh Shilimkar <santosh.shilimkar@...cle.com>,
syzkaller-bugs@...glegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in rds_cong_queue_updates
On Mon, Mar 19, 2018 at 9:37 AM, Sowmini Varadhan
<sowmini.varadhan@...cle.com> wrote:
> On (03/19/18 09:29), Dmitry Vyukov wrote:
>>
>> This looks the same as:
>>
>> #syz dup: KASAN: use-after-free Read in rds_cong_queue_updates
>
> correct, seems like the rds_destroy_pending() fixes did not seal
> this race condition. I need to look at this more carefully to see
> what race I missed.. no easy answer here, I am afraid.
Hi Sowmini,
What fix do you mean? syzbot does not know about any fixes for any of
the bugs as far as I see. So maybe your fix actually fixed it, but
it's not in upstream yes, and syzbot still finds this in upstream.
We tell syzbot about fixes (with Reported-by tags or "#syz fix" email
commands) to be able to later make sense of the state of the bugs.
Powered by blists - more mailing lists