From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757761AbcGZSWf (ORCPT ); Tue, 26 Jul 2016 14:22:35 -0400 Received: from mga04.intel.com ([192.55.52.120]:25686 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752549AbcGZSWe (ORCPT ); Tue, 26 Jul 2016 14:22:34 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,426,1464678000"; d="scan'208";a="1002960786" From: william.c.roberts@intel.com To: jason@lakedaemon.net, linux-mm@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com, akpm@linux-foundation.org Cc: keescook@chromium.org, gregkh@linuxfoundation.org, nnk@google.com, jeffv@google.com, salyzyn@android.com, dcashman@android.com Subject: [PATCH] [RFC] Introduce mmap randomization Date: Tue, 26 Jul 2016 11:22:25 -0700 Message-Id: <1469557346-5534-1-git-send-email-william.c.roberts@intel.com> X-Mailer: git-send-email 1.9.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The recent get_random_long() change in get_random_range() and then the subsequent patches Jason put out, all stemmed from my tinkering with the concept of randomizing mmap. Any feedback would be greatly appreciated, including any feedback indicating that I am idiot.