[PATCH 4.9 05/16] ARM: 8794/1: uaccess: Prevent speculative use of the current addr_limit

From: Julien Thierry Commit 621afc677465db231662ed126ae1f355bf8eac47 upstream. A mispredicted conditional call to set_fs could result in the wrong addr_limit being forwarded under speculation to a subsequent access_ok check, potentially forming part of a spectre-v1 attack using uaccess

[PATCH 4.9 07/16] ARM: 8796/1: spectre-v1,v1.1: provide helpers for address sanitization

From: Julien Thierry Commit afaf6838f4bc896a711180b702b388b8cfa638fc upstream. Introduce C and asm helpers to sanitize user address, taking the address range they target into account. Use asm helper for existing sanitization in __copy_from_user(). Signed-off-by: Julien Thierry Signed-off-by:

[PATCH 4.9 06/16] ARM: 8795/1: spectre-v1.1: use put_user() for __put_user()

From: Julien Thierry Commit e3aa6243434fd9a82e84bb79ab1abd14f2d9a5a7 upstream. When Spectre mitigation is required, __put_user() needs to include check_uaccess. This is already the case for put_user(), so just make __put_user() an alias of put_user(). Signed-off-by: Julien Thierry

[PATCH 4.9 08/16] ARM: 8797/1: spectre-v1.1: harden __copy_to_user

From: Julien Thierry Commit a1d09e074250fad24f1b993f327b18cc6812eb7a upstream. Sanitize user pointer given to __copy_to_user, both for standard version and memcopy version of the user accessor. Signed-off-by: Julien Thierry Signed-off-by: Russell King Signed-off-by: David A. Long ---

[PATCH 4.9 02/16] ARM: 8791/1: vfp: use __copy_to_user() when saving VFP state

From: Julien Thierry Commit 3aa2df6ec2ca6bc143a65351cca4266d03a8bc41 upstream. Use __copy_to_user() rather than __put_user_error() for individual members when saving VFP state. This has the benefit of disabling/enabling PAN once per copied struct intead of once per write. Signed-off-by: Julien

[PATCH 4.9 03/16] ARM: 8792/1: oabi-compat: copy oabi events using __copy_to_user()

From: Julien Thierry Commit 319508902600c2688e057750148487996396e9ca upstream. Copy events to user using __copy_to_user() rather than copy members of individually with __put_user_error(). This has the benefit of disabling/enabling PAN once per event intead of once per event member.

[PATCH 4.9 10/16] ARM: make lookup_processor_type() non-__init

From: Russell King Commit 899a42f836678a595f7d2bc36a5a0c2b03d08cbc upstream. Move lookup_processor_type() out of the __init section so it is callable from (eg) the secondary startup code during hotplug. Reviewed-by: Julien Thierry Signed-off-by: Russell King Signed-off-by: David A. Long ---

[PATCH 4.9 09/16] ARM: 8810/1: vfp: Fix wrong assignement to ufp_exc

From: Julien Thierry Commit 5df7a99bdd0de4a0480320264c44c04543c29d5a upstream. In vfp_preserve_user_clear_hwstate, ufp_exc->fpinst2 gets assigned to itself. It should actually be hwstate->fpinst2 that gets assigned to the ufp_exc field. Fixes commit 3aa2df6ec2ca6bc143a65351cca4266d03a8bc41

[PATCH 4.9 11/16] ARM: split out processor lookup

From: Russell King Commit 65987a8553061515b5851b472081aedb9837a391 upstream. Split out the lookup of the processor type and associated error handling from the rest of setup_processor() - we will need to use this in the secondary CPU bringup path for big.Little Spectre variant 2 mitigation.

[PATCH 4.9 13/16] ARM: add PROC_VTABLE and PROC_TABLE macros

From: Russell King Commit e209950fdd065d2cc46e6338e47e52841b830cba upstream. Allow the way we access members of the processor vtable to be changed at compile time. We will need to move to per-CPU vtables to fix the Spectre variant 2 issues on big.Little systems. However, we have a couple of

[PATCH 4.9 12/16] ARM: clean up per-processor check_bugs method call

From: Russell King Commit 945aceb1db8885d3a35790cf2e810f681db52756 upstream. Call the per-processor type check_bugs() method in the same way as we do other per-processor functions - move the "processor." detail into proc-fns.h. Reviewed-by: Julien Thierry Signed-off-by: Russell King

[PATCH 4.9 14/16] ARM: spectre-v2: per-CPU vtables to work around big.Little systems

From: Russell King Commit 383fb3ee8024d596f488d2dbaf45e572897acbdb upstream. In big.Little systems, some CPUs require the Spectre workarounds in paths such as the context switch, but other CPUs do not. In order to handle these differences, we need per-CPU vtables. We are unable to use the

