Re: [PATCH] regulator: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:26PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc:

Re: [PATCH] pinctrl: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:23PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc:

Re: [PATCH] regulator: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:26PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Liam Girdwood >

Re: [PATCH] pinctrl: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:23PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Linus Walleij >

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Tue, Jul 18, 2017 at 06:15:45PM -0300, Mauro Carvalho Chehab wrote: > The way it is, ghes_edac is a poor man's driver. What it hopefully > provide is a detection that an error happened, without really telling > the user what component should be replaced. I beg to differ. From the UEFI spec:

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Tue, Jul 18, 2017 at 06:15:45PM -0300, Mauro Carvalho Chehab wrote: > The way it is, ghes_edac is a poor man's driver. What it hopefully > provide is a detection that an error happened, without really telling > the user what component should be replaced. I beg to differ. From the UEFI spec:

Re: [PATCH] perf probe: Fix build failure for get_target_map()

Arnaldo Carvalho de Melo writes: > Em Tue, Jul 18, 2017 at 07:19:45PM +1000, Michael Ellerman escreveu: >> Arnaldo Carvalho de Melo writes: >> >> > Em Mon, Jul 17, 2017 at 04:02:22PM +0530, Ravi Bangoria escreveu: >> >> Commit 801bc8193463 ("perf probe: Allow

Re: [PATCH] perf probe: Fix build failure for get_target_map()

Arnaldo Carvalho de Melo writes: > Em Tue, Jul 18, 2017 at 07:19:45PM +1000, Michael Ellerman escreveu: >> Arnaldo Carvalho de Melo writes: >> >> > Em Mon, Jul 17, 2017 at 04:02:22PM +0530, Ravi Bangoria escreveu: >> >> Commit 801bc8193463 ("perf probe: Allow placing uprobes in >> >> alternate

Re: [PATCH v4 1/5] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs

Logan Gunthorpe writes: > Subsequent patches in this series makes use of the readq and writeq > defines in iomap.h. However, as is, they get missed on the powerpc > platform seeing the include comes before the define. This patch > moves the include down to fix this. > >

Re: [PATCH v4 1/5] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs

Logan Gunthorpe writes: > Subsequent patches in this series makes use of the readq and writeq > defines in iomap.h. However, as is, they get missed on the powerpc > platform seeing the include comes before the define. This patch > moves the include down to fix this. > > Signed-off-by: Logan

Re: [PATCH] mmc: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:16PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc:

Re: [PATCH] mmc: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:16PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Ulf Hansson >

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Tue, Jul 18, 2017 at 07:58:54PM +, Kani, Toshimitsu wrote: > I have HPE Haswell and Skylake test systems with GHES, but they do not > hide IMCs from the OS. So, the sb_edac and skx_edac drivers get > attached on these systems when ghes_edac is disabled. That's how it is supposed to work.

Re: [RFC PATCH] mm, oom: allow oom reaper to race with exit_mmap

On Thu 29-06-17 10:46:21, Michal Hocko wrote: > Forgot to CC Hugh. > > Hugh, Andrew, do you see this could cause any problem wrt. > ksm/khugepaged exit path? ping. I would really appreciate some help here. I would like to resend the patch soon. > On Mon 26-06-17 15:03:46, Michal Hocko wrote: >

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Tue, Jul 18, 2017 at 07:58:54PM +, Kani, Toshimitsu wrote: > I have HPE Haswell and Skylake test systems with GHES, but they do not > hide IMCs from the OS. So, the sb_edac and skx_edac drivers get > attached on these systems when ghes_edac is disabled. That's how it is supposed to work.

Re: [RFC PATCH] mm, oom: allow oom reaper to race with exit_mmap

On Thu 29-06-17 10:46:21, Michal Hocko wrote: > Forgot to CC Hugh. > > Hugh, Andrew, do you see this could cause any problem wrt. > ksm/khugepaged exit path? ping. I would really appreciate some help here. I would like to resend the patch soon. > On Mon 26-06-17 15:03:46, Michal Hocko wrote: >

Re: [PATCH] pinctrl: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:23PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc:

Re: [PATCH] pinctrl: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:23PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Linus Walleij >

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Tue, Jul 18, 2017 at 09:20:44PM +, Kani, Toshimitsu wrote: > I agree that 'osc_sb_apei_support_acked' should be checked when > enabling ghes_edac. I do not know the details of existing issues, but > it sounds unlikely that this will address all of them since bugs can be > everywhere. No,

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Tue, Jul 18, 2017 at 09:20:44PM +, Kani, Toshimitsu wrote: > I agree that 'osc_sb_apei_support_acked' should be checked when > enabling ghes_edac. I do not know the details of existing issues, but > it sounds unlikely that this will address all of them since bugs can be > everywhere. No,

Re: [PATCH] ARM: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:42:41PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc:

Re: [PATCH] ARM: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:42:41PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Russell King >

Re: [PATCH v5 4/4]: perf/core: complete replace of lists by rb trees for pinned and flexible groups at perf_event_context

Alexey Budankov writes: > On 18.07.2017 19:55, Alexander Shishkin wrote: >> Alexey Budankov writes: >> >>> I see. Do you personally have some more issues that needs to be addressed? >>> My intention is that this patch v5 4/4

Re: [PATCH v5 4/4]: perf/core: complete replace of lists by rb trees for pinned and flexible groups at perf_event_context

Alexey Budankov writes: > On 18.07.2017 19:55, Alexander Shishkin wrote: >> Alexey Budankov writes: >> >>> I see. Do you personally have some more issues that needs to be addressed? >>> My intention is that this patch v5 4/4 addresses all your comments raised >>> in >>> the previous reviews.

Re: [PATCH] memory: Convert to using %pOF instead of full_name

On 18/07/2017 at 16:43:14 -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Nicolas

Re: [PATCH] memory: Convert to using %pOF instead of full_name

On 18/07/2017 at 16:43:14 -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Nicolas Ferre > Cc:

Re: [PATCH] EDAC: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:42:59PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc:

Re: [PATCH] EDAC: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:42:59PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Borislav Petkov

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On 2017/7/18 23:20, Paul E. McKenney wrote: >> 2) for rcu idle enter/exit, I measured the details which Paul provided, and >> the result matches with what I have measured before, nothing notable found. >> But it still makes more sense if we can make rcu idle enter/exit hooked with >> tick off.

Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods

On 2017/7/18 23:20, Paul E. McKenney wrote: >> 2) for rcu idle enter/exit, I measured the details which Paul provided, and >> the result matches with what I have measured before, nothing notable found. >> But it still makes more sense if we can make rcu idle enter/exit hooked with >> tick off.

