[PATCH 8/10] ath9k: Use ARRAY_SIZE macro

ication. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- diff --git a/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c b/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c index 3dbfd86ebe36..c2e210c0a770 100644 --- a/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c +++ b/drivers/net/wireless/ath/ath9

[PATCH 10/10] staging/atomisp: Use ARRAY_SIZE macro

ication. Signed-off-by: Thomas Meyer --- diff --git a/drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/ifmtr/src/ifmtr.c b/drivers/staging/media/atomisp/pci/atomisp2/css2400/runtime/ifmtr/src/ifmtr.c index a7c6bba7e094..11d3995ba0db 100644 --- a/drivers/staging/media/atomisp/pci/atomisp2/c

[PATCH 8/10] ath9k: Use ARRAY_SIZE macro

ication. Signed-off-by: Thomas Meyer --- diff --git a/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c b/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c index 3dbfd86ebe36..c2e210c0a770 100644 --- a/drivers/net/wireless/ath/ath9k/ar9003_eeprom.c +++ b/drivers/net/wireless/ath/ath9k/ar9003_eep

[PATCH 2/10] drm/amdgpu: Use ARRAY_SIZE macro

ication. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- diff --git a/drivers/gpu/drm/amd/amdgpu/mmhub_v1_0.c b/drivers/gpu/drm/amd/amdgpu/mmhub_v1_0.c index 9804318f3488..7ef84d884714 100644 --- a/drivers/gpu/drm/amd/amdgpu/mmhub_v1_0.c +++ b/drivers/gpu/drm/amd/amdgpu/mmhub_v1_0.c @@ -20,6 +

[PATCH 2/10] drm/amdgpu: Use ARRAY_SIZE macro

ication. Signed-off-by: Thomas Meyer --- diff --git a/drivers/gpu/drm/amd/amdgpu/mmhub_v1_0.c b/drivers/gpu/drm/amd/amdgpu/mmhub_v1_0.c index 9804318f3488..7ef84d884714 100644 --- a/drivers/gpu/drm/amd/amdgpu/mmhub_v1_0.c +++ b/drivers/gpu/drm/amd/amdgpu/mmhub_v1_0.c @@ -20,6 +20,8 @@ * OTHER DEAL

[PATCH 0/10] Use ARRAY_SIZE macro - v4.13-rc7

Use ARRAY_SIZE macro, rather than explicitly coding some variant of it yourself. Found with: find -type f -name "*.c" -o -name "*.h" | xargs perl -p -i -e 's/\bsizeof\s*\(\s*(\w+)\s*\)\s*\ /\s*sizeof\s*\(\s*\1\s*\[\s*0\s*\]\s*\) /ARRAY_SIZE(\1)/g' and manual check/verification. Run against

[PATCH 5/10] [media] lgdt3306a: Use ARRAY_SIZE macro

ication. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- diff --git a/drivers/media/dvb-frontends/lgdt3306a.c b/drivers/media/dvb-frontends/lgdt3306a.c index c9b1eb38444e..724e9aac0f11 100644 --- a/drivers/media/dvb-frontends/lgdt3306a.c +++ b/drivers/media/dvb-frontends/lgdt3306a.c @@ -19,6 +1

[PATCH 0/10] Use ARRAY_SIZE macro - v4.13-rc7

Use ARRAY_SIZE macro, rather than explicitly coding some variant of it yourself. Found with: find -type f -name "*.c" -o -name "*.h" | xargs perl -p -i -e 's/\bsizeof\s*\(\s*(\w+)\s*\)\s*\ /\s*sizeof\s*\(\s*\1\s*\[\s*0\s*\]\s*\) /ARRAY_SIZE(\1)/g' and manual check/verification. Run against

[PATCH 5/10] [media] lgdt3306a: Use ARRAY_SIZE macro

ication. Signed-off-by: Thomas Meyer --- diff --git a/drivers/media/dvb-frontends/lgdt3306a.c b/drivers/media/dvb-frontends/lgdt3306a.c index c9b1eb38444e..724e9aac0f11 100644 --- a/drivers/media/dvb-frontends/lgdt3306a.c +++ b/drivers/media/dvb-frontends/lgdt3306a.c @@ -19,6 +19,7 @@ #define pr_fmt

Re: [PATCH] ipv6: sr: Use ARRAY_SIZE macro