[PATCH 4.9 16/16] ARM: fix the cockup in the previous patch

From: Russell King Commit d6951f582cc50ba0ad22ef46b599740966599b14 upstream. The intention in the previous patch was to only place the processor tables in the .rodata section if big.Little was being built and we wanted the branch target hardening, but instead (due to the way it was tested) it

[PATCH 4.9 00/16] V4.9 backport of more 32-bit arm spectre patches

From: "David A. Long" V4.9 backport of spectre patches from Russell M. King's spectre branch. Patches have been kvm-unit-test'ed on an arndale, run through kernelci, and handed off to ARM for functional testing. Julien Thierry (9): ARM: 8789/1: signal: copy registers using __copy_to_user()

[PATCH 4.9 15/16] ARM: ensure that processor vtables is not lost after boot

From: Russell King Commit 3a4d0c2172bcf15b7a3d9d498b2b355f9864286b upstream. Marek Szyprowski reported problems with CPU hotplug in current kernels. This was tracked down to the processor vtables being located in an init section, and therefore discarded after kernel boot, despite being required

[PATCH 4.9 01/16] ARM: 8789/1: signal: copy registers using __copy_to_user()

From: Julien Thierry Commit 5ca451cf6ed04443774bbb7ee45332dafa42e99f upstream. When saving the ARM integer registers, use __copy_to_user() to copy them into user signal frame, rather than __put_user_error(). This has the benefit of disabling/enabling PAN once for the whole copy intead of once

[PATCH 4.9 04/16] ARM: 8793/1: signal: replace __put_user_error with __put_user

From: Julien Thierry Commit 18ea66bd6e7a95bdc598223d72757190916af28b upstream. With Spectre-v1.1 mitigations, __put_user_error is pointless. In an attempt to remove it, replace its references in frame setups with __put_user. Signed-off-by: Julien Thierry Signed-off-by: Russell King

[PATCH 4.14 V2 01/17] ARM: 8789/1: signal: copy registers using __copy_to_user()

From: Julien Thierry Commit 5ca451cf6ed04443774bbb7ee45332dafa42e99f upstream. When saving the ARM integer registers, use __copy_to_user() to copy them into user signal frame, rather than __put_user_error(). This has the benefit of disabling/enabling PAN once for the whole copy intead of once

[PATCH 4.14 V2 05/17] ARM: 8793/1: signal: replace __put_user_error with __put_user

From: Julien Thierry Commit 18ea66bd6e7a95bdc598223d72757190916af28b upstream. With Spectre-v1.1 mitigations, __put_user_error is pointless. In an attempt to remove it, replace its references in frame setups with __put_user. Signed-off-by: Julien Thierry Signed-off-by: Russell King

[PATCH 4.14 V2 06/17] ARM: 8794/1: uaccess: Prevent speculative use of the current addr_limit

From: Julien Thierry Commit 621afc677465db231662ed126ae1f355bf8eac47 upstream. A mispredicted conditional call to set_fs could result in the wrong addr_limit being forwarded under speculation to a subsequent access_ok check, potentially forming part of a spectre-v1 attack using uaccess

[PATCH 4.14 V2 07/17] ARM: 8795/1: spectre-v1.1: use put_user() for __put_user()

From: Julien Thierry Commit e3aa6243434fd9a82e84bb79ab1abd14f2d9a5a7 upstream. When Spectre mitigation is required, __put_user() needs to include check_uaccess. This is already the case for put_user(), so just make __put_user() an alias of put_user(). Signed-off-by: Julien Thierry

[PATCH 4.14 V2 12/17] ARM: split out processor lookup

From: Russell King Commit 65987a8553061515b5851b472081aedb9837a391 upstream. Split out the lookup of the processor type and associated error handling from the rest of setup_processor() - we will need to use this in the secondary CPU bringup path for big.Little Spectre variant 2 mitigation.

[PATCH 4.14 V2 04/17] ARM: 8792/1: oabi-compat: copy oabi events using __copy_to_user()

From: Julien Thierry Commit 319508902600c2688e057750148487996396e9ca upstream. Copy events to user using __copy_to_user() rather than copy members of individually with __put_user_error(). This has the benefit of disabling/enabling PAN once per event intead of once per event member.

[PATCH 4.14 V2 10/17] ARM: 8810/1: vfp: Fix wrong assignement to ufp_exc

From: Julien Thierry Commit 5df7a99bdd0de4a0480320264c44c04543c29d5a upstream. In vfp_preserve_user_clear_hwstate, ufp_exc->fpinst2 gets assigned to itself. It should actually be hwstate->fpinst2 that gets assigned to the ufp_exc field. Fixes commit 3aa2df6ec2ca6bc143a65351cca4266d03a8bc41