Re: [PATCH RFC v5] cpufreq: schedutil: Make iowait boost more energy efficient

On 18-07-17, 15:02, Juri Lelli wrote: > Mmm, seems to make sense to me. :/ > > Would the following work (on top of Joel's v5)? Rationale being that > only in sugov_set_iowait_boost we might bump freq up (if no iowait_boost > was set) or start from policy->min. In sugov_iowait_boost (consumer) >

Re: [PATCH RFC v5] cpufreq: schedutil: Make iowait boost more energy efficient

On 18-07-17, 15:02, Juri Lelli wrote: > Mmm, seems to make sense to me. :/ > > Would the following work (on top of Joel's v5)? Rationale being that > only in sugov_set_iowait_boost we might bump freq up (if no iowait_boost > was set) or start from policy->min. In sugov_iowait_boost (consumer) >

Re: [PATCH] pci: quirk: Apply APM ACS quirk to XGene devices

> > I don't know what that means, does the hardware support an equivalent > to source validation or not? Yes, source validation is done through the smmu. What's the response of the root port if > the downstream device issues a transaction spoofing devices not within > the bus number ranges of

Re: [PATCH] pci: quirk: Apply APM ACS quirk to XGene devices

> > I don't know what that means, does the hardware support an equivalent > to source validation or not? Yes, source validation is done through the smmu. What's the response of the root port if > the downstream device issues a transaction spoofing devices not within > the bus number ranges of

Re: [PATCH] x86/microcode/AMD: fix memleak in update_cache()

On Wed, Jul 19, 2017 at 12:21:23PM +0800, shuw...@redhat.com wrote: > From: Shu Wang > > Found this issue by kmemleak. The mem is allocated in > verify_and_add_patch(), passed to update_cache(patch), > and just dropped the reference without free > if (p->patch_id >=

Re: [PATCH] x86/microcode/AMD: fix memleak in update_cache()

On Wed, Jul 19, 2017 at 12:21:23PM +0800, shuw...@redhat.com wrote: > From: Shu Wang > > Found this issue by kmemleak. The mem is allocated in > verify_and_add_patch(), passed to update_cache(patch), > and just dropped the reference without free > if (p->patch_id >= new_patch->patch_id) >

Re: [PATCH] KVM: VMX: Fix invalid guest state detection after task-switch emulation

Ping, :) 2017-07-11 15:13 GMT+08:00 Wanpeng Li : > From: Wanpeng Li > > This can be reproduced by EPT=1, unrestricted_guest=N, emulate_invalid_state=Y > or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it tries > to emulate invalid

Re: [PATCH] KVM: VMX: Fix invalid guest state detection after task-switch emulation

Ping, :) 2017-07-11 15:13 GMT+08:00 Wanpeng Li : > From: Wanpeng Li > > This can be reproduced by EPT=1, unrestricted_guest=N, emulate_invalid_state=Y > or EPT=0, the trace of kvm-unit-tests/taskswitch2.flat is like below, it tries > to emulate invalid guest state task-switch: > > kvm_exit:

[PATCH v2] gpio-exar: Use correct property prefix and document bindings

The device-specific property should be prefixed with the vendor name, not "linux,", as Linus Walleij pointed out. Change this and document the bindings of this platform device. We didn't ship the old binding in a release yet. So we can still change it without breaking an official API. Fixes:

[PATCH v2] gpio-exar: Use correct property prefix and document bindings

The device-specific property should be prefixed with the vendor name, not "linux,", as Linus Walleij pointed out. Change this and document the bindings of this platform device. We didn't ship the old binding in a release yet. So we can still change it without breaking an official API. Fixes:

[PATCH] omapfb: panel-sony-acx565akm: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 5227 560 05787169b

[PATCH] omapfb: panel-sony-acx565akm: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 5227 560 05787169b

Re: [PATCH v3 00/15] exec: Use sane stack rlimit under secureexec

On Tue, Jul 18, 2017 at 8:22 PM, Serge E. Hallyn wrote: > On Tue, Jul 18, 2017 at 03:25:21PM -0700, Kees Cook wrote: >> This series has grown... :P >> >> As discussed with Linus and Andy, we need to reset the stack rlimit >> before we do memory layouts when execing a

Re: [PATCH v3 00/15] exec: Use sane stack rlimit under secureexec

On Tue, Jul 18, 2017 at 8:22 PM, Serge E. Hallyn wrote: > On Tue, Jul 18, 2017 at 03:25:21PM -0700, Kees Cook wrote: >> This series has grown... :P >> >> As discussed with Linus and Andy, we need to reset the stack rlimit >> before we do memory layouts when execing a privilege-gaining (e.g. >>

[PATCH] omapfb: panel-tpo-td043mtea1: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 2673 368 03041 be1

[PATCH] omapfb: panel-tpo-td043mtea1: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 2673 368 03041 be1

Re: [PATCH 2/2] powernv/powerpc: Clear PECE1 in LPCR via stop-api only on Hotplug

On Wed, 19 Jul 2017 10:34:59 +0530 Gautham R Shenoy wrote: > Hello Nicholas, > > On Wed, Jul 19, 2017 at 12:14:12PM +1000, Nicholas Piggin wrote: > > Thanks for working on these patches. We really need to get this stuff > > merged and tested asap :) > > > > > On Tue,

Re: [PATCH 2/2] powernv/powerpc: Clear PECE1 in LPCR via stop-api only on Hotplug

On Wed, 19 Jul 2017 10:34:59 +0530 Gautham R Shenoy wrote: > Hello Nicholas, > > On Wed, Jul 19, 2017 at 12:14:12PM +1000, Nicholas Piggin wrote: > > Thanks for working on these patches. We really need to get this stuff > > merged and tested asap :) > > > > > On Tue, 18 Jul 2017 19:58:49

