Re: Linux 4.4.73

diff --git a/Makefile b/Makefile index 94d663c935c0..ba5a70b6e32c 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 72 +SUBLEVEL = 73 EXTRAVERSION = NAME = Blurry Fish Butt @@ -789,7 +789,7 @@ KBUILD_CFLAGS += $(call cc-option,-Werror=date-time)

Re: Linux 4.4.73

diff --git a/Makefile b/Makefile index 94d663c935c0..ba5a70b6e32c 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 72 +SUBLEVEL = 73 EXTRAVERSION = NAME = Blurry Fish Butt @@ -789,7 +789,7 @@ KBUILD_CFLAGS += $(call cc-option,-Werror=date-time)

Linux 4.4.73

I'm announcing the release of the 4.4.73 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Linux 4.4.73

I'm announcing the release of the 4.4.73 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH v2 3/4] KVM: async_pf: Force a nested vmexit if the injected #PF is async_pf

2017-06-16 23:38 GMT+08:00 Radim Krčmář : > 2017-06-16 22:24+0800, Wanpeng Li: >> 2017-06-16 21:37 GMT+08:00 Radim Krčmář : >> > 2017-06-14 19:26-0700, Wanpeng Li: >> >> From: Wanpeng Li >> >> >> >> Add an async_page_fault field to

Re: [PATCH v2 3/4] KVM: async_pf: Force a nested vmexit if the injected #PF is async_pf

2017-06-16 23:38 GMT+08:00 Radim Krčmář : > 2017-06-16 22:24+0800, Wanpeng Li: >> 2017-06-16 21:37 GMT+08:00 Radim Krčmář : >> > 2017-06-14 19:26-0700, Wanpeng Li: >> >> From: Wanpeng Li >> >> >> >> Add an async_page_fault field to vcpu->arch.exception to identify an async >> >> page fault, and

