From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756167AbdIRQ3I (ORCPT ); Mon, 18 Sep 2017 12:29:08 -0400 Received: from mail-qt0-f175.google.com ([209.85.216.175]:43192 "EHLO mail-qt0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755934AbdIRQ3G (ORCPT ); Mon, 18 Sep 2017 12:29:06 -0400 X-Google-Smtp-Source: AOwi7QCgCSHFvWzsoinsKTnHo4dxpAOEyIqiRwlLAkVYQ2jnueJY8gA4clNa5llsTfumR4VtwmbBvA== From: josef@toxicpanda.com X-Google-Original-From: jbacik@fb.com To: davem@davemloft.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, crobinso@redhat.com, labbott@redhat.com, kernel-team@fb.com Subject: [PATCH 0/3] fix reuseaddr regression Date: Mon, 18 Sep 2017 12:28:54 -0400 Message-Id: <1505752137-15522-1-git-send-email-jbacik@fb.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I introduced a regression when reworking the fastreuse port stuff that allows bind conflicts to occur once a reuseaddr socket successfully opens on an existing tb. The root cause is I reversed an if statement which caused us to set the tb as if there were no owners on the socket if there were, which obviously is not correct. Dave I have follow up patches that will add a selftest for this case and I ran the other reuseport related tests as well. These need to go in pretty quickly as it breaks kvm, I've marked them for stable. Sorry for the regression, Josef