Re: [PATCH v4 1/2] x86/unwind: add ORC unwinder

On Tue, Aug 8, 2017 at 11:58 AM, Josh Poimboeuf wrote: > > Take for example the lock_is_held_type() function. In vmlinux, it has > the following instruction: > > callq *0x85a94880 (pv_irq_ops.save_fl) > > At runtime, that instruction is patched and replaced with a

Re: [PATCH v4 1/2] x86/unwind: add ORC unwinder

On Tue, Aug 8, 2017 at 11:58 AM, Josh Poimboeuf wrote: > > Take for example the lock_is_held_type() function. In vmlinux, it has > the following instruction: > > callq *0x85a94880 (pv_irq_ops.save_fl) > > At runtime, that instruction is patched and replaced with a fast inline > version

Re: [RFC][PATCH] mm/slub.c: Allow poisoning to use the fast path

On Tue, Aug 8, 2017 at 8:01 AM, Christopher Lameter wrote: > > On Mon, 7 Aug 2017, Kees Cook wrote: >> >> To clarify, this is desirable to kill exploitation of >> exposure-after-free flaws and some classes of use-after-free flaws, >> since the contents will have be wiped out after

Re: [RFC][PATCH] mm/slub.c: Allow poisoning to use the fast path

On Tue, Aug 8, 2017 at 8:01 AM, Christopher Lameter wrote: > > On Mon, 7 Aug 2017, Kees Cook wrote: >> >> To clarify, this is desirable to kill exploitation of >> exposure-after-free flaws and some classes of use-after-free flaws, >> since the contents will have be wiped out after a free.

RE: [PATCH v6 1/3] mfd: Add new mfd device TPS68470

Thanks Lee. Sorry for the noise, as some keystrokes sent out the empty response earlier. Raj > -Original Message- > From: Mani, Rajmohan > Sent: Tuesday, August 08, 2017 11:58 AM > To: 'Lee Jones' > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org;

RE: [PATCH v6 1/3] mfd: Add new mfd device TPS68470

Thanks Lee. Sorry for the noise, as some keystrokes sent out the empty response earlier. Raj > -Original Message- > From: Mani, Rajmohan > Sent: Tuesday, August 08, 2017 11:58 AM > To: 'Lee Jones' > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org; linux- >

Re: [PATCH v4 1/2] x86/unwind: add ORC unwinder

On Fri, Jul 28, 2017 at 10:54:37PM -0500, Josh Poimboeuf wrote: > On Fri, Jul 28, 2017 at 07:59:12PM +, Levin, Alexander (Sasha Levin) > wrote: > > On Fri, Jul 28, 2017 at 01:57:20PM -0500, Josh Poimboeuf wrote: > > >Thanks, that's much better. I'm relieved the unwinder didn't screw that > >

Re: [PATCH v4 1/2] x86/unwind: add ORC unwinder

On Fri, Jul 28, 2017 at 10:54:37PM -0500, Josh Poimboeuf wrote: > On Fri, Jul 28, 2017 at 07:59:12PM +, Levin, Alexander (Sasha Levin) > wrote: > > On Fri, Jul 28, 2017 at 01:57:20PM -0500, Josh Poimboeuf wrote: > > >Thanks, that's much better. I'm relieved the unwinder didn't screw that > >

RE: [PATCH v6 1/3] mfd: Add new mfd device TPS68470

> -Original Message- > From: Lee Jones [mailto:lee.jo...@linaro.org] > Sent: Tuesday, August 08, 2017 12:40 AM > To: Mani, Rajmohan > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org; linux- > a...@vger.kernel.org; Linus Walleij

RE: [PATCH v6 1/3] mfd: Add new mfd device TPS68470

> -Original Message- > From: Lee Jones [mailto:lee.jo...@linaro.org] > Sent: Tuesday, August 08, 2017 12:40 AM > To: Mani, Rajmohan > Cc: linux-kernel@vger.kernel.org; linux-g...@vger.kernel.org; linux- > a...@vger.kernel.org; Linus Walleij ; Alexandre > Courbot ; Rafael J. Wysocki ;

Re: [PATCH 13/18] power: supply: bq24190_charger: Export 5V boost converter as regulator

On Tue, Aug 8, 2017 at 2:00 AM, Hans de Goede wrote: > Hi, > > On 08-08-17 10:39, Liam Breck wrote: >> >> Hi Hans, >> >> On Sun, Aug 6, 2017 at 5:35 AM, Hans de Goede wrote: >>> >>> Register the 5V boost converter as a regulator named >>>

Re: [PATCH] rcu: Skip additional checks if rcu_cpu_stall_suppress is set

On 08/08/2017 11:32 PM, Paul E. McKenney wrote: On Tue, Aug 08, 2017 at 10:50:26PM +0530, Neeraj Upadhyay wrote: If rcu_kick_kthreads is set, and gp is in progress, check_cpu_stall() does checks to figure out whether jiffies is past rsp->jiffies_stall, doing ordered accesses to avoid any