Admin

PERHATIAN Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali memvalidasi email mailbox Anda. Untuk memvalidasi ulang

Admin

PERHATIAN Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali memvalidasi email mailbox Anda. Untuk memvalidasi ulang

[PATCH] video: fbdev: uvesafb: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 154264952 187 205655055

[PATCH] video: fbdev: uvesafb: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 154264952 187 205655055

RE: [PATCH] usb: gadget: udc: fix the kernel NULL pointer in composite_setup

Hi, Balbi: 1. the issue reproduced very rarely, we run reboot test reproduce the issue, it reproduced two times on two board after more than 1500 cycles reboot. 2. the kernel version is 4.4, the test case is cold reboot, I think it's not android patches cause it, it's the

RE: [PATCH] usb: gadget: udc: fix the kernel NULL pointer in composite_setup

Hi, Balbi: 1. the issue reproduced very rarely, we run reboot test reproduce the issue, it reproduced two times on two board after more than 1500 cycles reboot. 2. the kernel version is 4.4, the test case is cold reboot, I think it's not android patches cause it, it's the

Re: 4.12 NULL pointer dereference in kmem_cache_free on USB storage removal

Hello, That patch fixes the problem, as far as I tested. However, it still is not included in stable by 4.12.2. The problem persists there, and is fixed when this patch is applied on top of it. What to to about it? Thanks, Yagmur Oymak. On 07/14/2017 12:07 AM, Bart Van Assche wrote: > On Thu,

