Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964872AbcJ0S7n (ORCPT ); Thu, 27 Oct 2016 14:59:43 -0400 Received: from mail-yw0-f195.google.com ([209.85.161.195]:35383 "EHLO mail-yw0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934141AbcJ0S7l (ORCPT ); Thu, 27 Oct 2016 14:59:41 -0400 Date: Thu, 27 Oct 2016 14:59:35 -0400 From: Tejun Heo To: Rob Herring Cc: Corentin Labbe , "linux-ide@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Greg Kroah-Hartman Subject: Re: [RFC PATCH] ata: piix: wait for end of asynchronous probing before Message-ID: <20161027185935.GA17657@htj.duckdns.org> References: <1476722704-12839-1-git-send-email-clabbe.montjoie@gmail.com> <20161019172848.GD18532@htj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.0 (2016-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 753 Lines: 20 Hello, Rob. On Thu, Oct 27, 2016 at 01:55:19PM -0500, Rob Herring wrote: > Seems like this is mixing async drv probe and async scsi scan and the > problem is in the latter? I don't think async drv probe should have > any problems. If a driver probe starts some async operation, then it > seems to me that it is its responsibility to wait for completion in > remove(). I'm not sure about that. The async operation synchronization isn't per-driver or module. Both during boot and module operations, they're synchronized globally, which makes sense given its purpose and that's also why we don't see these brekages without this debug option. It doesn't make sense to me to add a whole new set of behaviors just for a debug option. Thanks. -- tejun