Buildresult: powerpc-next/powernv_defconfig+STRICT_RWX/powerpc-gcc5 built on Jul 3 2018, 02:24

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Jul 3 2018, 02:24
Duration:	0:03:25.644967
Builder:	ka1
Revision:	ocxl: Fix page fault handler in case of fault on dying process (`d497ebf5fb3a026c0817f8c96cde578787f24093)`
Target:	powerpc-next/powernv_defconfig+STRICT_RWX/powerpc-gcc5
Branch:	powerpc-next
Compiler:	powerpc-gcc5 (powerpc64le-linux-gcc (GCC) 5.2.0)
Config:	powernv_defconfig+STRICT_RWX (download)
Log:	Download original Possible warnings (1) WARNING: modpost: Found 2 section mismatch(es). Full Log # git rev-parse -q --verify d497ebf5fb3a026c0817f8c96cde578787f24093^{commit} d497ebf5fb3a026c0817f8c96cde578787f24093 already have revision, skipping fetch # git checkout -q -f -B kisskb d497ebf5fb3a026c0817f8c96cde578787f24093 # git clean -qxdf # < git log -1 # commit d497ebf5fb3a026c0817f8c96cde578787f24093 # Author: Frederic Barrat <fbarrat@linux.ibm.com> # Date: Mon Jun 18 14:14:36 2018 +0200 # # ocxl: Fix page fault handler in case of fault on dying process # # If a process exits without doing proper cleanup, there's a window # where an opencapi device can try to access the memory of the dying # process and may trigger a page fault. That's an expected scenario and # the ocxl driver holds a reference on the mm_struct of the process # until the opencapi device is notified of the process exiting. # However, if mm_users is already at 0, i.e. the address space of the # process has already been destroyed, the driver shouldn't try resolving # the page fault, as it will fail, but it can also try accessing already # freed data. # # It is fixed by only calling the bottom half of the page fault handler # if mm_users is greater than 0 and get a reference on mm_users instead # of mm_count. Otherwise, we can safely return a translation fault to # the device, as its associated memory context is being removed. The # opencapi device will be properly cleaned up shortly after when closing # the file descriptors. # # Fixes: 5ef3166e8a32 ("ocxl: Driver code for 'generic' opencapi devices") # Cc: stable@vger.kernel.org # v4.16+ # Signed-off-by: Frederic Barrat <fbarrat@linux.ibm.com> # Reviewed-By: Alastair D'Silva <alastair@d-silva.org> # Acked-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com> # Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> # < /opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux-gcc --version # < git log --format=%s --max-count=1 d497ebf5fb3a026c0817f8c96cde578787f24093 # < make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_powernv_defconfig+STRICT_RWX_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- powernv_defconfig # Added to kconfig CONFIG_RELOCATABLE=n # Added to kconfig CONFIG_STRICT_KERNEL_RWX=y # yes \n \| make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_powernv_defconfig+STRICT_RWX_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- oldconfig yes: standard output: Broken pipe yes: write error # make -s -j 48 ARCH=powerpc O=/kisskb/build/powerpc-next_powernv_defconfig+STRICT_RWX_ppc64le CROSS_COMPILE=/opt/cross/kisskb/gcc-5.2.0-nolibc/powerpc64le-linux/bin/powerpc64le-linux- /kisskb/src/net/Makefile:24: CC cannot link executables. Skipping bpfilter. /kisskb/src/net/Makefile:24: CC cannot link executables. Skipping bpfilter. WARNING: modpost: Found 2 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' Completed OK # rm -rf /kisskb/build/powerpc-next_powernv_defconfig+STRICT_RWX_ppc64le # Build took: 0:03:25.644967

© Michael Ellerman 2006-2018.