Re: 4.12 NULL pointer dereference in kmem_cache_free on USB storage removal

Hello, That patch fixes the problem, as far as I tested. However, it still is not included in stable by 4.12.2. The problem persists there, and is fixed when this patch is applied on top of it. What to to about it? Thanks, Yagmur Oymak. On 07/14/2017 12:07 AM, Bart Van Assche wrote: > On Thu,

Re: [PATCH 2/2] powernv/powerpc: Clear PECE1 in LPCR via stop-api only on Hotplug

Hello Nicholas, On Wed, Jul 19, 2017 at 12:14:12PM +1000, Nicholas Piggin wrote: > Thanks for working on these patches. We really need to get this stuff > merged and tested asap :) > > On Tue, 18 Jul 2017 19:58:49 +0530 [..snip..] > > diff --git a/arch/powerpc/platforms/powernv/smp.c > >

Re: [PATCH 2/2] powernv/powerpc: Clear PECE1 in LPCR via stop-api only on Hotplug

Hello Nicholas, On Wed, Jul 19, 2017 at 12:14:12PM +1000, Nicholas Piggin wrote: > Thanks for working on these patches. We really need to get this stuff > merged and tested asap :) > > On Tue, 18 Jul 2017 19:58:49 +0530 [..snip..] > > diff --git a/arch/powerpc/platforms/powernv/smp.c > >

Re: [PATCH 1/9] ARM: ep93xx: allow NULL clock for clk_get_rate

On 18/07/17 12:17, Jonas Gorski wrote: > Make the behaviour of clk_get_rate consistent with common clk's > clk_get_rate by accepting NULL clocks as parameter. Some device > drivers rely on this, and will cause an OOPS otherwise. > > Fixes: 1d81eedb8f6c ("[ARM] 3634/1: ep93xx: initial

Re: [PATCH 1/9] ARM: ep93xx: allow NULL clock for clk_get_rate

On 18/07/17 12:17, Jonas Gorski wrote: > Make the behaviour of clk_get_rate consistent with common clk's > clk_get_rate by accepting NULL clocks as parameter. Some device > drivers rely on this, and will cause an OOPS otherwise. > > Fixes: 1d81eedb8f6c ("[ARM] 3634/1: ep93xx: initial

Re: fscrypt request_module() deadlock

On Tue, Jul 18, 2017 at 04:17:47PM -0700, Eric Biggers wrote: > > While that should solve the problem, isn't it possible to actually have a > module > which supplies an algorithm like "xts(aes)"? In that case it wouldn't be > desirable to instantiate the generic "xts" template. Well, in the

Re: fscrypt request_module() deadlock

On Tue, Jul 18, 2017 at 04:17:47PM -0700, Eric Biggers wrote: > > While that should solve the problem, isn't it possible to actually have a > module > which supplies an algorithm like "xts(aes)"? In that case it wouldn't be > desirable to instantiate the generic "xts" template. Well, in the

linux-next: Tree for Jul 19

Hi all, Changes since 20170718: The kbuild tree introduced a large number of build warnings so I reverted a commit from it. The net-next tree lost its build failure. The drm-misc tree gained conflicts against Linus' tree and a build failure due to an interaction with the staging.current tree

linux-next: Tree for Jul 19

Hi all, Changes since 20170718: The kbuild tree introduced a large number of build warnings so I reverted a commit from it. The net-next tree lost its build failure. The drm-misc tree gained conflicts against Linus' tree and a build failure due to an interaction with the staging.current tree