On Fri, Sep 01, 2017 at 08:51:55PM -0700, Joe Perches wrote: > On Fri, 2017-09-01 at 18:35 -0700, David Miller wrote: > > From: Thomas Meyer <tho...@m3y3r.de> > > Date: Thu, 31 Aug 2017 16:18:15 +0200 > > > > > Grepping for "sizeof\(.+\) / sizeof\(" f

Re: [PATCH] ipv6: sr: Use ARRAY_SIZE macro

On Fri, Sep 01, 2017 at 08:51:55PM -0700, Joe Perches wrote: > On Fri, 2017-09-01 at 18:35 -0700, David Miller wrote: > > From: Thomas Meyer > > Date: Thu, 31 Aug 2017 16:18:15 +0200 > > > > > Grepping for "sizeof\(.+\) / sizeof\(" found this as one of

[PATCH 6/6] x86/platform/intel-mid: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- arch/x86/platform/intel-mid/device_libs/platform_gpio_keys.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar

[PATCH 6/6] x86/platform/intel-mid: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer --- arch/x86/platform/intel-mid/device_libs/platform_gpio_keys.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/platform/intel-mid

[PATCH 1/6] perf tools: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- tools/perf/tests/bpf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/tests/bpf.c b/tools/perf/tests

[PATCH 1/6] perf tools: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer --- tools/perf/tests/bpf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/tests/bpf.c b/tools/perf/tests/bpf.c index 5876da126b58

[PATCH 2/6] perf dwarf: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- tools/perf/arch/x86/util/dwarf-regs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/arch/x86/util

[PATCH 2/6] perf dwarf: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer --- tools/perf/arch/x86/util/dwarf-regs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/arch/x86/util/dwarf-regs.c b/tools/perf

[PATCH 3/6] ia64: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- arch/ia64/kernel/perfmon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/ia64/kernel/perfmon.c b/arch/ia64/

[PATCH 4/6] skd: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- drivers/block/skd_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/block/skd_main.c b/drivers

[PATCH 3/6] ia64: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer --- arch/ia64/kernel/perfmon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/ia64/kernel/perfmon.c b/arch/ia64/kernel/perfmon.c index

[PATCH 4/6] skd: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer --- drivers/block/skd_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c index

[PATCH 5/6] powerpc/xmon: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- arch/powerpc/xmon/ppc-opc.c | 14 ++ 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/arch/powerpc/xmon/ppc-o

[PATCH 5/6] powerpc/xmon: Use ARRAY_SIZE macro

Found by a coccinelle run with: make coccicheck MODE=patch COCCI=scripts/coccinelle/misc/array_size.cocci Signed-off-by: Thomas Meyer --- arch/powerpc/xmon/ppc-opc.c | 14 ++ 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/arch/powerpc/xmon/ppc-opc.c b/arch/powerpc

Re: [PATCH v2] vt: Use bsearch library function in is_double_width

On Thu, Aug 31, 2017 at 05:02:53PM +0200, Greg KH wrote: > On Thu, Aug 31, 2017 at 04:21:15PM +0200, Thomas Meyer wrote: > > Use bsearch library function instead of duplicated functionality. > > One question: Having above changelog text and a nearly similar subject line is fine f

Re: [PATCH v2] vt: Use bsearch library function in is_double_width

On Thu, Aug 31, 2017 at 05:02:53PM +0200, Greg KH wrote: > On Thu, Aug 31, 2017 at 04:21:15PM +0200, Thomas Meyer wrote: > > Use bsearch library function instead of duplicated functionality. > > One question: Having above changelog text and a nearly similar subject line is fine f

Re: [PATCH v2] ipv6: sr: Use ARRAY_SIZE macro

On Thu, Aug 31, 2017 at 05:02:09PM +0200, Greg KH wrote: > On Thu, Aug 31, 2017 at 04:20:18PM +0200, Thomas Meyer wrote: > > Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first > > candidates. > > Maybe a coccinelle can catch all of those. >

Re: [PATCH v2] ipv6: sr: Use ARRAY_SIZE macro

On Thu, Aug 31, 2017 at 05:02:09PM +0200, Greg KH wrote: > On Thu, Aug 31, 2017 at 04:20:18PM +0200, Thomas Meyer wrote: > > Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first > > candidates. > > Maybe a coccinelle can catch all of those. >

[PATCH v2] vt: Use bsearch library function in is_double_width