Re: [PATCH 13/18] power: supply: bq24190_charger: Export 5V boost converter as regulator

On Tue, Aug 8, 2017 at 2:00 AM, Hans de Goede wrote: > Hi, > > On 08-08-17 10:39, Liam Breck wrote: >> >> Hi Hans, >> >> On Sun, Aug 6, 2017 at 5:35 AM, Hans de Goede wrote: >>> >>> Register the 5V boost converter as a regulator named >>> "regulator-bq24190-usb-vbus". Note the name includes

Re: [PATCH] rcu: Skip additional checks if rcu_cpu_stall_suppress is set

On 08/08/2017 11:32 PM, Paul E. McKenney wrote: On Tue, Aug 08, 2017 at 10:50:26PM +0530, Neeraj Upadhyay wrote: If rcu_kick_kthreads is set, and gp is in progress, check_cpu_stall() does checks to figure out whether jiffies is past rsp->jiffies_stall, doing ordered accesses to avoid any

Re: [PATCH] Add /proc/pid/smaps_rollup

On Tue, Aug 08, 2017 at 11:51:40AM -0700, Daniel Colascione wrote: > On Tue, Aug 08 2017, Greg KH wrote: > > On Tue, Aug 08, 2017 at 11:22:55AM -0700, Daniel Colascione wrote: > >> Adding more people. > >> > >> On Tue, Aug 08 2017, Daniel Colascione wrote: > >> > /proc/pid/smaps_rollup is a new

Re: [PATCH] Add /proc/pid/smaps_rollup

On Tue, Aug 08, 2017 at 11:51:40AM -0700, Daniel Colascione wrote: > On Tue, Aug 08 2017, Greg KH wrote: > > On Tue, Aug 08, 2017 at 11:22:55AM -0700, Daniel Colascione wrote: > >> Adding more people. > >> > >> On Tue, Aug 08 2017, Daniel Colascione wrote: > >> > /proc/pid/smaps_rollup is a new

Re: [PATCH] Add /proc/pid/smaps_rollup

On Tue, Aug 08 2017, Greg KH wrote: > On Tue, Aug 08, 2017 at 11:22:55AM -0700, Daniel Colascione wrote: >> Adding more people. >> >> On Tue, Aug 08 2017, Daniel Colascione wrote: >> > /proc/pid/smaps_rollup is a new proc file that improves the >> > performance of user programs that determine

Re: [PATCH] Add /proc/pid/smaps_rollup

On Tue, Aug 08 2017, Greg KH wrote: > On Tue, Aug 08, 2017 at 11:22:55AM -0700, Daniel Colascione wrote: >> Adding more people. >> >> On Tue, Aug 08 2017, Daniel Colascione wrote: >> > /proc/pid/smaps_rollup is a new proc file that improves the >> > performance of user programs that determine

Re: [PATCH] sctp: fully initialize the IPv6 address in sctp_v6_to_addr()

On Tue, Jul 18, 2017 at 04:55:57PM +0200, Alexander Potapenko wrote: > KMSAN reported use of uninitialized sctp_addr->v4.sin_addr.s_addr and > sctp_addr->v6.sin6_scope_id in sctp_v6_cmp_addr() (see below). > Make sure all fields of an IPv6 address are initialized, which > guarantees that the IPv4

Re: [PATCH] sctp: fully initialize the IPv6 address in sctp_v6_to_addr()

On Tue, Jul 18, 2017 at 04:55:57PM +0200, Alexander Potapenko wrote: > KMSAN reported use of uninitialized sctp_addr->v4.sin_addr.s_addr and > sctp_addr->v6.sin6_scope_id in sctp_v6_cmp_addr() (see below). > Make sure all fields of an IPv6 address are initialized, which > guarantees that the IPv4

Re: [PATCH v2 0/2] mm,fork,security: introduce MADV_WIPEONFORK

On Tue, 2017-08-08 at 09:52 -0700, Matthew Wilcox wrote: > On Tue, Aug 08, 2017 at 11:46:08AM -0400, Rik van Riel wrote: > > On Tue, 2017-08-08 at 08:19 -0700, Mike Kravetz wrote: > > > If the use case is fairly specific, then perhaps it makes sense > > > to > > > make MADV_WIPEONFORK not

Re: [PATCH v2 0/2] mm,fork,security: introduce MADV_WIPEONFORK

On Tue, 2017-08-08 at 09:52 -0700, Matthew Wilcox wrote: > On Tue, Aug 08, 2017 at 11:46:08AM -0400, Rik van Riel wrote: > > On Tue, 2017-08-08 at 08:19 -0700, Mike Kravetz wrote: > > > If the use case is fairly specific, then perhaps it makes sense > > > to > > > make MADV_WIPEONFORK not

Re: [PATCH] Add /proc/pid/smaps_rollup