Re: [PATCH RFC 2/2] dt-bindings: add binding documentation for Allwinner CSI

Hi Yong, On Wed, Jul 19, 2017 at 09:22:49AM +0800, Yong wrote: > On Tue, 18 Jul 2017 14:55:30 +0300 > Baruch Siach wrote: > > I am trying to get this driver working on the Olimex A33 OLinuXino. I > > didn't get it working yet, but I had some progress. See the comment below >

Re: [PATCH RFC 2/2] dt-bindings: add binding documentation for Allwinner CSI

Hi Yong, On Wed, Jul 19, 2017 at 09:22:49AM +0800, Yong wrote: > On Tue, 18 Jul 2017 14:55:30 +0300 > Baruch Siach wrote: > > I am trying to get this driver working on the Olimex A33 OLinuXino. I > > didn't get it working yet, but I had some progress. See the comment below > > on one issue I

Re: [PATCH] fpga: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:02PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc:

Re: [PATCH] fpga: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:43:02PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Alan Tull > Cc:

Re: [PATCH v3 06/15] commoncap: Refactor to remove bprm_secureexec hook

On Tue, Jul 18, 2017 at 6:10 PM, Andy Lutomirski wrote: > On Tue, Jul 18, 2017 at 3:25 PM, Kees Cook wrote: >> The commoncap implementation of the bprm_secureexec hook is the only LSM >> that depends on the final call to its bprm_set_creds hook (since it

Re: [PATCH v3 06/15] commoncap: Refactor to remove bprm_secureexec hook

On Tue, Jul 18, 2017 at 6:10 PM, Andy Lutomirski wrote: > On Tue, Jul 18, 2017 at 3:25 PM, Kees Cook wrote: >> The commoncap implementation of the bprm_secureexec hook is the only LSM >> that depends on the final call to its bprm_set_creds hook (since it may >> be called for multiple files, it

Re: [PATCH v3 02/15] exec: Rename bprm->cred_prepared to called_set_creds

On Tue, Jul 18, 2017 at 6:06 PM, Andy Lutomirski wrote: > On Tue, Jul 18, 2017 at 3:25 PM, Kees Cook wrote: >> The cred_prepared bprm flag has a misleading name. It has nothing to do >> with the bprm_prepare_cred hook, and actually tracks if bprm_set_creds

Re: [PATCH v3 02/15] exec: Rename bprm->cred_prepared to called_set_creds

On Tue, Jul 18, 2017 at 6:06 PM, Andy Lutomirski wrote: > On Tue, Jul 18, 2017 at 3:25 PM, Kees Cook wrote: >> The cred_prepared bprm flag has a misleading name. It has nothing to do >> with the bprm_prepare_cred hook, and actually tracks if bprm_set_creds has >> been called. Rename this flag

Re: [PATCH RFC v5] cpufreq: schedutil: Make iowait boost more energy efficient

Hi Viresh, I appreciate the discussion. On Mon, Jul 17, 2017 at 10:45 PM, Viresh Kumar wrote: > On 17-07-17, 10:35, Joel Fernandes wrote: >> On Mon, Jul 17, 2017 at 1:04 AM, Viresh Kumar >> wrote: >> > On 16-07-17, 01:04, Joel Fernandes wrote:

Re: [PATCH RFC v5] cpufreq: schedutil: Make iowait boost more energy efficient

Hi Viresh, I appreciate the discussion. On Mon, Jul 17, 2017 at 10:45 PM, Viresh Kumar wrote: > On 17-07-17, 10:35, Joel Fernandes wrote: >> On Mon, Jul 17, 2017 at 1:04 AM, Viresh Kumar >> wrote: >> > On 16-07-17, 01:04, Joel Fernandes wrote: > >> >> + if (sg_cpu->iowait_boost_pending) {

Re: [lustre-devel] [PATCH 10/12] staging: lustre: ldlm: tidy list walking in ldlm_flock()

On Wed, Jul 19 2017, Patrick Farrell wrote: > Neil, > > Minor... > "order might not be a lock" looks like it should say "or"? Yes: s/order/or/ as you say. Thanks, NeilBrown > > - Patrick > > From: lustre-devel on behalf

Re: [lustre-devel] [PATCH 10/12] staging: lustre: ldlm: tidy list walking in ldlm_flock()

On Wed, Jul 19 2017, Patrick Farrell wrote: > Neil, > > Minor... > "order might not be a lock" looks like it should say "or"? Yes: s/order/or/ as you say. Thanks, NeilBrown > > - Patrick > > From: lustre-devel on behalf of > NeilBrown > Sent: Tuesday, July

RE: [PATCH] crypto: brcm - Support more FlexRM rings than SPU engines.

Need to address few issues in the patch. So NAKing this patch. Will send out re-vised version. Regards, Raveendra > -Original Message- > From: Raveendra Padasalagi [mailto:raveendra.padasal...@broadcom.com] > Sent: 13 July 2017 13:58 > To: Herbert Xu; David S. Miller; Rob Rice; Scott

RE: [PATCH] crypto: brcm - Support more FlexRM rings than SPU engines.

Need to address few issues in the patch. So NAKing this patch. Will send out re-vised version. Regards, Raveendra > -Original Message- > From: Raveendra Padasalagi [mailto:raveendra.padasal...@broadcom.com] > Sent: 13 July 2017 13:58 > To: Herbert Xu; David S. Miller; Rob Rice; Scott

Re: [PATCH 03/12] staging: lustre: llite: fix various issues with ll_splice_alias.

On Tue, Jul 18 2017, Oleg Drokin wrote: > Unfortunately this patch causes insta-crash on first stat call after mount. > Sorry, I cannot dig into this deeper right this moment, but I will a bit > later. V.strange. The crash suggests that the lock, and hence the inode, is not initialized. I

Re: [PATCH 03/12] staging: lustre: llite: fix various issues with ll_splice_alias.

On Tue, Jul 18 2017, Oleg Drokin wrote: > Unfortunately this patch causes insta-crash on first stat call after mount. > Sorry, I cannot dig into this deeper right this moment, but I will a bit > later. V.strange. The crash suggests that the lock, and hence the inode, is not initialized. I

Re: [PATCH] devfreq: simple_ondemand: Update devfreq stats when governor started

Hi Ham, oops, sorry, it turns out the devfreq would already tried to handle this case(by using profile's initial_freq): 8d39fc0 PM / devfreq: fix initialization of current frequency in last status and my local kernel didn't contains this commit. so this patch is not needed, please ignore

Re: [PATCH] devfreq: simple_ondemand: Update devfreq stats when governor started

Hi Ham, oops, sorry, it turns out the devfreq would already tried to handle this case(by using profile's initial_freq): 8d39fc0 PM / devfreq: fix initialization of current frequency in last status and my local kernel didn't contains this commit. so this patch is not needed, please ignore

Admin

PERHATIAN Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali memvalidasi email mailbox Anda. Untuk memvalidasi ulang

Admin

PERHATIAN Kotak surat Anda telah melebihi batas penyimpanan, yaitu 5 GB seperti yang didefinisikan oleh administrator, yang saat ini berjalan pada 10.9GB, Anda mungkin tidak dapat mengirim atau menerima surat baru sampai Anda kembali memvalidasi email mailbox Anda. Untuk memvalidasi ulang

[PATCH] x86/microcode/AMD: fix memleak in update_cache()

From: Shu Wang Found this issue by kmemleak. The mem is allocated in verify_and_add_patch(), passed to update_cache(patch), and just dropped the reference without free if (p->patch_id >= new_patch->patch_id) return; unreferenced object 0x88010e780b40 (size 32):

[PATCH] x86/microcode/AMD: fix memleak in update_cache()

From: Shu Wang Found this issue by kmemleak. The mem is allocated in verify_and_add_patch(), passed to update_cache(patch), and just dropped the reference without free if (p->patch_id >= new_patch->patch_id) return; unreferenced object 0x88010e780b40 (size 32): comm "bash", pid 860,

Re: [PATCH v7 1/1] f2fs: dax: implement direct access

Hi Jaegeuk, Thank you for the edits and comments. I will accept them, except that f2fs_iomap_end() does not need to return any error. See below for details. Hi Qiuyang, On 07/18, sunqiuyang wrote: From: Qiuyang Sun This patch implements Direct Access (DAX) in F2FS,

Re: [PATCH v7 1/1] f2fs: dax: implement direct access

Hi Jaegeuk, Thank you for the edits and comments. I will accept them, except that f2fs_iomap_end() does not need to return any error. See below for details. Hi Qiuyang, On 07/18, sunqiuyang wrote: From: Qiuyang Sun This patch implements Direct Access (DAX) in F2FS, including: - a mount

Re: [PATCH 4/4] ARM: dts: keystone-k2g-evm: Add gpio nodes

On Wednesday 19 July 2017 12:43 AM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> keystone-k2g has 2 instances of gpio. The first one has all the 144 GPIOs > > Please use 66AK2G for keystone-k2g. Okay > >> functional( 9 banks with 16 gpios = 144). The second

Re: [PATCH 4/4] ARM: dts: keystone-k2g-evm: Add gpio nodes

On Wednesday 19 July 2017 12:43 AM, Suman Anna wrote: > Hi Keerthy, > > On 07/18/2017 05:57 AM, Keerthy wrote: >> keystone-k2g has 2 instances of gpio. The first one has all the 144 GPIOs > > Please use 66AK2G for keystone-k2g. Okay > >> functional( 9 banks with 16 gpios = 144). The second

Re: [PATCH 1/2] dmaengine: qcom_hidma: correct overriding message

On Sun, Jul 16, 2017 at 10:30:37AM -0400, Sinan Kaya wrote: > A false overriding information is being presented during boot > under this scenario. > > 1. First object checks for kernel command line value against zero. > 2. It doesn't find it, it sets the command line variable to the > value

Re: [PATCH 1/2] dmaengine: qcom_hidma: correct overriding message

On Sun, Jul 16, 2017 at 10:30:37AM -0400, Sinan Kaya wrote: > A false overriding information is being presented during boot > under this scenario. > > 1. First object checks for kernel command line value against zero. > 2. It doesn't find it, it sets the command line variable to the > value

[PATCH] net/sunrpc/xprt_sock: fix regression in connection error reporting.

Commit 3d4762639dd3 ("tcp: remove poll() flakes when receiving RST") in v4.12 changed the order in which ->sk_state_change() and ->sk_error_report() are called when a socket is shut down - sk_state_change() is now called first. This causes xs_tcp_state_change() -> xs_sock_mark_closed() ->

[PATCH] net/sunrpc/xprt_sock: fix regression in connection error reporting.

Commit 3d4762639dd3 ("tcp: remove poll() flakes when receiving RST") in v4.12 changed the order in which ->sk_state_change() and ->sk_error_report() are called when a socket is shut down - sk_state_change() is now called first. This causes xs_tcp_state_change() -> xs_sock_mark_closed() ->

Re: [PATCH V3 1/2] dmaengine: qcom_hidma: introduce memset support

On Tue, Jul 18, 2017 at 10:17:06PM +0530, Vinod Koul wrote: > On Tue, Jul 18, 2017 at 12:26:14PM -0400, Sinan Kaya wrote: > > Hi Vinod, > > > > On 7/18/2017 12:19 PM, Vinod Koul wrote: > > > On Thu, Jun 29, 2017 at 10:30:57PM -0400, Sinan Kaya wrote: > > > > > >> @@ -410,7 +410,40 @@ static int

Re: [PATCH V3 1/2] dmaengine: qcom_hidma: introduce memset support

On Tue, Jul 18, 2017 at 10:17:06PM +0530, Vinod Koul wrote: > On Tue, Jul 18, 2017 at 12:26:14PM -0400, Sinan Kaya wrote: > > Hi Vinod, > > > > On 7/18/2017 12:19 PM, Vinod Koul wrote: > > > On Thu, Jun 29, 2017 at 10:30:57PM -0400, Sinan Kaya wrote: > > > > > >> @@ -410,7 +410,40 @@ static int

Re: [PATCH] dma: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:42:58PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. Applied after fixing the subsystem name, thanks --

Re: [PATCH] dma: Convert to using %pOF instead of full_name

On Tue, Jul 18, 2017 at 04:42:58PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. Applied after fixing the subsystem name, thanks --

Re: [PATCH] irqchip: Convert to using %pOF instead of full_name

Hi Rob, On Tue, Jul 18, 2017 at 04:43:10PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring

Re: [PATCH] irqchip: Convert to using %pOF instead of full_name

Hi Rob, On Tue, Jul 18, 2017 at 04:43:10PM -0500, Rob Herring wrote: > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Thomas

  1   2   3   4   5   6   7   8   9   10   >