Re: [PATCH v2 1/9] powerpc/lib/code-patching: Enhance code patching

Balbir Singh writes: > On Wed, Jun 7, 2017 at 8:25 PM, Christophe LEROY > wrote: >> Le 04/06/2017 à 01:45, kbuild test robot a écrit : >>> [auto build test ERROR on powerpc/next] >>> [also build test ERROR on v4.12-rc3 next-20170602] >>> [if your patch is applied to the wrong git tree, please dro

Re: [PATCH v2 1/9] powerpc/lib/code-patching: Enhance code patching

On Wed, Jun 7, 2017 at 8:25 PM, Christophe LEROY wrote: > Hi Balbir > > Le 04/06/2017 à 01:45, kbuild test robot a écrit : >> >> Hi Balbir, >> >> [auto build test ERROR on powerpc/next] >> [also build test ERROR on v4.12-rc3 next-20170602] >> [if your patch is applied to the wrong git tree, please

Re: [PATCH v2 1/9] powerpc/lib/code-patching: Enhance code patching

Hi Balbir Le 04/06/2017 à 01:45, kbuild test robot a écrit : Hi Balbir, [auto build test ERROR on powerpc/next] [also build test ERROR on v4.12-rc3 next-20170602] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0da

Re: [PATCH v2 1/9] powerpc/lib/code-patching: Enhance code patching

Hi Balbir, [auto build test ERROR on powerpc/next] [also build test ERROR on v4.12-rc3 next-20170602] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Balbir-Singh/Enable-STRICT_KERNEL_RWX/2017060

[PATCH v2 1/9] powerpc/lib/code-patching: Enhance code patching

Today our patching happens via direct copy and patch_instruction. The patching code is well contained in the sense that copying bits are limited. While considering implementation of CONFIG_STRICT_RWX, the first requirement is to a create another mapping that will allow for patching. We create the