[PATCH 4.14 V2 03/17] ARM: 8791/1: vfp: use __copy_to_user() when saving VFP state

From: Julien Thierry Commit 3aa2df6ec2ca6bc143a65351cca4266d03a8bc41 upstream. Use __copy_to_user() rather than __put_user_error() for individual members when saving VFP state. This has the benefit of disabling/enabling PAN once per copied struct intead of once per write. Signed-off-by: Julien

[PATCH 4.14 V2 16/17] ARM: ensure that processor vtables is not lost after boot

From: Russell King Commit 3a4d0c2172bcf15b7a3d9d498b2b355f9864286b upstream. Marek Szyprowski reported problems with CPU hotplug in current kernels. This was tracked down to the processor vtables being located in an init section, and therefore discarded after kernel boot, despite being required

[PATCH 4.14 V2 08/17] ARM: 8796/1: spectre-v1,v1.1: provide helpers for address sanitization

From: Julien Thierry Commit afaf6838f4bc896a711180b702b388b8cfa638fc upstream. Introduce C and asm helpers to sanitize user address, taking the address range they target into account. Use asm helper for existing sanitization in __copy_from_user(). Signed-off-by: Julien Thierry Signed-off-by:

[PATCH 4.14 V2 14/17] ARM: add PROC_VTABLE and PROC_TABLE macros

From: Russell King Commit e209950fdd065d2cc46e6338e47e52841b830cba upstream. Allow the way we access members of the processor vtable to be changed at compile time. We will need to move to per-CPU vtables to fix the Spectre variant 2 issues on big.Little systems. However, we have a couple of

[PATCH 4.14 V2 13/17] ARM: clean up per-processor check_bugs method call

From: Russell King Commit 945aceb1db8885d3a35790cf2e810f681db52756 upstream. Call the per-processor type check_bugs() method in the same way as we do other per-processor functions - move the "processor." detail into proc-fns.h. Reviewed-by: Julien Thierry Signed-off-by: Russell King

[PATCH 4.14 V2 11/17] ARM: make lookup_processor_type() non-__init

From: Russell King Commit 899a42f836678a595f7d2bc36a5a0c2b03d08cbc upstream. Move lookup_processor_type() out of the __init section so it is callable from (eg) the secondary startup code during hotplug. Reviewed-by: Julien Thierry Signed-off-by: Russell King Signed-off-by: David A. Long ---

[PATCH 4.14 V2 15/17] ARM: spectre-v2: per-CPU vtables to work around big.Little systems

From: Russell King Commit 383fb3ee8024d596f488d2dbaf45e572897acbdb upstream. In big.Little systems, some CPUs require the Spectre workarounds in paths such as the context switch, but other CPUs do not. In order to handle these differences, we need per-CPU vtables. We are unable to use the

[PATCH 4.14 V2 00/17] V4.14 backport of more 32-bit arm spectre patches

From: "David A. Long" V4.14 backport of spectre patches from Russell M. King's spectre branch. Patches have been kvm-unit-test'ed on an arndale, run through kernelci, and handed off to ARM for functional testing. Julien Thierry (10): ARM: 8789/1: signal: copy registers using __copy_to_user()

[PATCH 4.14 V2 02/17] ARM: 8790/1: signal: always use __copy_to_user to save iwmmxt context

From: Julien Thierry Commit 73839798af7ebc6c8d0c9271ebbbc148700e521f upstream. When setting a dummy iwmmxt context, create a local instance and use __copy_to_user both cases whether iwmmxt is being used or not. This has the benefit of disabling/enabling PAN once for the whole copy intead of

[PATCH 4.14 V2 09/17] ARM: 8797/1: spectre-v1.1: harden __copy_to_user

From: Julien Thierry Commit a1d09e074250fad24f1b993f327b18cc6812eb7a upstream. Sanitize user pointer given to __copy_to_user, both for standard version and memcopy version of the user accessor. Signed-off-by: Julien Thierry Signed-off-by: Russell King Signed-off-by: David A. Long ---

[PATCH 4.14 V2 17/17] ARM: fix the cockup in the previous patch

From: Russell King Commit d6951f582cc50ba0ad22ef46b599740966599b14 upstream. The intention in the previous patch was to only place the processor tables in the .rodata section if big.Little was being built and we wanted the branch target hardening, but instead (due to the way it was tested) it

[PATCH 4.19 01/17] ARM: 8789/1: signal: copy registers using __copy_to_user()

