[PATCH 3/3] Input: synaptics-rmi4 - log when we create a guest serio port

To ease analyzing boot behavior from logs, let's log when we are about to register the pass-through serio port. Also, let's drop "Synaptics" prefix from the port name, as RMI4 is good enough indicator already, and having the prefix means that the name does not fit into serio->name field. While at

[PATCH 3/3] Input: synaptics-rmi4 - log when we create a guest serio port

To ease analyzing boot behavior from logs, let's log when we are about to register the pass-through serio port. Also, let's drop "Synaptics" prefix from the port name, as RMI4 is good enough indicator already, and having the prefix means that the name does not fit into serio->name field. While at

[PATCH 2/3] Input: synaptics_rmi4 - unmask F03 interrupts when port is opened

Currently we register the pass-through serio port when we probe the F03 RMI function, and then, in sensor configure phase, we unmask interrupts. Unfortunately this is too late, as other drivers are free probe devices attached to the serio port as soon as it is probed. Because interrupts are

[PATCH 2/3] Input: synaptics_rmi4 - unmask F03 interrupts when port is opened

Currently we register the pass-through serio port when we probe the F03 RMI function, and then, in sensor configure phase, we unmask interrupts. Unfortunately this is too late, as other drivers are free probe devices attached to the serio port as soon as it is probed. Because interrupts are

[PATCH] drm/vmwgfx: Return boolean instead of integer in vmw_fence_obj_signaled

Return statements in functions returning bool should use true/false instead of 1/0. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] drm/vmwgfx: Return boolean instead of integer in vmw_fence_obj_signaled

Return statements in functions returning bool should use true/false instead of 1/0. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/gpu/drm/vmwgfx/vmwgfx_fence.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH 30/35] x86/speculation: Use Indirect Branch Prediction Barrier in context switch

