Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753269Ab3H0IgW (ORCPT ); Tue, 27 Aug 2013 04:36:22 -0400 Received: from cantor2.suse.de ([195.135.220.15]:57472 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752895Ab3H0IgS (ORCPT ); Tue, 27 Aug 2013 04:36:18 -0400 Date: Tue, 27 Aug 2013 10:36:09 +0200 (CEST) From: Jiri Kosina X-X-Sender: jkosina@pobox.suse.cz To: Pavel Machek Cc: joeyli , linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-efi@vger.kernel.org, linux-pm@vger.kernel.org, linux-crypto@vger.kernel.org, opensuse-kernel@opensuse.org, David Howells , "Rafael J. Wysocki" , Matthew Garrett , Len Brown , Josh Boyer , Vojtech Pavlik , Matt Fleming , James Bottomley , Greg KH , Rusty Russell , Herbert Xu , "David S. Miller" , "H. Peter Anvin" , Michal Marek , Gary Lin , Vivek Goyal Subject: Re: [PATCH 03/18] asymmetric keys: separate the length checking of octet string from RSA_I2OSP In-Reply-To: <20130826112737.GA18300@amd.pavel.ucw.cz> Message-ID: References: <1377169317-5959-1-git-send-email-jlee@suse.com> <1377169317-5959-4-git-send-email-jlee@suse.com> <20130825160147.GB5171@amd.pavel.ucw.cz> <1377512731.27967.34.camel@linux-s257.site> <20130826112737.GA18300@amd.pavel.ucw.cz> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1741 Lines: 46 On Mon, 26 Aug 2013, Pavel Machek wrote: > > > > Due to RSA_I2OSP is not only used by signature verification path but also used > > > > in signature generation path. So, separate the length checking of octet string > > > > because it's not for generate 0x00 0x01 leading string when used in signature > > > > generation. > > > > > > > > Reviewed-by: Jiri Kosina > > > > Signed-off-by: Lee, Chun-Yi > > > > > > > +static int RSA_I2OSP(MPI x, size_t xLen, u8 **_X) > > > > +{ > > > > + unsigned x_size; > > > > + unsigned X_size; > > > > + u8 *X = NULL; > > > > > > Is this kernel code or entry into obfuscated C code contest? This is not funny. > > > > > The small "x" is the input integer that will transfer to big "X" that is > > a octet sting. > > > > Sorry for I direct give variable name to match with spec, maybe I need > > use big_X or.... > > Having variables that differ only in case is confusing. Actually > RSA_I2OSP is not a good name for function, either. > > If it converts x into X, perhaps you can name one input and second output? The variable naming is according to spec, and I believe it makes sense to keep it so, no matter how stupid the naming in the spec might be. Otherwise you have to do mental remapping when looking at the code and the spec at the same time, which is very inconvenient. Would a comment next to the variable declaration, that would point this fact out, be satisfactory for you? -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/