From: Julien Thierry Commit 5ca451cf6ed04443774bbb7ee45332dafa42e99f upstream. When saving the ARM integer registers, use __copy_to_user() to copy them into user signal frame, rather than __put_user_error(). This has the benefit of disabling/enabling PAN once for the whole copy intead of once

[PATCH 4.19 07/17] ARM: 8795/1: spectre-v1.1: use put_user() for __put_user()

From: Julien Thierry Commit e3aa6243434fd9a82e84bb79ab1abd14f2d9a5a7 upstream. When Spectre mitigation is required, __put_user() needs to include check_uaccess. This is already the case for put_user(), so just make __put_user() an alias of put_user(). Signed-off-by: Julien Thierry

[PATCH 4.19 03/17] ARM: 8791/1: vfp: use __copy_to_user() when saving VFP state

From: Julien Thierry Commit 3aa2df6ec2ca6bc143a65351cca4266d03a8bc41 upstream. Use __copy_to_user() rather than __put_user_error() for individual members when saving VFP state. This has the benefit of disabling/enabling PAN once per copied struct intead of once per write. Signed-off-by: Julien

[PATCH 4.19 04/17] ARM: 8792/1: oabi-compat: copy oabi events using __copy_to_user()

From: Julien Thierry Commit 319508902600c2688e057750148487996396e9ca upstream. Copy events to user using __copy_to_user() rather than copy members of individually with __put_user_error(). This has the benefit of disabling/enabling PAN once per event intead of once per event member.

[PATCH 4.19 10/17] ARM: 8810/1: vfp: Fix wrong assignement to ufp_exc

From: Julien Thierry Commit 5df7a99bdd0de4a0480320264c44c04543c29d5a upstream. In vfp_preserve_user_clear_hwstate, ufp_exc->fpinst2 gets assigned to itself. It should actually be hwstate->fpinst2 that gets assigned to the ufp_exc field. Fixes commit 3aa2df6ec2ca6bc143a65351cca4266d03a8bc41

[PATCH 4.19 05/17] ARM: 8793/1: signal: replace __put_user_error with __put_user

From: Julien Thierry Commit 18ea66bd6e7a95bdc598223d72757190916af28b upstream. With Spectre-v1.1 mitigations, __put_user_error is pointless. In an attempt to remove it, replace its references in frame setups with __put_user. Signed-off-by: Julien Thierry Signed-off-by: Russell King

[PATCH 4.19 09/17] ARM: 8797/1: spectre-v1.1: harden __copy_to_user

From: Julien Thierry Commit a1d09e074250fad24f1b993f327b18cc6812eb7a upstream. Sanitize user pointer given to __copy_to_user, both for standard version and memcopy version of the user accessor. Signed-off-by: Julien Thierry Signed-off-by: Russell King Signed-off-by: David A. Long ---

[PATCH 4.19 08/17] ARM: 8796/1: spectre-v1,v1.1: provide helpers for address sanitization

From: Julien Thierry Commit afaf6838f4bc896a711180b702b388b8cfa638fc upstream. Introduce C and asm helpers to sanitize user address, taking the address range they target into account. Use asm helper for existing sanitization in __copy_from_user(). Signed-off-by: Julien Thierry Signed-off-by:

[PATCH 4.19 14/17] ARM: add PROC_VTABLE and PROC_TABLE macros

From: Russell King Commit e209950fdd065d2cc46e6338e47e52841b830cba upstream. Allow the way we access members of the processor vtable to be changed at compile time. We will need to move to per-CPU vtables to fix the Spectre variant 2 issues on big.Little systems. However, we have a couple of

[PATCH 4.19 15/17] ARM: spectre-v2: per-CPU vtables to work around big.Little systems

From: Russell King Commit 383fb3ee8024d596f488d2dbaf45e572897acbdb upstream. In big.Little systems, some CPUs require the Spectre workarounds in paths such as the context switch, but other CPUs do not. In order to handle these differences, we need per-CPU vtables. We are unable to use the

[PATCH 4.19 12/17] ARM: split out processor lookup

From: Russell King Commit 65987a8553061515b5851b472081aedb9837a391 upstream. Split out the lookup of the processor type and associated error handling from the rest of setup_processor() - we will need to use this in the secondary CPU bringup path for big.Little Spectre variant 2 mitigation.

[PATCH 4.19 11/17] ARM: make lookup_processor_type() non-__init

From: Russell King Commit 899a42f836678a595f7d2bc36a5a0c2b03d08cbc upstream. Move lookup_processor_type() out of the __init section so it is callable from (eg) the secondary startup code during hotplug. Reviewed-by: Julien Thierry Signed-off-by: Russell King Signed-off-by: David A. Long ---

