[RFC PATCH v2 2/2] Architecture defined limit on memory region random shift.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: [RFC PATCH v2 2/2] Architecture defined limit on memory region random shift.
From: akpm@xxxxxxxxxxxxxxxxxxxx (Andrew Morton)
Date: Thu, 22 Mar 2018 13:54:48 -0700
In-reply-to: <1521736598-12812-3-git-send-email-blackzert@gmail.com>
References: <1521736598-12812-1-git-send-email-blackzert@gmail.com> <1521736598-12812-3-git-send-email-blackzert@gmail.com>

Please add changelogs.  An explanation of what a "limit on memory
region random shift" is would be nice ;) Why does it exist, why are we
doing this, etc.  Surely there's something to be said - at present this
is just a lump of random code?

Follow-Ups:
- [RFC PATCH v2 2/2] Architecture defined limit on memory region random shift.
  - From: Ilya Smith

References:
- [RFC PATCH v2 0/2] Randomization of address chosen by mmap.
  - From: Ilya Smith
- [RFC PATCH v2 2/2] Architecture defined limit on memory region random shift.
  - From: Ilya Smith

Prev by Date: [RFC PATCH v2 1/2] Randomization of address chosen by mmap.
Next by Date: [RFC PATCH v2 0/2] Randomization of address chosen by mmap.
Previous by thread: [RFC PATCH v2 2/2] Architecture defined limit on memory region random shift.
Next by thread: [RFC PATCH v2 2/2] Architecture defined limit on memory region random shift.
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]

Powered by Linux