Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753127AbdF2RaH (ORCPT ); Thu, 29 Jun 2017 13:30:07 -0400 Received: from mx2.suse.de ([195.135.220.15]:36800 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751783AbdF2R36 (ORCPT ); Thu, 29 Jun 2017 13:29:58 -0400 Date: Thu, 29 Jun 2017 19:29:53 +0200 From: "Luis R. Rodriguez" To: Greg KH Cc: "Luis R. Rodriguez" , mfuzzey@parkeon.com, ebiederm@xmission.com, dmitry.torokhov@gmail.com, wagi@monom.org, dwmw2@infradead.org, jewalt@lgsinnovations.com, rafal@milecki.pl, arend.vanspriel@broadcom.com, rjw@rjwysocki.net, yi1.li@linux.intel.com, atull@kernel.org, moritz.fischer@ettus.com, pmladek@suse.com, johannes.berg@intel.com, emmanuel.grumbach@intel.com, luciano.coelho@intel.com, kvalo@codeaurora.org, luto@kernel.org, torvalds@linux-foundation.org, keescook@chromium.org, takahiro.akashi@linaro.org, dhowells@redhat.com, pjones@redhat.com, hdegoede@redhat.com, alan@linux.intel.com, tytso@mit.edu, mtk.manpages@gmail.com, paul.gortmaker@windriver.com, mtosatti@redhat.com, mawilcox@microsoft.com, linux-api@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/4] firmware: fix fallback mechanism by ignoring SIGCHLD Message-ID: <20170629172953.GN21846@wotan.suse.de> References: <20170614222017.14653-1-mcgrof@kernel.org> <20170629151442.GA4880@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170629151442.GA4880@kroah.com> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 553 Lines: 13 On Thu, Jun 29, 2017 at 05:14:42PM +0200, Greg KH wrote: > On Wed, Jun 14, 2017 at 03:20:13PM -0700, Luis R. Rodriguez wrote: > > Martin reported an issue with Android where if sysfs is used to trigger a sync > > fw load which *relies* on the fallback mechanism and a background job completes > > while the trigger is ongoing in the foreground it will immediately fail the fw > > request. The issue can be observed in this simple test script using the > > test_firmware driver: > > Please respin this with the swait code removed. Sure thing. Luis