Use bsearch library function instead of duplicated functionality. v2: Re-introduce early exit from old binary search. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- drivers/tty/vt/vt.c | 29 ++--- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/d

[PATCH v2] vt: Use bsearch library function in is_double_width

Use bsearch library function instead of duplicated functionality. v2: Re-introduce early exit from old binary search. Signed-off-by: Thomas Meyer --- drivers/tty/vt/vt.c | 29 ++--- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/drivers/tty/vt/vt.c b

[PATCH v2] ipv6: sr: Use ARRAY_SIZE macro

Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first candidates. Maybe a coccinelle can catch all of those. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- net/ipv6/seg6_hmac.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/net/ip

[PATCH v2] ipv6: sr: Use ARRAY_SIZE macro

Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first candidates. Maybe a coccinelle can catch all of those. Signed-off-by: Thomas Meyer --- net/ipv6/seg6_hmac.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/net/ipv6/seg6_hmac.c

[PATCH] ipv6: sr: Use ARRAY_SIZE macro

Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first candidates. Maybe a coccinelle can catch all of those. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- net/ipv6/seg6_hmac.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/net/ip

[PATCH] ipv6: sr: Use ARRAY_SIZE macro

Grepping for "sizeof\(.+\) / sizeof\(" found this as one of the first candidates. Maybe a coccinelle can catch all of those. Signed-off-by: Thomas Meyer --- net/ipv6/seg6_hmac.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/net/ipv6/seg6_hmac.c

[PATCH] vt: Use bsearch library function in is_double_width

Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- drivers/tty/vt/vt.c | 25 ++--- 1 file changed, 10 insertions(+), 15 deletions(-) diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c index 2ebaba16f785..725777a5d35e 100644 --- a/drivers/tty/vt/vt.c +++ b/drivers/

[PATCH] vt: Use bsearch library function in is_double_width

Signed-off-by: Thomas Meyer --- drivers/tty/vt/vt.c | 25 ++--- 1 file changed, 10 insertions(+), 15 deletions(-) diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c index 2ebaba16f785..725777a5d35e 100644 --- a/drivers/tty/vt/vt.c +++ b/drivers/tty/vt/vt.c @@ -102,6

kselftests results under uml

Hi, I am writing a script which bundles all kselftests and run them under an UML kernel. The script is available here: https://github.com/thomasmey/uml/blob/master/uml-fedora-kselftest.sh kselftests needed some fixing on debian. See the commits here:

kselftests results under uml

Hi, I am writing a script which bundles all kselftests and run them under an UML kernel. The script is available here: https://github.com/thomasmey/uml/blob/master/uml-fedora-kselftest.sh kselftests needed some fixing on debian. See the commits here:

[PATCH 2/2] um: Use relative modversions with LD_SCRIPT_DYN

When building a dynamic kernel image use relative symbols with MODVERSIONS. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- arch/um/Kconfig.um | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/um/Kconfig.um b/arch/um/Kconfig.um index 4b2ed5858b2e..e26376ab5452 100644 --- a/a

[PATCH 1/2] um: link vmlinux with -no-pie

Debian's gcc defaults to pie. The global Makefile already defines the -fno-pie option. Link UML dynamic kernel image also with -no-pie to fix the build. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- arch/um/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/a

[PATCH 1/2] um: link vmlinux with -no-pie

Debian's gcc defaults to pie. The global Makefile already defines the -fno-pie option. Link UML dynamic kernel image also with -no-pie to fix the build. Signed-off-by: Thomas Meyer --- arch/um/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/um/Makefile b/arch

[PATCH 2/2] um: Use relative modversions with LD_SCRIPT_DYN

When building a dynamic kernel image use relative symbols with MODVERSIONS. Signed-off-by: Thomas Meyer --- arch/um/Kconfig.um | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/um/Kconfig.um b/arch/um/Kconfig.um index 4b2ed5858b2e..e26376ab5452 100644 --- a/arch/um/Kconfig.um +++ b/arch

[PATCH] um: Fix CONFIG_GCOV for modules.

Explicitly export symbols so modpost doesn't complain. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- arch/um/kernel/gmon_syms.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/um/kernel/gmon_syms.c b/arch/um/kernel/gmon_syms.c index 1bf61266da8e..f138a4a0db99

[PATCH] um: Fix CONFIG_GCOV for modules.

