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: Tue, 26 Jun 2018 10:53:23 -0400 Message-ID: <20180626145323.GH20575@oracle.com> References: <1529934085-181126-1-git-send-email-sowmini.varadhan@oracle.com> <20180626.222345.1953178647182804872.davem@davemloft.net> <20180626134043.GE20575@oracle.com> <20180626.232956.1181108479532700313.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org, rds-devel@oss.oracle.com, santosh.shilimkar@oracle.com To: David Miller Return-path: Received: from userp2130.oracle.com ([156.151.31.86]:43774 "EHLO userp2130.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751121AbeFZOxf (ORCPT ); Tue, 26 Jun 2018 10:53:35 -0400 Content-Disposition: inline In-Reply-To: <20180626.232956.1181108479532700313.davem@davemloft.net> Sender: netdev-owner@vger.kernel.org List-ID: On (06/26/18 23:29), David Miller wrote: > >> > >> Since this probably fixes syzbot reports, this can be targetted > >> at 'net' instead? > > > > that thought occurred to me but I wanted to be conservative and have > > it in net-next first, have the syzkaller-bugs team confirm the > > the fixes and then backport to earlier kernels (if needed).. > > I think there is a way to ask syzbot to test a patch in an > email. and just to add, the fix itself is logically correct, so belongs in net-next. What I dont have (and therefore did not target net) is official confirmation that the syzbot failures are root-caused to the absence of this patch (since there is no reproducer for many of these, and no crash dumps available from syzbot). --Sowmini