On Tue, Aug 08, 2017 at 11:22:55AM -0700, Daniel Colascione wrote: > Adding more people. > > On Tue, Aug 08 2017, Daniel Colascione wrote: > > /proc/pid/smaps_rollup is a new proc file that improves the > > performance of user programs that determine aggregate memory > > statistics (e.g., total

Re: [PATCH] Add /proc/pid/smaps_rollup

On Tue, Aug 08, 2017 at 11:22:55AM -0700, Daniel Colascione wrote: > Adding more people. > > On Tue, Aug 08 2017, Daniel Colascione wrote: > > /proc/pid/smaps_rollup is a new proc file that improves the > > performance of user programs that determine aggregate memory > > statistics (e.g., total

Re: [PATCH] KVM: arm64: add esr_el2 and far_el2 to sysreg

Hi James, On 2017/8/9 0:27, James Morse wrote: > Hi gengdongjiu, > > On 07/08/17 18:43, gengdongjiu wrote: >> Another question, For the SEI, I want to also use SIGBUS both for the KVM >> user and non-kvm user, >> if SEA and SEI Error all use the SIGBUS to notify user space(Qemu), > >

Re: [PATCH] KVM: arm64: add esr_el2 and far_el2 to sysreg

Hi James, On 2017/8/9 0:27, James Morse wrote: > Hi gengdongjiu, > > On 07/08/17 18:43, gengdongjiu wrote: >> Another question, For the SEI, I want to also use SIGBUS both for the KVM >> user and non-kvm user, >> if SEA and SEI Error all use the SIGBUS to notify user space(Qemu), > >

Re: [PATCH 00/35] constify net usb_device_id

Arvind Yadav writes: > usb_device_id are not supposed to change at runtime. All functions > working with usb_device_id provided by work with > const usb_device_id. So mark the non-const structs as const. [...] > [PATCH 16/35] wireless: ath: ar5523: constify

Re: [PATCH 00/35] constify net usb_device_id

Arvind Yadav writes: > usb_device_id are not supposed to change at runtime. All functions > working with usb_device_id provided by work with > const usb_device_id. So mark the non-const structs as const. [...] > [PATCH 16/35] wireless: ath: ar5523: constify usb_device_id > [PATCH 17/35]

Re: blk-mq breaks suspend even with runtime PM patch

On 08/08/2017 12:33 PM, Mike Galbraith wrote: > On Tue, 2017-08-08 at 18:50 +0200, Mike Galbraith wrote: >> On Tue, 2017-08-08 at 09:44 -0700, Greg KH wrote: >>> >>> Should these go back farther than 4.12? Looks like they apply cleanly >>> to 4.9, didn't look older than that... >> >> I met

Re: blk-mq breaks suspend even with runtime PM patch

On 08/08/2017 12:33 PM, Mike Galbraith wrote: > On Tue, 2017-08-08 at 18:50 +0200, Mike Galbraith wrote: >> On Tue, 2017-08-08 at 09:44 -0700, Greg KH wrote: >>> >>> Should these go back farther than 4.12? Looks like they apply cleanly >>> to 4.9, didn't look older than that... >> >> I met

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

Hi Dou and Baoquan, On 08/03/2017 11:28 PM, Dou Liyang wrote: > > > At 08/04/2017 10:55 AM, Baoquan He wrote: >> On 08/04/17 at 10:42am, Dou Liyang wrote: >>> Hi Baoquan, >>> >>> At 08/04/2017 10:00 AM, Baoquan He wrote: On 08/04/17 at 09:37am, Dou Liyang wrote: > Hi Chao,Baoquan >

Re: [PATCH] x86/boot/KASLR: Extend movable_node option for KASLR

Hi Dou and Baoquan, On 08/03/2017 11:28 PM, Dou Liyang wrote: > > > At 08/04/2017 10:55 AM, Baoquan He wrote: >> On 08/04/17 at 10:42am, Dou Liyang wrote: >>> Hi Baoquan, >>> >>> At 08/04/2017 10:00 AM, Baoquan He wrote: On 08/04/17 at 09:37am, Dou Liyang wrote: > Hi Chao,Baoquan >

Re: [PATCH] lib: Add test module for CONFIG_DEBUG_VIRTUAL

On Tue, Aug 08, 2017 at 11:04:11AM -0700, Florian Fainelli wrote: > On 08/08/2017 10:57 AM, Luis R. Rodriguez wrote: > > On Tue, Aug 08, 2017 at 09:40:26AM -0700, Florian Fainelli wrote: > >> Add a test module that allows testing that CONFIG_DEBUG_VIRTUAL works > >> correctly, at least that it can

Re: [PATCH] lib: Add test module for CONFIG_DEBUG_VIRTUAL

On Tue, Aug 08, 2017 at 11:04:11AM -0700, Florian Fainelli wrote: > On 08/08/2017 10:57 AM, Luis R. Rodriguez wrote: > > On Tue, Aug 08, 2017 at 09:40:26AM -0700, Florian Fainelli wrote: > >> Add a test module that allows testing that CONFIG_DEBUG_VIRTUAL works > >> correctly, at least that it can

Re: [PATCH 4/4] scripts/move_maintainer_sections.bash

On Mon, Aug 7, 2017 at 10:04 AM, Joe Perches wrote: > On Sat, 2017-08-05 at 18:45 -0700, Joe Perches wrote: >> Move MAINTAINERS into a separate directory and reorder it. >> Separate various blocks of MAINTAINER sections into separate files. > > Hey Linus. > > If/when you try

Re: blk-mq breaks suspend even with runtime PM patch

On Tue, 2017-08-08 at 18:50 +0200, Mike Galbraith wrote: > On Tue, 2017-08-08 at 09:44 -0700, Greg KH wrote: > > > > Should these go back farther than 4.12? Looks like they apply cleanly > > to 4.9, didn't look older than that... > > I met prerequisites at 4.11... FWIW, I took/modified

Re: [PATCH 4/4] scripts/move_maintainer_sections.bash

On Mon, Aug 7, 2017 at 10:04 AM, Joe Perches wrote: > On Sat, 2017-08-05 at 18:45 -0700, Joe Perches wrote: >> Move MAINTAINERS into a separate directory and reorder it. >> Separate various blocks of MAINTAINER sections into separate files. > > Hey Linus. > > If/when you try this out, do please

Re: blk-mq breaks suspend even with runtime PM patch

On Tue, 2017-08-08 at 18:50 +0200, Mike Galbraith wrote: > On Tue, 2017-08-08 at 09:44 -0700, Greg KH wrote: > > > > Should these go back farther than 4.12? Looks like they apply cleanly > > to 4.9, didn't look older than that... > > I met prerequisites at 4.11... FWIW, I took/modified

[RFC v2 01/12] clk: qcom: flag for 64 bit CONFIG_CTL

Some of the Alpha PLL’s (like Spark, Brammo PLL) do not have CONFIG_CTL_U register. This patch adds the flag for PLL’s which have CONFIG_CTL_U register and checks the same while doing PLL initial configuration. Signed-off-by: Abhishek Sahu ---

[RFC v2 01/12] clk: qcom: flag for 64 bit CONFIG_CTL

Some of the Alpha PLL’s (like Spark, Brammo PLL) do not have CONFIG_CTL_U register. This patch adds the flag for PLL’s which have CONFIG_CTL_U register and checks the same while doing PLL initial configuration. Signed-off-by: Abhishek Sahu --- drivers/clk/qcom/clk-alpha-pll.c | 5 -

[RFC v2 04/12] clk: qcom: fix 16 bit alpha support calculation

The alpha value calculation function has been written for 40 bit alpha which is not coming properly for 16 bit 1. Alpha value is being calculated on the basis of ALPHA_BITWIDTH to make the computation easy for 40 bit alpha. After calculating the 32 bit alpha, It is being converted to 40

[RFC v2 04/12] clk: qcom: fix 16 bit alpha support calculation

The alpha value calculation function has been written for 40 bit alpha which is not coming properly for 16 bit 1. Alpha value is being calculated on the basis of ALPHA_BITWIDTH to make the computation easy for 40 bit alpha. After calculating the 32 bit alpha, It is being converted to 40

Re: Switching to MQ by default may generate some bug reports

On Tue, Aug 08, 2017 at 07:33:37PM +0200, Paolo Valente wrote: > > Differently from bfq-sq, setting slice_idle to 0 doesn't provide any > > benefit, which lets me suspect that there is some other issue in > > blk-mq (only a suspect). I think I may have already understood how to > > guarantee that

Re: Switching to MQ by default may generate some bug reports

On Tue, Aug 08, 2017 at 07:33:37PM +0200, Paolo Valente wrote: > > Differently from bfq-sq, setting slice_idle to 0 doesn't provide any > > benefit, which lets me suspect that there is some other issue in > > blk-mq (only a suspect). I think I may have already understood how to > > guarantee that

[RFC v2 08/12] clk: qcom: support for Brammo PLL

1. Brammo PLL does not allow configuration of VCO 2. Supports the dynamic update in which the frequency can be changed dynamically without turning off the PLL 3. The register offsets are different from normal Alpha PLL Signed-off-by: Abhishek Sahu ---

[RFC v2 08/12] clk: qcom: support for Brammo PLL

1. Brammo PLL does not allow configuration of VCO 2. Supports the dynamic update in which the frequency can be changed dynamically without turning off the PLL 3. The register offsets are different from normal Alpha PLL Signed-off-by: Abhishek Sahu --- drivers/clk/qcom/clk-alpha-pll.c | 12

[RFC v2 07/12] clk: qcom: support for Huayra PLL

Following are the major differences in Huayra PLL 1. PLL Alpha Value is 16 bits 2. Depending on alpha_mode, the pll_alpha_val can be treated as M/N value or as a two’s compliment number. 3. Huayra PLL supports PLL dynamic programming. User can change L_VAL, without having to go through the

[RFC v2 07/12] clk: qcom: support for Huayra PLL

Following are the major differences in Huayra PLL 1. PLL Alpha Value is 16 bits 2. Depending on alpha_mode, the pll_alpha_val can be treated as M/N value or as a two’s compliment number. 3. Huayra PLL supports PLL dynamic programming. User can change L_VAL, without having to go through the

Re: sysctl, argument parsing, possible bug

I make another test with kernel 4.9.32-15.41 sysctl procps version 3.2.8 sysctl net.ipv4.conf.eth0.100.forwarding error: "net.ipv4.conf.eth0.100.forwarding" is an unknown key so I install busybox : BusyBox v1.19.3 busybox sysctl net.ipv4.conf.eth0.100.forwarding

Re: sysctl, argument parsing, possible bug

I make another test with kernel 4.9.32-15.41 sysctl procps version 3.2.8 sysctl net.ipv4.conf.eth0.100.forwarding error: "net.ipv4.conf.eth0.100.forwarding" is an unknown key so I install busybox : BusyBox v1.19.3 busybox sysctl net.ipv4.conf.eth0.100.forwarding

Re: [PATCH] NTB: ntb_tool: Add full multi-port NTB API support

On 08/08/17 04:11 AM, Serge Semin wrote: > +static ssize_t tool_db_event_write(struct file *filep, > +const char __user *ubuf, > +size_t size, loff_t *offp) > +{ > + struct tool_ctx *tc = filep->private_data; > + u64 val; >

Re: [PATCH] NTB: ntb_tool: Add full multi-port NTB API support

On 08/08/17 04:11 AM, Serge Semin wrote: > +static ssize_t tool_db_event_write(struct file *filep, > +const char __user *ubuf, > +size_t size, loff_t *offp) > +{ > + struct tool_ctx *tc = filep->private_data; > + u64 val; >

RE: [PATCH RFC] fpga: add FPGA Bus device framework

> On Thu, Aug 3, 2017 at 2:53 AM, Wu Hao wrote: > > On Wed, Aug 02, 2017 at 04:16:32PM -0500, Alan Tull wrote: > >> On Wed, Aug 2, 2017 at 7:19 AM, Wu Hao wrote: > >> > This patch is a RFC patch which replaces the patch[1] which > >> > creates 'fpga-dev' class

RE: [PATCH RFC] fpga: add FPGA Bus device framework

> On Thu, Aug 3, 2017 at 2:53 AM, Wu Hao wrote: > > On Wed, Aug 02, 2017 at 04:16:32PM -0500, Alan Tull wrote: > >> On Wed, Aug 2, 2017 at 7:19 AM, Wu Hao wrote: > >> > This patch is a RFC patch which replaces the patch[1] which > >> > creates 'fpga-dev' class as container device. It introduces

Re: [PATCH] mfd: exynos-lpass: Handle return value of clk_prepare_enable

On Tue, Aug 08, 2017 at 05:20:55PM +0530, Arvind Yadav wrote: > clk_prepare_enable() can fail here and we must check its return value. > we must call pm_runtime_disable() and pm_runtime_set_suspended(), > If exynos_lpass_probe is not successful. > > Signed-off-by: Arvind Yadav

Re: [PATCH] mfd: exynos-lpass: Handle return value of clk_prepare_enable

On Tue, Aug 08, 2017 at 05:20:55PM +0530, Arvind Yadav wrote: > clk_prepare_enable() can fail here and we must check its return value. > we must call pm_runtime_disable() and pm_runtime_set_suspended(), > If exynos_lpass_probe is not successful. > > Signed-off-by: Arvind Yadav This is not a

[RFC v2 11/12] clk: qcom: add read-only divider operations

Some of the divider settings are preconfigured and should not be changed by the clock framework during frequency change. This patch adds the read-only divider operation for QCOM dividers which is equivalent to generic divider operations in 'commit 79c6ab509558 ("clk: divider: add

[RFC v2 11/12] clk: qcom: add read-only divider operations

Some of the divider settings are preconfigured and should not be changed by the clock framework during frequency change. This patch adds the read-only divider operation for QCOM dividers which is equivalent to generic divider operations in 'commit 79c6ab509558 ("clk: divider: add

[RFC v2 05/12] clk: qcom: support for dynamic updating the PLL

Some of the Alpha PLL’s support dynamic update in which the frequency can be changed dynamically without turning off the PLL. This dynamic update requires the following sequence 1. Write the desired values to pll_l_val and pll_alpha_val 2. Toggle pll_latch_input from low to high 3. Wait for

[RFC v2 05/12] clk: qcom: support for dynamic updating the PLL

Some of the Alpha PLL’s support dynamic update in which the frequency can be changed dynamically without turning off the PLL. This dynamic update requires the following sequence 1. Write the desired values to pll_l_val and pll_alpha_val 2. Toggle pll_latch_input from low to high 3. Wait for

[RFC v2 12/12] clk: qcom: add parent map for regmap mux

Currently the driver assumes the register configuration value is identical to its index in the parent map. This patch adds the parent map field in regmap mux clock node which contains the mapping of parent index with actual register configuration value. If regmap node contains this parent map then

[RFC v2 12/12] clk: qcom: add parent map for regmap mux

Currently the driver assumes the register configuration value is identical to its index in the parent map. This patch adds the parent map field in regmap mux clock node which contains the mapping of parent index with actual register configuration value. If regmap node contains this parent map then

[RFC v2 10/12] clk: qcom: add read-only alpha pll post divider operations

Some of the divider settings are preconfigured and should not be changed by the clock framework during frequency change. This patch adds the read-only divider operation for QCOM alpha pll post divider which is equivalent to generic divider operations in 'commit 79c6ab509558 ("clk: divider: add

[RFC v2 09/12] clk: qcom: support for 2 bit PLL post divider

Current PLL driver only supports 4 bit PLL post divider so modified the PLL divider operations to support 2 bit PLL post divider. Signed-off-by: Abhishek Sahu --- drivers/clk/qcom/clk-alpha-pll.c | 20 1 file changed, 16 insertions(+), 4 deletions(-)

[RFC v2 10/12] clk: qcom: add read-only alpha pll post divider operations

Some of the divider settings are preconfigured and should not be changed by the clock framework during frequency change. This patch adds the read-only divider operation for QCOM alpha pll post divider which is equivalent to generic divider operations in 'commit 79c6ab509558 ("clk: divider: add

[RFC v2 09/12] clk: qcom: support for 2 bit PLL post divider

Current PLL driver only supports 4 bit PLL post divider so modified the PLL divider operations to support 2 bit PLL post divider. Signed-off-by: Abhishek Sahu --- drivers/clk/qcom/clk-alpha-pll.c | 20 1 file changed, 16 insertions(+), 4 deletions(-) diff --git

[RFC v2 06/12] clk: qcom: add flag for VCO operation

Some of the Alpha PLL’s does not have VCO configuration so this patch adds the flag and does not perform VCO operation if this flag is set. Signed-off-by: Abhishek Sahu --- drivers/clk/qcom/clk-alpha-pll.c | 19 +++ drivers/clk/qcom/clk-alpha-pll.h | 1 +

[RFC v2 06/12] clk: qcom: add flag for VCO operation

Some of the Alpha PLL’s does not have VCO configuration so this patch adds the flag and does not perform VCO operation if this flag is set. Signed-off-by: Abhishek Sahu --- drivers/clk/qcom/clk-alpha-pll.c | 19 +++ drivers/clk/qcom/clk-alpha-pll.h | 1 + 2 files changed, 12

Re: [PATCH 3/3] ANDROID: binder: fix proc->tsk check.

On Tue, Aug 8, 2017 at 11:08 AM, Greg KH wrote: > On Tue, Aug 08, 2017 at 10:34:47AM -0700, John Stultz wrote: >> On Fri, Jul 28, 2017 at 4:56 AM, Martijn Coenen wrote: >> > Commit c4ea41ba195d ("binder: use group leader instead of open thread")' >>

Re: [PATCH 3/3] ANDROID: binder: fix proc->tsk check.

On Tue, Aug 8, 2017 at 11:08 AM, Greg KH wrote: > On Tue, Aug 08, 2017 at 10:34:47AM -0700, John Stultz wrote: >> On Fri, Jul 28, 2017 at 4:56 AM, Martijn Coenen wrote: >> > Commit c4ea41ba195d ("binder: use group leader instead of open thread")' >> > was incomplete and didn't update a check in

[RFC v2 03/12] clk: qcom: use offset from alpha pll node

Alpha PLL is a generic name used for Qualcomm PLL’s which uses L and Alpha values for configuring the integer and fractional part. Qualcomm SoC’s use different types of Alpha PLL’s for which basic software configuration part is common. These PLL’s will have same basic registers like PLL_MODE,

[RFC v2 02/12] clk: qcom: support for alpha mode configuration

The current configuration does not fully configure PLL alpha mode and values so this patch 1. Configures PLL_ALPHA_VAL_U for PLL which supports 40 bit alpha. 2. Adds alpha enable and alpha mode configuration support. Signed-off-by: Abhishek Sahu ---

[RFC v2 03/12] clk: qcom: use offset from alpha pll node

Alpha PLL is a generic name used for Qualcomm PLL’s which uses L and Alpha values for configuring the integer and fractional part. Qualcomm SoC’s use different types of Alpha PLL’s for which basic software configuration part is common. These PLL’s will have same basic registers like PLL_MODE,

[RFC v2 02/12] clk: qcom: support for alpha mode configuration

The current configuration does not fully configure PLL alpha mode and values so this patch 1. Configures PLL_ALPHA_VAL_U for PLL which supports 40 bit alpha. 2. Adds alpha enable and alpha mode configuration support. Signed-off-by: Abhishek Sahu --- drivers/clk/qcom/clk-alpha-pll.c | 5 +

[RFC v2 00/12] Misc patches for QCOM clocks

* v2: 1. Discussion is going on with HW team to fix the offset issue in next chip version so removed the RCG patch 2. Made “fix 16 bit alpha support calculation” generic to support all cases. 3. Clubbed the [1] and Patch [2] for "support for dynamic updating the PLL" a. The

[RFC v2 00/12] Misc patches for QCOM clocks

* v2: 1. Discussion is going on with HW team to fix the offset issue in next chip version so removed the RCG patch 2. Made “fix 16 bit alpha support calculation” generic to support all cases. 3. Clubbed the [1] and Patch [2] for "support for dynamic updating the PLL" a. The

Re: [PATCH] NTB: ntb_tool: Add full multi-port NTB API support

On 08/08/17 04:11 AM, Serge Semin wrote: > NTB API has been updated to support multi-port devices like IDT > 89HPESx series or Microsemi Switchtec. Message registers > functionality has also been added to new API. In order to keep > the new hardware and corresponding capabilities well tested,

Re: [PATCH] NTB: ntb_tool: Add full multi-port NTB API support

On 08/08/17 04:11 AM, Serge Semin wrote: > NTB API has been updated to support multi-port devices like IDT > 89HPESx series or Microsemi Switchtec. Message registers > functionality has also been added to new API. In order to keep > the new hardware and corresponding capabilities well tested,

Re: [PATCH] Add /proc/pid/smaps_rollup

Adding more people. On Tue, Aug 08 2017, Daniel Colascione wrote: > /proc/pid/smaps_rollup is a new proc file that improves the > performance of user programs that determine aggregate memory > statistics (e.g., total PSS) of a process. > > Anroid regularly "samples" the memory usage of various

Re: [PATCH] Add /proc/pid/smaps_rollup

Adding more people. On Tue, Aug 08 2017, Daniel Colascione wrote: > /proc/pid/smaps_rollup is a new proc file that improves the > performance of user programs that determine aggregate memory > statistics (e.g., total PSS) of a process. > > Anroid regularly "samples" the memory usage of various

Re: [PATCH] IB/hfi1: fix spelling mistake: "Maximim" -> "Maximum"

On 8/5/2017 9:11 AM, Colin King wrote: From: Colin Ian King Trivial fix to spelling mistake in pr_warn_ratelimited warning message Signed-off-by: Colin Ian King --- drivers/infiniband/hw/hfi1/mad.c | 2 +- 1 file changed, 1 insertion(+),

Re: [PATCH] IB/hfi1: fix spelling mistake: "Maximim" -> "Maximum"

On 8/5/2017 9:11 AM, Colin King wrote: From: Colin Ian King Trivial fix to spelling mistake in pr_warn_ratelimited warning message Signed-off-by: Colin Ian King --- drivers/infiniband/hw/hfi1/mad.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: kexec_file: use crypto_free_shash to free memory

Pan Bian writes: > In function kexec_calculate_store_digests(), kfree() is used to free > memory allocated by crypto_alloc_shash(). It is better to use function > crypto_free_shash(), which also zeroizes the memory to be freed. Why is it important to zero memory? There is

Re: kexec_file: use crypto_free_shash to free memory

Pan Bian writes: > In function kexec_calculate_store_digests(), kfree() is used to free > memory allocated by crypto_alloc_shash(). It is better to use function > crypto_free_shash(), which also zeroizes the memory to be freed. Why is it important to zero memory? There is nothing sensitive

Re: [PATCH] block: Fix warning when I/O elevator is changed as request_queue is being removed

On 08/07/2017 07:53 PM, Ming Lei wrote: > On Tue, Aug 8, 2017 at 3:38 AM, David Jeffery wrote: >> >> Signed-off-by: David Jeffery >> --- >> block/blk-sysfs.c |2 ++ >> block/elevator.c |4 >> 2 files changed, 6 insertions(+) >> >> >> diff

Re: [PATCH] block: Fix warning when I/O elevator is changed as request_queue is being removed

On 08/07/2017 07:53 PM, Ming Lei wrote: > On Tue, Aug 8, 2017 at 3:38 AM, David Jeffery wrote: >> >> Signed-off-by: David Jeffery >> --- >> block/blk-sysfs.c |2 ++ >> block/elevator.c |4 >> 2 files changed, 6 insertions(+) >> >> >> diff --git a/block/blk-sysfs.c

Re: [PATCH 3/3] ANDROID: binder: fix proc->tsk check.

On Tue, Aug 08, 2017 at 10:34:47AM -0700, John Stultz wrote: > On Fri, Jul 28, 2017 at 4:56 AM, Martijn Coenen wrote: > > Commit c4ea41ba195d ("binder: use group leader instead of open thread")' > > was incomplete and didn't update a check in binder_mmap(), causing all > >

Re: [PATCH 3/3] ANDROID: binder: fix proc->tsk check.

On Tue, Aug 08, 2017 at 10:34:47AM -0700, John Stultz wrote: > On Fri, Jul 28, 2017 at 4:56 AM, Martijn Coenen wrote: > > Commit c4ea41ba195d ("binder: use group leader instead of open thread")' > > was incomplete and didn't update a check in binder_mmap(), causing all > > mmap() calls into the

Re: [PATCH] lib: Add test module for CONFIG_DEBUG_VIRTUAL

On 08/08/2017 10:57 AM, Luis R. Rodriguez wrote: > On Tue, Aug 08, 2017 at 09:40:26AM -0700, Florian Fainelli wrote: >> Add a test module that allows testing that CONFIG_DEBUG_VIRTUAL works >> correctly, at least that it can catch invalid calls to virt_to_phys() >> against the non-linear kernel

Re: [PATCH] lib: Add test module for CONFIG_DEBUG_VIRTUAL

On 08/08/2017 10:57 AM, Luis R. Rodriguez wrote: > On Tue, Aug 08, 2017 at 09:40:26AM -0700, Florian Fainelli wrote: >> Add a test module that allows testing that CONFIG_DEBUG_VIRTUAL works >> correctly, at least that it can catch invalid calls to virt_to_phys() >> against the non-linear kernel

Re: [PATCH v3] dma-mapping: skip USB devices when configuring DMA during probe

On Sat, Aug 05, 2017 at 10:38:07AM +0200, Christoph Hellwig wrote: > I think the root problem is that the code added by > " of/acpi: Configure dma operations at probe time for platform/amba/pci bus > devices" > > is completely bogus and needs to be reverted. We can't simply iterate > over all

Re: [PATCH v3] dma-mapping: skip USB devices when configuring DMA during probe

On Sat, Aug 05, 2017 at 10:38:07AM +0200, Christoph Hellwig wrote: > I think the root problem is that the code added by > " of/acpi: Configure dma operations at probe time for platform/amba/pci bus > devices" > > is completely bogus and needs to be reverted. We can't simply iterate > over all

Re: [PATCH] rcu: Skip additional checks if rcu_cpu_stall_suppress is set

On Tue, Aug 08, 2017 at 10:50:26PM +0530, Neeraj Upadhyay wrote: > If rcu_kick_kthreads is set, and gp is in progress, check_cpu_stall() > does checks to figure out whether jiffies is past rsp->jiffies_stall, > doing ordered accesses to avoid any false positives for new grace > period

Re: [PATCH] rcu: Skip additional checks if rcu_cpu_stall_suppress is set

On Tue, Aug 08, 2017 at 10:50:26PM +0530, Neeraj Upadhyay wrote: > If rcu_kick_kthreads is set, and gp is in progress, check_cpu_stall() > does checks to figure out whether jiffies is past rsp->jiffies_stall, > doing ordered accesses to avoid any false positives for new grace > period

Re: [RFC][PATCH] timer: Add function-change canary

On Mon, Aug 7, 2017 at 5:33 PM, Kees Cook wrote: > This introduces canaries to struct timer_list in an effort to protect the > function callback pointer from getting rewritten during stack or heap > overflow attacks. The struct timer_list has become a recent target for >

Re: [RFC][PATCH] timer: Add function-change canary

On Mon, Aug 7, 2017 at 5:33 PM, Kees Cook wrote: > This introduces canaries to struct timer_list in an effort to protect the > function callback pointer from getting rewritten during stack or heap > overflow attacks. The struct timer_list has become a recent target for > security flaw

Re: [PATCH] lib: Add test module for CONFIG_DEBUG_VIRTUAL

On Tue, Aug 08, 2017 at 09:40:26AM -0700, Florian Fainelli wrote: > Add a test module that allows testing that CONFIG_DEBUG_VIRTUAL works > correctly, at least that it can catch invalid calls to virt_to_phys() > against the non-linear kernel virtual address map. > > Signed-off-by: Florian

Re: [PATCH] lib: Add test module for CONFIG_DEBUG_VIRTUAL

On Tue, Aug 08, 2017 at 09:40:26AM -0700, Florian Fainelli wrote: > Add a test module that allows testing that CONFIG_DEBUG_VIRTUAL works > correctly, at least that it can catch invalid calls to virt_to_phys() > against the non-linear kernel virtual address map. > > Signed-off-by: Florian

Re: [PATCH 1/5] test_kmod: make selftest executable

On Tue, Aug 08, 2017 at 07:50:04PM +1000, Michael Ellerman wrote: > Andrew Morton writes: > > On Wed, 2 Aug 2017 14:14:46 -0700 "Luis R. Rodriguez" > > wrote: > > > >> We had just forgotten to do this. > >> > >> Fixes: 39258f448d71 ("kmod: add

Re: [PATCH 1/5] test_kmod: make selftest executable

On Tue, Aug 08, 2017 at 07:50:04PM +1000, Michael Ellerman wrote: > Andrew Morton writes: > > On Wed, 2 Aug 2017 14:14:46 -0700 "Luis R. Rodriguez" > > wrote: > > > >> We had just forgotten to do this. > >> > >> Fixes: 39258f448d71 ("kmod: add test driver to stress test the module > >>

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