From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965180AbdCWPqk (ORCPT ); Thu, 23 Mar 2017 11:46:40 -0400 Received: from s3.sipsolutions.net ([5.9.151.49]:42710 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933773AbdCWPqk (ORCPT ); Thu, 23 Mar 2017 11:46:40 -0400 Message-ID: <1490283997.2766.11.camel@sipsolutions.net> Subject: Re: deadlock in synchronize_srcu() in debugfs? From: Johannes Berg To: paulmck@linux.vnet.ibm.com Cc: linux-kernel , Nicolai Stange , gregkh Date: Thu, 23 Mar 2017 16:46:37 +0100 In-Reply-To: <20170323153758.GE3637@linux.vnet.ibm.com> References: <1490280886.2766.4.camel@sipsolutions.net> <20170323153758.GE3637@linux.vnet.ibm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.4-1 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 Thu, 2017-03-23 at 08:37 -0700, Paul E. McKenney wrote: > I have not seen this, but my usual question for __synchronize_srcu() > is if some other task is blocked holding srcu_read_lock() for that > same srcu_struct. > Not as far as I can see - but that was the scenario I was outlining in my second email, I guess. I'll need to reproduce it and a get a fuller view of the system, I only have the "echo w > sysrq-trigger" output right now. Thanks, johannes