On 01/18/2018 05:48 AM, Peter Zijlstra wrote: > >+ /* >+ * Avoid user/user BTB poisoning by flushing the branch >predictor >+ * when switching between processes. This stops one process from >+ * doing spectre-v2 attacks on another process's

Re: [PATCH 30/35] x86/speculation: Use Indirect Branch Prediction Barrier in context switch

On 01/18/2018 05:48 AM, Peter Zijlstra wrote: > >+ /* >+ * Avoid user/user BTB poisoning by flushing the branch >predictor >+ * when switching between processes. This stops one process from >+ * doing spectre-v2 attacks on another process's

[PATCH] selftests: bpf: update .gitignore with missing generated files

Update .gitignore with missing generated files. Signed-off-by: Shuah Khan --- tools/testing/selftests/bpf/.gitignore | 7 +++ 1 file changed, 7 insertions(+) diff --git a/tools/testing/selftests/bpf/.gitignore b/tools/testing/selftests/bpf/.gitignore index

[PATCH] selftests: bpf: update .gitignore with missing generated files

Update .gitignore with missing generated files. Signed-off-by: Shuah Khan --- tools/testing/selftests/bpf/.gitignore | 7 +++ 1 file changed, 7 insertions(+) diff --git a/tools/testing/selftests/bpf/.gitignore b/tools/testing/selftests/bpf/.gitignore index 541d9d7fad5a..1e09d77f1948

[PATCH] selftests: vm: update .gitignore with missing generated file

Add missing generated file to .gitignore. Signed-off-by: Shuah Khan --- tools/testing/selftests/vm/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/testing/selftests/vm/.gitignore b/tools/testing/selftests/vm/.gitignore index

[PATCH] selftests: vm: update .gitignore with missing generated file

Add missing generated file to .gitignore. Signed-off-by: Shuah Khan --- tools/testing/selftests/vm/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/testing/selftests/vm/.gitignore b/tools/testing/selftests/vm/.gitignore index 1ca2ee4d15b9..63c94d776e89 100644 ---

Re: [PATCHv2] selftests/x86: Add {,_32,_64} targets

On 01/18/2018 03:26 PM, Dmitry Safonov wrote: > One can only use `make all` or `make _` > as make targets. > `make ` doesn't work as Ingo noticed: > x86> make test_vsyscall > gcc -O2 -g -std=gnu99 -pthread -Wall -no-pie test_vsyscall.c -o > test_vsyscall > /tmp/aBaoo3nb.o: In function

Re: [PATCHv2] selftests/x86: Add {,_32,_64} targets

On 01/18/2018 03:26 PM, Dmitry Safonov wrote: > One can only use `make all` or `make _` > as make targets. > `make ` doesn't work as Ingo noticed: > x86> make test_vsyscall > gcc -O2 -g -std=gnu99 -pthread -Wall -no-pie test_vsyscall.c -o > test_vsyscall > /tmp/aBaoo3nb.o: In function

Re: [PATCH-next] init/main.c: make local symbol static

On Thu, 18 Jan 2018 18:33:27 -0500 Christopher Díaz Riveros wrote: > > > What about the other user(s) of envp_init? > > > > It looks like it's referenced in init/do_mounts_initrd.c. Rather > > than making it static, it should be declared in .h file. > > > > Ok, I'll

mmotm 2018-01-18-16-31 uploaded

The mm-of-the-moment snapshot 2018-01-18-16-31 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH-next] init/main.c: make local symbol static

On Thu, 18 Jan 2018 18:33:27 -0500 Christopher Díaz Riveros wrote: > > > What about the other user(s) of envp_init? > > > > It looks like it's referenced in init/do_mounts_initrd.c. Rather > > than making it static, it should be declared in .h file. > > > > Ok, I'll try to figure it out,

mmotm 2018-01-18-16-31 uploaded

The mm-of-the-moment snapshot 2018-01-18-16-31 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH 4.4 040/115] scsi: hpsa: update check for logical volume status

On Mon, 2017-12-18 at 16:48 +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Don Brace > > > [ Upstream commit 85b29008d8af6d94a0723aaa8d93cfb6e041158b ] > >  - Add in a

Re: [PATCH 4.4 040/115] scsi: hpsa: update check for logical volume status

On Mon, 2017-12-18 at 16:48 +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Don Brace > > > [ Upstream commit 85b29008d8af6d94a0723aaa8d93cfb6e041158b ] > >  - Add in a new case for volume

Re: [PATCH] selftests/x86: Add {,_32,_64} targets

On 01/18/2018 04:10 PM, Andy Lutomirski wrote: > On Thu, Jan 18, 2018 at 2:19 PM, Dmitry Safonov wrote: >> One can only use `make all` or `make _` >> as make targets. >> `make ` doesn't work as Ingo noticed: >> x86> make test_vsyscall >> gcc -O2 -g -std=gnu99 -pthread -Wall

Re: [PATCH] selftests/x86: Add {,_32,_64} targets

On 01/18/2018 04:10 PM, Andy Lutomirski wrote: > On Thu, Jan 18, 2018 at 2:19 PM, Dmitry Safonov wrote: >> One can only use `make all` or `make _` >> as make targets. >> `make ` doesn't work as Ingo noticed: >> x86> make test_vsyscall >> gcc -O2 -g -std=gnu99 -pthread -Wall -no-pie

Re: [PATCH v2] x86/microcode/intel: Extend BDW late-loading with LLC size check

在 2018/1/17 上午5:51, Borislav Petkov 写道: > On Tue, Jan 16, 2018 at 01:30:19PM -0800, Luck, Tony wrote: >> I could get you a list of model numbers that you can check against >> model_name. > > Yeah, we're not doing that again. :) > >> But that seems way worse. Especially as the 2.5MB thing is

Re: [PATCH v2] x86/microcode/intel: Extend BDW late-loading with LLC size check

在 2018/1/17 上午5:51, Borislav Petkov 写道: > On Tue, Jan 16, 2018 at 01:30:19PM -0800, Luck, Tony wrote: >> I could get you a list of model numbers that you can check against >> model_name. > > Yeah, we're not doing that again. :) > >> But that seems way worse. Especially as the 2.5MB thing is

Re: [PATCH V8 1/5] crypto: Multi-buffer encryption infrastructure support

On Thu, 2018-01-18 at 22:39 +1100, Herbert Xu wrote: > On Tue, Jan 09, 2018 at 04:09:04PM -0800, Megha Dey wrote: > > > > +static void mcryptd_skcipher_encrypt(struct crypto_async_request *base, > > + int err) > > +{ > > + struct

Re: [PATCH V8 1/5] crypto: Multi-buffer encryption infrastructure support

On Thu, 2018-01-18 at 22:39 +1100, Herbert Xu wrote: > On Tue, Jan 09, 2018 at 04:09:04PM -0800, Megha Dey wrote: > > > > +static void mcryptd_skcipher_encrypt(struct crypto_async_request *base, > > + int err) > > +{ > > + struct

[PATCH v3] x86/microcode/intel: Extend BDW late-loading with LLC size check

The commit b94b73733171 ("x86/microcode/intel: Extend BDW late-loading with a revision check") reduces the impact of erratum BDF90 for Broadwell process model. Actually, the impact can be reduced further through adding the checks for the size of LLC per core. For more details, see erratum BDF90

[PATCH v3] x86/microcode/intel: Extend BDW late-loading with LLC size check

The commit b94b73733171 ("x86/microcode/intel: Extend BDW late-loading with a revision check") reduces the impact of erratum BDF90 for Broadwell process model. Actually, the impact can be reduced further through adding the checks for the size of LLC per core. For more details, see erratum BDF90

[PATCH] usbip: vhci_hcd: update 'status' file header and format

Commit 2f2d0088eb93 ("usbip: prevent vhci_hcd driver from leaking a socket pointer address") in the /sys/devices/platform/vhci_hcd/status. Fix the header and field alignment to reflect the changes and make it easier to read. Signed-off-by: Shuah Khan ---

[PATCH] usbip: vhci_hcd: update 'status' file header and format

Commit 2f2d0088eb93 ("usbip: prevent vhci_hcd driver from leaking a socket pointer address") in the /sys/devices/platform/vhci_hcd/status. Fix the header and field alignment to reflect the changes and make it easier to read. Signed-off-by: Shuah Khan --- drivers/usb/usbip/vhci_sysfs.c | 12

Re: [PATCH] bridge: return boolean instead of integer in br_multicast_is_router

On Thu, 18 Jan 2018 17:37:45 -0600 "Gustavo A. R. Silva" wrote: > Return statements in functions returning bool should use > true/false instead of 1/0. > > This issue was detected with the help of Coccinelle. > > Signed-off-by: Gustavo A. R. Silva

Re: [PATCH] bridge: return boolean instead of integer in br_multicast_is_router

On Thu, 18 Jan 2018 17:37:45 -0600 "Gustavo A. R. Silva" wrote: > Return statements in functions returning bool should use > true/false instead of 1/0. > > This issue was detected with the help of Coccinelle. > > Signed-off-by: Gustavo A. R. Silva LGTM Fixes: 85b352693264 ("bridge: Fix

Re: [PATCH v5 1/2] printk: Add console owner and waiter logic to load balance console writes

On Thu, 18 Jan 2018 23:03:24 +0100 Pavel Machek wrote: > > To demonstrate the issue, this module has been shown to lock up a > > system with 4 CPUs and a slow console (like a serial console). It is > > also able to lock up a 8 CPU system with only a fast (VGA) console, by > >

Re: [PATCH v5 1/2] printk: Add console owner and waiter logic to load balance console writes

On Thu, 18 Jan 2018 23:03:24 +0100 Pavel Machek wrote: > > To demonstrate the issue, this module has been shown to lock up a > > system with 4 CPUs and a slow console (like a serial console). It is > > also able to lock up a 8 CPU system with only a fast (VGA) console, by > > passing in

[PATCH v4 08/10] vfs, fdtable: prevent bounds-check bypass via speculative execution

'fd' is a user controlled value that is used as a data dependency to read from the 'fdt->fd' array. In order to avoid potential leaks of kernel memory values, block speculative execution of the instruction stream that could issue reads based on an invalid 'file *' returned from __fcheck_files.

[PATCH] ARM: dts: imx6ull: add Toradex Colibri iMX6ULL support

Add support for the Computer on Module Colibri iMX6ULL and its Bluetooth/Wifi variant along with the development/evaluation carrier board device trees. Follow the usual hierarchic include model, maintaining shared configuration in imx6ull-colibri.dtsi and imx6ull-colibri-eval-v3.dtsi respectively.

[PATCH v4 08/10] vfs, fdtable: prevent bounds-check bypass via speculative execution

'fd' is a user controlled value that is used as a data dependency to read from the 'fdt->fd' array. In order to avoid potential leaks of kernel memory values, block speculative execution of the instruction stream that could issue reads based on an invalid 'file *' returned from __fcheck_files.

[PATCH] ARM: dts: imx6ull: add Toradex Colibri iMX6ULL support

Add support for the Computer on Module Colibri iMX6ULL and its Bluetooth/Wifi variant along with the development/evaluation carrier board device trees. Follow the usual hierarchic include model, maintaining shared configuration in imx6ull-colibri.dtsi and imx6ull-colibri-eval-v3.dtsi respectively.

[PATCH v4 05/10] x86, __get_user: use __uaccess_begin_nospec

Quoting Linus: I do think that it would be a good idea to very expressly document the fact that it's not that the user access itself is unsafe. I do agree that things like "get_user()" want to be protected, but not because of any direct bugs or problems with get_user() and

[PATCH v4 05/10] x86, __get_user: use __uaccess_begin_nospec

Quoting Linus: I do think that it would be a good idea to very expressly document the fact that it's not that the user access itself is unsafe. I do agree that things like "get_user()" want to be protected, but not because of any direct bugs or problems with get_user() and

[PATCH v4 09/10] kvm, x86: fix spectre-v1 mitigation

Commit 75f139aaf896 "KVM: x86: Add memory barrier on vmcs field lookup" added a raw 'asm("lfence");' to prevent a bounds check bypass of 'vmcs_field_to_offset_table'. This does not work for some AMD cpus, see the 'ifence' helper, and it otherwise does not use the common 'array_ptr' helper designed

[PATCH v4 07/10] x86: narrow out of bounds syscalls to sys_read under speculation

The syscall table base is a user controlled function pointer in kernel space. Like, 'get_user, use 'MASK_NOSPEC' to prevent any out of bounds speculation. While retpoline prevents speculating into the user controlled target it does not stop the pointer de-reference, the concern is leaking memory

[PATCH v4 09/10] kvm, x86: fix spectre-v1 mitigation

Commit 75f139aaf896 "KVM: x86: Add memory barrier on vmcs field lookup" added a raw 'asm("lfence");' to prevent a bounds check bypass of 'vmcs_field_to_offset_table'. This does not work for some AMD cpus, see the 'ifence' helper, and it otherwise does not use the common 'array_ptr' helper designed

[PATCH v4 07/10] x86: narrow out of bounds syscalls to sys_read under speculation

The syscall table base is a user controlled function pointer in kernel space. Like, 'get_user, use 'MASK_NOSPEC' to prevent any out of bounds speculation. While retpoline prevents speculating into the user controlled target it does not stop the pointer de-reference, the concern is leaking memory

[PATCH v4 10/10] nl80211: sanitize array index in parse_txq_params

Wireless drivers rely on parse_txq_params to validate that txq_params->ac is less than NL80211_NUM_ACS by the time the low-level driver's ->conf_tx() handler is called. Use a new helper, 'array_idx', to sanitize txq_params->ac with respect to speculation. I.e. ensure that any speculation into

[PATCH v4 10/10] nl80211: sanitize array index in parse_txq_params

Wireless drivers rely on parse_txq_params to validate that txq_params->ac is less than NL80211_NUM_ACS by the time the low-level driver's ->conf_tx() handler is called. Use a new helper, 'array_idx', to sanitize txq_params->ac with respect to speculation. I.e. ensure that any speculation into

[PATCH v4 06/10] x86, get_user: use pointer masking to limit speculation

Quoting Linus: I do think that it would be a good idea to very expressly document the fact that it's not that the user access itself is unsafe. I do agree that things like "get_user()" want to be protected, but not because of any direct bugs or problems with get_user() and

[PATCH v4 06/10] x86, get_user: use pointer masking to limit speculation

Quoting Linus: I do think that it would be a good idea to very expressly document the fact that it's not that the user access itself is unsafe. I do agree that things like "get_user()" want to be protected, but not because of any direct bugs or problems with get_user() and

[PATCH v4 04/10] x86: introduce __uaccess_begin_nospec and ifence

For '__get_user' paths, do not allow the kernel to speculate on the value of a user controlled pointer. In addition to the 'stac' instruction for Supervisor Mode Access Protection, an 'ifence' causes the 'access_ok' result to resolve in the pipeline before the cpu might take any speculative action

[PATCH v4 04/10] x86: introduce __uaccess_begin_nospec and ifence

For '__get_user' paths, do not allow the kernel to speculate on the value of a user controlled pointer. In addition to the 'stac' instruction for Supervisor Mode Access Protection, an 'ifence' causes the 'access_ok' result to resolve in the pipeline before the cpu might take any speculative action

[PATCH v4 03/10] x86: implement array_ptr_mask()

'array_ptr' uses a mask to sanitize user controllable pointers. The x86 'array_ptr_mask' is an assembler optimized way to generate a 0 or ~0 mask if an array index is out-of-bounds or in-bounds. Suggested-by: Linus Torvalds Cc: Thomas Gleixner

[PATCH v4 03/10] x86: implement array_ptr_mask()

'array_ptr' uses a mask to sanitize user controllable pointers. The x86 'array_ptr_mask' is an assembler optimized way to generate a 0 or ~0 mask if an array index is out-of-bounds or in-bounds. Suggested-by: Linus Torvalds Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc:

[PATCH v4 02/10] asm/nospec, array_ptr: sanitize speculative array de-references

'array_ptr' is proposed as a generic mechanism to mitigate against Spectre-variant-1 attacks, i.e. an attack that bypasses boundary checks via speculative execution). The 'array_ptr' implementation is expected to be safe for current generation cpus across multiple architectures (ARM, x86). Based

[PATCH v4 02/10] asm/nospec, array_ptr: sanitize speculative array de-references

'array_ptr' is proposed as a generic mechanism to mitigate against Spectre-variant-1 attacks, i.e. an attack that bypasses boundary checks via speculative execution). The 'array_ptr' implementation is expected to be safe for current generation cpus across multiple architectures (ARM, x86). Based

[PATCH v4 00/10] prevent bounds-check bypass via speculative execution

Changes since v3 [1] * Drop 'ifence_array_ptr' and associated compile-time + run-time switching and just use the masking approach all the time. * Convert 'get_user' to use pointer sanitization via masking rather than lfence. '__get_user' and associated paths still rely on lfence. (Linus)

[PATCH v4 00/10] prevent bounds-check bypass via speculative execution

Changes since v3 [1] * Drop 'ifence_array_ptr' and associated compile-time + run-time switching and just use the masking approach all the time. * Convert 'get_user' to use pointer sanitization via masking rather than lfence. '__get_user' and associated paths still rely on lfence. (Linus)

[PATCH v4 01/10] Documentation: document array_ptr

From: Mark Rutland Document the rationale and usage of the new array_ptr() helper. Signed-off-by: Mark Rutland Signed-off-by: Will Deacon Cc: Dan Williams Cc: Jonathan Corbet Cc: Peter

[PATCH v4 01/10] Documentation: document array_ptr

From: Mark Rutland Document the rationale and usage of the new array_ptr() helper. Signed-off-by: Mark Rutland Signed-off-by: Will Deacon Cc: Dan Williams Cc: Jonathan Corbet Cc: Peter Zijlstra Reviewed-by: Kees Cook Signed-off-by: Dan Williams --- Documentation/speculation.txt | 143

[PATCH 5/6] sched/nohz: Remove the 1 Hz tick code

Now that the 1Hz tick is offloaded to workqueues, we can safely remove the residual code that used to handle it locally. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino

[PATCH 4/6] sched/isolation: Residual 1Hz scheduler tick offload

When a CPU runs in full dynticks mode, a 1Hz tick remains in order to keep the scheduler stats alive. However this residual tick is a burden for bare metal tasks that can't stand any interruption at all, or want to minimize them. The usual boot parameters "nohz_full=" or "isolcpus=nohz" will now

[PATCH 5/6] sched/nohz: Remove the 1 Hz tick code

Now that the 1Hz tick is offloaded to workqueues, we can safely remove the residual code that used to handle it locally. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van

[PATCH 4/6] sched/isolation: Residual 1Hz scheduler tick offload

When a CPU runs in full dynticks mode, a 1Hz tick remains in order to keep the scheduler stats alive. However this residual tick is a burden for bare metal tasks that can't stand any interruption at all, or want to minimize them. The usual boot parameters "nohz_full=" or "isolcpus=nohz" will now

[PATCH 2/6] nohz: Allow to check if remote CPU tick is stopped

This check is racy but provides a good heuristic to determine whether a CPU may need a remote tick or not. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc:

[PATCH 2/6] nohz: Allow to check if remote CPU tick is stopped

This check is racy but provides a good heuristic to determine whether a CPU may need a remote tick or not. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van Riel Cc: Thomas

[PATCH 3/6] sched/isolation: Isolate workqueues when "nohz_full=" is set

As we prepare for offloading the residual 1hz scheduler ticks to workqueue, let's affine those to housekeepers so that they don't interrupt the CPUs that don't want to be disturbed. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph

[PATCH 3/6] sched/isolation: Isolate workqueues when "nohz_full=" is set

As we prepare for offloading the residual 1hz scheduler ticks to workqueue, let's affine those to housekeepers so that they don't interrupt the CPUs that don't want to be disturbed. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike

[PATCH 6/6] sched/isolation: Tick offload documentation

Update the documentation to reflect the 1Hz tick offload changes. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E.

[PATCH 6/6] sched/isolation: Tick offload documentation

Update the documentation to reflect the 1Hz tick offload changes. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van Riel Cc: Thomas Gleixner Cc: Wanpeng Li Cc: Ingo Molnar

[PATCH 1/6] sched: Rename init_rq_hrtick to hrtick_rq_init

Do that rename in order to normalize the hrtick namespace. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney

[PATCH 1/6] sched: Rename init_rq_hrtick to hrtick_rq_init

Do that rename in order to normalize the hrtick namespace. Signed-off-by: Frederic Weisbecker Cc: Chris Metcalf Cc: Christoph Lameter Cc: Luiz Capitulino Cc: Mike Galbraith Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Rik van Riel Cc: Thomas Gleixner Cc: Wanpeng Li Cc: Ingo Molnar ---

[GIT PULL] isolation: 1Hz residual tick offloading v4

Ingo, Please pull the sched/0hz-v2 branch that can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git sched/0hz-v2 HEAD: 9b14d5204490f9acd03998a5e406ecadb87cddba Changes in v4: * Remove the nohz_offload option, just stick with the existing

[GIT PULL] isolation: 1Hz residual tick offloading v4

Ingo, Please pull the sched/0hz-v2 branch that can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git sched/0hz-v2 HEAD: 9b14d5204490f9acd03998a5e406ecadb87cddba Changes in v4: * Remove the nohz_offload option, just stick with the existing

[PATCH] cpufreq: imx6q: support frequencies >528MHz for i.MX6UL/ULL

Depending on SKU i.MX6UL/i.MX6ULL support frequencies up to 900MHz. Use PLL1 sys clock for all operating points higher than 528MHz. Note: For higher operating points VDD_SOC_IN needs to be 125mV higher than the ARM set-point (see datasheet). Specifically, the i.MX6UL/ULL EVK boards have an

[PATCH] cpufreq: imx6q: support frequencies >528MHz for i.MX6UL/ULL

Depending on SKU i.MX6UL/i.MX6ULL support frequencies up to 900MHz. Use PLL1 sys clock for all operating points higher than 528MHz. Note: For higher operating points VDD_SOC_IN needs to be 125mV higher than the ARM set-point (see datasheet). Specifically, the i.MX6UL/ULL EVK boards have an

[PATCH] smc: return boolean instead of integer in using_ipsec

Return statements in functions returning bool should use true/false instead of 1/0. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- net/smc/smc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] smc: return boolean instead of integer in using_ipsec

Return statements in functions returning bool should use true/false instead of 1/0. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- net/smc/smc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/smc/smc.h b/net/smc/smc.h index

[PATCH] ssb: return boolean instead of integer in ssb_dma_translation_special_bit

Return statements in functions returning bool should use true/false instead of 1/0. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/ssb/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] ssb: return boolean instead of integer in ssb_dma_translation_special_bit

Return statements in functions returning bool should use true/false instead of 1/0. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/ssb/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/ssb/main.c

Re: [mm 4.15-rc8] Random oopses under memory pressure.

On Thu, Jan 18, 2018 at 09:26:25AM -0800, Linus Torvalds wrote: > On Thu, Jan 18, 2018 at 8:56 AM, Kirill A. Shutemov > wrote: > > > > I can't say I fully grasp how 'diff' got this value and how it leads to both > > checks being false. > > I think the problem is that page

Re: [mm 4.15-rc8] Random oopses under memory pressure.

On Thu, Jan 18, 2018 at 09:26:25AM -0800, Linus Torvalds wrote: > On Thu, Jan 18, 2018 at 8:56 AM, Kirill A. Shutemov > wrote: > > > > I can't say I fully grasp how 'diff' got this value and how it leads to both > > checks being false. > > I think the problem is that page difference when they

[PATCH bpf-next v6 2/4] libbpf: add error reporting in XDP

Parse netlink ext attribute to get the error message returned by the card. Code is partially take from libnl. Signed-off-by: Eric Leblond Acked-by: Alexei Starovoitov --- samples/bpf/Makefile | 2 +- tools/lib/bpf/Build| 2 +- tools/lib/bpf/bpf.c|

[PATCH bpf-next v6 2/4] libbpf: add error reporting in XDP

Parse netlink ext attribute to get the error message returned by the card. Code is partially take from libnl. Signed-off-by: Eric Leblond Acked-by: Alexei Starovoitov --- samples/bpf/Makefile | 2 +- tools/lib/bpf/Build| 2 +- tools/lib/bpf/bpf.c| 8 +++ tools/lib/bpf/nlattr.c

[PATCH bpf-next v6 1/4] libbpf: add function to setup XDP

Most of the code is taken from set_link_xdp_fd() in bpf_load.c and slightly modified to be library compliant. Signed-off-by: Eric Leblond Acked-by: Alexei Starovoitov --- tools/lib/bpf/bpf.c| 126 +

[PATCH bpf-next 0/4] libbpf: add XDP binding support

Hello, This patchset rebases the libbpf code on latest bpf-next code and addresses remarks by Daniel. Best regards, -- Eric Leblond

[PATCH bpf-next v6 1/4] libbpf: add function to setup XDP

Most of the code is taken from set_link_xdp_fd() in bpf_load.c and slightly modified to be library compliant. Signed-off-by: Eric Leblond Acked-by: Alexei Starovoitov --- tools/lib/bpf/bpf.c| 126 + tools/lib/bpf/libbpf.c | 2 +

[PATCH bpf-next 0/4] libbpf: add XDP binding support

Hello, This patchset rebases the libbpf code on latest bpf-next code and addresses remarks by Daniel. Best regards, -- Eric Leblond

[PATCH bpf-next v6 4/4] samples/bpf: use bpf_set_link_xdp_fd

Use bpf_set_link_xdp_fd instead of set_link_xdp_fd to remove some code duplication and benefit of netlink ext ack errors message. Signed-off-by: Eric Leblond --- samples/bpf/bpf_load.c | 102 samples/bpf/bpf_load.h |

[PATCH bpf-next v6 4/4] samples/bpf: use bpf_set_link_xdp_fd

Use bpf_set_link_xdp_fd instead of set_link_xdp_fd to remove some code duplication and benefit of netlink ext ack errors message. Signed-off-by: Eric Leblond --- samples/bpf/bpf_load.c | 102 samples/bpf/bpf_load.h | 2 +-

[PATCH bpf-next v6 3/4] libbpf: add missing SPDX-License-Identifier

Signed-off-by: Eric Leblond Acked-by: Alexei Starovoitov --- tools/lib/bpf/bpf.c| 2 ++ tools/lib/bpf/bpf.h| 2 ++ tools/lib/bpf/libbpf.c | 2 ++ tools/lib/bpf/libbpf.h | 2 ++ 4 files changed, 8 insertions(+) diff --git a/tools/lib/bpf/bpf.c

[PATCH bpf-next v6 3/4] libbpf: add missing SPDX-License-Identifier

Signed-off-by: Eric Leblond Acked-by: Alexei Starovoitov --- tools/lib/bpf/bpf.c| 2 ++ tools/lib/bpf/bpf.h| 2 ++ tools/lib/bpf/libbpf.c | 2 ++ tools/lib/bpf/libbpf.h | 2 ++ 4 files changed, 8 insertions(+) diff --git a/tools/lib/bpf/bpf.c b/tools/lib/bpf/bpf.c index

[PATCH] bridge: return boolean instead of integer in br_multicast_is_router

Return statements in functions returning bool should use true/false instead of 1/0. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- net/bridge/br_private.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] bridge: return boolean instead of integer in br_multicast_is_router

Return statements in functions returning bool should use true/false instead of 1/0. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- net/bridge/br_private.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/bridge/br_private.h

Re: [PATCH bpf-next v5 2/4] libbpf: add error reporting in XDP

Hi, Sorry for the delay, missed the mail. On Sat, 2018-01-06 at 22:16 +0100, Daniel Borkmann wrote: > On 01/04/2018 09:21 AM, Eric Leblond wrote: > > Parse netlink ext attribute to get the error message returned by > > the card. Code is partially take from libnl. > > > > Signed-off-by: Eric

Re: [PATCH bpf-next v5 2/4] libbpf: add error reporting in XDP

Hi, Sorry for the delay, missed the mail. On Sat, 2018-01-06 at 22:16 +0100, Daniel Borkmann wrote: > On 01/04/2018 09:21 AM, Eric Leblond wrote: > > Parse netlink ext attribute to get the error message returned by > > the card. Code is partially take from libnl. > > > > Signed-off-by: Eric

Re: [PATCH 23/35] x86/speculation: Add basic speculation control code

On 18/01/2018 23:25, Andy Lutomirski wrote: > On Thu, Jan 18, 2018 at 11:08 AM, Andrea Arcangeli > wrote: >> On Thu, Jan 18, 2018 at 12:24:31PM -0600, Josh Poimboeuf wrote: >>> On Thu, Jan 18, 2018 at 06:12:36PM +0100, Paolo Bonzini wrote: On 18/01/2018 18:08, Dave

Re: [PATCH 23/35] x86/speculation: Add basic speculation control code

On 18/01/2018 23:25, Andy Lutomirski wrote: > On Thu, Jan 18, 2018 at 11:08 AM, Andrea Arcangeli > wrote: >> On Thu, Jan 18, 2018 at 12:24:31PM -0600, Josh Poimboeuf wrote: >>> On Thu, Jan 18, 2018 at 06:12:36PM +0100, Paolo Bonzini wrote: On 18/01/2018 18:08, Dave Hansen wrote: > On

Re: [PATCH-next] init/main.c: make local symbol static

On 01/18/2018 03:33 PM, Christopher Díaz Riveros wrote: > El jue, 18-01-2018 a las 16:31 -0600, Tom Lendacky escribió: >> On 1/18/2018 4:09 PM, Randy Dunlap wrote: >>> On 01/18/2018 02:06 PM, Christopher Díaz Riveros wrote: Fixes the following sparse warning: init/main.c:167:12:

Re: [PATCH-next] init/main.c: make local symbol static

On 01/18/2018 03:33 PM, Christopher Díaz Riveros wrote: > El jue, 18-01-2018 a las 16:31 -0600, Tom Lendacky escribió: >> On 1/18/2018 4:09 PM, Randy Dunlap wrote: >>> On 01/18/2018 02:06 PM, Christopher Díaz Riveros wrote: Fixes the following sparse warning: init/main.c:167:12:

Re: [PATCH-next] init/main.c: make local symbol static

El jue, 18-01-2018 a las 16:31 -0600, Tom Lendacky escribió: > On 1/18/2018 4:09 PM, Randy Dunlap wrote: > > On 01/18/2018 02:06 PM, Christopher Díaz Riveros wrote: > > > Fixes the following sparse warning: > > > > > > init/main.c:167:12: warning: > > > symbol 'envp_init' was not declared.

Re: [PATCH-next] init/main.c: make local symbol static

El jue, 18-01-2018 a las 16:31 -0600, Tom Lendacky escribió: > On 1/18/2018 4:09 PM, Randy Dunlap wrote: > > On 01/18/2018 02:06 PM, Christopher Díaz Riveros wrote: > > > Fixes the following sparse warning: > > > > > > init/main.c:167:12: warning: > > > symbol 'envp_init' was not declared.

<    1   2   3   4   5   6   7   8   9   10   >