Re: endian bitshift defects [ was: staging: fusb302: don't bitshift __le16 type ]

On Sat, 2017-06-17 at 07:23 +0200, Julia Lawall wrote: > On Fri, 16 Jun 2017, Joe Perches wrote: > > On Fri, 2017-06-16 at 19:45 +0200, Frans Klaver wrote: > > > The header field in struct pd_message is declared as an __le16 type. The > > > data in the message is supposed to be little endian. This

Re: endian bitshift defects [ was: staging: fusb302: don't bitshift __le16 type ]

On Sat, 2017-06-17 at 07:23 +0200, Julia Lawall wrote: > On Fri, 16 Jun 2017, Joe Perches wrote: > > On Fri, 2017-06-16 at 19:45 +0200, Frans Klaver wrote: > > > The header field in struct pd_message is declared as an __le16 type. The > > > data in the message is supposed to be little endian. This

Re: [RFC PATCH 1/3] atmel-hlcdc: add support for 8-bit color lookup table mode

Le Sat, 17 Jun 2017 00:46:12 +0200, Peter Rosin a écrit : > Hm, it's probably too late to do it here. Planes have already been > enabled and the engine may have started to fetch data and do the > composition. You could do that in ->update_plane() [1], and make it

Re: [RFC PATCH 1/3] atmel-hlcdc: add support for 8-bit color lookup table mode

Le Sat, 17 Jun 2017 00:46:12 +0200, Peter Rosin a écrit : > Hm, it's probably too late to do it here. Planes have already been > enabled and the engine may have started to fetch data and do the > composition. You could do that in ->update_plane() [1], and make it a >

Re: endian bitshift defects [ was: staging: fusb302: don't bitshift __le16 type ]

On Fri, 16 Jun 2017, Joe Perches wrote: > On Fri, 2017-06-16 at 19:45 +0200, Frans Klaver wrote: > > The header field in struct pd_message is declared as an __le16 type. The > > data in the message is supposed to be little endian. This means we don't > > have to go and shift the individual

Re: endian bitshift defects [ was: staging: fusb302: don't bitshift __le16 type ]

On Fri, 16 Jun 2017, Joe Perches wrote: > On Fri, 2017-06-16 at 19:45 +0200, Frans Klaver wrote: > > The header field in struct pd_message is declared as an __le16 type. The > > data in the message is supposed to be little endian. This means we don't > > have to go and shift the individual

[PATCH 2/2][RFC] PM / hibernate: Utilize the original e820 map for consistent check

Use the e820_table_ori instead of e820_table_firmware to check the consistence of memory layout provided by BIOS, because the e820_table_firmware might be modified by the kernel such as efi boot stub. To be more specific, during bootup, the efi boot stub might allocate memory via efi service for

[PATCH 2/2][RFC] PM / hibernate: Utilize the original e820 map for consistent check

Use the e820_table_ori instead of e820_table_firmware to check the consistence of memory layout provided by BIOS, because the e820_table_firmware might be modified by the kernel such as efi boot stub. To be more specific, during bootup, the efi boot stub might allocate memory via efi service for

Re: [RFC PATCH 1/2] mm: introduce bmap_walk()

On Fri, Jun 16, 2017 at 06:15:29PM -0700, Dan Williams wrote: > Refactor the core of generic_swapfile_activate() into bmap_walk() so > that it can be used by a new daxfile_activate() helper (to be added). No way in hell! generic_swapfile_activate needs to day and no new users of ->bmap over my

[PATCH 1/2][RFC] x86/boot/e820: Introduce e820_table_ori to represent the real original e820 layout

Currently we try to have e820_table_firmware to represent the original firmware memory layout passed to us by the bootloader, however it is not the case, the e820_table_firmware might still be modified by linux: 1. During bootup, the efi boot stub might allocate memory via efi service for the

Re: [RFC PATCH 1/2] mm: introduce bmap_walk()

On Fri, Jun 16, 2017 at 06:15:29PM -0700, Dan Williams wrote: > Refactor the core of generic_swapfile_activate() into bmap_walk() so > that it can be used by a new daxfile_activate() helper (to be added). No way in hell! generic_swapfile_activate needs to day and no new users of ->bmap over my

[PATCH 1/2][RFC] x86/boot/e820: Introduce e820_table_ori to represent the real original e820 layout

Currently we try to have e820_table_firmware to represent the original firmware memory layout passed to us by the bootloader, however it is not the case, the e820_table_firmware might still be modified by linux: 1. During bootup, the efi boot stub might allocate memory via efi service for the

[PATCH 0/2][RFC] Introduce e820_table_ori to fix the memory inconsistent problem during hibernation

This is a patch set to fix the issue found during hibernation restore that, the MD5 fingerprint of the physical memory layout checking code has reported a false-positive failure due to incorrect input from the e820 map. Chen Yu (2): x86/boot/e820: Introduce e820_table_ori to represent the real

[PATCH 0/2][RFC] Introduce e820_table_ori to fix the memory inconsistent problem during hibernation

This is a patch set to fix the issue found during hibernation restore that, the MD5 fingerprint of the physical memory layout checking code has reported a false-positive failure due to incorrect input from the e820 map. Chen Yu (2): x86/boot/e820: Introduce e820_table_ori to represent the real

[PATCH] mm,oom_kill: Close race window of needlessly selecting new victims.

Michal Hocko wrote: > On Fri 16-06-17 21:22:20, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > OK, could you play with the patch/idea suggested in > > > http://lkml.kernel.org/r/20170615122031.gl1...@dhcp22.suse.cz? > > > > I think we don't need to worry about mmap_sem dependency inside

[PATCH] mm,oom_kill: Close race window of needlessly selecting new victims.

Michal Hocko wrote: > On Fri 16-06-17 21:22:20, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > OK, could you play with the patch/idea suggested in > > > http://lkml.kernel.org/r/20170615122031.gl1...@dhcp22.suse.cz? > > > > I think we don't need to worry about mmap_sem dependency inside

Re: [RFC PATCH 06/13] switchtec_ntb: initialize hardware for memory windows

On Thu, Jun 15, 2017 at 02:37:22PM -0600, Logan Gunthorpe wrote: > This commit adds the code to initialize the memory windows in the > hardware. This includes setting up the requester ID table, and > figuring out which bar corresponds to which memory window. (Seeing > the switch can be configured

Re: [RFC PATCH 06/13] switchtec_ntb: initialize hardware for memory windows

On Thu, Jun 15, 2017 at 02:37:22PM -0600, Logan Gunthorpe wrote: > This commit adds the code to initialize the memory windows in the > hardware. This includes setting up the requester ID table, and > figuring out which bar corresponds to which memory window. (Seeing > the switch can be configured

Re: [RFC PATCH 04/13] switchtec: add link event notifier block

On Thu, Jun 15, 2017 at 02:37:20PM -0600, Logan Gunthorpe wrote: > In order for the switchtec NTB code to handle link change events we > create a notifier block in the switchtec code which gets called > whenever an appropriate event interrupt occurs. > > In order to preserve userspace's ability

Re: [RFC PATCH 04/13] switchtec: add link event notifier block

On Thu, Jun 15, 2017 at 02:37:20PM -0600, Logan Gunthorpe wrote: > In order for the switchtec NTB code to handle link change events we > create a notifier block in the switchtec code which gets called > whenever an appropriate event interrupt occurs. > > In order to preserve userspace's ability

Re: [RFC PATCH 01/13] switchtec: move structure definitions into a common header

On Thu, Jun 15, 2017 at 02:37:17PM -0600, Logan Gunthorpe wrote: > Create the switchtec.h header in include/linux with hardware defines > and the switchtec_dev structure moved directly from switchtec.c. > This is a prep patch for created an NTB driver for switchtec. > > Signed-off-by: Logan

Re: [RFC PATCH 01/13] switchtec: move structure definitions into a common header

On Thu, Jun 15, 2017 at 02:37:17PM -0600, Logan Gunthorpe wrote: > Create the switchtec.h header in include/linux with hardware defines > and the switchtec_dev structure moved directly from switchtec.c. > This is a prep patch for created an NTB driver for switchtec. > > Signed-off-by: Logan

Re: [RFC PATCH 02/13] switchtec: export class symbol for use in upper layer driver

On Thu, Jun 15, 2017 at 02:37:18PM -0600, Logan Gunthorpe wrote: > We switch to class_register/unregister and a declared class which > is exported for use in the switchtec_ntb driver. > > Signed-off-by: Logan Gunthorpe > Reviewed-by: Stephen Bates >

Re: [RFC PATCH 02/13] switchtec: export class symbol for use in upper layer driver

On Thu, Jun 15, 2017 at 02:37:18PM -0600, Logan Gunthorpe wrote: > We switch to class_register/unregister and a declared class which > is exported for use in the switchtec_ntb driver. > > Signed-off-by: Logan Gunthorpe > Reviewed-by: Stephen Bates > Reviewed-by: Kurt Schwemmer > --- >

Re: [RFC PATCH 00/13] Switchtec NTB Support

On Fri, Jun 16, 2017 at 11:21:00PM +0300, Serge Semin wrote: > On Fri, Jun 16, 2017 at 01:34:59PM -0600, Logan Gunthorpe > wrote: > > Now, if you'd like to actually review the code I'd be happy to address > > any concerns you find. I won't be responding to any more

Re: [RFC PATCH 00/13] Switchtec NTB Support

On Fri, Jun 16, 2017 at 11:21:00PM +0300, Serge Semin wrote: > On Fri, Jun 16, 2017 at 01:34:59PM -0600, Logan Gunthorpe > wrote: > > Now, if you'd like to actually review the code I'd be happy to address > > any concerns you find. I won't be responding to any more philosophical > > arguments or

Re: LTS testing with latest kselftests - some failures

On Fri, Jun 16, 2017 at 09:47:21PM +0200, Luis R. Rodriguez wrote: > Some of the knobs however are for extending tests for > existing APIs in older kernels, the async and custom fallback one are an > example. There are a series of test cases later added which could help > test LTS kernels. Would

Re: LTS testing with latest kselftests - some failures

On Fri, Jun 16, 2017 at 09:47:21PM +0200, Luis R. Rodriguez wrote: > Some of the knobs however are for extending tests for > existing APIs in older kernels, the async and custom fallback one are an > example. There are a series of test cases later added which could help > test LTS kernels. Would

Re: [PATCH v2 1/3] mm: add vm_insert_mixed_mkwrite()

On Thu, Jun 15, 2017 at 04:42:04PM +0200, Jan Kara wrote: > On Wed 14-06-17 11:22:09, Ross Zwisler wrote: > > To be able to use the common 4k zero page in DAX we need to have our PTE > > fault path look more like our PMD fault path where a PTE entry can be > > marked as dirty and writeable as it

Re: [PATCH v2 1/3] mm: add vm_insert_mixed_mkwrite()

On Thu, Jun 15, 2017 at 04:42:04PM +0200, Jan Kara wrote: > On Wed 14-06-17 11:22:09, Ross Zwisler wrote: > > To be able to use the common 4k zero page in DAX we need to have our PTE > > fault path look more like our PMD fault path where a PTE entry can be > > marked as dirty and writeable as it

[RFC v2 03/12] powerpc: Implement sys_pkey_alloc and sys_pkey_free system call.

Sys_pkey_alloc() allocates and returns available pkey Sys_pkey_free() frees up the pkey. Total 32 keys are supported on powerpc. However pkey 0,1 and 31 are reserved. So effectively we have 29 pkeys. Signed-off-by: Ram Pai --- arch/powerpc/Kconfig

[RFC v2 03/12] powerpc: Implement sys_pkey_alloc and sys_pkey_free system call.

Sys_pkey_alloc() allocates and returns available pkey Sys_pkey_free() frees up the pkey. Total 32 keys are supported on powerpc. However pkey 0,1 and 31 are reserved. So effectively we have 29 pkeys. Signed-off-by: Ram Pai --- arch/powerpc/Kconfig | 15

[RFC v2 02/12] powerpc: Free up four 64K PTE bits in 64K backed hpte pages.

Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 in the 64K backed hpte pages. This along with the earlier patch will entirely free up the four bits from 64K PTE. This patch does the following change to 64K PTE that is backed by 64K hpte. H_PAGE_F_SECOND which occupied bit 4 moves to

[RFC v2 02/12] powerpc: Free up four 64K PTE bits in 64K backed hpte pages.

Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 in the 64K backed hpte pages. This along with the earlier patch will entirely free up the four bits from 64K PTE. This patch does the following change to 64K PTE that is backed by 64K hpte. H_PAGE_F_SECOND which occupied bit 4 moves to

[RFC v2 06/12] powerpc: Program HPTE key protection bits.

Map the PTE protection key bits to the HPTE key protection bits, while creatiing HPTE entries. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/mmu-hash.h | 5 + arch/powerpc/include/asm/pkeys.h | 7 +++ arch/powerpc/mm/hash_utils_64.c

[RFC v2 06/12] powerpc: Program HPTE key protection bits.

Map the PTE protection key bits to the HPTE key protection bits, while creatiing HPTE entries. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/mmu-hash.h | 5 + arch/powerpc/include/asm/pkeys.h | 7 +++ arch/powerpc/mm/hash_utils_64.c | 5 +

[RFC v2 04/12] powerpc: store and restore the pkey state across context switches.

Signed-off-by: Ram Pai --- arch/powerpc/include/asm/processor.h | 5 + arch/powerpc/kernel/process.c| 18 ++ 2 files changed, 23 insertions(+) diff --git a/arch/powerpc/include/asm/processor.h b/arch/powerpc/include/asm/processor.h index

[RFC v2 04/12] powerpc: store and restore the pkey state across context switches.

Signed-off-by: Ram Pai --- arch/powerpc/include/asm/processor.h | 5 + arch/powerpc/kernel/process.c| 18 ++ 2 files changed, 23 insertions(+) diff --git a/arch/powerpc/include/asm/processor.h b/arch/powerpc/include/asm/processor.h index a2123f2..1f714df 100644 ---

[RFC v2 09/12] powerpc: Deliver SEGV signal on pkey violation.

The value of the AMR register at the time of exception is made available in gp_regs[PT_AMR] of the siginfo. This field can be used to reprogram the permission bits of any valid pkey. Similarly the value of the pkey, whose protection got violated, is made available at si_pkey field of the siginfo

[RFC v2 09/12] powerpc: Deliver SEGV signal on pkey violation.

The value of the AMR register at the time of exception is made available in gp_regs[PT_AMR] of the siginfo. This field can be used to reprogram the permission bits of any valid pkey. Similarly the value of the pkey, whose protection got violated, is made available at si_pkey field of the siginfo

[RFC v2 07/12] powerpc: Macro the mask used for checking DSI exception

Replace the magic number used to check for DSI exception with a meaningful value. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/reg.h | 9 - arch/powerpc/kernel/exceptions-64s.S | 2 +- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git

[RFC v2 07/12] powerpc: Macro the mask used for checking DSI exception

Replace the magic number used to check for DSI exception with a meaningful value. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/reg.h | 9 - arch/powerpc/kernel/exceptions-64s.S | 2 +- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git

[RFC v2 12/12]selftest: Updated protection key selftest

Added test support for PowerPC implementation off protection keys. Signed-off-by: Ram Pai --- tools/testing/selftests/vm/Makefile |1 + tools/testing/selftests/vm/pkey-helpers.h | 365 +++ tools/testing/selftests/vm/protection_keys.c | 1451

[RFC v2 12/12]selftest: Updated protection key selftest

Added test support for PowerPC implementation off protection keys. Signed-off-by: Ram Pai --- tools/testing/selftests/vm/Makefile |1 + tools/testing/selftests/vm/pkey-helpers.h | 365 +++ tools/testing/selftests/vm/protection_keys.c | 1451 +

[RFC v2 11/12]Documentation: Documentation updates.

The Documentaton file is moved from x86 into the generic area, since this feature is now supported by more than one archs. Signed-off-by: Ram Pai --- Documentation/vm/protection-keys.txt | 110 ++ Documentation/x86/protection-keys.txt | 85

[RFC v2 08/12] powerpc: Handle exceptions caused by violation of pkey protection.

Handle Data and Instruction exceptions caused by memory protection-key. Signed-off-by: Ram Pai (cherry picked from commit a5e5217619a0c475fe0cacc3b0cf1d3d33c79a09) Conflicts: arch/powerpc/include/asm/reg.h arch/powerpc/kernel/exceptions-64s.S ---

[RFC v2 11/12]Documentation: Documentation updates.

The Documentaton file is moved from x86 into the generic area, since this feature is now supported by more than one archs. Signed-off-by: Ram Pai --- Documentation/vm/protection-keys.txt | 110 ++ Documentation/x86/protection-keys.txt | 85

[RFC v2 08/12] powerpc: Handle exceptions caused by violation of pkey protection.

Handle Data and Instruction exceptions caused by memory protection-key. Signed-off-by: Ram Pai (cherry picked from commit a5e5217619a0c475fe0cacc3b0cf1d3d33c79a09) Conflicts: arch/powerpc/include/asm/reg.h arch/powerpc/kernel/exceptions-64s.S ---

[RFC v2 05/12] powerpc: Implementation for sys_mprotect_pkey() system call.

This system call, associates the pkey with PTE of all pages corresponding to the given address range. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/pgtable.h | 22 ++- arch/powerpc/include/asm/mman.h | 29 +

[RFC v2 10/12] powerpc: Read AMR only if pkey-violation caused the exception.

Signed-off-by: Ram Pai --- arch/powerpc/kernel/exceptions-64s.S | 16 ++-- 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/arch/powerpc/kernel/exceptions-64s.S b/arch/powerpc/kernel/exceptions-64s.S index 8db9ef8..a4de1b4 100644 ---

[RFC v2 01/12] powerpc: Free up four 64K PTE bits in 4K backed hpte pages.

Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 in the 4K backed hpte pages. These bits continue to be used for 64K backed hpte pages in this patch, but will be freed up in the next patch. The patch does the following change to the 64K PTE format H_PAGE_BUSY moves from bit 3 to bit 9

[RFC v2 05/12] powerpc: Implementation for sys_mprotect_pkey() system call.

This system call, associates the pkey with PTE of all pages corresponding to the given address range. Signed-off-by: Ram Pai --- arch/powerpc/include/asm/book3s/64/pgtable.h | 22 ++- arch/powerpc/include/asm/mman.h | 29 + arch/powerpc/include/asm/pkeys.h |

[RFC v2 10/12] powerpc: Read AMR only if pkey-violation caused the exception.

Signed-off-by: Ram Pai --- arch/powerpc/kernel/exceptions-64s.S | 16 ++-- 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/arch/powerpc/kernel/exceptions-64s.S b/arch/powerpc/kernel/exceptions-64s.S index 8db9ef8..a4de1b4 100644 ---

[RFC v2 01/12] powerpc: Free up four 64K PTE bits in 4K backed hpte pages.

Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 in the 4K backed hpte pages. These bits continue to be used for 64K backed hpte pages in this patch, but will be freed up in the next patch. The patch does the following change to the 64K PTE format H_PAGE_BUSY moves from bit 3 to bit 9

[RFC v2 00/12] powerpc: Memory Protection Keys

Memory protection keys enable applications to protect its address space from inadvertent access or corruption from itself. The overall idea: A process allocates a key and associates it with a address range withinits address space. The process than can dynamically set

[RFC v2 00/12] powerpc: Memory Protection Keys

Memory protection keys enable applications to protect its address space from inadvertent access or corruption from itself. The overall idea: A process allocates a key and associates it with a address range withinits address space. The process than can dynamically set

[PATCH v4 0/5] perf config: Bugfixes & Refactoring

Hi all, This is simple patchset for perf-config to fix small bugs and refactor code. I'd appreciate some feedback on this patchset. The code is also available at 'config/refactoring-v4' branch on git://github.com/taeung/linux-perf.git Thanks, Taeung v4: - rebase on current acme/perf/core

[PATCH v4 0/5] perf config: Bugfixes & Refactoring

Hi all, This is simple patchset for perf-config to fix small bugs and refactor code. I'd appreciate some feedback on this patchset. The code is also available at 'config/refactoring-v4' branch on git://github.com/taeung/linux-perf.git Thanks, Taeung v4: - rebase on current acme/perf/core

[PATCH v4 4/5] perf config: Check not only section->from_system_config but also item's

Currently only section->from_system_config is being checked multiple times. items->from_system_config should be also checked, so fix it. Cc: Jiri Olsa Cc: Namhyung Kim Signed-off-by: Taeung Song --- tools/perf/builtin-config.c |

[PATCH v4 3/5] perf config: Finally write changed configs on config file at a time

Currently set_config() can be repeatedly called for each input config on the below case: $ perf config kmem.default=slab report.children=false ... But it's a waste, so finally write changed configs at a time. Cc: Jiri Olsa Cc: Namhyung Kim

[PATCH v4 2/5] perf config: Refactor the code using 'ret' variable in cmd_config()

To simplify the code related to 'ret' variable in cmd_config(), initialize 'ret' with -1 instead of 0. Cc: Jiri Olsa Cc: Namhyung Kim Signed-off-by: Taeung Song --- tools/perf/builtin-config.c | 30 +-

[PATCH v4 1/5] perf config: Check error cases of {show_spec, set}_config()

show_spec_config() and set_config() can be called multiple times in the loop in cmd_config(). However, The error cases of them wasn't checked, so fix it. Reported-by: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc: Namhyung Kim Signed-off-by:

[PATCH v4 4/5] perf config: Check not only section->from_system_config but also item's

Currently only section->from_system_config is being checked multiple times. items->from_system_config should be also checked, so fix it. Cc: Jiri Olsa Cc: Namhyung Kim Signed-off-by: Taeung Song --- tools/perf/builtin-config.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v4 3/5] perf config: Finally write changed configs on config file at a time

Currently set_config() can be repeatedly called for each input config on the below case: $ perf config kmem.default=slab report.children=false ... But it's a waste, so finally write changed configs at a time. Cc: Jiri Olsa Cc: Namhyung Kim Signed-off-by: Taeung Song ---

[PATCH v4 2/5] perf config: Refactor the code using 'ret' variable in cmd_config()

To simplify the code related to 'ret' variable in cmd_config(), initialize 'ret' with -1 instead of 0. Cc: Jiri Olsa Cc: Namhyung Kim Signed-off-by: Taeung Song --- tools/perf/builtin-config.c | 30 +- 1 file changed, 13 insertions(+), 17 deletions(-) diff --git

[PATCH v4 1/5] perf config: Check error cases of {show_spec, set}_config()

show_spec_config() and set_config() can be called multiple times in the loop in cmd_config(). However, The error cases of them wasn't checked, so fix it. Reported-by: Arnaldo Carvalho de Melo Cc: Jiri Olsa Cc: Namhyung Kim Signed-off-by: Taeung Song --- tools/perf/builtin-config.c | 17

[PATCH v4 5/5] perf config: Autogenerate a config file if it does not exist on setting feature.

Currently the users can not create a config file in the below case. Before: $ rm -f ~/.perfconfig $ perf config --user report.children=false $ cat ~/.perfconfig cat: /root/.perfconfig: No such file or directory But I think it should work no matter whether a config file exists or not.

[PATCH v4 5/5] perf config: Autogenerate a config file if it does not exist on setting feature.

Currently the users can not create a config file in the below case. Before: $ rm -f ~/.perfconfig $ perf config --user report.children=false $ cat ~/.perfconfig cat: /root/.perfconfig: No such file or directory But I think it should work no matter whether a config file exists or not.

Re: [kernel-hardening] Re: [PATCH v4 06/13] iscsi: ensure RNG is seeded before use

On 06/16/2017 05:41 PM, Jason A. Donenfeld wrote: > Hi Lee, > > On Fri, Jun 16, 2017 at 11:58 PM, Lee Duncan wrote: >> It seems like what you are doing is basically "good", i.e. if there is >> not enough random data, don't use it. But what happens in that case? The >>

Re: [kernel-hardening] Re: [PATCH v4 06/13] iscsi: ensure RNG is seeded before use

On 06/16/2017 05:41 PM, Jason A. Donenfeld wrote: > Hi Lee, > > On Fri, Jun 16, 2017 at 11:58 PM, Lee Duncan wrote: >> It seems like what you are doing is basically "good", i.e. if there is >> not enough random data, don't use it. But what happens in that case? The >> authentication fails? How

[PATCH v3] ip6_tunnel: Correct tos value in collect_md mode

Same as ip_gre, geneve and vxlan, use key->tos as traffic class value. CC: Peter Dawson Fixes: 0e9a709560db ("ip6_tunnel, ip6_gre: fix setting of DSCP on encapsulated packets”) Signed-off-by: Haishuang Yan --- Changes since v3: * Add

[PATCH v3] ip6_tunnel: Correct tos value in collect_md mode

Same as ip_gre, geneve and vxlan, use key->tos as traffic class value. CC: Peter Dawson Fixes: 0e9a709560db ("ip6_tunnel, ip6_gre: fix setting of DSCP on encapsulated packets”) Signed-off-by: Haishuang Yan --- Changes since v3: * Add fixes information * Remove obsoleted RT_TOS mask ---

[PATCH v2 1/2] ip_tunnel: fix ip tunnel lookup in collect_md mode

In collect_md mode, if the tun dev is down, it still can call ip_tunnel_rcv to receive on packets, and the rx statistics increase improperly. Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.") Cc: Pravin B Shelar Signed-off-by: Haishuang Yan

[PATCH v2 2/2] ip6_tunnel: fix ip6 tunnel lookup in collect_md mode

In collect_md mode, if the tun dev is down, it still can call __ip6_tnl_rcv to receive on packets, and the rx statistics increase improperly. Fixes: 8d79266bc48c ("ip6_tunnel: add collect_md mode to IPv6 tunnels") Cc: Alexei Starovoitov Signed-off-by: Haishuang Yan

[PATCH v2 2/2] ip6_tunnel: fix ip6 tunnel lookup in collect_md mode

In collect_md mode, if the tun dev is down, it still can call __ip6_tnl_rcv to receive on packets, and the rx statistics increase improperly. Fixes: 8d79266bc48c ("ip6_tunnel: add collect_md mode to IPv6 tunnels") Cc: Alexei Starovoitov Signed-off-by: Haishuang Yan --- Change since v2: * Fix

[PATCH v2 1/2] ip_tunnel: fix ip tunnel lookup in collect_md mode

In collect_md mode, if the tun dev is down, it still can call ip_tunnel_rcv to receive on packets, and the rx statistics increase improperly. Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.") Cc: Pravin B Shelar Signed-off-by: Haishuang Yan --- Change since v2: * Fix

[PATCH V2] staging: rtl8192u: style fix

Fixed checkpatch.pl warnings of "function definition argument FOO should also have an identifier name" Found using checkpatch Signed-off-by: Derek Robson V1 had vauge subjet --- drivers/staging/rtl8192u/ieee80211/ieee80211.h | 2 +-

[PATCH V2] staging: rtl8192u: style fix

Fixed checkpatch.pl warnings of "function definition argument FOO should also have an identifier name" Found using checkpatch Signed-off-by: Derek Robson V1 had vauge subjet --- drivers/staging/rtl8192u/ieee80211/ieee80211.h | 2 +- drivers/staging/rtl8192u/ieee80211/ieee80211_crypt.h |

[PATCH V2] staging: rtl8723bs - remove asm includes

Fixed checkpatch warnings "Use #include instead of " Found using checkpatch Signed-off-by: Derek Robson V1 had vauge subject. --- drivers/staging/rtl8723bs/include/osdep_service_linux.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH V2] staging: rtl8723bs - remove asm includes

Fixed checkpatch warnings "Use #include instead of " Found using checkpatch Signed-off-by: Derek Robson V1 had vauge subject. --- drivers/staging/rtl8723bs/include/osdep_service_linux.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH V2] staging: unisys: visorhba - style fix

Fixed style of permissions to octal. Found using checkpatch Signed-off-by: Derek Robson V1 has vauge subject --- drivers/staging/unisys/visorhba/visorhba_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH V2] staging: unisys: visorhba - style fix

Fixed style of permissions to octal. Found using checkpatch Signed-off-by: Derek Robson V1 has vauge subject --- drivers/staging/unisys/visorhba/visorhba_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/unisys/visorhba/visorhba_main.c

Re: [PATCH v2] ip6_tunnel: Correct tos value in collect_md mode

> On 16 Jun 2017, at 10:44 PM, Daniel Borkmann wrote: > > On 06/15/2017 05:54 AM, Peter Dawson wrote: >> On Thu, 15 Jun 2017 10:30:29 +0800 >> Haishuang Yan wrote: >> >>> Same as ip_gre, geneve and vxlan, use key->tos as tos value. >>>

Re: [PATCH v2] ip6_tunnel: Correct tos value in collect_md mode

> On 16 Jun 2017, at 10:44 PM, Daniel Borkmann wrote: > > On 06/15/2017 05:54 AM, Peter Dawson wrote: >> On Thu, 15 Jun 2017 10:30:29 +0800 >> Haishuang Yan wrote: >> >>> Same as ip_gre, geneve and vxlan, use key->tos as tos value. >>> >>> CC: Peter Dawson >>> Fixes: 0e9a709560db

[PATCH 1/4] x86: do not use cpufreq_quick_get() for /proc/cpuinfo "cpu MHz"

From: Len Brown cpufreq_quick_get() allows cpufreq drivers to over-ride cpu_khz that is otherwise reported in x86 /proc/cpuinfo "cpu MHz". There are four problems with this scheme, any of them is sufficient justification to delete it. 1. Depending on which cpufreq driver

[PATCH 1/4] x86: do not use cpufreq_quick_get() for /proc/cpuinfo "cpu MHz"

From: Len Brown cpufreq_quick_get() allows cpufreq drivers to over-ride cpu_khz that is otherwise reported in x86 /proc/cpuinfo "cpu MHz". There are four problems with this scheme, any of them is sufficient justification to delete it. 1. Depending on which cpufreq driver is loaded, the

[GIT PULL] x86,cpufreq: unify APERF/MPERF computation

In-Reply-To: Hi Rafael, This patch series has 3 goals: 1. Make "cpu MHz" in /proc/cpuinfo supportable. 2. Make /sys/.../cpufreq/scaling_cur_freq meaningful and consistent on modern x86 systems. 3. Use 1. and 2. to remove scheduler and cpufreq overhead There are 3 main changes since this

[PATCH 3/4] intel_pstate: delete scheduler hook in HWP mode

From: Len Brown The cpufreq/scaling_cur_freq sysfs attribute is now provided by shared x86 cpufreq code on modern x86 systems, including all systems supported by the intel_pstate driver. In HWP mode, maintaining that value was the sole purpose of the scheduler hook,

[GIT PULL] x86,cpufreq: unify APERF/MPERF computation

In-Reply-To: Hi Rafael, This patch series has 3 goals: 1. Make "cpu MHz" in /proc/cpuinfo supportable. 2. Make /sys/.../cpufreq/scaling_cur_freq meaningful and consistent on modern x86 systems. 3. Use 1. and 2. to remove scheduler and cpufreq overhead There are 3 main changes since this

[PATCH 3/4] intel_pstate: delete scheduler hook in HWP mode

From: Len Brown The cpufreq/scaling_cur_freq sysfs attribute is now provided by shared x86 cpufreq code on modern x86 systems, including all systems supported by the intel_pstate driver. In HWP mode, maintaining that value was the sole purpose of the scheduler hook,

[PATCH 4/4] intel_pstate: skip scheduler hook when in "performance" mode.

From: Len Brown When the governor is set to "performance", intel_pstate does not need the scheduler hook for doing any calculations. Under these conditions, its only purpose is to continue to maintain cpufreq/scaling_cur_freq. The cpufreq/scaling_cur_freq sysfs attribute

[PATCH V2] staging: sm750fb - style fix

Fixed checkpatch.pl warnings of the form "function definition argument 'foo' should also have an identifier name" in header files. Signed-off-by: Derek Robson V1 had vague subject --- drivers/staging/sm750fb/sm750.h | 24 1 file changed, 16

[PATCH 4/4] intel_pstate: skip scheduler hook when in "performance" mode.

From: Len Brown When the governor is set to "performance", intel_pstate does not need the scheduler hook for doing any calculations. Under these conditions, its only purpose is to continue to maintain cpufreq/scaling_cur_freq. The cpufreq/scaling_cur_freq sysfs attribute is now provided by

[PATCH V2] staging: sm750fb - style fix

Fixed checkpatch.pl warnings of the form "function definition argument 'foo' should also have an identifier name" in header files. Signed-off-by: Derek Robson V1 had vague subject --- drivers/staging/sm750fb/sm750.h | 24 1 file changed, 16 insertions(+), 8

  1   2   3   4   5   6   7   8   9   10   >