[PATCH 4.19 16/17] ARM: ensure that processor vtables is not lost after boot

From: Russell King Commit 3a4d0c2172bcf15b7a3d9d498b2b355f9864286b upstream. Marek Szyprowski reported problems with CPU hotplug in current kernels. This was tracked down to the processor vtables being located in an init section, and therefore discarded after kernel boot, despite being required

[PATCH 4.19 17/17] ARM: fix the cockup in the previous patch

From: Russell King Commit d6951f582cc50ba0ad22ef46b599740966599b14 upstream. The intention in the previous patch was to only place the processor tables in the .rodata section if big.Little was being built and we wanted the branch target hardening, but instead (due to the way it was tested) it

[PATCH 4.19 13/17] ARM: clean up per-processor check_bugs method call

From: Russell King Commit 945aceb1db8885d3a35790cf2e810f681db52756 upstream. Call the per-processor type check_bugs() method in the same way as we do other per-processor functions - move the "processor." detail into proc-fns.h. Reviewed-by: Julien Thierry Signed-off-by: Russell King

[PATCH 4.19 06/17] ARM: 8794/1: uaccess: Prevent speculative use of the current addr_limit

From: Julien Thierry Commit 621afc677465db231662ed126ae1f355bf8eac47 upstream. A mispredicted conditional call to set_fs could result in the wrong addr_limit being forwarded under speculation to a subsequent access_ok check, potentially forming part of a spectre-v1 attack using uaccess

[PATCH 4.19 02/17] ARM: 8790/1: signal: always use __copy_to_user to save iwmmxt context

From: Julien Thierry Commit 73839798af7ebc6c8d0c9271ebbbc148700e521f upstream. When setting a dummy iwmmxt context, create a local instance and use __copy_to_user both cases whether iwmmxt is being used or not. This has the benefit of disabling/enabling PAN once for the whole copy intead of

[PATCH 4.19 00/17] V4.19 backport of more 32-bit arm spectre patches

From: "David A. Long" V4.19 backport of spectre patches from Russell M. King's spectre branch. Patches have been kvm-unit-test'ed on an arndale, run through kernelci, and handed off to ARM for functional testing. Julien Thierry (10): ARM: 8789/1: signal: copy registers using __copy_to_user()

Re: [RESEND x3][PATCH 2/2 v4] drm/bridge: adv7511: Enable the audio data and clock pads on adv7533

On 11/28/2016 08:22 PM, John Stultz wrote: From: Srinivas Kandagatla This patch enables the Audio Data and Clock pads to the adv7533 bridge. Without this patch audio can not be played. Cc: David Airlie Cc: Archit Taneja

Re: [RESEND x3][PATCH 2/2 v4] drm/bridge: adv7511: Enable the audio data and clock pads on adv7533

On 11/28/2016 08:22 PM, John Stultz wrote: From: Srinivas Kandagatla This patch enables the Audio Data and Clock pads to the adv7533 bridge. Without this patch audio can not be played. Cc: David Airlie Cc: Archit Taneja Cc: Laurent Pinchart Cc: Wolfram Sang Cc: Srinivas Kandagatla Cc:

Re: [RESEND x3][PATCH 1/2 v4] drm/bridge: adv7511: Add Audio support.

On 11/28/2016 08:22 PM, John Stultz wrote: This patch adds support to Audio for both adv7511 and adv7533 bridge chips. This patch was originally from [1] by Lars-Peter Clausen and was adapted by Archit Taneja and Srinivas Kandagatla

Re: [RESEND x3][PATCH 1/2 v4] drm/bridge: adv7511: Add Audio support.

On 11/28/2016 08:22 PM, John Stultz wrote: This patch adds support to Audio for both adv7511 and adv7533 bridge chips. This patch was originally from [1] by Lars-Peter Clausen and was adapted by Archit Taneja and Srinivas Kandagatla . Then I heavily reworked it to use the hdmi-codec driver.

Re: [PATCH v4] arm64: Improve kprobes test for atomic sequence

On 09/12/2016 08:46 PM, Masami Hiramatsu wrote: On Mon, 12 Sep 2016 14:21:27 -0400 David Long <dave.l...@linaro.org> wrote: From: "David A. Long" <dave.l...@linaro.org> Kprobes searches backwards a finite number of instructions to determine if there is an attempt

Re: [PATCH v4] arm64: Improve kprobes test for atomic sequence

On 09/12/2016 08:46 PM, Masami Hiramatsu wrote: On Mon, 12 Sep 2016 14:21:27 -0400 David Long wrote: From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops wh

[PATCH v4] arm64: Improve kprobes test for atomic sequence

