From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sowmini Varadhan Subject: Re: KASAN: use-after-free Read in rds_tcp_tune Date: Wed, 14 Feb 2018 10:21:09 -0500 Message-ID: <20180214152109.GF11528@oracle.com> References: <001a1141a524c513ca05628d8ad4@google.com> <20180112183046.GA26098@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: syzbot , David Miller , LKML , linux-rdma@vger.kernel.org, netdev , rds-devel@oss.oracle.com, Santosh Shilimkar , syzkaller-bugs@googlegroups.com To: Dmitry Vyukov Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On (02/14/18 16:11), Dmitry Vyukov wrote: > > Hi Sowmini, > > Was this ever fixed? What's the fix? This still hangs as open. Please > provide "syz fix" tag. Are you still seeing this problem? I had expected that the changes around rds_destroy_pending - see commit ebeeb1ad9b8a - would have taken care of this (note that ebeeb1ad9b8a refactors/updates 3db6e0d172c9) but those fixes were done by inspection only. In other words, I was never able to reproduce this, so we may still have missed some race condition. --Sowmini