From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Stable <stable@vger.kernel.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: [PATCH for-4.9.y 04/14] random: convert get_random_int/long into get_random_u32/u64
Date: Sun, 16 Sep 2018 15:29:47 +0200 [thread overview]
Message-ID: <20180916132947.GA6061@kroah.com> (raw)
In-Reply-To: <1535487205-26280-5-git-send-email-amit.pundir@linaro.org>
On Wed, Aug 29, 2018 at 01:43:15AM +0530, Amit Pundir wrote:
> From: "Jason A. Donenfeld" <Jason@zx2c4.com>
>
> 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
next prev parent reply other threads:[~2018-09-16 18:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 20:13 [PATCH for-4.9.y 00/14] Few upstream fixes from OnePlus6's kernel tree Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 01/14] cfq: Give a chance for arming slice idle timer in case of group_idle Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 02/14] kthread: Fix use-after-free if kthread fork fails Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 03/14] kthread: fix boot hang (regression) on MIPS/OpenRISC Amit Pundir
2018-08-28 20:13 ` [OpenRISC] " Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 04/14] random: convert get_random_int/long into get_random_u32/u64 Amit Pundir
2018-09-16 13:29 ` Greg KH [this message]
2018-08-28 20:13 ` [PATCH for-4.9.y 05/14] staging: rt5208: Fix a sleep-in-atomic bug in xd_copy_page Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 06/14] staging/rts5208: Fix read overflow in memcpy Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 07/14] IB/rxe: do not copy extra stack memory to skb Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 08/14] block,blkcg: use __GFP_NOWARN for best-effort allocations in blkcg Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 09/14] nl80211: fix null-ptr dereference on invalid mesh configuration Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 10/14] locking/rwsem-xadd: Fix missed wakeup due to reordering of load Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 11/14] selinux: use GFP_NOWAIT in the AVC kmem_caches Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 12/14] locking/osq_lock: Fix osq_lock queue corruption Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 13/14] mm, vmscan: clear PGDAT_WRITEBACK when zone is balanced Amit Pundir
2018-08-28 20:13 ` [PATCH for-4.9.y 14/14] mm: remove seemingly spurious reclaimability check from laptop_mode gating Amit Pundir
2018-09-16 13:36 ` [PATCH for-4.9.y 00/14] Few upstream fixes from OnePlus6's kernel tree Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180916132947.GA6061@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=amit.pundir@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.