Explicitly export symbols so modpost doesn't complain. Signed-off-by: Thomas Meyer --- arch/um/kernel/gmon_syms.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/um/kernel/gmon_syms.c b/arch/um/kernel/gmon_syms.c index 1bf61266da8e..f138a4a0db99 100644 --- a/arch/um/kernel

[PATCH] kselftests: timers: Fix frequency step build error

Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- tools/testing/selftests/timers/freq-step.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/timers/freq-step.c b/tools/testing/selftests/timers/freq-step.c index e8c61830825a..150406fe3869

[PATCH] kselftests: timers: Fix frequency step build error

Signed-off-by: Thomas Meyer --- tools/testing/selftests/timers/freq-step.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/testing/selftests/timers/freq-step.c b/tools/testing/selftests/timers/freq-step.c index e8c61830825a..150406fe3869 100644 --- a/tools/testing

Re: make clean all broken with -j? + question regarding modpost

On Sat, Aug 12, 2017 at 12:15:11PM +0900, Masahiro Yamada wrote: > Hi. > > 2017-08-11 3:28 GMT+09:00 Randy Dunlap : > > >> 2.) compile modpost with debug symbols, -g > >> how do I compile the modpost helper program with debug symbols? In what > >> makefile, kbuild file do

Re: make clean all broken with -j? + question regarding modpost

On Sat, Aug 12, 2017 at 12:15:11PM +0900, Masahiro Yamada wrote: > Hi. > > 2017-08-11 3:28 GMT+09:00 Randy Dunlap : > > >> 2.) compile modpost with debug symbols, -g > >> how do I compile the modpost helper program with debug symbols? In what > >> makefile, kbuild file do I need to add the

Re: make clean all broken with -j? + question regarding modpost

On Sat, Aug 12, 2017 at 12:11:50PM +0900, Masahiro Yamada wrote: > Hi. > > > 2017-08-11 7:11 GMT+09:00 Jim Davis <jim.ep...@gmail.com>: > > On Thu, Aug 10, 2017 at 11:28 AM, Randy Dunlap <rdun...@infradead.org> > > wrote: > >> [adding linux-kbuild] &

Re: make clean all broken with -j? + question regarding modpost

On Sat, Aug 12, 2017 at 12:11:50PM +0900, Masahiro Yamada wrote: > Hi. > > > 2017-08-11 7:11 GMT+09:00 Jim Davis : > > On Thu, Aug 10, 2017 at 11:28 AM, Randy Dunlap > > wrote: > >> [adding linux-kbuild] > >> > >> On 08/10/2017 08:42 AM,

make clean all broken with -j? + question regarding modpost

