Received: by 10.223.176.46 with SMTP id f43csp1169575wra; Fri, 19 Jan 2018 07:51:17 -0800 (PST) X-Google-Smtp-Source: ACJfBotnUp86QJlHa/zj2G5/sYe9nCL/jBwH7qark/w3ZKvJRiP1nqCWyhEtW4Vt4YOA0B7UMfC6 X-Received: by 10.99.115.94 with SMTP id d30mr30439346pgn.172.1516377077733; Fri, 19 Jan 2018 07:51:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516377077; cv=none; d=google.com; s=arc-20160816; b=pQfo90crboC0VgwaXqsIoK9n64OlS6EEohpwCS1mi4b11bn+hdHe2YwSCquuIcrMDi JiyKPsKNs5MI8/AEisJzc9b40pzcJxoqfGq3QJdxcUMB7KloDBZZY7wr5VcnzvRsyqys JFGuTxrUMJ6kmRJjwpMpXfyqRQ/qVaHC/lEUB0CkIIRQ7hAQLmEqzMsq4kt0+375PIJM xGdMkUDmoWqAtSYnRo3wgAJ/vR+MQz9YFxwuWJDz3eBCof3CisN4ZARkx3VKinO3LDy0 Eb1T1CgFr9aRgJDw45/4R9xnQkcG6aLWAB6PEmiDCeEQtzfOhD/gXA4yegAfKg7XIY/o MNwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id :dkim-signature:arc-authentication-results; bh=y/KEHUIVcl0+vMJN6gw1WkbiSc9oJYyUBarGut2ZNnA=; b=UTHRWGn/3HNp9Xmb0smoR7qGSEvIojbFOxjwbjP/HFG4Z3moWpadvBpA6pQHYnOjyj RqdaYVlto/ffERNEf50S+JdDTSC0hOCfvmaVZUxIpdskFvqJCMKcFifRUd/ryXWD0C40 IYMWb0jB+PKXL5go+6ldwBpzgtIy3Z6oTZ3t6Sv4s7lJmeAdiag/jyyd7tslhNSNml+A IayXeGU3tsV9Wt2qtORjolwwbznsSo4UtO8grkOKyt7LDsF5HVUjPaGQyRAoexoJAJKU U3lE8a1APWRbedyI/pIGc7tJ/8oYlQeow7HL2hHebj4mF7ML6aEKH6aaE5hEbeL+SDvP T39g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=u7LvlOAP; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 34-v6si911966plz.587.2018.01.19.07.51.03; Fri, 19 Jan 2018 07:51:17 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=u7LvlOAP; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755988AbeASPu0 (ORCPT + 99 others); Fri, 19 Jan 2018 10:50:26 -0500 Received: from mail-pg0-f45.google.com ([74.125.83.45]:45552 "EHLO mail-pg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755779AbeASPuD (ORCPT ); Fri, 19 Jan 2018 10:50:03 -0500 Received: by mail-pg0-f45.google.com with SMTP id c194so1703603pga.12; Fri, 19 Jan 2018 07:50:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=y/KEHUIVcl0+vMJN6gw1WkbiSc9oJYyUBarGut2ZNnA=; b=u7LvlOAPmx6UVsDLo2blKOC7aWCyopJq/vx7kDWe0wZmZ7lRKRTiit3iQ+N7voTae1 dk/sAWaTpMtkMu6gYBKr/LaxtX/UV5vnzaviTAFTwBm1KSJuNl2cL7WzNyL6eGuPahPY bxSAqE2TTn/H7chc/s9ieemwcwjU2AwPl1PztFbErMVD4ZV//Gl6M/zpcPe8KkTNoNQY GqG6fGmBNPvb+yR6yp+mrguOW0CppTmxE+bbHklmzMqqDNPk85diB1iAyxz4qJ6oWfjs tBqEUu8HNN7YQAJPSaJ+qBcMQ0qJEGaRh17KbelTVCUXFMfA4zlmp/PycYfmRGgb5FQd DBDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=y/KEHUIVcl0+vMJN6gw1WkbiSc9oJYyUBarGut2ZNnA=; b=aQpHUzfuFbkPI/w0Y/5D7f5aWdyuS/hhaho66m79b1qS0/WoDU67ncQZrOXMN73vGn Or4RUaUJZdWdDKB9jRw6gu2qGKn+rNwacP5/M0i/9wAfgsfnAEwgeVcUtczyqWdYWRev Kv+AYivUbcIFj2XDNY4n33aGagOJRZEZcoX94rpLfd9zpcZkQ8aq8OhzqtZxpq82MTiX /g/a2LMpQYErxYWxuuZLaw+gUxTeJCfJS1+oSrO+AGs31O47spdDjrFlFtm9KIzfsIoT +vRtDxMfTYdsqNIiDzzMK/gH+0ttZtp6eVAsclfKQJ+TtGtQHEBjvuRUTadsapzESfB+ KsMw== X-Gm-Message-State: AKGB3mJJaLf6Vu8LfteXgo/P+3Je2GwMPZNK5Zb0J7T+CbuDUwkOdwkp 5ohY2yVV4syhpJk2JZ29vW29sA== X-Received: by 10.99.97.210 with SMTP id v201mr36409414pgb.344.1516377002694; Fri, 19 Jan 2018 07:50:02 -0800 (PST) Received: from [10.1.104.125] ([207.198.105.19]) by smtp.googlemail.com with ESMTPSA id f78sm18726775pfk.144.2018.01.19.07.50.01 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 19 Jan 2018 07:50:01 -0800 (PST) Message-ID: <1516376999.3606.39.camel@gmail.com> Subject: Re: [PATCH] net/mlx4_en: ensure rx_desc updating reaches HW before prod db updating From: Eric Dumazet To: "jianchao.wang" , Tariq Toukan , Jason Gunthorpe Cc: junxiao.bi@oracle.com, netdev@vger.kernel.org, linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org, Saeed Mahameed Date: Fri, 19 Jan 2018 07:49:59 -0800 In-Reply-To: <53b1ac4d-a294-eb98-149e-65d7954243da@oracle.com> References: <1515728542-3060-1-git-send-email-jianchao.w.wang@oracle.com> <20180112163247.GB15974@ziepe.ca> <1515775567.131759.42.camel@gmail.com> <53b1ac4d-a294-eb98-149e-65d7954243da@oracle.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2018-01-19 at 23:16 +0800, jianchao.wang wrote: > Hi Tariq > > Very sad that the crash was reproduced again after applied the patch. > > --- a/drivers/net/ethernet/mellanox/mlx4/en_rx.c > +++ b/drivers/net/ethernet/mellanox/mlx4/en_rx.c > @@ -252,6 +252,7 @@ static inline bool mlx4_en_is_ring_empty(struct mlx4_en_rx_ring *ring) > > static inline void mlx4_en_update_rx_prod_db(struct mlx4_en_rx_ring *ring) > { > + dma_wmb(); So... is wmb() here fixing the issue ? > *ring->wqres.db.db = cpu_to_be32(ring->prod & 0xffff); > } > > I analyzed the kdump, it should be a memory corruption. > > Thanks > Jianchao > On 01/15/2018 01:50 PM, jianchao.wang wrote: > > Hi Tariq > > > > Thanks for your kindly response. > > > > On 01/14/2018 05:47 PM, Tariq Toukan wrote: > > > Thanks Jianchao for your patch. > > > > > > And Thank you guys for your reviews, much appreciated. > > > I was off-work on Friday and Saturday. > > > > > > On 14/01/2018 4:40 AM, jianchao.wang wrote: > > > > Dear all > > > > > > > > Thanks for the kindly response and reviewing. That's really appreciated. > > > > > > > > On 01/13/2018 12:46 AM, Eric Dumazet wrote: > > > > > > Does this need to be dma_wmb(), and should it be in > > > > > > mlx4_en_update_rx_prod_db ? > > > > > > > > > > > > > > > > +1 on dma_wmb() > > > > > > > > > > On what architecture bug was observed ? > > > > > > > > This issue was observed on x86-64. > > > > And I will send a new patch, in which replace wmb() with dma_wmb(), to customer > > > > to confirm. > > > > > > +1 on dma_wmb, let us know once customer confirms. > > > Please place it within mlx4_en_update_rx_prod_db as suggested. > > > > Yes, I have recommended it to customer. > > Once I get the result, I will share it here. > > > All other calls to mlx4_en_update_rx_prod_db are in control/slow path so I prefer being on the safe side, and care less about bulking the barrier. > > > > > > Thanks, > > > Tariq > > >