From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,T_DKIMWL_WL_HIGH,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 83E21C3279B for ; Wed, 4 Jul 2018 04:11:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 37787246FD for ; Wed, 4 Jul 2018 04:11:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="mEYk7iye" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 37787246FD Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753664AbeGDELM (ORCPT ); Wed, 4 Jul 2018 00:11:12 -0400 Received: from mail.kernel.org ([198.145.29.99]:55964 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753617AbeGDELH (ORCPT ); Wed, 4 Jul 2018 00:11:07 -0400 Received: from localhost (unknown [171.76.122.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9E85C246FD; Wed, 4 Jul 2018 04:11:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1530677467; bh=Rx/mz+J1tDUUF4Kz4bE+DhONcLWbfL5Q9EWEjVjqb6Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mEYk7iyeTnN+1qCZwzc/fR3ZpeqKav7UUDzNkoK/u747h2U1y7nJxxKb0RNHIby5P 27rtmWQXZyeEGKdkC8Yr6R7t/AVW4Aut9s+/080aR6DHD8OBrMbTTO9rzyj0xfITeZ BgPLzZJbVVB0yqnjNiAKUudL2jy0Npx+ty62FozQ= Date: Wed, 4 Jul 2018 09:40:59 +0530 From: Vinod To: Stephan Mueller Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, Bjorn Andersson , Matt Mackall , Herbert Xu , Arnd Bergmann , Greg Kroah-Hartman , linux-arm-msm@vger.kernel.org, Stephen Boyd , Timur Tabi Subject: Re: [PATCH v3 3/6] crypto: Add Qcom prng driver Message-ID: <20180704041059.GT22377@vkoul-mobl> References: <20180703060434.19293-1-vkoul@kernel.org> <20180703060434.19293-4-vkoul@kernel.org> <2990655.vKmMgW600W@tauon.chronox.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2990655.vKmMgW600W@tauon.chronox.de> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephan, On 03-07-18, 15:28, Stephan Mueller wrote: > Am Dienstag, 3. Juli 2018, 08:04:31 CEST schrieb Vinod Koul: > > +static int qcom_rng_read(struct qcom_rng *rng, void *data, size_t max) > > +{ > > + size_t currsize = 0; > > + u32 *retdata = data; > > How can you be sure that this cast is appropriate? I.e. how is it guaranteed > that data is 4-byte aligned? While reading we check the alignment: /* make sure we stay on 32bit boundary */ if ((max - currsize) < WORD_SZ) break; > Also, the data variable in qcom_rng_generate is a u8 -- shouldn't this type be > used instead of a void? That does make sense to me. IIRC the read is for a byte. I will check this and update it Thanks for the quick review -- ~Vinod