From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops when it hits the maximum number of instructions or a load or store exclusive. However this means it can

[PATCH v4] arm64: Improve kprobes test for atomic sequence

From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops when it hits the maximum number of instructions or a load or store exclusive. However this means it can run up past the

Re: [PATCH v3] arm64: Improve kprobes test for atomic sequence

On 09/12/2016 12:29 PM, Masami Hiramatsu wrote: On Sun, 11 Sep 2016 21:53:43 -0400 David Long <dave.l...@linaro.org> wrote: On 09/10/2016 01:48 AM, Masami Hiramatsu wrote: On Fri, 9 Sep 2016 15:26:09 -0400 David Long <dave.l...@linaro.org> wrote: From: "David A. Long"

Re: [PATCH v3] arm64: Improve kprobes test for atomic sequence

On 09/12/2016 12:29 PM, Masami Hiramatsu wrote: On Sun, 11 Sep 2016 21:53:43 -0400 David Long wrote: On 09/10/2016 01:48 AM, Masami Hiramatsu wrote: On Fri, 9 Sep 2016 15:26:09 -0400 David Long wrote: From: "David A. Long" Kprobes searches backwards a finite number of in

Re: [PATCH v3] arm64: Improve kprobes test for atomic sequence

On 09/10/2016 01:48 AM, Masami Hiramatsu wrote: On Fri, 9 Sep 2016 15:26:09 -0400 David Long <dave.l...@linaro.org> wrote: From: "David A. Long" <dave.l...@linaro.org> Kprobes searches backwards a finite number of instructions to determine if there is an attempt

Re: [PATCH v3] arm64: Improve kprobes test for atomic sequence

On 09/10/2016 01:48 AM, Masami Hiramatsu wrote: On Fri, 9 Sep 2016 15:26:09 -0400 David Long wrote: From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops wh

[PATCH v3] arm64: Improve kprobes test for atomic sequence

From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops when it hits the maximum number of instructions or a load or store exclusive. However this means it can

[PATCH v3] arm64: Improve kprobes test for atomic sequence

From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops when it hits the maximum number of instructions or a load or store exclusive. However this means it can run up past the

Re: [PATCH v2] arm64: Improve kprobes test for atomic sequence

On 09/07/2016 01:52 AM, Masami Hiramatsu wrote: On Tue, 6 Sep 2016 13:54:59 -0400 David Long <dave.l...@linaro.org> wrote: From: "David A. Long" <dave.l...@linaro.org> Kprobes searches backwards a finite number of instructions to determine if there is an attempt

Re: [PATCH v2] arm64: Improve kprobes test for atomic sequence

On 09/07/2016 01:52 AM, Masami Hiramatsu wrote: On Tue, 6 Sep 2016 13:54:59 -0400 David Long wrote: From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops wh

Re: [PATCH 3/5] arm64: Handle TRAP_HWBRKPT for user mode as well

On 09/06/2016 12:11 PM, Catalin Marinas wrote: On Tue, Aug 02, 2016 at 11:00:07AM +0530, Pratyush Anand wrote: --- a/arch/arm64/kernel/debug-monitors.c +++ b/arch/arm64/kernel/debug-monitors.c @@ -246,6 +246,8 @@ static void send_user_sigtrap(int si_code) static int

Re: [PATCH 3/5] arm64: Handle TRAP_HWBRKPT for user mode as well

On 09/06/2016 12:11 PM, Catalin Marinas wrote: On Tue, Aug 02, 2016 at 11:00:07AM +0530, Pratyush Anand wrote: --- a/arch/arm64/kernel/debug-monitors.c +++ b/arch/arm64/kernel/debug-monitors.c @@ -246,6 +246,8 @@ static void send_user_sigtrap(int si_code) static int

[PATCH v2] arm64: Improve kprobes test for atomic sequence

From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops when it hits the maximum number of instructions or a load or store exclusive. However this means it can

[PATCH v2] arm64: Improve kprobes test for atomic sequence

From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops when it hits the maximum number of instructions or a load or store exclusive. However this means it can run up past the

Re: [PATCH] arm64: Improve kprobes test for atomic sequence

On 08/31/2016 10:38 PM, Masami Hiramatsu wrote: Hi Dave, On Wed, 31 Aug 2016 16:52:22 -0400 David Long <dave.l...@linaro.org> wrote: From: "David A. Long" <dave.l...@linaro.org> Kprobes searches backwards a finite number of instructions to determine if there is an a

Re: [PATCH] arm64: Improve kprobes test for atomic sequence

On 08/31/2016 10:38 PM, Masami Hiramatsu wrote: Hi Dave, On Wed, 31 Aug 2016 16:52:22 -0400 David Long wrote: From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops wh

