Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754907AbaJUKI5 (ORCPT ); Tue, 21 Oct 2014 06:08:57 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:43987 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751283AbaJUKIz (ORCPT ); Tue, 21 Oct 2014 06:08:55 -0400 X-Sasl-enc: usDHosPNY6NThobSUXrOhYX6hPOGgGZasB4chry8ccc4 1413886134 Message-ID: <1413886132.32553.14.camel@localhost> Subject: Re: RCU stall in af_unix.c, should use spin_lock_irqsave? From: Hannes Frederic Sowa To: Thomas Petazzoni Cc: "David S. Miller" , Eric Dumazet , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Alexandre FOURNIER , Ezequiel Garcia , Marcin Wojtas , Gregory =?ISO-8859-1?Q?Cl=E9ment?= Date: Tue, 21 Oct 2014 12:08:52 +0200 In-Reply-To: <20141021100313.397f4962@free-electrons.com> References: <20141021100313.397f4962@free-electrons.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 (3.10.4-4.fc20) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Di, 2014-10-21 at 10:03 +0200, Thomas Petazzoni wrote: > So, the question is: is this patch the correct solution (but then other > usage of spin_lock in af_unix.c might also need fixing) ? Or is the > network driver at fault? It feels like a false positive. Do you see one core spinning tightly on a lock? Does the system get unusable? Bye, Hannes -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/