[PATCH 19/33] x86, pkeys: check VMAs and PTEs for protection keys
From: Dave Hansen <dave.hansen@linux.intel.com> Today, for normal faults and page table walks, we check the VMA and/or PTE to ensure that it is compa
View Article[PATCH 20/33] mm: do not enforce PKEY permissions on "foreign" mm...
From: Dave Hansen <dave.hansen@linux.intel.com> We try to enforce protection keys in software the same way that we do in hardware. (See long example
View Article[PATCH 21/33] x86, pkeys: optimize fault handling in access_error()
From: Dave Hansen <dave.hansen@linux.intel.com> We might not strictly have to make modifictions to access_error() to check the VMA here. If we do no
View Article[PATCH 22/33] x86, pkeys: differentiate instruction fetches
From: Dave Hansen <dave.hansen@linux.intel.com> As discussed earlier, we attempt to enforce protection keys in software. However, the code checks al
View Article[PATCH 23/33] x86, pkeys: dump PKRU with other kernel registers
From: Dave Hansen <dave.hansen@linux.intel.com> Protection Keys never affect kernel mappings. But, they can affect whether the kernel will fault whe
View Article[PATCH 24/33] x86, pkeys: dump pkey from VMA in /proc/pid/smaps
From: Dave Hansen <dave.hansen@linux.intel.com> The protection key can now be just as important as read/write permissions on a VMA. We need some deb
View Article[PATCH 25/33] x86, pkeys: add Kconfig prompt to existing config option
From: Dave Hansen <dave.hansen@linux.intel.com> I don't have a strong opinion on whether we need this or not. Protection Keys has relatively little c
View Article[PATCH 26/33] x86, pkeys: actually enable Memory Protection Keys in CPU
From: Dave Hansen <dave.hansen@linux.intel.com> This sets the bit in 'cr4' to actually enable the protection keys feature. We also include a boot-ti
View Article[PATCH 27/33] mm, multi-arch: pass a protection key in to calc_vm_flag_bits()
From: Dave Hansen <dave.hansen@linux.intel.com> This plumbs a protection key through calc_vm_flag_bits(). We could have done this in calc_vm_prot_bi
View Article[PATCH 28/33] x86, pkeys: add arch_validate_pkey()
From: Dave Hansen <dave.hansen@linux.intel.com> The syscall-level code is passed a protection key and need to return an appropriate error code if the
View Article[PATCH 29/33] x86: separate out LDT init from context init
From: Dave Hansen <dave.hansen@linux.intel.com> The arch-specific mm_context_t is a great place to put protection-key allocation state. But, we need
View Article[PATCH 30/33] x86, fpu: allow setting of XSAVE state
From: Dave Hansen <dave.hansen@linux.intel.com> We want to modify the Protection Key rights inside the kernel, so we need to change PKRU's contents.
View Article[PATCH 31/33] x86, pkeys: allow kernel to modify user pkey rights register
From: Dave Hansen <dave.hansen@linux.intel.com> The Protection Key Rights for User memory (PKRU) is a 32-bit user-accessible register. It contains t
View Article[PATCH 32/33] x86, pkeys: create an x86 arch_calc_vm_prot_bits() for VMA flags
From: Dave Hansen <dave.hansen@linux.intel.com> calc_vm_prot_bits() takes PROT_{READ,WRITE,EXECUTE} bits and turns them in to the vma->vm_flags/VM_*
View Article[PATCH 33/33] x86, pkeys: execute-only support
From: Dave Hansen <dave.hansen@linux.intel.com> Protection keys provide new page-based protection in hardware. But, they have an interesting attribut
View Article[PATCH v2 0/3] iProc I2C driver enhancement
This patch series 1) adds recovery support to the I2C host controller; 2) fix a typo in the driver; and 3) adds support for large TX payload size Thi
View Article[PATCH v2 1/3] i2c: iproc: Add recovery mechanism in error case
From: Ray Jui <rjui@broadcom.com> Add proper recovery mechanism to the iProc I2C driver in error cases Signed-off-by: Icarus Chau <ichau@broadcom.co
View Article[PATCH v2 2/3] i2c: iproc: Fix typo in the driver
From: Ray Jui <rjui@broadcom.com> Fix typo in the driver from 'I2C_TIMEOUT_MESC' to 'I2C_TIMEOUT_MSEC' Signed-off-by: Ray Jui <rjui@broadcom.com> Re
View Article[PATCH v2 3/3] i2c: iproc: Support larger TX transfer
From: Ray Jui <rjui@broadcom.com> The current iProc I2C driver only allows each TX transfer up to 63 bytes (the TX FIFO has a size of 64 bytes, and o
View Article[PATCH] branch tracer: fix freak link error
In my randconfig tests, I came across a bug that involves several components: * gcc-4.9 through at least 5.3 * CONFIG_GCOV_PROFILE_ALL enabling -fpro
View Article
