Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754051AbcKJG5q (ORCPT ); Thu, 10 Nov 2016 01:57:46 -0500 Received: from pic75-3-78-194-244-226.fbxo.proxad.net ([78.194.244.226]:47660 "EHLO mail.corsac.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752941AbcKJG5o (ORCPT ); Thu, 10 Nov 2016 01:57:44 -0500 Message-ID: <1478761052.31531.1.camel@corsac.net> Subject: Re: [PATCH] firmware: fix async/manual firmware loading From: Yves-Alexis Perez To: "Luis R. Rodriguez" , Matt Domsch , Fengguang Wu , Richard Purdie , Jacek Anaszewski , linux-leds@vger.kernel.org, Abhay Salunke , David Woodhouse Cc: linux-kernel@vger.kernel.org, Ming Lei , Greg Kroah-Hartman , Johannes Berg , Jouni Malinen , Kees Cook , Jiri Kosina , Jiri Slaby , Tom Gundersen , Kay Sievers , Josh Boyer , Dmitry Torokhov , Andy Lutomirski , Harald Hoyer , Seth Forshee , Bjorn Andersson , Linus Torvalds , Daniel Wagner , stable@vger.kernel.org Date: Thu, 10 Nov 2016 07:57:32 +0100 In-Reply-To: <20161109220210.GJ13978@wotan.suse.de> References: <20161030145048.6291-1-corsac@corsac.net> <20161030145048.6291-2-corsac@corsac.net> <1477848538.3456.1.camel@corsac.net> <20161109203656.GG13978@wotan.suse.de> <20161109220210.GJ13978@wotan.suse.de> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-iDvmpXioHZZmWg0FUyXa" X-Mailer: Evolution 3.22.2-1 Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1879 Lines: 51 --=-iDvmpXioHZZmWg0FUyXa Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2016-11-09 at 23:02 +0100, Luis R. Rodriguez wrote: > Actually... we also set the timeout to MAX_JIFFY_OFFSET when FW_OPT_UEVEN= T is > not set. This happens *only* when the UMH was explicitly requested on the > async call, when the second argument to request_firmware_nowait() is fals= e. > There are *only* two callers that do this in the kernel. If this is corre= ct *and* > the assessment of the cast from long to int here is correct that should m= ean > these two callers in the kernel that have always requested the UMH firmwa= re > *fallback* have *always* had a faulty UMH fallback return value... Thanks for all your mails. Yes, that was my case here, and I noticed it loo= ked broken for a long time, I didn't investigate who was using it in the kernel but I had the feeling it was a bit of an abuse of the infrastructure. I sti= ll reported the bug because the quick fix looked OK but I can understand the w= ill to actually rethink if and how this part is really needed. Maybe I need to wait a bit before resubmitting any patch with rephrased com= mit log to see where this is going? Regards, --=20 Yves-Alexis --=-iDvmpXioHZZmWg0FUyXa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQEcBAABCAAGBQJYJBpcAAoJEG3bU/KmdcClgOcH/31VeRfRLWyByQBPoETNsNXz mn2qy35bu1fLe6gEbjRixsq0465j3fStUxlrzKXOGP8zusObMP5ptBDPwJvRWscC E2zVBs9IYKvZ6H1ycZHEvvV2q5tWw32fWuOp4tYTeO6MLcu5L0XncgkklWQjrZnd PSY9bRQxwW0pf7LDKRTFGW5KYY8NplhS5DG3T+fQqwdnuNSbmipSU/6OhMfiaB9I qHysT7IFz2iC6MONYuzEmo0mquGpZ2E91dNBz2N77KxCeGiP/NI0dextxmcj3xFE wZmVC/jgXMsfw036xmUxUCY9Qm6rpQwN8PMitl53xwB+03ZOlYskfVO7zPA5lA0= =xDH1 -----END PGP SIGNATURE----- --=-iDvmpXioHZZmWg0FUyXa--