Re: [PATCH 1/2] rtc-cmos: Clear expired alarm after resume

Hi, On 25/08/2016 at 16:54:18 +0200, Gabriele Mazzotta wrote : > Hi, > > were you able to verify that no other driver is affect? > I had a closer look at the issue. I think what is happening is that you don't enter the do/while loop in cmos_resume twice. That is supposed to handle then clear

Re: [PATCH 1/2] rtc-cmos: Clear expired alarm after resume

Hi, On 25/08/2016 at 16:54:18 +0200, Gabriele Mazzotta wrote : > Hi, > > were you able to verify that no other driver is affect? > I had a closer look at the issue. I think what is happening is that you don't enter the do/while loop in cmos_resume twice. That is supposed to handle then clear

Re: [PATCH v2 0/2] extend kexec_file_load system call

Hello Mark, Sorry for taking this long to respond. I've been focusing on getting my kexec_file_load and kexec buffer hand-over series in shape. Am Donnerstag, 18 August 2016, 11:21:13 schrieb Mark Rutland: > On Thu, Aug 11, 2016 at 08:03:56PM -0300, Thiago Jung Bauermann wrote: > > Device tree

Re: [PATCH v2 0/2] extend kexec_file_load system call

Hello Mark, Sorry for taking this long to respond. I've been focusing on getting my kexec_file_load and kexec buffer hand-over series in shape. Am Donnerstag, 18 August 2016, 11:21:13 schrieb Mark Rutland: > On Thu, Aug 11, 2016 at 08:03:56PM -0300, Thiago Jung Bauermann wrote: > > Device tree

[GIT PULL] seccomp fix for v4.8-rc5

Hi, Please pull this seccomp fix for v4.8-rc5. Thanks! -Kees The following changes since commit ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea: Merge tag 'arc-4.8-rc4-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc (2016-08-22 17:53:02 -0500) are available in the git

[GIT PULL] seccomp fix for v4.8-rc5

Hi, Please pull this seccomp fix for v4.8-rc5. Thanks! -Kees The following changes since commit ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea: Merge tag 'arc-4.8-rc4-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc (2016-08-22 17:53:02 -0500) are available in the git

Re: [PATCH 2/2] remoteproc: core: Add fixed memory region support

Hi Loic, Bjorn, On 08/29/2016 03:09 AM, loic pallardy wrote: > > > On 08/27/2016 02:32 AM, Bjorn Andersson wrote: >> On Fri 26 Aug 13:19 PDT 2016, Loic Pallardy wrote: >> >>> Some coprocessors request fixed memory mapping for firmware execution >>> and associated communication linked. >>>

Re: [PATCH 2/2] remoteproc: core: Add fixed memory region support

Hi Loic, Bjorn, On 08/29/2016 03:09 AM, loic pallardy wrote: > > > On 08/27/2016 02:32 AM, Bjorn Andersson wrote: >> On Fri 26 Aug 13:19 PDT 2016, Loic Pallardy wrote: >> >>> Some coprocessors request fixed memory mapping for firmware execution >>> and associated communication linked. >>>

Re: [RFC PATCH-queue/locking/rfc 2/2] locking/mutex: Enable optimistic spinning of woken waiter