[PATCH] arm64: Improve kprobes test for atomic sequence

From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops when it hits the maximum number of instructions or a load or store exclusive. However this means it can

[PATCH] arm64: Improve kprobes test for atomic sequence

From: "David A. Long" Kprobes searches backwards a finite number of instructions to determine if there is an attempt to probe a load/store exclusive sequence. It stops when it hits the maximum number of instructions or a load or store exclusive. However this means it can run up past the

Re: [PATCH] Documentation: kprobes: Document jprobes stack copying limitations

On 08/15/2016 11:32 AM, Jonathan Corbet wrote: On Mon, 15 Aug 2016 10:49:36 -0400 David Long <dave.l...@linaro.org> wrote: On 08/15/2016 10:25 AM, Jonathan Corbet wrote: On Fri, 12 Aug 2016 16:24:44 -0400 David Long <dave.l...@linaro.org> wrote: Some architectures (i.e.: sparc

Re: [PATCH] Documentation: kprobes: Document jprobes stack copying limitations

On 08/15/2016 11:32 AM, Jonathan Corbet wrote: On Mon, 15 Aug 2016 10:49:36 -0400 David Long wrote: On 08/15/2016 10:25 AM, Jonathan Corbet wrote: On Fri, 12 Aug 2016 16:24:44 -0400 David Long wrote: Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack duplication

Re: [PATCH] Documentation: kprobes: Document jprobes stack copying limitations

On 08/15/2016 10:25 AM, Jonathan Corbet wrote: On Fri, 12 Aug 2016 16:24:44 -0400 David Long <dave.l...@linaro.org> wrote: Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack duplication for jprobes problematic. Document this. Applied to the docs tree, thanks

Re: [PATCH] Documentation: kprobes: Document jprobes stack copying limitations

On 08/15/2016 10:25 AM, Jonathan Corbet wrote: On Fri, 12 Aug 2016 16:24:44 -0400 David Long wrote: Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack duplication for jprobes problematic. Document this. Applied to the docs tree, thanks. jon Was kind of hoping

[PATCH] Documentation: kprobes: Document jprobes stack copying limitations

From: "David A. Long" Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack duplication for jprobes problematic. Document this. Signed-off-by: David A. Long --- Documentation/kprobes.txt | 10 ++ 1 file changed, 10

[PATCH] Documentation: kprobes: Document jprobes stack copying limitations

From: "David A. Long" Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack duplication for jprobes problematic. Document this. Signed-off-by: David A. Long --- Documentation/kprobes.txt | 10 ++ 1 file changed, 10 insertions(+) diff --git

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 08/09/2016 01:23 PM, Catalin Marinas wrote: On Mon, Aug 08, 2016 at 10:29:05AM -0400, David Long wrote: On 08/08/2016 07:13 AM, Daniel Thompson wrote: On 04/08/16 05:47, David Long wrote: >From b451caa1adaf1d03e08a44b5dad3fca31cebd97a Mon Sep 17 00:00:00 2001 From: "David A. Long&

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 08/09/2016 01:23 PM, Catalin Marinas wrote: On Mon, Aug 08, 2016 at 10:29:05AM -0400, David Long wrote: On 08/08/2016 07:13 AM, Daniel Thompson wrote: On 04/08/16 05:47, David Long wrote: >From b451caa1adaf1d03e08a44b5dad3fca31cebd97a Mon Sep 17 00:00:00 2001 From: "David A. Lon

[PATCH 1/1] arm64: Remove stack duplicating code from jprobes

From: "David A. Long" Because the arm64 calling standard allows stacked function arguments to be anywhere in the stack frame, do not attempt to duplicate the stack frame for jprobes handler functions. Documenation changes to describe this issue have been broken out into a

[PATCH 1/1] arm64: Remove stack duplicating code from jprobes

From: "David A. Long" Because the arm64 calling standard allows stacked function arguments to be anywhere in the stack frame, do not attempt to duplicate the stack frame for jprobes handler functions. Documenation changes to describe this issue have been broken out into a separate patch in

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 08/08/2016 07:13 AM, Daniel Thompson wrote: On 04/08/16 05:47, David Long wrote: From b451caa1adaf1d03e08a44b5dad3fca31cebd97a Mon Sep 17 00:00:00 2001 From: "David A. Long" <dave.l...@linaro.org> Date: Thu, 4 Aug 2016 00:35:33 -0400 Subject: [PATCH] arm64: Remove stack dupli

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 08/08/2016 07:13 AM, Daniel Thompson wrote: On 04/08/16 05:47, David Long wrote: From b451caa1adaf1d03e08a44b5dad3fca31cebd97a Mon Sep 17 00:00:00 2001 From: "David A. Long" Date: Thu, 4 Aug 2016 00:35:33 -0400 Subject: [PATCH] arm64: Remove stack duplicating code from jprobe

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/29/2016 05:01 AM, Daniel Thompson wrote: > On 28/07/16 15:40, Catalin Marinas wrote: >> On Wed, Jul 27, 2016 at 06:13:37PM -0400, David Long wrote: >>> On 07/27/2016 07:50 AM, Daniel Thompson wrote: >>>> On 25/07/16 23:27, David Long wrote: >>>>>

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/29/2016 05:01 AM, Daniel Thompson wrote: > On 28/07/16 15:40, Catalin Marinas wrote: >> On Wed, Jul 27, 2016 at 06:13:37PM -0400, David Long wrote: >>> On 07/27/2016 07:50 AM, Daniel Thompson wrote: >>>> On 25/07/16 23:27, David Long wrote: >>>>>

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/27/2016 07:50 AM, Daniel Thompson wrote: On 25/07/16 23:27, David Long wrote: On 07/25/2016 01:13 PM, Catalin Marinas wrote: On Fri, Jul 22, 2016 at 11:51:32AM -0400, David Long wrote: On 07/22/2016 06:16 AM, Catalin Marinas wrote: On Thu, Jul 21, 2016 at 02:33:52PM -0400, David Long

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/27/2016 07:50 AM, Daniel Thompson wrote: On 25/07/16 23:27, David Long wrote: On 07/25/2016 01:13 PM, Catalin Marinas wrote: On Fri, Jul 22, 2016 at 11:51:32AM -0400, David Long wrote: On 07/22/2016 06:16 AM, Catalin Marinas wrote: On Thu, Jul 21, 2016 at 02:33:52PM -0400, David Long

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/25/2016 01:13 PM, Catalin Marinas wrote: On Fri, Jul 22, 2016 at 11:51:32AM -0400, David Long wrote: On 07/22/2016 06:16 AM, Catalin Marinas wrote: On Thu, Jul 21, 2016 at 02:33:52PM -0400, David Long wrote: On 07/21/2016 01:23 PM, Marc Zyngier wrote: On 21/07/16 17:33, David Long

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/25/2016 01:13 PM, Catalin Marinas wrote: On Fri, Jul 22, 2016 at 11:51:32AM -0400, David Long wrote: On 07/22/2016 06:16 AM, Catalin Marinas wrote: On Thu, Jul 21, 2016 at 02:33:52PM -0400, David Long wrote: On 07/21/2016 01:23 PM, Marc Zyngier wrote: On 21/07/16 17:33, David Long

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/22/2016 06:16 AM, Catalin Marinas wrote: On Thu, Jul 21, 2016 at 02:33:52PM -0400, David Long wrote: On 07/21/2016 01:23 PM, Marc Zyngier wrote: On 21/07/16 17:33, David Long wrote: On 07/20/2016 12:09 PM, Marc Zyngier wrote: On 08/07/16 17:35, David Long wrote: +#define MAX_INSN_SIZE

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/22/2016 06:16 AM, Catalin Marinas wrote: On Thu, Jul 21, 2016 at 02:33:52PM -0400, David Long wrote: On 07/21/2016 01:23 PM, Marc Zyngier wrote: On 21/07/16 17:33, David Long wrote: On 07/20/2016 12:09 PM, Marc Zyngier wrote: On 08/07/16 17:35, David Long wrote: +#define MAX_INSN_SIZE

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/21/2016 01:23 PM, Marc Zyngier wrote: On 21/07/16 17:33, David Long wrote: On 07/20/2016 12:09 PM, Marc Zyngier wrote: On 08/07/16 17:35, David Long wrote: From: Sandeepa Prabhu <sandeepa.s.pra...@gmail.com> Add support for basic kernel probes(kprobes) and jump probes (j

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/21/2016 01:23 PM, Marc Zyngier wrote: On 21/07/16 17:33, David Long wrote: On 07/20/2016 12:09 PM, Marc Zyngier wrote: On 08/07/16 17:35, David Long wrote: From: Sandeepa Prabhu Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes

Re: [PATCH v15 04/10] arm64: Kprobes with single stepping support

On 07/20/2016 12:09 PM, Marc Zyngier wrote: On 08/07/16 17:35, David Long wrote: From: Sandeepa Prabhu <sandeepa.s.pra...@gmail.com> Add support for basic kernel probes(kprobes) and jump probes (jprobes) for ARM64. Kprobes utilizes software breakpoint and single step debug exce

  1   2   3   4   5   6   7   8   9   >