From: Bryan O'Donoghue Subject: Re: [PATCH v3 2/5] crypto: caam: Fix endless loop when RNG is already initialized Date: Fri, 2 Feb 2018 11:20:56 +0000 Message-ID: <78ad6a62-190c-e4fe-dd23-e1d058f9bbb2@nexus-software.ie> References: <1517364040-27607-1-git-send-email-pure.logic@nexus-software.ie> <1517364040-27607-3-git-send-email-pure.logic@nexus-software.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2; format=flowed Content-Transfer-Encoding: 8bit Cc: Fabio Estevam , Peng Fan , "davem@davemloft.net" , "lukas.auer@aisec.fraunhofer.de" , "rui.silva@linaro.org" , "ryan.harkin@linaro.org" , Herbert Xu To: =?UTF-8?Q?Horia_Geant=c4=83?= , Aymen Sghaier , "linux-crypto@vger.kernel.org" , "linux-kernel@vger.kernel.org" Return-path: In-Reply-To: Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org On 01/02/18 12:16, Horia Geant? wrote: > If the loop cannot exit based on value of "ret" != -EAGAIN, then it means > caam_probe() will eventually fail due to ret == -EAGAIN: > if (ret) { > dev_err(dev, "failed to instantiate RNG"); > goto caam_remove; > } For me it's an endless loop applying the first two https://patchwork.ozlabs.org/patch/866460/ https://patchwork.ozlabs.org/patch/866462/ but not this one https://patchwork.ozlabs.org/patch/865890/ > Please provide more details, so that the root cause is found and fixed. np --- bod