From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sowmini Varadhan Subject: Re: [PATCH net-next] rds: clean up loopback rds_connections on netns deletion Date: Mon, 25 Jun 2018 10:49:07 -0400 Message-ID: <20180625144907.GE14823@oracle.com> References: <1529934085-181126-1-git-send-email-sowmini.varadhan@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: syzkaller-bugs@googlegroups.com To: davem@davemloft.net, rds-devel@oss.oracle.com, santosh.shilimkar@oracle.com, netdev@vger.kernel.org Return-path: Received: from userp2120.oracle.com ([156.151.31.85]:52268 "EHLO userp2120.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934325AbeFYOtU (ORCPT ); Mon, 25 Jun 2018 10:49:20 -0400 Content-Disposition: inline In-Reply-To: <1529934085-181126-1-git-send-email-sowmini.varadhan@oracle.com> Sender: netdev-owner@vger.kernel.org List-ID: On (06/25/18 06:41), Sowmini Varadhan wrote: : > Add the changes aligned with the changes from > commit ebeeb1ad9b8a ("rds: tcp: use rds_destroy_pending() to synchronize > netns/module teardown and rds connection/workq management") for > rds_loop_transport FWIW, I am optimistic that this will take care of a number of the use-after-free panics reported by syzbot (I have not marked the patch with the recommended syzkaller Reported-by tags because I was not able to reproduce each original issue, but inspection of the traces suggests this missing patch may be behind the races that cause the reports). --Sowmini