On Mon, Nov 06, 2017 at 11:28:55AM +0800, Yu Chen wrote:
> From: Yu Chen
>
> Check vdev->real_port 0 to avoid panic
> [9.261347] []
> xhci_free_virt_devices_depth_first+0x58/0x108
> [9.261352] [] xhci_mem_cleanup+0x1bc/0x570
> [9.261355] [] xhci_stop+0x140/0x1c8
> [9.261365] [] u
On Mon, Nov 06, 2017 at 08:35:41AM +0800, Lu Baolu wrote:
> Hi,
>
> On 11/03/2017 02:27 PM, Greg Kroah-Hartman wrote:
> > On Fri, Nov 03, 2017 at 08:45:46AM +0800, Lu Baolu wrote:
> >> Hi,
> >>
> >> On 11/03/2017 12:51 AM, Greg Kroah-Hartman wrote:
> >>> On Thu, Nov 02, 2017 at 12:38:57PM +0200, F
Hi Joel,
On 4 November 2017 at 06:44, Joel Fernandes wrote:
> On Wed, Nov 1, 2017 at 12:35 PM, Steve Muckle wrote:
>> On 10/30/2017 12:02 PM, Joel Fernandes wrote:
Also, this more looks like a policy decision. Will it be better to
put that directly into schedutil? Like this:
On Sun, Nov 05, 2017 at 05:51:34PM +0100, Mylène Josserand wrote:
> i2c1 and i2c2 bits for CCU are not bit 0 but bit 1 and bit 2.
> Because of that, the i2c0 (bit 0) was not correctly configured.
> Fixed the correct bits for i2c1 and i2c2.
>
> Fixes: 05359be1176b ("clk: sunxi-ng: Add driver for A8
From: Markus Elfring
Date: Sun, 5 Nov 2017 22:03:22 +0100
* Adjust jump targets so that a call of the function "mutex_unlock"
can be better reused for error cases at the end of this function.
* Replace three calls by goto statements.
This issue was detected by using the Coccinelle software.
> On 6 Nov 2017, at 06:58, Andreas Färber wrote:
>
>> Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
>>> On 4 November 2017 at 20:06, Andreas Färber wrote:
Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
> On 4 November 2017 at 15:30, Andreas Färber wrote:
>> Am 04.11.2017 um 22:5
On (11/06/17 13:25), Liu, Changcheng wrote:
> kaslr feature is enabled in kernel.
> Remove kernel text address when dumping idle IP info
>
> Signed-off-by: Liu Changcheng
> Signed-off-by: Jerry Liu
>
> diff --git a/lib/nmi_backtrace.c b/lib/nmi_backtrace.c
> index 0bc0a35..9cc4178 100644
> ---
Hi Jason,
On Nov 03 2017 or thereabouts, Jason Gerecke wrote:
> On November 3, 2017 10:29:47 AM PDT, Benjamin Tissoires
> wrote:
> >The Dell Canvas exports 2 collections for the Pen part. The only
> >difference between the 2 is that the default one has half the
> >resolution
> >of the second one
On 28 October 2017 at 00:17, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The motivation for this change is to provide a way to work around
> a problem with the direct-complete mechanism used for avoiding
> system suspend/resume handling for devices in runtime suspend.
>
> The problem i
When update data reached the threshold for data processing,
we must inform that processing is on going.
Signed-off-by: Lionel Debieve
---
drivers/crypto/stm32/stm32-hash.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/drivers/crypto/stm32/stm32-hash.c
b/drivers/cryp
On 28 October 2017 at 00:22, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Define and document a SMART_SUSPEND flag to instruct bus types and PM
> domains that the system suspend callbacks provided by the driver can
> cope with runtime-suspended devices, so from the driver's perspective
On 2017/11/6 15:59, Greg KH wrote:
>>
>> diff --git a/drivers/usb/host/xhci-mem.c b/drivers/usb/host/xhci-mem.c
>> index 2a82c927ded2..295789d993b0 100644
>> --- a/drivers/usb/host/xhci-mem.c
>> +++ b/drivers/usb/host/xhci-mem.c
>> @@ -947,6 +947,11 @@ void xhci_free_virt_devices_depth_first(stru
On Nov 02 2017 or thereabouts, Sébastien Szymanski wrote:
> When everything goes smoothly, ret is set to 0 which makes the function
> to return EIO error.
>
> Fixes: 8e9faa15469e ("HID: cp2112: fix gpio-callback error handling")
> Signed-off-by: Sébastien Szymanski
> ---
> drivers/hid/hid-cp2112
On Nov 02 2017 or thereabouts, Sébastien Szymanski wrote:
> Otherwise, with HIDRAW=n, the probe function crashes because of null
> dereference of hdev->hidraw.
>
> Fixes: 42cb6b35b9e6 ("HID: cp2112: use proper hidraw name with minor number")
> Signed-off-by: Sébastien Szymanski
Patches 1 and 2 (
On 11/03/2017 06:55 PM, Tetsuo Handa wrote:
I'm commenting without understanding the logic.
Wei Wang wrote:
+
+bool xb_preload(gfp_t gfp);
+
Want __must_check annotation, for __radix_tree_preload() is marked
with __must_check annotation. By error failing to check result of
xb_preload() will le
t; Since the patch wasn't accepted, i want to know is there another solution?
The patch should be in next-20171106
--
Michal Hocko
SUSE Labs
On Sun, Nov 05, 2017 at 04:39:22PM +0100, Philippe Ombredanne wrote:
> On Sun, Nov 5, 2017 at 2:51 PM, Greg Kroah-Hartman
> wrote:
> > On Sun, Nov 05, 2017 at 01:53:54PM +0100, Philippe Ombredanne wrote:
> >> On Sat, Nov 4, 2017 at 11:40 AM, Greg Kroah-Hartman
> >> wrote:
> >> > On Fri, Nov 03, 2
On 11/04/2017 07:28 PM, Tetsuo Handa wrote:
Wei Wang wrote:
On 11/03/2017 07:25 PM, Tetsuo Handa wrote:
If this is inside vb->balloon_lock mutex (isn't this?), xb_set_page() must not
use __GFP_DIRECT_RECLAIM allocation, for leak_balloon_sg_oom() will be blocked
on vb->balloon_lock mutex.
OK. Si
Hi Colin
Thank you for the patch.
On 29/10/17 14:43, Colin King wrote:
> From: Colin Ian King
>
> Pointer pix is being initialized to a value and a little later
> being assigned the same value again. Remove the initial assignment to
> avoid a duplicate assignment. Cleans up the clang warning:
>
From: Yu Chen
Check vdev->real_port 0 to avoid panic
[9.261347] []
xhci_free_virt_devices_depth_first+0x58/0x108
[9.261352] [] xhci_mem_cleanup+0x1bc/0x570
[9.261355] [] xhci_stop+0x140/0x1c8
[9.261365] [] usb_remove_hcd+0xfc/0x1d0
[9.261369] [] xhci_plat_remove+0x6c/0xa8
[
On Mon, Nov 06, 2017 at 04:20:23PM +0800, Yu Chen wrote:
> From: Yu Chen
>
> Check vdev->real_port 0 to avoid panic
> [9.261347] []
> xhci_free_virt_devices_depth_first+0x58/0x108
> [9.261352] [] xhci_mem_cleanup+0x1bc/0x570
> [9.261355] [] xhci_stop+0x140/0x1c8
> [9.261365] [] u
On Mon, Nov 06, 2017 at 03:19:14PM +1100, Tobin C. Harding wrote:
> Hi,
>
> When parsing drivers/staging/unisys/visorbus/visorchipset.c in Greg's
> staging tree checkpatch emits
>
> --
> visorchipset.c
> --
> WARNING: char * array declaration might be better as static cons
On Mon, Nov 06, 2017 at 06:55:52AM +, Gilad Ben-Yossef wrote:
> Registers ioread/iowrite operations were done via macros,
> sometime using a "magical" implicit parameter.
>
> Replace all register access with simple inline macros.
>
> Signed-off-by: Gilad Ben-Yossef
Hi,
Nice work. I had a l
On Fri, Nov 3, 2017 at 2:20 PM, Adrian Hunter wrote:
> Until mmc has blk-mq support fully implemented and tested, add a
> parameter use_blk_mq, default to false unless config option MMC_MQ_DEFAULT
> is selected.
>
> Signed-off-by: Adrian Hunter
(...)
> +config MMC_MQ_DEFAULT
> + bool "MMC
On Fri, Nov 03, 2017 at 01:07:57PM -0700, Eric Anholt wrote:
> Kees Cook writes:
>
> > On Mon, Oct 30, 2017 at 4:49 PM, Eric Anholt wrote:
> >> Kees Cook writes:
> >>
> >>> In preparation for unconditionally passing the struct timer_list pointer
> >>> to
> >>> all timer callbacks, switch to us
On Fri, Nov 3, 2017 at 2:20 PM, Adrian Hunter wrote:
> Add error-handling comments to explain what would also be done for blk-mq
> if it used the legacy error-handling.
>
> Signed-off-by: Adrian Hunter
Reviewed-by: Linus Walleij
Safe to apply right now, during -rc8 as well.
Yours,
Linus Wall
On 05/11/2017 at 14:10, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Sun, 5 Nov 2017 14:00:52 +0100
>
> Add a jump target so that a specific error message is stored only once
> at the end of this function implementation.
> Replace two calls of the function "dev_err" by goto statements.
On Thu, Nov 02, 2017 at 04:44:47PM +0100, Maxime Ripard wrote:
> On Thu, Nov 02, 2017 at 04:51:29PM +0800, Icenowy Zheng wrote:
> > 在 2017-10-27 23:06，Icenowy Zheng 写道：
> > > This patchset adds support for the SimpleFB on Allwinner SoCs with
> > > "Display Engine 2.0".
> > >
> > > PATCH 1 to PATCH
Hi,
On Mon, 30 Oct 2017, Gustavo A. R. Silva wrote:
> Make use of the swap macro and remove unnecessary variables tmp.
> This makes the code easier to read and maintain.
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by: Gustavo A. R. Silva
> ---
> net/netfilter/ipset/
2017-08-03 0:09 GMT+08:00 Vitaly Kuznetsov :
> Changes since v9:
> - Rebase to 4.13-rc3.
> - Drop PATCH1 as it was already taken by Greg to char-misc tree. There're no
> functional dependencies on this patch so the series can go through a
> different tree
> (and it actually belongs to x86 if I
The actual_length in dwc2_hcd_urb structure is used
to indicate the total data length transferred so far,
but in dwc2_update_isoc_urb_state(), it just updates
the actual_length of isoc frame, and don't update the
urb actual_length at the same time, this will cause
device drivers working error which
issue.
> Thanks for your testing. Can I assume your Tested-by?
Yes
>
>> Since the patch wasn't accepted, i want to know is there another solution?
> The patch should be in next-20171106
>
Hi,
> +static struct pixel_format bdw_pixel_formats[] = {
> + {DRM_FORMAT_C8, 8, "8-bit Indexed"},
> +static struct pixel_format skl_pixel_formats[] = {
> + {DRM_FORMAT_YUYV, 16, "16-bit packed YUYV (8:8:8:8 MSB-
> V:Y2:U:Y1)"},
Broadwell and Skylake.
What is the state for newer chips
On Mon 06-11-17 15:04:40, Bob Liu wrote:
> On Mon, Nov 6, 2017 at 11:36 AM, Wang Nan wrote:
> > tlb_gather_mmu(&tlb, mm, 0, -1) means gathering all virtual memory space.
> > In this case, tlb->fullmm is true. Some archs like arm64 doesn't flush
> > TLB when tlb->fullmm is true:
> >
> > commit 5a
On Mon, Nov 06, 2017 at 09:40:19AM +0100, Nicolas Ferre wrote:
> If you want to lower the size of strings in this driver, you can do it,
> but not like this.
Just so we're clear, GCC already detects and combines it when you use
the same string constant twice.
regards,
dan carpenter
On 06/11/2017 08:52, Yixun Lan wrote:
> According to the datasheet, in Meson-GXBB/GXL series,
> The clock gate bit for SARADC is HHI_GCLK_MPEG2 bit[22],
> while clock gate bit for SANA is HHI_GCLK_MPEG0 bit[10].
>
> Test passed at gxl_skt dev board.
>
> Tested-by: Xingyu Chen
> Signed-off-by: Yi
Memory protection keys enable applications to protect its
address space from inadvertent access from or corruption
by itself.
These patches along with the pte-bit freeing patch series
enables the protection key feature on powerpc; 4k and 64k
hashpage kernels. It also changes the generic and x86
co
Map the key protection bits of the vma to the pkey bits in
the PTE.
The PTE bits used for pkey are 3,4,5,6 and 57. The first
four bits are the same four bits that were freed up initially
in this patch series. remember? :-) Without those four bits
this patch wouldn't be possible.
BUT, o
Store and restore the AMR, IAMR and UAMOR register state of the task
before scheduling out and after scheduling in, respectively.
Signed-off-by: Ram Pai
---
arch/powerpc/include/asm/mmu_context.h |3 ++
arch/powerpc/include/asm/pkeys.h |4 ++
arch/powerpc/include/asm/processor.h
VM_PKEY_BITx are defined only if CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS
is enabled. Powerpc also needs these bits. Hence lets define the
VM_PKEY_BITx bits for any architecture that enables
CONFIG_ARCH_HAS_PKEYS.
Signed-off-by: Ram Pai
---
fs/proc/task_mmu.c |4 ++--
include/linux/mm.h |
arch-independent code expects the arch to map
a pkey into the vma's protection bit setting.
The patch provides that ability.
Signed-off-by: Ram Pai
---
arch/powerpc/include/asm/mman.h |7 ++-
arch/powerpc/include/asm/pkeys.h | 11 +++
arch/powerpc/mm/pkeys.c |8
Make sure that the kernel does not access user pages without
checking their key-protection.
Signed-off-by: Ram Pai
---
arch/powerpc/include/asm/book3s/64/pgtable.h | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/include/asm/book3s/64/pgtable.h
This patch provides the detailed implementation for
a user to allocate a key and enable it in the hardware.
It provides the plumbing, but it cannot be used till
the system call is implemented. The next patch will
do so.
Reviewed-by: Thiago Jung Bauermann
Signed-off-by: Ram Pai
---
arch/powerp
get_mm_addr_key() helper returns the pkey associated with
an address corresponding to a given mm_struct.
Signed-off-by: Ram Pai
---
arch/powerpc/include/asm/mmu.h |9 +
arch/powerpc/mm/hash_utils_64.c | 24
2 files changed, 33 insertions(+), 0 deletions(-)
Currently the architecture specific code is expected to
display the protection keys in smap for a given vma.
This can lead to redundant code and possibly to divergent
formats in which the key gets displayed.
This patch changes the implementation. It displays the
pkey only if the archite
sys_pkey_modify() is powerpc specific system call. It
enables the ability to modify *any* attribute of a key.
Since powerpc disallows modification of IAMR from user space
an application is unable to change a key's execute-attribute.
This system call helps accomplish the above.
Signed-off
Since PowerPC and Intel both support memory protection keys, moving
the documenation to arch-neutral directory.
Signed-off-by: Ram Pai
---
Documentation/vm/protection-keys.txt | 85 +
Documentation/x86/protection-keys.txt | 85
instead of clearing the bits, pkey_disable_clear() was setting
the bits. Fixed it.
Also fixed a wrong assertion in that function. When bits are
cleared, the resulting bit value will be less than the original.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/protection_keys.c |4 ++--
1
open_hugepage_file() <- opens the huge page file
get_start_key() <-- provides the first non-reserved key.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/pkey-helpers.h| 11 +++
tools/testing/selftests/vm/protection_keys.c |6 +++---
2 files changed, 14 insertions(+), 3
This is in preparation to accomadate a differing size register
across architectures.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/pkey-helpers.h| 27 +-
tools/testing/selftests/vm/protection_keys.c | 71 ++
2 files changed, 52 insertions(+), 46 de
cleanup the code to satisfy coding styles.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/protection_keys.c | 81 ++
1 files changed, 43 insertions(+), 38 deletions(-)
diff --git a/tools/testing/selftests/vm/protection_keys.c
b/tools/testing/selftests/vm/protec
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/Makefile |1 +
tools/testing/selftests/vm/pkey-helpers.h | 220
tools/testing/selftests/vm/protection_keys.c | 1395 +
tools/testing/selftests/x86/Makefile |2 +-
tools/testing/self
introduce a new allocator that allocates 4k hardware-pages to back
64k linux-page. This allocator is only applicable on powerpc.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/protection_keys.c | 30 ++
1 files changed, 30 insertions(+), 0 deletions(-)
diff --gi
>> If you want to lower the size of strings in this driver, you can do it,
>> but not like this.
>
> Just so we're clear, GCC already detects and combines it when you use
> the same string constant twice.
Do you distinguish between merging of constants and the combination
of statements for such a
From: Thiago Jung Bauermann
This test verifies that the AMR is being written to a
process' core file.
Signed-off-by: Thiago Jung Bauermann
---
tools/testing/selftests/powerpc/ptrace/Makefile|2 +-
tools/testing/selftests/powerpc/ptrace/core-pkey.c | 438
2 files c
detect write-violation on a page to which write-disabled
key is associated much after the page is mapped.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/protection_keys.c | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/tools/testing/selftests/vm/protec
Hi,
> +/**
> + * VFIO_DEVICE_QUERY_GFX_PLANE - _IOW(VFIO_TYPE, VFIO_BASE + 14,
> + *struct
> vfio_device_query_gfx_plane)
> + *
> + * Set the drm_plane_type and flags, then retrieve the gfx plane
> info.
> + *
> + * flags supported:
> + * - VFIO_GFX_PLANE_TYPE
From: Thiago Jung Bauermann
This test exercises read and write access to the AMR.
Signed-off-by: Thiago Jung Bauermann
---
tools/testing/selftests/powerpc/include/reg.h |1 +
tools/testing/selftests/powerpc/ptrace/Makefile|5 +-
.../testing/selftests/powerpc/ptrace/ptrace-pkey
Hi Baoquan,
On Mon, Nov 06, 2017 at 10:41:43AM +0800, Baoquan He wrote:
> Is this reproduced on a machine with GART existing and passing test with
> this patch applied? Do you have a /proc/iomem printing about the machine
> you are testing on?
I've seen this on at least three different machines.
Commit-ID: c7da092a1f243bfd1bfb4124f538e69e941882da
Gitweb: https://git.kernel.org/tip/c7da092a1f243bfd1bfb4124f538e69e941882da
Author: Borislav Petkov
AuthorDate: Fri, 3 Nov 2017 11:20:28 +0100
Committer: Ingo Molnar
CommitDate: Mon, 6 Nov 2017 09:50:14 +0100
x86/mm: Define _PAGE_TABL
> - Original Message -
> Sender : Bjorn Andersson
>
> Propagate the error of devfreq_add_device() in devm_devfreq_add_device()
> rather than statically returning ENOMEM. This makes it slightly faster
> to pinpoint the cause of a returned error.
>
> Fixes: 8cd84092d35e ("PM /
detect write-violation on a page to which access-disabled
key is associated much after the page is mapped.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/protection_keys.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/tools/testing/selftests/vm/prot
detect access-violation on a page to which access-disabled
key is associated much after the page is mapped.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/protection_keys.c | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/tools/testing/selftests/
On 18/10/2017 18:49, Ganapatrao Kulkarni wrote:
Hi Arnaldo, Will,
can this be queued to next?
Is there any update on the status of this patchset? From searching the
acme git, I can only assume that it has not been merged. So we'll have
to work on top of this out-of-tree series.
John
On
Introduce powerpc implementation for the different
abstactions.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/pkey-helpers.h| 109 ++
tools/testing/selftests/vm/protection_keys.c | 38 ++
2 files changed, 117 insertions(+), 30 deletions(-)
diff --g
expected_pkey_fault() is comparing the contents of pkey
register with 0. This may not be true all the time. There
could be bits set by default by the architecture
which can never be changed. Hence compare the value against
shadow pkey register, which is supposed to track the bits
accurately all thr
On Wed, Oct 18, 2017 at 7:06 PM, Robin Murphy wrote:
> On 04/10/17 14:53, Ganapatrao Kulkarni wrote:
>> Hi Robin,
>>
>>
>> On Thu, Sep 21, 2017 at 5:28 PM, Robin Murphy wrote:
>>> [+Christoph and Marek]
>>>
>>> On 21/09/17 09:59, Ganapatrao Kulkarni wrote:
Introduce smmu_alloc_coherent and s
The maximum number of keys that can be allocated has to
take into consideration, that some keys are reserved by
the architecture for specific purpose. Hence cannot
be allocated.
Fix the assertion in test_pkey_alloc_exhaust()
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/pkey-helpers
Hi,
> > I thought we had agreed to make this behave similar to
> > VFIO_GROUP_GET_DEVICE_FD, the ioctl would take a __u32 dmabuf_id
> > and
> > return the file descriptor as the ioctl return value. Thanks,
>
> If we follow VFIO_GROUP_GET_DEVICE_FD, we would lose flags
> functionality.
> Zhi an
Hi Rob,
On Nov 01 2017 or thereabouts, Rob Herring wrote:
> On Tue, Oct 31, 2017 at 11:03:16AM +0800, Lin Huang wrote:
> > Document a "reset" and "assert-reset-us", it can be used for
> > driver control reset property. And reuse post-power-on-delay-ms
> > for deassert reset delay.
>
> "dt-binding
When a key is freed, the key is no more effective.
Clear the bits corresponding to the pkey in the shadow
register. Otherwise it will carry some spurious bits
which can trigger false-positive asserts.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/protection_keys.c |3 +++
1 fi
alloc_random_pkey() was allocating the same pkey every time.
Not all pkeys were geting tested. fixed it.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/protection_keys.c | 10 +++---
1 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/vm/protection
helper functions to handler shadow pkey register
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/pkey-helpers.h| 27
tools/testing/selftests/vm/protection_keys.c | 34 -
2 files changed, 49 insertions(+), 12 deletions(-)
diff --git a/to
> -Original Message-
> From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
> Behalf Of Gerd Hoffmann
> Sent: Monday, November 6, 2017 4:49 PM
> To: Zhang, Tina ; alex.william...@redhat.com;
> ch...@chris-wilson.co.uk; joonas.lahti...@linux.intel.com;
> zhen...@linu
If the flag is 0, no bits will be set. Hence we cant expect
the resulting bitmap to have a higher value than what it
was earlier.
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/protection_keys.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tools/testing/selfte
Moved all the generic definition and helper functions to the
header file
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/pkey-helpers.h| 62 +++--
tools/testing/selftests/vm/protection_keys.c | 54 --
2 files changed, 57 insertions(+), 59 del
On Mon, Nov 6, 2017 at 10:37 AM, Tobin C. Harding wrote:
> On Mon, Nov 06, 2017 at 06:55:52AM +, Gilad Ben-Yossef wrote:
>> Registers ioread/iowrite operations were done via macros,
>> sometime using a "magical" implicit parameter.
>>
>> Replace all register access with simple inline macros.
>
some pkru references are named to pkey_reg
and some prku references are renamed to pkey
Signed-off-by: Ram Pai
---
tools/testing/selftests/vm/pkey-helpers.h| 85 +-
tools/testing/selftests/vm/protection_keys.c | 227 ++
2 files changed, 164 insertions(+), 1
From: Thiago Jung Bauermann
Expose useful information for programs using memory protection keys.
Provide implementation for powerpc and x86.
On a powerpc system with pkeys support, here is what is shown:
$ head /sys/kernel/mm/protection_keys/*
==> /sys/kernel/mm/protection_keys/disable_access_s
Add documentation updates that capture PowerPC specific changes.
Signed-off-by: Thiago Jung Bauermann
Signed-off-by: Ram Pai
---
Documentation/vm/protection-keys.txt | 126 +++---
1 files changed, 101 insertions(+), 25 deletions(-)
diff --git a/Documentation/vm/pro
On Mon, 2017-11-06 at 15:52 +0800, Yixun Lan wrote:
> According to the datasheet, in Meson-GXBB/GXL series,
> The clock gate bit for SARADC is HHI_GCLK_MPEG2 bit[22],
> while clock gate bit for SANA is HHI_GCLK_MPEG0 bit[10].
>
> Test passed at gxl_skt dev board.
I think this refer to a board nami
Finally this patch provides the ability for a process to
allocate and free a protection key.
Signed-off-by: Ram Pai
---
arch/powerpc/include/asm/systbl.h |2 ++
arch/powerpc/include/asm/unistd.h |4 +---
arch/powerpc/include/uapi/asm/unistd.h |2 ++
3 files changed, 5 inser
Arch neutral code needs to know if the architecture supports
protection keys to display protection key in smaps. Hence
introducing arch_pkeys_enabled().
This patch also provides x86 implementation for
arch_pkeys_enabled().
Signed-off-by: Ram Pai
---
arch/x86/include/asm/pkeys.h |1 +
arc
On Sat, Nov 04, 2017 at 09:38:45AM -0600, Keith Busch wrote:
> That's not quite right. For non-PI metadata formats, we use the
> 'nop_profile', which gets the metadata buffer allocated so we can safely
> use a metadata formatted namespace. There's no in-kernel user of the
> allocated payload, but w
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Dongjiu Geng
commit fd6c8c206fc5d0717b0433b191de0715122f33bb upstream.
When a exception is trapped to EL2, hardware uses ELR_ELx to hold
the current fault instruction address. If KVM wants to
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Andrea Arcangeli
commit 1e3921471354244f70fe268586ff94a97a6dd4df upstream.
This oops:
kernel BUG at fs/hugetlbfs/inode.c:484!
RIP: remove_inode_hugepages+0x3d0/0x410
Call Trace:
hug
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Huang Ying
commit 2628bd6fc052bd85e9864dae4de494d8a6313391 upstream.
One page may store a set of entries of the sis->swap_map
(swap_info_struct->swap_map) in multiple swap clusters.
If some o
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Tero Kristo
commit 2a9a86d5c81389cd9afe6a4fea42c585733cd705 upstream.
The recent change to the PM QoS framework to introduce a proper
no constraint value overlooked to handle the devices which
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Yan Markman
commit cda80a82ac3e89309706c027ada6ab232be1d640 upstream.
Under heavy system stress mvebu SoC using Cortex A9 sporadically
encountered instability issues.
The "double linefill" fe
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Leo Liu
commit cb4b02d7cac56a69d8137d8d843507cca9182aed upstream.
Fixes init failures on polaris cards with harvested UVD.
Signed-off-by: Leo Liu
Reviewed-by: Alex Deucher
Signed-off-by: Al
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 79fb0518fec8c8b4ea7f1729f54f293724b3dbb0 upstream.
The races among ioctl and other operations were protected by the
commit af368027a49a ("ALSA: timer: Fix race among timer
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 7298f08ea8870d44d36c7d6cd07dd0303faef6c2 upstream.
Jeremy reported a suspicious RCU usage warning in mcelog.
/dev/mcelog is called in process context now as part of the
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Gustavo A. R. Silva
commit 77238e76b9156d28d86c1e31c00ed2960df0e4de upstream.
It seems that this is a typo error and the proper bit masking is
"RT | RS" instead of "RS | RS".
This issue was d
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 2eb9eabf1e868fda15808954fb29b0f105ed65f1 upstream.
syzkaller with KASAN reported an out-of-bounds read in
asn1_ber_decoder(). It can be reproduced by the following command
This is the start of the stable review cycle for the 4.13.12 release.
There are 36 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed Nov 8 08:50:26 UTC 2017.
Anything receiv
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Naveen N. Rao
commit 63be1a81e40733ecd175713b6a7558dc43f00851 upstream.
This reverts commit 83e840c770f2c5 ("powerpc64/elfv1: Only dereference
function descriptor for non-text symbols").
Chan
Wanpeng Li writes:
> 2017-08-03 0:09 GMT+08:00 Vitaly Kuznetsov :
>> Changes since v9:
>> - Rebase to 4.13-rc3.
>> - Drop PATCH1 as it was already taken by Greg to char-misc tree. There're no
>> functional dependencies on this patch so the series can go through a
>> different tree
>> (and it
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit efea2abcb03215f2efadfe994ff7f652aaff196b upstream.
Avoid that submitting an SG_IO ioctl triggers a kernel oops that
is preceded by:
usercopy: kernel memory overwrite at
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Antoine Tenart
commit c9bb86338a6bb91e4d32db04feb6b8d423e04d06 upstream.
A spin lock is used in the irq-mvebu-gicp driver, but it is never
initialized. This patch adds the missing spin_lock_in
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Rafael J. Wysocki
commit 0cc2b4e5a020fc7f4d1795741c116c983e9467d7 upstream.
The special value of 0 for device resume latency PM QoS means
"no restriction", but there are two problems with that
1 - 100 of 1588 matches
Mail list logo