Hi, 1.) make with multiple targets When running $ make -j4 clean all I get error from make (probably in scripts/Makefile.modbuiltin): Output from above with V=1: make -f ./scripts/Makefile.modbuiltin obj=drivers/tty/vt make -f ./scripts/Makefile.modbuiltin obj=drivers/video/backlight (for m in

make clean all broken with -j? + question regarding modpost

Hi, 1.) make with multiple targets When running $ make -j4 clean all I get error from make (probably in scripts/Makefile.modbuiltin): Output from above with V=1: make -f ./scripts/Makefile.modbuiltin obj=drivers/tty/vt make -f ./scripts/Makefile.modbuiltin obj=drivers/video/backlight (for m in

[PATCH] auxdisplay: img-ascii-lcd: Only build on archs that have IOMEM

This avoids the MODPOST error: ERROR: "devm_ioremap_resource" [drivers/auxdisplay/img-ascii-lcd.ko] undefined! Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- drivers/auxdisplay/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/auxdisplay/Kconfig b/drivers/au

[PATCH] auxdisplay: img-ascii-lcd: Only build on archs that have IOMEM

This avoids the MODPOST error: ERROR: "devm_ioremap_resource" [drivers/auxdisplay/img-ascii-lcd.ko] undefined! Signed-off-by: Thomas Meyer --- drivers/auxdisplay/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/auxdisplay/Kconfig b/drivers/auxdisplay/Kco

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

On Tue, Aug 08, 2017 at 02:04:42PM +0200, Willy Tarreau wrote: > Hi Thomas, > > On Tue, Aug 08, 2017 at 01:46:25PM +0200, Thomas Meyer wrote: > > Hi, > > > > did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break a linux kernel > > build with an inclu

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

On Tue, Aug 08, 2017 at 02:04:42PM +0200, Willy Tarreau wrote: > Hi Thomas, > > On Tue, Aug 08, 2017 at 01:46:25PM +0200, Thomas Meyer wrote: > > Hi, > > > > did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break a linux kernel > > build with an inclu

INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

Hi, did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break a linux kernel build with an included ramdisk? As fas as I understand you must expliclity add rootfstype=ramfs to the kernel command line to boot from the included ramfsdisk? bug or feature? with kind regards thomas

INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

Hi, did the commit 6e19eded3684dc184181093af3bff2ff440f5b53 break a linux kernel build with an included ramdisk? As fas as I understand you must expliclity add rootfstype=ramfs to the kernel command line to boot from the included ramfsdisk? bug or feature? with kind regards thomas

Re: um: PTRACE_SETREGSET failure with XSTATE on Kabylake CPU

> Am 20.06.2017 um 21:53 schrieb Yu-cheng Yu : > >> On Tue, 2017-06-20 at 20:59 +0200, Richard Weinberger wrote: >> Yu-cheng, >> >>> Am 20.06.2017 um 20:17 schrieb Richard Weinberger: >>> Yu-cheng, >>> >>> Am 20.06.2017 um 20:04 schrieb Yu-cheng Yu: >> So to

Re: um: PTRACE_SETREGSET failure with XSTATE on Kabylake CPU

> Am 20.06.2017 um 21:53 schrieb Yu-cheng Yu : > >> On Tue, 2017-06-20 at 20:59 +0200, Richard Weinberger wrote: >> Yu-cheng, >> >>> Am 20.06.2017 um 20:17 schrieb Richard Weinberger: >>> Yu-cheng, >>> >>> Am 20.06.2017 um 20:04 schrieb Yu-cheng Yu: >> So to summarize: >> >> -

Re: um: PTRACE_SETREGSET failure with XSTATE on Kabylake CPU

Am Dienstag, den 20.06.2017, 08:58 +0200 schrieb Richard Weinberger: > Thomas, > > Am 20.06.2017 um 03:56 schrieb Thomas Meyer: > > Hi, > > > > I finally did figure out where in the host kernel the ptrace > > syscall > > fails with -EFAULT. > > Nice

Re: um: PTRACE_SETREGSET failure with XSTATE on Kabylake CPU

Am Dienstag, den 20.06.2017, 08:58 +0200 schrieb Richard Weinberger: > Thomas, > > Am 20.06.2017 um 03:56 schrieb Thomas Meyer: > > Hi, > > > > I finally did figure out where in the host kernel the ptrace > > syscall > > fails with -EFAULT. > > Nice

um: PTRACE_SETREGSET failure with XSTATE on Kabylake CPU

Hi, I finally did figure out where in the host kernel the ptrace syscall fails with -EFAULT. In arch/x86/kernel/fpu/regset.c:130: 114 int xstateregs_set(struct task_struct *target, const struct user_regset *regset, 115 unsigned int pos, unsigned int count, 116

um: PTRACE_SETREGSET failure with XSTATE on Kabylake CPU

Hi, I finally did figure out where in the host kernel the ptrace syscall fails with -EFAULT. In arch/x86/kernel/fpu/regset.c:130: 114 int xstateregs_set(struct task_struct *target, const struct user_regset *regset, 115 unsigned int pos, unsigned int count, 116

[PATCH v3] lib/extable.c: use bsearch() library function in search_extable()

v3: Fix arch specific implementations Signed-off-by: Thomas Meyer <tho...@m3y3r.de> --- arch/mips/kernel/module.c | 3 ++- arch/mips/kernel/traps.c | 3 ++- arch/sh/mm/extable_64.c | 34 ++ arch/sparc/mm/extable.c | 28 ++-- i

[PATCH v3] lib/extable.c: use bsearch() library function in search_extable()

v3: Fix arch specific implementations Signed-off-by: Thomas Meyer --- arch/mips/kernel/module.c | 3 ++- arch/mips/kernel/traps.c | 3 ++- arch/sh/mm/extable_64.c | 34 ++ arch/sparc/mm/extable.c | 28 ++-- include/linux/extable.h

[RESEND PATCH v2] lib/extable.c: use bsearch() library function in search_extable()

Signed-off-by: Thomas Meyer <tho...@m3y3r.de> ---  include/linux/extable.h |  3 ++-  kernel/extable.c|  2 +-  kernel/module.c |  2 +-  lib/extable.c   | 38 +++---  4 files changed, 23 insertions(+), 22 deletions(-) diff --git a/include

[RESEND PATCH v2] lib/extable.c: use bsearch() library function in search_extable()

Signed-off-by: Thomas Meyer ---  include/linux/extable.h |  3 ++-  kernel/extable.c|  2 +-  kernel/module.c |  2 +-  lib/extable.c   | 38 +++---  4 files changed, 23 insertions(+), 22 deletions(-) diff --git a/include/linux/extable.h b

[PATCH v2] lib/extable.c: use bsearch() library function in search_extable()

Signed-off-by: Thomas Meyer <tho...@m3y3r.de> ---  include/linux/extable.h |  3 ++-  kernel/extable.c|  2 +-  kernel/module.c |  2 +-  lib/extable.c   | 38 +++---  4 files changed, 23 insertions(+), 22 deletions(-) diff --git a/include

[PATCH v2] lib/extable.c: use bsearch() library function in search_extable()

Signed-off-by: Thomas Meyer ---  include/linux/extable.h |  3 ++-  kernel/extable.c|  2 +-  kernel/module.c |  2 +-  lib/extable.c   | 38 +++---  4 files changed, 23 insertions(+), 22 deletions(-) diff --git a/include/linux/extable.h b

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Freitag, den 02.06.2017, 09:38 +0200 schrieb Richard Weinberger: > Thomas, > > Am 02.06.2017 um 07:49 schrieb Florian Fainelli: > > > the put_fp_registers fails with errno 4 if I recall correctly. > > > > > > I didn't investigate yet further, why the the xstate ptrace call > > > fails. > > >

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Freitag, den 02.06.2017, 09:38 +0200 schrieb Richard Weinberger: > Thomas, > > Am 02.06.2017 um 07:49 schrieb Florian Fainelli: > > > the put_fp_registers fails with errno 4 if I recall correctly. > > > > > > I didn't investigate yet further, why the the xstate ptrace call > > > fails. > > >

Re: [PATCH] lib/extable.c: use bsearch() library function in search_extable()

With kind regards Thomas > Am 02.06.2017 um 01:40 schrieb Rasmus Villemoes <li...@rasmusvillemoes.dk>: > >> On Wed, May 31 2017, Thomas Meyer <tho...@m3y3r.de> wrote: >> >> Signed-off-by: Thomas Meyer <tho...@m3y3r.de> >> --- >> lib/ex

Re: [PATCH] lib/extable.c: use bsearch() library function in search_extable()

With kind regards Thomas > Am 02.06.2017 um 01:40 schrieb Rasmus Villemoes : > >> On Wed, May 31 2017, Thomas Meyer wrote: >> >> Signed-off-by: Thomas Meyer >> --- >> lib/extable.c | 30 +- >> 1 file changed, 13 insert

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Freitag, den 02.06.2017, 10:30 +0200 schrieb Richard Weinberger: > Thomas, > > Am 02.06.2017 um 10:04 schrieb Thomas Meyer: > > Am Donnerstag, den 01.06.2017, 22:49 -0700 schrieb Florian > > Fainelli: > > I see this in the kernel log: > > > >

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Freitag, den 02.06.2017, 10:30 +0200 schrieb Richard Weinberger: > Thomas, > > Am 02.06.2017 um 10:04 schrieb Thomas Meyer: > > Am Donnerstag, den 01.06.2017, 22:49 -0700 schrieb Florian > > Fainelli: > > I see this in the kernel log: > > > >

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Freitag, den 02.06.2017, 10:30 +0200 schrieb Richard Weinberger: > Thomas, > > Am 02.06.2017 um 10:04 schrieb Thomas Meyer: > > Am Donnerstag, den 01.06.2017, 22:49 -0700 schrieb Florian > > Fainelli: > > I see this in the kernel log: > > > >

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Freitag, den 02.06.2017, 10:30 +0200 schrieb Richard Weinberger: > Thomas, > > Am 02.06.2017 um 10:04 schrieb Thomas Meyer: > > Am Donnerstag, den 01.06.2017, 22:49 -0700 schrieb Florian > > Fainelli: > > I see this in the kernel log: > > > >

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Donnerstag, den 01.06.2017, 22:49 -0700 schrieb Florian Fainelli: > > On 06/01/2017 02:25 PM, Thomas Meyer wrote: > > Am Donnerstag, den 01.06.2017, 22:58 +0200 schrieb Richard > > Weinberger: > > > > > > Sorry, I thought you are CC'ed. > > > Th

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Donnerstag, den 01.06.2017, 22:49 -0700 schrieb Florian Fainelli: > > On 06/01/2017 02:25 PM, Thomas Meyer wrote: > > Am Donnerstag, den 01.06.2017, 22:58 +0200 schrieb Richard > > Weinberger: > > > > > > Sorry, I thought you are CC'ed. > > > Th

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Donnerstag, den 01.06.2017, 22:58 +0200 schrieb Richard Weinberger: > > Sorry, I thought you are CC'ed. > Thomas please speak up. AFAIR UML fails to boot on one of your new > Laptops. Hi, yes, the first userspace process failes here: void userspace(struct uml_pt_regs *regs) { int

Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a

Am Donnerstag, den 01.06.2017, 22:58 +0200 schrieb Richard Weinberger: > > Sorry, I thought you are CC'ed. > Thomas please speak up. AFAIR UML fails to boot on one of your new > Laptops. Hi, yes, the first userspace process failes here: void userspace(struct uml_pt_regs *regs) { int

[PATCH] lib/extable.c: use bsearch() library function in search_extable()

Signed-off-by: Thomas Meyer <tho...@m3y3r.de> ---  lib/extable.c | 30 +-  1 file changed, 13 insertions(+), 17 deletions(-) diff --git a/lib/extable.c b/lib/extable.c index 62968da..eb16cb3 100644 --- a/lib/extable.c +++ b/lib/extable.c @@ -9,6 +9,7 @@

[PATCH] lib/extable.c: use bsearch() library function in search_extable()

Signed-off-by: Thomas Meyer ---  lib/extable.c | 30 +-  1 file changed, 13 insertions(+), 17 deletions(-) diff --git a/lib/extable.c b/lib/extable.c index 62968da..eb16cb3 100644 --- a/lib/extable.c +++ b/lib/extable.c @@ -9,6 +9,7 @@   * 2 of the License, or (at your

Re: [PATCH v2] um: Allow building and running on older hosts

> Am 25.05.2017 um 20:36 schrieb Florian Fainelli : > > Commit a78ff1112263 ("um: add extended processor state save/restore > support") and b6024b21fec8 ("um: extend fpstate to _xstate to support > YMM registers") forced the use of the x86 FP _xstate and >

Re: [PATCH v2] um: Allow building and running on older hosts

> Am 25.05.2017 um 20:36 schrieb Florian Fainelli : > > Commit a78ff1112263 ("um: add extended processor state save/restore > support") and b6024b21fec8 ("um: extend fpstate to _xstate to support > YMM registers") forced the use of the x86 FP _xstate and > PTRACE_GETREGSET/SETREGSET. On older

Re: [PATCH] um: Allow building and running on older hosts

> Am 24.05.2017 um 09:01 schrieb Richard Weinberger : > > CC'ing Thomas. We is also facing issues with these commits. > >> Am 24.05.2017 um 03:08 schrieb Florian Fainelli: >> Commit a78ff1112263 ("um: add extended processor state save/restore >> support") and b6024b21fec8 ("um:

Re: [PATCH] um: Allow building and running on older hosts

> Am 24.05.2017 um 09:01 schrieb Richard Weinberger : > > CC'ing Thomas. We is also facing issues with these commits. > >> Am 24.05.2017 um 03:08 schrieb Florian Fainelli: >> Commit a78ff1112263 ("um: add extended processor state save/restore >> support") and b6024b21fec8 ("um: extend fpstate

Re: [uml-devel] [PATCH] um: Add mark_rodata_ro support.

> Am 22.05.2017 um 21:37 schrieb Richard Weinberger <rich...@nod.at>: > > Thomas, > >> Am 22.05.2017 um 21:18 schrieb Thomas Meyer: >> >>> Am 22.05.2017 um 20:34 schrieb Richard Weinberger <rich...@nod.at>: >>> >>> Thomas, &

Re: [uml-devel] [PATCH] um: Add mark_rodata_ro support.

> Am 22.05.2017 um 21:37 schrieb Richard Weinberger : > > Thomas, > >> Am 22.05.2017 um 21:18 schrieb Thomas Meyer: >> >>> Am 22.05.2017 um 20:34 schrieb Richard Weinberger : >>> >>> Thomas, >>> >>>> Am 22.05.2

Re: [uml-devel] [PATCH] um: Add mark_rodata_ro support.

> Am 22.05.2017 um 20:34 schrieb Richard Weinberger <rich...@nod.at>: > > Thomas, > >> Am 22.05.2017 um 20:14 schrieb Thomas Meyer: >> It's purely cosmetic; to get rid of the boot message: "This architecture >> does not have kernel memory protection

Re: [uml-devel] [PATCH] um: Add mark_rodata_ro support.

> Am 22.05.2017 um 20:34 schrieb Richard Weinberger : > > Thomas, > >> Am 22.05.2017 um 20:14 schrieb Thomas Meyer: >> It's purely cosmetic; to get rid of the boot message: "This architecture >> does not have kernel memory protection." in init/main.c >

Re: [uml-devel] [PATCH] um: Add mark_rodata_ro support.

> Am 21.05.2017 um 23:28 schrieb Richard Weinberger > <richard.weinber...@gmail.com>: > > Thomas, > >> On Thu, May 18, 2017 at 12:11 AM, Thomas Meyer <tho...@m3y3r.de> wrote: >> This is actually a no-op as all read-only should be read-only in the ELF

Re: [uml-devel] [PATCH] um: Add mark_rodata_ro support.

> Am 21.05.2017 um 23:28 schrieb Richard Weinberger > : > > Thomas, > >> On Thu, May 18, 2017 at 12:11 AM, Thomas Meyer wrote: >> This is actually a no-op as all read-only should be read-only in the ELF. > > What problem does this patch fix? Or what is the pu

[PATCH] um: Add mark_rodata_ro support.

This is actually a no-op as all read-only should be read-only in the ELF. Signed-off-by: Thomas Meyer <tho...@m3y3r.de> ---  arch/um/Kconfig.common | 1 +  arch/um/kernel/mem.c   | 5 -  2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/um/Kconfig.common b/a

[PATCH] um: Add mark_rodata_ro support.

This is actually a no-op as all read-only should be read-only in the ELF. Signed-off-by: Thomas Meyer ---  arch/um/Kconfig.common | 1 +  arch/um/kernel/mem.c   | 5 -  2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/um/Kconfig.common b/arch/um/Kconfig.common index 85f6dd2

[PATCH] um: Don't build arch/x86/um/user-offsets.s with gcc plugins

/gcc-plugins/latent_entropy_plugin.so   HOSTCXX -fPIC scripts/gcc-plugins/structleak_plugin.o   HOSTLLD -shared scripts/gcc-plugins/structleak_plugin.so Signed-off-by: Thomas Meyer <tho...@m3y3r.de> ---  arch/x86/um/Makefile | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ar

[PATCH] um: Don't build arch/x86/um/user-offsets.s with gcc plugins

/gcc-plugins/latent_entropy_plugin.so   HOSTCXX -fPIC scripts/gcc-plugins/structleak_plugin.o   HOSTLLD -shared scripts/gcc-plugins/structleak_plugin.so Signed-off-by: Thomas Meyer ---  arch/x86/um/Makefile | 2 +-  1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/um/Makefile b

[ACPI] BUG: KASan: out of bounds on stack in vsnprintf

Hi, I started to run my kernels with KASan enabled and found this after resume from ram on a 4.3.3 kernel: Jan 01 15:16:59 localhost.localdomain kernel: == Jan 01 15:16:59 localhost.localdomain kernel: BUG: KASan: out of bounds on

[ACPI] BUG: KASan: out of bounds on stack in vsnprintf

Hi, I started to run my kernels with KASan enabled and found this after resume from ram on a 4.3.3 kernel: Jan 01 15:16:59 localhost.localdomain kernel: == Jan 01 15:16:59 localhost.localdomain kernel: BUG: KASan: out of bounds on

Re: [uml-devel] [PATCH] um: link with -lpthread

Am 31.12.2015 5:06 nachm. schrieb Vegard Nossum : > > Similarly to commit fb1770aa78a43530940d0c2dd161e77bc705bdac, with gcc 5 > on Ubuntu and CONFIG_STATIC_LINK=y I was seeing these linker errors: Hi, Oops, yes this patch looks good to me. Honestly I did never test the static link case.

<    1   2   3   4   5   6   7   >