From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:34120 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728350AbeIPSwt (ORCPT ); Sun, 16 Sep 2018 14:52:49 -0400 Date: Sun, 16 Sep 2018 15:29:47 +0200 From: Greg KH To: Amit Pundir Cc: Stable , "Jason A. Donenfeld" , Theodore Ts'o Subject: Re: [PATCH for-4.9.y 04/14] random: convert get_random_int/long into get_random_u32/u64 Message-ID: <20180916132947.GA6061@kroah.com> References: <1535487205-26280-1-git-send-email-amit.pundir@linaro.org> <1535487205-26280-5-git-send-email-amit.pundir@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1535487205-26280-5-git-send-email-amit.pundir@linaro.org> Sender: stable-owner@vger.kernel.org List-ID: On Wed, Aug 29, 2018 at 01:43:15AM +0530, Amit Pundir wrote: > From: "Jason A. Donenfeld" > > commit c440408cf6901eeb2c09563397e24a9097907078 upstream. > > Many times, when a user wants a random number, he wants a random number > of a guaranteed size. So, thinking of get_random_int and get_random_long > in terms of get_random_u32 and get_random_u64 makes it much easier to > achieve this. It also makes the code simpler. > > On 32-bit platforms, get_random_int and get_random_long are both aliased > to get_random_u32. On 64-bit platforms, int->u32 and long->u64. What bug is this fixing that it needs to be in a stable kernel tree? The end result is the same before and after this patch, right? thanks, greg k-h