On 08/30/2016 11:08 AM, Peter Zijlstra wrote: On Fri, Aug 26, 2016 at 07:35:09PM -0400, Waiman Long wrote: @@ -624,13 +649,24 @@ __mutex_lock_common(struct mutex *lock, long state, unsigned int subclass, /* didn't get the lock, go to sleep: */

Re: [RFC PATCH-queue/locking/rfc 2/2] locking/mutex: Enable optimistic spinning of woken waiter

On 08/30/2016 11:08 AM, Peter Zijlstra wrote: On Fri, Aug 26, 2016 at 07:35:09PM -0400, Waiman Long wrote: @@ -624,13 +649,24 @@ __mutex_lock_common(struct mutex *lock, long state, unsigned int subclass, /* didn't get the lock, go to sleep: */

Re: [RESEND][PATCH] proc: Fix timerslack_ns CAP_SYS_NICE check when adjusting self

On Tue, Aug 30, 2016 at 7:06 PM, Andrew Morton wrote: > On Tue, 30 Aug 2016 18:46:23 -0400 Kees Cook wrote: > >> On Mon, Aug 22, 2016 at 7:01 PM, John Stultz wrote: >> > In changing from checking ptrace_may_access(p,

Re: [RESEND][PATCH] proc: Fix timerslack_ns CAP_SYS_NICE check when adjusting self

On Tue, Aug 30, 2016 at 7:06 PM, Andrew Morton wrote: > On Tue, 30 Aug 2016 18:46:23 -0400 Kees Cook wrote: > >> On Mon, Aug 22, 2016 at 7:01 PM, John Stultz wrote: >> > In changing from checking ptrace_may_access(p, PTRACE_MODE_ATTACH_FSCREDS) >> > to capable(CAP_SYS_NICE), I missed that

Re: [PATCH v14 04/14] task_isolation: add initial support

On 8/30/2016 1:10 PM, Frederic Weisbecker wrote: On Tue, Aug 30, 2016 at 11:41:36AM -0400, Chris Metcalf wrote: On 8/29/2016 8:55 PM, Frederic Weisbecker wrote: On Mon, Aug 15, 2016 at 10:59:55AM -0400, Chris Metcalf wrote: On 8/11/2016 2:50 PM, Christoph Lameter wrote: On Thu, 11 Aug 2016,

Re: [PATCH v14 04/14] task_isolation: add initial support

On 8/30/2016 1:10 PM, Frederic Weisbecker wrote: On Tue, Aug 30, 2016 at 11:41:36AM -0400, Chris Metcalf wrote: On 8/29/2016 8:55 PM, Frederic Weisbecker wrote: On Mon, Aug 15, 2016 at 10:59:55AM -0400, Chris Metcalf wrote: On 8/11/2016 2:50 PM, Christoph Lameter wrote: On Thu, 11 Aug 2016,

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Tue, Aug 30, 2016 at 3:30 PM, Steven Rostedt wrote: > On Tue, 30 Aug 2016 15:08:19 -0700 > Andy Lutomirski wrote: > >> On Tue, Aug 30, 2016 at 3:03 PM, Steven Rostedt wrote: >> > On Tue, 30 Aug 2016 14:45:05 -0700 >> > Andy

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Tue, Aug 30, 2016 at 3:30 PM, Steven Rostedt wrote: > On Tue, 30 Aug 2016 15:08:19 -0700 > Andy Lutomirski wrote: > >> On Tue, Aug 30, 2016 at 3:03 PM, Steven Rostedt wrote: >> > On Tue, 30 Aug 2016 14:45:05 -0700 >> > Andy Lutomirski wrote: >> > >> >> I wonder: could more of it be

Re: [RESEND][PATCH] proc: Fix timerslack_ns CAP_SYS_NICE check when adjusting self

On Tue, 30 Aug 2016 18:46:23 -0400 Kees Cook wrote: > On Mon, Aug 22, 2016 at 7:01 PM, John Stultz wrote: > > In changing from checking ptrace_may_access(p, PTRACE_MODE_ATTACH_FSCREDS) > > to capable(CAP_SYS_NICE), I missed that ptrace_my_access

Re: [RESEND][PATCH] proc: Fix timerslack_ns CAP_SYS_NICE check when adjusting self

On Tue, 30 Aug 2016 18:46:23 -0400 Kees Cook wrote: > On Mon, Aug 22, 2016 at 7:01 PM, John Stultz wrote: > > In changing from checking ptrace_may_access(p, PTRACE_MODE_ATTACH_FSCREDS) > > to capable(CAP_SYS_NICE), I missed that ptrace_my_access succeeds > > when p == current, but the

Re: [GIT PULL] seccomp fix for v4.8-rc4

On 30/08/16 15:28, Kees Cook wrote: Hi James, Are you able to forward this up to Linus, or would it be better for me to send this to him directly? You can send it to him directly. Acked-by: James Morris Thanks! -Kees On Tue, Aug 23, 2016 at 3:34 PM, Kees

Re: [GIT PULL] seccomp fix for v4.8-rc4

On 30/08/16 15:28, Kees Cook wrote: Hi James, Are you able to forward this up to Linus, or would it be better for me to send this to him directly? You can send it to him directly. Acked-by: James Morris Thanks! -Kees On Tue, Aug 23, 2016 at 3:34 PM, Kees Cook wrote: Hi, Please

[PATCH] staging: i4l: act2000: Fix checkpatch warning

Fix checkpatch.pl warning: braces {} are not necessary for single statement blocks Missing a blank line after declarations Signed-off-by: Anson Jacob --- drivers/staging/i4l/act2000/act2000_isa.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

[PATCH] staging: i4l: act2000: Fix checkpatch warning

Fix checkpatch.pl warning: braces {} are not necessary for single statement blocks Missing a blank line after declarations Signed-off-by: Anson Jacob --- drivers/staging/i4l/act2000/act2000_isa.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

Re: [PATCH v2 0/9] re-enable DAX PMD support

On Tue, Aug 23, 2016 at 04:04:10PM -0600, Ross Zwisler wrote: > DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based > locking. This series allows DAX PMDs to participate in the DAX radix tree > based locking scheme so that they can be re-enabled. > > Changes since v1: > -

Re: [PATCH v2 0/9] re-enable DAX PMD support

On Tue, Aug 23, 2016 at 04:04:10PM -0600, Ross Zwisler wrote: > DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based > locking. This series allows DAX PMDs to participate in the DAX radix tree > based locking scheme so that they can be re-enabled. > > Changes since v1: > -

Re: [PATCH 10/15] acpi: Export acpi_bus_type

On Wed, Aug 31, 2016 at 12:47:39AM +0200, Rafael J. Wysocki wrote: > On Tue, Aug 30, 2016 at 6:49 PM, wrote: > > From: Ankitprasad Sharma > > > > Some modules, like i915.ko, needs to detect when certain ACPI features are > > active inorder

Re: [PATCH 10/15] acpi: Export acpi_bus_type

On Wed, Aug 31, 2016 at 12:47:39AM +0200, Rafael J. Wysocki wrote: > On Tue, Aug 30, 2016 at 6:49 PM, wrote: > > From: Ankitprasad Sharma > > > > Some modules, like i915.ko, needs to detect when certain ACPI features are > > active inorder to prevent corruption on contended resources. > > In

[PATCH] staging: i4l: act2000: Fix checkpatch warning

Fix checkpatch.pl warning: line over 80 characters Signed-off-by: Anson Jacob --- drivers/staging/i4l/act2000/act2000.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/i4l/act2000/act2000.h b/drivers/staging/i4l/act2000/act2000.h

[PATCH] staging: i4l: act2000: Fix checkpatch warning

Fix checkpatch.pl warning: line over 80 characters Signed-off-by: Anson Jacob --- drivers/staging/i4l/act2000/act2000.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/i4l/act2000/act2000.h b/drivers/staging/i4l/act2000/act2000.h index 321d437..16be456

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Tue, Aug 30, 2016 at 03:21:24PM -0700, Dan Williams wrote: > On Tue, Aug 30, 2016 at 3:03 PM, Ross Zwisler > wrote: > > On Tue, Aug 30, 2016 at 02:56:17PM -0700, Dan Williams wrote: > >> On Mon, Aug 29, 2016 at 11:52 AM, Matthew Wilcox >

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Tue, Aug 30, 2016 at 03:21:24PM -0700, Dan Williams wrote: > On Tue, Aug 30, 2016 at 3:03 PM, Ross Zwisler > wrote: > > On Tue, Aug 30, 2016 at 02:56:17PM -0700, Dan Williams wrote: > >> On Mon, Aug 29, 2016 at 11:52 AM, Matthew Wilcox > >> wrote: > >> > It may be protected by the mapping

Re: [PATCH] sparc64 mm: Fix more TSB sizing issues

Hi Mike, [auto build test ERROR on sparc/master] [also build test ERROR on v4.8-rc4 next-20160825] [cannot apply to sparc-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or

Re: [PATCH] sparc64 mm: Fix more TSB sizing issues

Hi Mike, [auto build test ERROR on sparc/master] [also build test ERROR on v4.8-rc4 next-20160825] [cannot apply to sparc-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] [Suggest to use git(>=2.9.0) format-patch --base= (or

[PATCH v3] perf inject: Make it possible to merge sys_enter/exit events

This makes it much more useful to report data recorded with `perf trace record`. E.g.: #include int main() { sleep(1); usleep(1000); usleep(1); return 0; } Compile and trace it: # gcc -g sleep.c -o ex_sleep # perf trace record --call-graph

[PATCH v3] perf inject: Make it possible to merge sys_enter/exit events

This makes it much more useful to report data recorded with `perf trace record`. E.g.: #include int main() { sleep(1); usleep(1000); usleep(1); return 0; } Compile and trace it: # gcc -g sleep.c -o ex_sleep # perf trace record --call-graph

Re: [PATCH 10/15] acpi: Export acpi_bus_type

On Tue, Aug 30, 2016 at 6:49 PM, wrote: > From: Ankitprasad Sharma > > Some modules, like i915.ko, needs to detect when certain ACPI features are > active inorder to prevent corruption on contended resources. > In particular, use of BIOS

Re: [PATCH 10/15] acpi: Export acpi_bus_type

On Tue, Aug 30, 2016 at 6:49 PM, wrote: > From: Ankitprasad Sharma > > Some modules, like i915.ko, needs to detect when certain ACPI features are > active inorder to prevent corruption on contended resources. > In particular, use of BIOS RapidStart Technology may corrupt the contents of > the

Re: [RESEND][PATCH] proc: Fix timerslack_ns CAP_SYS_NICE check when adjusting self

On Mon, Aug 22, 2016 at 7:01 PM, John Stultz wrote: > In changing from checking ptrace_may_access(p, PTRACE_MODE_ATTACH_FSCREDS) > to capable(CAP_SYS_NICE), I missed that ptrace_my_access succeeds > when p == current, but the CAP_SYS_NICE doesn't. > > Thus while the

Re: [RESEND][PATCH] proc: Fix timerslack_ns CAP_SYS_NICE check when adjusting self

On Mon, Aug 22, 2016 at 7:01 PM, John Stultz wrote: > In changing from checking ptrace_may_access(p, PTRACE_MODE_ATTACH_FSCREDS) > to capable(CAP_SYS_NICE), I missed that ptrace_my_access succeeds > when p == current, but the CAP_SYS_NICE doesn't. > > Thus while the previous commit was intended

screen rotation flipped in 4.8-rc

Hi All, I observed that using iio-sensor-proxy.service, the auto screen rotation flipped on my laptop (Normal -> vertical, vertical->normal) using kernel v4.8. Anyone else has seen this? I did a bisect and found a commit, which I am not sure how can it impact. commit

[PATHC v2 2/9] ima: permit duplicate measurement list entries

Measurements carried across kexec need to be added to the IMA measurement list, but should not prevent measurements of the newly booted kernel from being added to the measurement list. This patch adds support for allowing duplicate measurements. The "boot_aggregate" measurement entry is the

[PATHC v2 3/9] ima: maintain memory size needed for serializing the measurement list

In preparation for serializing the binary_runtime_measurements, this patch maintains the amount of memory required. Signed-off-by: Mimi Zohar --- security/integrity/ima/Kconfig | 12 ++ security/integrity/ima/ima.h | 1 +

screen rotation flipped in 4.8-rc

Hi All, I observed that using iio-sensor-proxy.service, the auto screen rotation flipped on my laptop (Normal -> vertical, vertical->normal) using kernel v4.8. Anyone else has seen this? I did a bisect and found a commit, which I am not sure how can it impact. commit

[PATHC v2 2/9] ima: permit duplicate measurement list entries

Measurements carried across kexec need to be added to the IMA measurement list, but should not prevent measurements of the newly booted kernel from being added to the measurement list. This patch adds support for allowing duplicate measurements. The "boot_aggregate" measurement entry is the

[PATHC v2 3/9] ima: maintain memory size needed for serializing the measurement list

In preparation for serializing the binary_runtime_measurements, this patch maintains the amount of memory required. Signed-off-by: Mimi Zohar --- security/integrity/ima/Kconfig | 12 ++ security/integrity/ima/ima.h | 1 + security/integrity/ima/ima_queue.c | 49

[PATHC v2 5/9] ima: on soft reboot, save the measurement list

From: Thiago Jung Bauermann This patch uses the kexec buffer passing mechanism to pass the serialized IMA binary_runtime_measurements to the next kernel. Changelog v2: - Fix build issue by defining a stub ima_add_kexec_buffer and stub struct kimage when

[PATHC v2 5/9] ima: on soft reboot, save the measurement list

From: Thiago Jung Bauermann This patch uses the kexec buffer passing mechanism to pass the serialized IMA binary_runtime_measurements to the next kernel. Changelog v2: - Fix build issue by defining a stub ima_add_kexec_buffer and stub struct kimage when CONFIG_IMA=n and CONFIG_IMA_KEXEC=n.

[PATHC v2 9/9] ima: platform-independent hash value

From: Andreas Steffen For remote attestion it is important for the ima measurement values to be platform-independent. Therefore integer fields to be hashed must be converted to canonical format. Changelog: - Define canonical format as little endian (Mimi)

[PATHC v2 9/9] ima: platform-independent hash value

From: Andreas Steffen For remote attestion it is important for the ima measurement values to be platform-independent. Therefore integer fields to be hashed must be converted to canonical format. Changelog: - Define canonical format as little endian (Mimi) Signed-off-by: Andreas Steffen

[PATHC v2 7/9] ima: support restoring multiple template formats

The configured IMA measurement list template format can be replaced at runtime on the boot command line, including a custom template format. This patch adds support for restoring a measuremement list containing multiple builtin/custom template formats. Signed-off-by: Mimi Zohar

[PATHC v2 7/9] ima: support restoring multiple template formats

The configured IMA measurement list template format can be replaced at runtime on the boot command line, including a custom template format. This patch adds support for restoring a measuremement list containing multiple builtin/custom template formats. Signed-off-by: Mimi Zohar ---

[PATHC v2 6/9] ima: store the builtin/custom template definitions in a list

The builtin and single custom templates are currently stored in an array. In preparation for being able to restore a measurement list containing multiple builtin/custom templates, this patch stores the builtin and custom templates as a linked list. This will permit defining more than one custom

[PATHC v2 4/9] ima: serialize the binary_runtime_measurements

The TPM PCRs are only reset on a hard reboot. In order to validate a TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list of the running kernel must be saved and restored on boot. This patch serializes the IMA measurement list in the binary_runtime_measurements format.

[PATHC v2 8/9] ima: define a canonical binary_runtime_measurements list format

The IMA binary_runtime_measurements list is currently in platform native format. To allow restoring a measurement list carried across kexec with a different endianness than the targeted kernel, this patch defines little-endian as the canonical format. For big endian systems wanting to

[PATHC v2 6/9] ima: store the builtin/custom template definitions in a list

The builtin and single custom templates are currently stored in an array. In preparation for being able to restore a measurement list containing multiple builtin/custom templates, this patch stores the builtin and custom templates as a linked list. This will permit defining more than one custom

[PATHC v2 4/9] ima: serialize the binary_runtime_measurements

The TPM PCRs are only reset on a hard reboot. In order to validate a TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list of the running kernel must be saved and restored on boot. This patch serializes the IMA measurement list in the binary_runtime_measurements format.

[PATHC v2 8/9] ima: define a canonical binary_runtime_measurements list format

The IMA binary_runtime_measurements list is currently in platform native format. To allow restoring a measurement list carried across kexec with a different endianness than the targeted kernel, this patch defines little-endian as the canonical format. For big endian systems wanting to

[PATHC v2 0/9] ima: carry the measurement list across kexec

The TPM PCRs are only reset on a hard reboot. In order to validate a TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list of the running kernel must be saved and then restored on the subsequent boot, possibly of a different architecture. The existing securityfs

[PATHC v2 1/9] ima: on soft reboot, restore the measurement list

The TPM PCRs are only reset on a hard reboot. In order to validate a TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list of the running kernel must be saved and restored on boot. This patch restores the measurement list. Changelog v2: - redefined ima_kexec_hdr to use types

[PATHC v2 0/9] ima: carry the measurement list across kexec

The TPM PCRs are only reset on a hard reboot. In order to validate a TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list of the running kernel must be saved and then restored on the subsequent boot, possibly of a different architecture. The existing securityfs

[PATHC v2 1/9] ima: on soft reboot, restore the measurement list

The TPM PCRs are only reset on a hard reboot. In order to validate a TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list of the running kernel must be saved and restored on boot. This patch restores the measurement list. Changelog v2: - redefined ima_kexec_hdr to use types

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Sat, Aug 27, 2016 at 05:14:34PM +0300, Konstantin Khlebnikov wrote: > Tags should be set only for last index of THP range: this way iterator > will find them regardless of starting index. I don't think this works well for DAX. We really want to to have the tags be consistent for all indices

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Sat, Aug 27, 2016 at 05:14:34PM +0300, Konstantin Khlebnikov wrote: > Tags should be set only for last index of THP range: this way iterator > will find them regardless of starting index. I don't think this works well for DAX. We really want to to have the tags be consistent for all indices

Re: [RFC][PATCH -v2 4/4] locking/mutex: Add lock handoff to avoid starvation

On 08/30/2016 07:53 AM, Peter Zijlstra wrote: On Mon, Aug 29, 2016 at 05:41:09PM +0200, Peter Zijlstra wrote: On Fri, Aug 26, 2016 at 07:40:34PM -0400, Waiman Long wrote: On 08/26/2016 11:18 AM, Peter Zijlstra wrote: Still need to look at adding spinning to the handoff case. Also need to look

Re: [RFC][PATCH -v2 4/4] locking/mutex: Add lock handoff to avoid starvation

On 08/30/2016 07:53 AM, Peter Zijlstra wrote: On Mon, Aug 29, 2016 at 05:41:09PM +0200, Peter Zijlstra wrote: On Fri, Aug 26, 2016 at 07:40:34PM -0400, Waiman Long wrote: On 08/26/2016 11:18 AM, Peter Zijlstra wrote: Still need to look at adding spinning to the handoff case. Also need to look

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Tue, 30 Aug 2016 15:08:19 -0700 Andy Lutomirski wrote: > On Tue, Aug 30, 2016 at 3:03 PM, Steven Rostedt wrote: > > On Tue, 30 Aug 2016 14:45:05 -0700 > > Andy Lutomirski wrote: > > > >> I wonder: could more of it be

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Tue, 30 Aug 2016 15:08:19 -0700 Andy Lutomirski wrote: > On Tue, Aug 30, 2016 at 3:03 PM, Steven Rostedt wrote: > > On Tue, 30 Aug 2016 14:45:05 -0700 > > Andy Lutomirski wrote: > > > >> I wonder: could more of it be dynamically allocated? I.e. statically > >> generate metadata with args

Re: [GIT PULL] seccomp fix for v4.8-rc4

Hi James, Are you able to forward this up to Linus, or would it be better for me to send this to him directly? Thanks! -Kees On Tue, Aug 23, 2016 at 3:34 PM, Kees Cook wrote: > Hi, > > Please pull this seccomp fix for v4.8-rc4. > > Thanks! > > -Kees > > The following

Re: [GIT PULL] seccomp fix for v4.8-rc4

Hi James, Are you able to forward this up to Linus, or would it be better for me to send this to him directly? Thanks! -Kees On Tue, Aug 23, 2016 at 3:34 PM, Kees Cook wrote: > Hi, > > Please pull this seccomp fix for v4.8-rc4. > > Thanks! > > -Kees > > The following changes since commit

Re: [PATCH v6 1/3] fork: Add generic vmalloced stack support

On Tue, Aug 30, 2016 at 03:01:51PM -0700, Andy Lutomirski wrote: > On Wed, Aug 24, 2016 at 9:51 AM, Josh Cartwright wrote: [..] > >> diff --git a/kernel/fork.c b/kernel/fork.c > >> index 52e725d4a866..05f7ef796fb4 100644 > >> --- a/kernel/fork.c > >> +++ b/kernel/fork.c > >> @@

Re: [PATCH v6 1/3] fork: Add generic vmalloced stack support

On Tue, Aug 30, 2016 at 03:01:51PM -0700, Andy Lutomirski wrote: > On Wed, Aug 24, 2016 at 9:51 AM, Josh Cartwright wrote: [..] > >> diff --git a/kernel/fork.c b/kernel/fork.c > >> index 52e725d4a866..05f7ef796fb4 100644 > >> --- a/kernel/fork.c > >> +++ b/kernel/fork.c > >> @@ -158,19 +158,39 @@

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Tue, Aug 30, 2016 at 3:03 PM, Ross Zwisler wrote: > On Tue, Aug 30, 2016 at 02:56:17PM -0700, Dan Williams wrote: >> On Mon, Aug 29, 2016 at 11:52 AM, Matthew Wilcox >> wrote: >> > It may be protected by the mapping lock in the current

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Tue, Aug 30, 2016 at 3:03 PM, Ross Zwisler wrote: > On Tue, Aug 30, 2016 at 02:56:17PM -0700, Dan Williams wrote: >> On Mon, Aug 29, 2016 at 11:52 AM, Matthew Wilcox >> wrote: >> > It may be protected by the mapping lock in the current code, but I would >> > it expect it to become an RCU

Re: [PATCH v3] mm/usercopy: get rid of CONFIG_DEBUG_STRICT_USER_COPY_CHECKS

On Tue, Aug 30, 2016 at 4:13 PM, Al Viro wrote: > On Tue, Aug 30, 2016 at 02:15:58PM -0400, Kees Cook wrote: > >> First, some current API usage which we'll need to maintain at least >> for now: __copy_*_user() is just copy_*_user() without the access_ok() >> checks.

Re: [PATCH v3] mm/usercopy: get rid of CONFIG_DEBUG_STRICT_USER_COPY_CHECKS

On Tue, Aug 30, 2016 at 4:13 PM, Al Viro wrote: > On Tue, Aug 30, 2016 at 02:15:58PM -0400, Kees Cook wrote: > >> First, some current API usage which we'll need to maintain at least >> for now: __copy_*_user() is just copy_*_user() without the access_ok() >> checks. Unfortunately, some arch

Re: [PATCH v2 2/4] fs/afs/rxrpc: Remove deprecated create_singlethread_workqueue

Bhaktipriya Shridhar wrote: > The workqueue "afs_async_calls" queues a single work item viz > >async_work and hence it doesn't require execution ordering. > ... > Since there are fixed number of work items, explicit concurrency > limit is unnecessary here. There can be

Re: [PATCH v2 2/4] fs/afs/rxrpc: Remove deprecated create_singlethread_workqueue

Bhaktipriya Shridhar wrote: > The workqueue "afs_async_calls" queues a single work item viz > >async_work and hence it doesn't require execution ordering. > ... > Since there are fixed number of work items, explicit concurrency > limit is unnecessary here. There can be more than one single call

Re: constification and cocci / kernel build test robot ?

On Tue, Aug 30, 2016 at 3:23 PM, Julia Lawall wrote: > > > On Tue, 30 Aug 2016, Kees Cook wrote: > >> On Sun, Aug 28, 2016 at 9:13 AM, Julia Lawall wrote: >> > [Adding Kees, in case it's of interest] >> > >> > Below is the list of types of top-level

Re: constification and cocci / kernel build test robot ?

On Tue, Aug 30, 2016 at 3:23 PM, Julia Lawall wrote: > > > On Tue, 30 Aug 2016, Kees Cook wrote: > >> On Sun, Aug 28, 2016 at 9:13 AM, Julia Lawall wrote: >> > [Adding Kees, in case it's of interest] >> > >> > Below is the list of types of top-level initialized structures and the >> > number

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Tue, Aug 30, 2016 at 3:03 PM, Steven Rostedt wrote: > On Tue, 30 Aug 2016 14:45:05 -0700 > Andy Lutomirski wrote: > >> I wonder: could more of it be dynamically allocated? I.e. statically >> generate metadata with args and name and whatever but

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Tue, Aug 30, 2016 at 3:03 PM, Steven Rostedt wrote: > On Tue, 30 Aug 2016 14:45:05 -0700 > Andy Lutomirski wrote: > >> I wonder: could more of it be dynamically allocated? I.e. statically >> generate metadata with args and name and whatever but without any nr. >> Then dynamically allocate

Re: [PATCH 3/4] arm64: dts: rockchip: support gmac for rk3399

Am Mittwoch, 31. August 2016, 04:30:06 schrieb Caesar Wang: > This patch adds needed gamc information for rk3399, > also support the gmac pd. > > Signed-off-by: Roger Chen > Signed-off-by: Caesar Wang > --- > >

Re: [PATCH 3/4] arm64: dts: rockchip: support gmac for rk3399

Am Mittwoch, 31. August 2016, 04:30:06 schrieb Caesar Wang: > This patch adds needed gamc information for rk3399, > also support the gmac pd. > > Signed-off-by: Roger Chen > Signed-off-by: Caesar Wang > --- > > arch/arm64/boot/dts/rockchip/rk3399.dtsi | 90 > 1

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Tue, Aug 30, 2016 at 02:56:17PM -0700, Dan Williams wrote: > On Mon, Aug 29, 2016 at 11:52 AM, Matthew Wilcox > wrote: > > It may be protected by the mapping lock in the current code, but I would it > > expect it to become an RCU lookup + lock eventually. No mapping

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Tue, Aug 30, 2016 at 02:56:17PM -0700, Dan Williams wrote: > On Mon, Aug 29, 2016 at 11:52 AM, Matthew Wilcox > wrote: > > It may be protected by the mapping lock in the current code, but I would it > > expect it to become an RCU lookup + lock eventually. No mapping lock, just > > like the

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Tue, 30 Aug 2016 14:45:05 -0700 Andy Lutomirski wrote: > I wonder: could more of it be dynamically allocated? I.e. statically > generate metadata with args and name and whatever but without any nr. > Then dynamically allocate the map from nr to metadata? Any ideas on

Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall

On Tue, 30 Aug 2016 14:45:05 -0700 Andy Lutomirski wrote: > I wonder: could more of it be dynamically allocated? I.e. statically > generate metadata with args and name and whatever but without any nr. > Then dynamically allocate the map from nr to metadata? Any ideas on how to do that? > > >

Re: [PATCH v2] printk/nmi: avoid direct printk()-s from __printk_nmi_flush()

On Wed, 31 Aug 2016 01:13:54 +0900 Sergey Senozhatsky wrote: > __printk_nmi_flush() can be called from nmi_panic(), therefore it has to > test whether it's executed in NMI context and thus must route the messages > through deferred printk() or via direct printk().

Re: [PATCH v2] printk/nmi: avoid direct printk()-s from __printk_nmi_flush()

On Wed, 31 Aug 2016 01:13:54 +0900 Sergey Senozhatsky wrote: > __printk_nmi_flush() can be called from nmi_panic(), therefore it has to > test whether it's executed in NMI context and thus must route the messages > through deferred printk() or via direct printk(). Why? What misbehaviour does

Re: [PATCH v6 1/3] fork: Add generic vmalloced stack support

On Wed, Aug 24, 2016 at 9:51 AM, Josh Cartwright wrote: > Hey Andy- > > Small non-critical/potential future optimization comment below: > > On Thu, Aug 11, 2016 at 02:35:21AM -0700, Andy Lutomirski wrote: >> If CONFIG_VMAP_STACK is selected, kernel stacks are allocated with >>

Re: [PATCH v6 1/3] fork: Add generic vmalloced stack support

On Wed, Aug 24, 2016 at 9:51 AM, Josh Cartwright wrote: > Hey Andy- > > Small non-critical/potential future optimization comment below: > > On Thu, Aug 11, 2016 at 02:35:21AM -0700, Andy Lutomirski wrote: >> If CONFIG_VMAP_STACK is selected, kernel stacks are allocated with >> vmalloc_node. >> >>

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Mon, Aug 29, 2016 at 06:52:54PM +, Matthew Wilcox wrote: > It may be protected by the mapping lock in the current code, but I would it > expect it to become an RCU lookup + lock eventually. No mapping lock, just > like the page cache. > > Even if we can work around it, why do we want to?

Re: [PATCH RFC 1/4] lib/radix: add universal radix_tree_fill_range

On Mon, Aug 29, 2016 at 06:52:54PM +, Matthew Wilcox wrote: > It may be protected by the mapping lock in the current code, but I would it > expect it to become an RCU lookup + lock eventually. No mapping lock, just > like the page cache. > > Even if we can work around it, why do we want to?

[PATCH v2 2/3] nvme: Pass pointers, not dma addresses, to nvme_get/set_features()

Any user I can imagine that needs a buffer at all will want to pass a pointer directly. There are no currently callers that use buffers, so this change is painless, and it will make it much easier to start using features that use buffers (e.g. APST). Signed-off-by: Andy Lutomirski

[PATCH v2 0/3] nvme power saving

Hi all- Here's v1 of the APST patch set. The biggest bikesheddable thing (I think) is the scaling factor. I currently have it hardcoded so that we wait 50x the total latency before entering a power saving state. On my Samsung 950, this means we enter state 3 (70mW, 0.5ms entry latency, 5ms exit

[PATCH v2 1/3] nvme/scsi: Remove power management support

As far as I can tell, there is basically nothing correct about this code. It misinterprets npss (off-by-one). It hardcodes a bunch of power states, which is nonsense, because they're all just indices into a table that software needs to parse. It completely ignores the distinction between

[PATCH v2 3/3] nvme: Enable autonomous power state transitions

NVME devices can advertise multiple power states. These states can be either "operational" (the device is fully functional but possibly slow) or "non-operational" (the device is asleep until woken up). Some devices can automatically enter a non-operational state when idle for a specified amount

[PATCH v2 2/3] nvme: Pass pointers, not dma addresses, to nvme_get/set_features()

Any user I can imagine that needs a buffer at all will want to pass a pointer directly. There are no currently callers that use buffers, so this change is painless, and it will make it much easier to start using features that use buffers (e.g. APST). Signed-off-by: Andy Lutomirski ---

[PATCH v2 0/3] nvme power saving

Hi all- Here's v1 of the APST patch set. The biggest bikesheddable thing (I think) is the scaling factor. I currently have it hardcoded so that we wait 50x the total latency before entering a power saving state. On my Samsung 950, this means we enter state 3 (70mW, 0.5ms entry latency, 5ms exit

[PATCH v2 1/3] nvme/scsi: Remove power management support

As far as I can tell, there is basically nothing correct about this code. It misinterprets npss (off-by-one). It hardcodes a bunch of power states, which is nonsense, because they're all just indices into a table that software needs to parse. It completely ignores the distinction between

[PATCH v2 3/3] nvme: Enable autonomous power state transitions

NVME devices can advertise multiple power states. These states can be either "operational" (the device is fully functional but possibly slow) or "non-operational" (the device is asleep until woken up). Some devices can automatically enter a non-operational state when idle for a specified amount

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