[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170228173328.GL31155@oracle.com>
Date: Tue, 28 Feb 2017 12:33:28 -0500
From: Sowmini Varadhan <sowmini.varadhan@...cle.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: santosh.shilimkar@...cle.com, David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>, linux-rdma@...r.kernel.org,
rds-devel@....oracle.com, LKML <linux-kernel@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: net/rds: use-after-free in inet_create
On (02/28/17 17:51), Dmitry Vyukov wrote:
> Searching other crashes for "net/rds" I found 2 more crashes that may
> be related. They suggest that the delayed works are not properly
> stopped when the socket is destroyed. That would explain how
> rds_connect_worker accesses freed net, right?
yes, I think we may want to explicitly cancel this workq.. this
in rds_conn_destroy().
I'm trying to build/sanity-test (if lucky, reproduce the bug)
as I send this out.. let me get back to you..
If I have a patch against net-next, would you be willing/able to
try it out? given that this does not show up on demand, I'm not
sure how we can check that "the fix worked"..
--Sowmini
Powered by blists - more mailing lists