From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751919AbbFYPB0 (ORCPT ); Thu, 25 Jun 2015 11:01:26 -0400 Received: from mail-ob0-f176.google.com ([209.85.214.176]:35055 "EHLO mail-ob0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750786AbbFYPBS (ORCPT ); Thu, 25 Jun 2015 11:01:18 -0400 MIME-Version: 1.0 In-Reply-To: References: <20150624.063911.1220157256743743341.davem@davemloft.net> Date: Thu, 25 Jun 2015 18:01:17 +0300 Message-ID: Subject: Re: [GIT] Networking From: Or Gerlitz To: Linus Torvalds Cc: David Miller , Doug Ledford , Ira Weiny , Andrew Morton , Network Development , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jun 25, 2015 at 2:38 AM, Linus Torvalds wrote: > > On Wed, Jun 24, 2015 at 6:39 AM, David Miller wrote: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master > > Just going through the conflicts, I see commit 7193a141eb74 ("IB/mlx4: > Set VF to read from QP counters"), and wonder... > > Is that code really supposed to fall through to the > infiniband-over-ethernet case when the link layer is > IB_LINK_LAYER_INFINIBAND but it's a slave? > > The commit message is not in the least helpful. > And this is a bug indeed. Under IB links, we should use the the infiniband-over-ethernet flow only for one specific case (reading link performance counters by SRIOV VFs) and nothing else. I sent a fix, https://patchwork.kernel.org/patch/6675921/ Or.