From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio Estevam Subject: Re: [PATCH 0/3] URGENT for 3.9: net: fec: revert NAPI introduction Date: Fri, 19 Apr 2013 15:22:38 -0300 Message-ID: References: <1366382164-10968-1-git-send-email-l.stach@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: netdev@vger.kernel.org, David Miller , Frank Li , Shawn Guo To: Lucas Stach Return-path: Received: from mail-vb0-f52.google.com ([209.85.212.52]:46359 "EHLO mail-vb0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752945Ab3DSSWj (ORCPT ); Fri, 19 Apr 2013 14:22:39 -0400 Received: by mail-vb0-f52.google.com with SMTP id w8so3983614vbf.11 for ; Fri, 19 Apr 2013 11:22:39 -0700 (PDT) In-Reply-To: <1366382164-10968-1-git-send-email-l.stach@pengutronix.de> Sender: netdev-owner@vger.kernel.org List-ID: Hi Lucas, On Fri, Apr 19, 2013 at 11:36 AM, Lucas Stach wrote: > Those patches introduce instability to the point of kernel OOPSes with > NULL-ptr dereferences. > > The patches drop locks from the code without justifying why this would > be safe at all. In fact it isn't safe as now the controller restart can > happily free the RX and TX ring buffers while the NAPI poll function is > still accessing them. So with a heavily loaded but slightly instable > link we regularly end up with OOPSes because link change restarts > the FEC and bombs away buffers still in use. Can you please let us know how to reproduce the oopses? Which SoC did you use in your tests?