[PATCH] ARM: imx_v6_v7_defconfig: select the CONFIG_CPUFREQ_DT

Select CONFIG_CPUFREQ_DT by default to enable cpu-freq driver for i.MX7D. The rest changes are generated by "make savedefconfig". Signed-off-by: Anson Huang --- arch/arm/configs/imx_v6_v7_defconfig | 17 ++--- 1 file changed, 6 insertions(+), 11 deletions(-)

[PATCH] ARM: imx_v6_v7_defconfig: select the CONFIG_CPUFREQ_DT

Select CONFIG_CPUFREQ_DT by default to enable cpu-freq driver for i.MX7D. The rest changes are generated by "make savedefconfig". Signed-off-by: Anson Huang --- arch/arm/configs/imx_v6_v7_defconfig | 17 ++--- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git

Re: [PATCH v5 26/39] nds32: Device tree support

2018-01-04 3:14 GMT+08:00 Rob Herring : > On Tue, Jan 2, 2018 at 2:24 AM, Greentime Hu wrote: >> From: Greentime Hu >> >> This patch adds support for device tree. >> >> Signed-off-by: Vincent Chen >>

Re: [PATCH v5 26/39] nds32: Device tree support

2018-01-04 3:14 GMT+08:00 Rob Herring : > On Tue, Jan 2, 2018 at 2:24 AM, Greentime Hu wrote: >> From: Greentime Hu >> >> This patch adds support for device tree. >> >> Signed-off-by: Vincent Chen >> Signed-off-by: Greentime Hu >> --- >> arch/nds32/boot/dts/Makefile |8 + >>

[PATCH v1 3/6] ASoC: mediatek: update MT2701 AFE documentation to adapt mfd device

As the new MFD parent is in place, modify MT2701 AFE documentation to adapt it. Also add three core clocks in example. Signed-off-by: Ryder Lee --- .../devicetree/bindings/sound/mt2701-afe-pcm.txt | 171 +++-- 1 file changed, 93 insertions(+), 78

[PATCH v1 3/6] ASoC: mediatek: update MT2701 AFE documentation to adapt mfd device

As the new MFD parent is in place, modify MT2701 AFE documentation to adapt it. Also add three core clocks in example. Signed-off-by: Ryder Lee --- .../devicetree/bindings/sound/mt2701-afe-pcm.txt | 171 +++-- 1 file changed, 93 insertions(+), 78 deletions(-) diff --git

[PATCH v1 5/6] clk: mediatek: update missing clock data for MT7622 audsys

Add missing clock data 'CLK_AUDIO_AFE_CONN' for MT7622 audsys. Signed-off-by: Ryder Lee --- drivers/clk/mediatek/clk-mt7622-aud.c | 3 ++- include/dt-bindings/clock/mt7622-clk.h | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git

[PATCH v1 5/6] clk: mediatek: update missing clock data for MT7622 audsys

Add missing clock data 'CLK_AUDIO_AFE_CONN' for MT7622 audsys. Signed-off-by: Ryder Lee --- drivers/clk/mediatek/clk-mt7622-aud.c | 3 ++- include/dt-bindings/clock/mt7622-clk.h | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/clk/mediatek/clk-mt7622-aud.c

[PATCH v1 6/6] clk: mediatek: add audsys support for MT2701

Add clock driver support for MT2701 audsys. Signed-off-by: Ryder Lee --- drivers/clk/mediatek/Kconfig | 6 ++ drivers/clk/mediatek/Makefile | 1 + drivers/clk/mediatek/clk-mt2701-aud.c | 174 ++ 3 files changed, 181

[PATCH v1 1/6] ASoC: mediatek: add some core clocks for MT2701 AFE

Add three core clocks for MT2701 AFE. Signed-off-by: Ryder Lee --- sound/soc/mediatek/mt2701/mt2701-afe-clock-ctrl.c | 30 ++- sound/soc/mediatek/mt2701/mt2701-afe-common.h | 3 +++ 2 files changed, 32 insertions(+), 1 deletion(-) diff --git

[PATCH v1 4/6] dt-bindings: clock: mediatek: add "simple-mfd" in audsys documentation

Add "simple-mfd" to support MFD device and add a compatible string for MT2701. Signed-off-by: Ryder Lee --- .../bindings/arm/mediatek/mediatek,audsys.txt | 21 +++-- 1 file changed, 15 insertions(+), 6 deletions(-) diff --git

Re: [PATCH] mm/fadvise: discard partial pages iff endbyte is also eof

On 2018/1/4 14:13, 夷则(Caspar) wrote: This patch is trying to help to solve a real issue. Sometimes we need to evict the whole file from page cache because we are sure it will not be used in the near future. We try to use posix_fadvise() to finish our work but we often see a "small tail" at

[PATCH v1 6/6] clk: mediatek: add audsys support for MT2701

Add clock driver support for MT2701 audsys. Signed-off-by: Ryder Lee --- drivers/clk/mediatek/Kconfig | 6 ++ drivers/clk/mediatek/Makefile | 1 + drivers/clk/mediatek/clk-mt2701-aud.c | 174 ++ 3 files changed, 181 insertions(+) create mode

[PATCH v1 1/6] ASoC: mediatek: add some core clocks for MT2701 AFE

Add three core clocks for MT2701 AFE. Signed-off-by: Ryder Lee --- sound/soc/mediatek/mt2701/mt2701-afe-clock-ctrl.c | 30 ++- sound/soc/mediatek/mt2701/mt2701-afe-common.h | 3 +++ 2 files changed, 32 insertions(+), 1 deletion(-) diff --git

[PATCH v1 4/6] dt-bindings: clock: mediatek: add "simple-mfd" in audsys documentation

Add "simple-mfd" to support MFD device and add a compatible string for MT2701. Signed-off-by: Ryder Lee --- .../bindings/arm/mediatek/mediatek,audsys.txt | 21 +++-- 1 file changed, 15 insertions(+), 6 deletions(-) diff --git

Re: [PATCH] mm/fadvise: discard partial pages iff endbyte is also eof

On 2018/1/4 14:13, 夷则(Caspar) wrote: This patch is trying to help to solve a real issue. Sometimes we need to evict the whole file from page cache because we are sure it will not be used in the near future. We try to use posix_fadvise() to finish our work but we often see a "small tail" at

[PATCH v1 0/6] add "simple-mfd" support for MediaTek audio subsystem

Hi, The reason for this series is that MediaTek audio hardware block expose more than a single functionality, but register those in different kernel subsystems. Same issue could also be found in MMSYS: https://lkml.org/lkml/2017/11/14/669 Hence use "simple-mfd" to handle this kind of situation,

[PATCH v1 2/6] ASoC: mediatek: modify MT2701 AFE driver to adapt mfd device

As the new MFD parent is in place, modify MT2701 AFE driver to adapt it. Signed-off-by: Ryder Lee --- sound/soc/mediatek/mt2701/mt2701-afe-pcm.c | 45 +- sound/soc/mediatek/mt2701/mt2701-reg.h | 1 - 2 files changed, 20 insertions(+), 26

[PATCH v1 0/6] add "simple-mfd" support for MediaTek audio subsystem

Hi, The reason for this series is that MediaTek audio hardware block expose more than a single functionality, but register those in different kernel subsystems. Same issue could also be found in MMSYS: https://lkml.org/lkml/2017/11/14/669 Hence use "simple-mfd" to handle this kind of situation,

[PATCH v1 2/6] ASoC: mediatek: modify MT2701 AFE driver to adapt mfd device

As the new MFD parent is in place, modify MT2701 AFE driver to adapt it. Signed-off-by: Ryder Lee --- sound/soc/mediatek/mt2701/mt2701-afe-pcm.c | 45 +- sound/soc/mediatek/mt2701/mt2701-reg.h | 1 - 2 files changed, 20 insertions(+), 26 deletions(-) diff --git

Re: [PATCH 4.9 00/39] 4.9.75-stable review

On Thu, Jan 04, 2018 at 08:39:41AM +0100, Greg Kroah-Hartman wrote: > On Thu, Jan 04, 2018 at 01:24:55AM +, Ben Hutchings wrote: > > On Wed, 2018-01-03 at 21:11 +0100, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.9.75 release. > > > There are 39

Re: [PATCH 4.9 00/39] 4.9.75-stable review

On Thu, Jan 04, 2018 at 08:39:41AM +0100, Greg Kroah-Hartman wrote: > On Thu, Jan 04, 2018 at 01:24:55AM +, Ben Hutchings wrote: > > On Wed, 2018-01-03 at 21:11 +0100, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.9.75 release. > > > There are 39

Re: [PATCH 4.9 00/39] 4.9.75-stable review

On Thu, Jan 04, 2018 at 01:24:55AM +, Ben Hutchings wrote: > On Wed, 2018-01-03 at 21:11 +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.75 release. > > There are 39 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH 4.9 00/39] 4.9.75-stable review

On Thu, Jan 04, 2018 at 01:24:55AM +, Ben Hutchings wrote: > On Wed, 2018-01-03 at 21:11 +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.75 release. > > There are 39 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH 4.9 29/39] x86/kaiser: Check boottime cmdline params

On Thu, Jan 04, 2018 at 08:05:50AM +0100, Borislav Petkov wrote: > On Thu, Jan 04, 2018 at 12:16:08AM +, Ben Hutchings wrote: > > No such exception has been added upstream, so I don't think it's > > appropriate to add it in stable. > > On its way: > >

Re: [PATCH 4.9 29/39] x86/kaiser: Check boottime cmdline params

On Thu, Jan 04, 2018 at 08:05:50AM +0100, Borislav Petkov wrote: > On Thu, Jan 04, 2018 at 12:16:08AM +, Ben Hutchings wrote: > > No such exception has been added upstream, so I don't think it's > > appropriate to add it in stable. > > On its way: > >

Re: [PATCH 7/9] scsi: bnx2fc: Use zeroing allocator rather than allocator/memset

Hello Martin, On Thu, Jan 04, 2018 at 01:17:52AM -0500, Martin K. Petersen wrote: > > Himanshu, > > > Use dma_zalloc_coherent instead of dma_alloc_coherent followed by > > memset 0. > > Does not apply to 4.16/scsi-queue. Please resubmit. Thanks! No problem, I will resend the patch. scsi:

Re: [PATCH 7/9] scsi: bnx2fc: Use zeroing allocator rather than allocator/memset

Hello Martin, On Thu, Jan 04, 2018 at 01:17:52AM -0500, Martin K. Petersen wrote: > > Himanshu, > > > Use dma_zalloc_coherent instead of dma_alloc_coherent followed by > > memset 0. > > Does not apply to 4.16/scsi-queue. Please resubmit. Thanks! No problem, I will resend the patch. scsi:

Re: [f2fs-dev] [PATCH 2/2 v2] f2fs: add reserved blocks for root user

On 2018/1/4 14:51, Jaegeuk Kim wrote: > This patch allows root to reserve some blocks via mount option. > > "-o reserve_root=N" means N x 4KB-sized blocks for root only. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks,

Re: [f2fs-dev] [PATCH 2/2 v2] f2fs: add reserved blocks for root user

On 2018/1/4 14:51, Jaegeuk Kim wrote: > This patch allows root to reserve some blocks via mount option. > > "-o reserve_root=N" means N x 4KB-sized blocks for root only. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks,

Re: [PATCH 1/2] jump_label: export static_key_slow_inc/dec_cpuslocked()

On Thu, Jan 4, 2018 at 2:20 AM, Peter Zijlstra wrote: > On Wed, Jan 03, 2018 at 11:29:50PM +0300, Konstantin Khlebnikov wrote: >> For fixing cpu_hotplug_lock recursion in tg_set_cfs_bandwidth(). > > Why would that need module exports? Just for symmetry with other functions.

Re: [PATCH 1/2] jump_label: export static_key_slow_inc/dec_cpuslocked()

On Thu, Jan 4, 2018 at 2:20 AM, Peter Zijlstra wrote: > On Wed, Jan 03, 2018 at 11:29:50PM +0300, Konstantin Khlebnikov wrote: >> For fixing cpu_hotplug_lock recursion in tg_set_cfs_bandwidth(). > > Why would that need module exports? Just for symmetry with other functions.

Re: [PATCH 0/6] mm, hugetlb: allocation API and migration improvements

On Wed 03-01-18 16:05:23, Andrew Morton wrote: > On Wed, 3 Jan 2018 10:32:07 +0100 Michal Hocko wrote: > > > I've posted this as an RFC [1] and both Mike and Naoya seem to be OK > > both with patches and the approach. I have rebased this on top of [2] > > because there is a

Re: [PATCH 0/6] mm, hugetlb: allocation API and migration improvements

On Wed 03-01-18 16:05:23, Andrew Morton wrote: > On Wed, 3 Jan 2018 10:32:07 +0100 Michal Hocko wrote: > > > I've posted this as an RFC [1] and both Mike and Naoya seem to be OK > > both with patches and the approach. I have rebased this on top of [2] > > because there is a small conflict in

[PATCH 1/2] clk: imx: imx7d: add the snvs clock

According to the i.MX7D Reference Manual, SNVS block has a clock gate, accessing SNVS block would need this clock gate to be enabled, add it into clock tree so that SNVS module driver can operate this clock gate. Signed-off-by: Anson Huang --- drivers/clk/imx/clk-imx7d.c

[PATCH 2/2] ARM: dts: imx7s: add snvs rtc clock

Add i.MX7 SNVS RTC clock. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx7s.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/imx7s.dtsi b/arch/arm/boot/dts/imx7s.dtsi index e718fd2..f9b97f3 100644 --- a/arch/arm/boot/dts/imx7s.dtsi +++

[PATCH 1/2] clk: imx: imx7d: add the snvs clock

According to the i.MX7D Reference Manual, SNVS block has a clock gate, accessing SNVS block would need this clock gate to be enabled, add it into clock tree so that SNVS module driver can operate this clock gate. Signed-off-by: Anson Huang --- drivers/clk/imx/clk-imx7d.c | 1 +

[PATCH 2/2] ARM: dts: imx7s: add snvs rtc clock

Add i.MX7 SNVS RTC clock. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx7s.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/imx7s.dtsi b/arch/arm/boot/dts/imx7s.dtsi index e718fd2..f9b97f3 100644 --- a/arch/arm/boot/dts/imx7s.dtsi +++

Re: [PATCH net-next 2/2] tun: allow to attach ebpf socket filter

On 2018年01月02日 17:19, Willem de Bruijn wrote: More importantly, should this program just return a boolean pass or drop. Taking a length and trimming may introduce bugs later on if the stack parses the packet unconditionally, expecting a minimum size to be present. This was the reason for

Re: [PATCH net-next 2/2] tun: allow to attach ebpf socket filter

On 2018年01月02日 17:19, Willem de Bruijn wrote: More importantly, should this program just return a boolean pass or drop. Taking a length and trimming may introduce bugs later on if the stack parses the packet unconditionally, expecting a minimum size to be present. This was the reason for

Re: [PATCH v4] f2fs: check segment type in __f2fs_replace_block

On 2018/1/4 15:10, Jaegeuk Kim wrote: > On 01/04, Yunlong Song wrote: >> In some case, the node blocks has wrong blkaddr whose segment type is >> NODE, e.g., recover inode has missing xattr flag and the blkaddr is in >> the xattr range. Since fsck.f2fs does not check the recovery nodes, this >>

Re: [PATCH v4] f2fs: check segment type in __f2fs_replace_block

On 2018/1/4 15:10, Jaegeuk Kim wrote: > On 01/04, Yunlong Song wrote: >> In some case, the node blocks has wrong blkaddr whose segment type is >> NODE, e.g., recover inode has missing xattr flag and the blkaddr is in >> the xattr range. Since fsck.f2fs does not check the recovery nodes, this >>

[PATCH V2 3/5] drivers: regulator: leave one item to record whether regulator is enabled

The items "disabled" and "enabled" are a little redundant, since only one of them would be set to record if the regulator device should keep on or be switched to off in suspend states. So in this patch, the "disabled" was removed, only leave the "enabled": - enabled == 1 for

[PATCH V2 3/5] drivers: regulator: leave one item to record whether regulator is enabled

The items "disabled" and "enabled" are a little redundant, since only one of them would be set to record if the regulator device should keep on or be switched to off in suspend states. So in this patch, the "disabled" was removed, only leave the "enabled": - enabled == 1 for

Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509 certs

* Ingo Molnar wrote: > These will cherry-pick cleanly, so it would be nice to test them on top of of > the > -stable kernel that fails: > > for N in 450cbdd0125c 4d2dc2cc766c 1e0f25dbf246 be62a3204406 0c3292ca8025 > 9d0b62328d34; do git cherry-pick $N; done > > if this

Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509 certs

* Ingo Molnar wrote: > These will cherry-pick cleanly, so it would be nice to test them on top of of > the > -stable kernel that fails: > > for N in 450cbdd0125c 4d2dc2cc766c 1e0f25dbf246 be62a3204406 0c3292ca8025 > 9d0b62328d34; do git cherry-pick $N; done > > if this brute-force

Re: [PATCH v9 7/8] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64

On 1/3/2018 8:07 PM, Logan Gunthorpe wrote: > Clean up the extra ifdefs which defined the wr_reg64 and rd_reg64 > functions in non-64bit cases in favour of the new common > io-64-nonatomic-lo-hi header. > > Signed-off-by: Logan Gunthorpe > Cc: Andy Shevchenko

Re: [PATCH v9 7/8] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64

On 1/3/2018 8:07 PM, Logan Gunthorpe wrote: > Clean up the extra ifdefs which defined the wr_reg64 and rd_reg64 > functions in non-64bit cases in favour of the new common > io-64-nonatomic-lo-hi header. > > Signed-off-by: Logan Gunthorpe > Cc: Andy Shevchenko > Cc: Horia Geantă > Cc: Dan

[PATCH V2 5/5] regulator: add PM suspend and resume hooks

In this patch, consumers are allowed to set suspend voltage, and this actually just set the "uV" in constraint::regulator_state, when the regulator_suspend_late() was called by PM core through callback when the system is entering into suspend, the regulator device would act suspend activity then.

[PATCH V2 5/5] regulator: add PM suspend and resume hooks

In this patch, consumers are allowed to set suspend voltage, and this actually just set the "uV" in constraint::regulator_state, when the regulator_suspend_late() was called by PM core through callback when the system is entering into suspend, the regulator device would act suspend activity then.

[PATCH V2 4/5] drivers: regulator: empty the old suspend functions

Regualtor suspend/resume functions should only be called by PM suspend core via registering dev_pm_ops, and regulator devices should implement the callback functions. Thus, any regulator consumer shouldn't call the regulator suspend/resume functions directly. In order to avoid compile errors,

[PATCH V2 4/5] drivers: regulator: empty the old suspend functions

Regualtor suspend/resume functions should only be called by PM suspend core via registering dev_pm_ops, and regulator devices should implement the callback functions. Thus, any regulator consumer shouldn't call the regulator suspend/resume functions directly. In order to avoid compile errors,

[PATCH V2 2/5] regulator: make regulator voltage be an array to support more states

Some regulator consumers would like to make the regulator device keeping a voltage range output when the system entering into suspend states. Making regulator voltage be an array can allow consumers to set voltage for normal state as well as for suspend states through the same code.

[PATCH V2 1/5] bindings: regulator: added support for suspend states

Some systems need to set regulators to specific states when they enter low power modes, especially around CPUs. There are many of these modes depending on the particular runtime state. Currently the regulator consumers are not granted permission to change suspend state of regulator devices, the

[PATCH V2 0/5] Add regulator suspend and resume support

Some systems need to set regulators to specific states when they enter low power modes, especially around CPUs. Currently the regulator driver, for suspend and resume features, provides two functions which are exported for being called directly by any modules or subsystems when they thought the

[PATCH V2 2/5] regulator: make regulator voltage be an array to support more states

Some regulator consumers would like to make the regulator device keeping a voltage range output when the system entering into suspend states. Making regulator voltage be an array can allow consumers to set voltage for normal state as well as for suspend states through the same code.

[PATCH V2 1/5] bindings: regulator: added support for suspend states

Some systems need to set regulators to specific states when they enter low power modes, especially around CPUs. There are many of these modes depending on the particular runtime state. Currently the regulator consumers are not granted permission to change suspend state of regulator devices, the

[PATCH V2 0/5] Add regulator suspend and resume support

Some systems need to set regulators to specific states when they enter low power modes, especially around CPUs. Currently the regulator driver, for suspend and resume features, provides two functions which are exported for being called directly by any modules or subsystems when they thought the

Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: show precise # of blocks that user/root can use

On 2018/1/4 14:50, Jaegeuk Kim wrote: > Let's show precise # of blocks that user/root can use through bavail and bfree > respectively. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks,

Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: show precise # of blocks that user/root can use

On 2018/1/4 14:50, Jaegeuk Kim wrote: > Let's show precise # of blocks that user/root can use through bavail and bfree > respectively. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks,

Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509 certs

* Greg Kroah-Hartman wrote: > On Thu, Jan 04, 2018 at 08:14:21AM +0100, Ingo Molnar wrote: > > - (or it's something I missed to consider) > > It was a operator error, the issue is also on 4.15-rc6, see another > email in this thread :) ah, ok :-) Nevertheless it

Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509 certs

* Greg Kroah-Hartman wrote: > On Thu, Jan 04, 2018 at 08:14:21AM +0100, Ingo Molnar wrote: > > - (or it's something I missed to consider) > > It was a operator error, the issue is also on 4.15-rc6, see another > email in this thread :) ah, ok :-) Nevertheless it made sense to go through all

Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509 certs

On Thu, Jan 04, 2018 at 08:14:21AM +0100, Ingo Molnar wrote: > - (or it's something I missed to consider) It was a operator error, the issue is also on 4.15-rc6, see another email in this thread :)

Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509 certs

On Thu, Jan 04, 2018 at 08:14:21AM +0100, Ingo Molnar wrote: > - (or it's something I missed to consider) It was a operator error, the issue is also on 4.15-rc6, see another email in this thread :)

Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509 certs

* Thomas Gleixner wrote: > On Wed, 3 Jan 2018, Benjamin Gilbert wrote: > > > On Wed, Jan 03, 2018 at 10:20:16AM +0100, Greg Kroah-Hartman wrote: > > > Ick, not good, any chance you can test 4.15-rc6 to verify that the issue > > > is also there (or not)? > > > > I haven't

Re: "bad pmd" errors + oops with KPTI on 4.14.11 after loading X.509 certs

* Thomas Gleixner wrote: > On Wed, 3 Jan 2018, Benjamin Gilbert wrote: > > > On Wed, Jan 03, 2018 at 10:20:16AM +0100, Greg Kroah-Hartman wrote: > > > Ick, not good, any chance you can test 4.15-rc6 to verify that the issue > > > is also there (or not)? > > > > I haven't been able to

Re: [PATCH v4] f2fs: check segment type in __f2fs_replace_block

On 01/04, Yunlong Song wrote: > In some case, the node blocks has wrong blkaddr whose segment type is > NODE, e.g., recover inode has missing xattr flag and the blkaddr is in > the xattr range. Since fsck.f2fs does not check the recovery nodes, this > will cause __f2fs_replace_block change the

Re: [PATCH v4] f2fs: check segment type in __f2fs_replace_block

On 01/04, Yunlong Song wrote: > In some case, the node blocks has wrong blkaddr whose segment type is > NODE, e.g., recover inode has missing xattr flag and the blkaddr is in > the xattr range. Since fsck.f2fs does not check the recovery nodes, this > will cause __f2fs_replace_block change the

[RECEND PATCH V7 11/12] arm64: dts: add syscon for whale2 platform

From: Chunyan Zhang Some clocks on SC9860 are in the same address area with syscon devices, the proper syscon node will be quoted under the definitions of those clocks in DT. Signed-off-by: Chunyan Zhang ---

[RECEND PATCH V7 11/12] arm64: dts: add syscon for whale2 platform

From: Chunyan Zhang Some clocks on SC9860 are in the same address area with syscon devices, the proper syscon node will be quoted under the definitions of those clocks in DT. Signed-off-by: Chunyan Zhang --- arch/arm64/boot/dts/sprd/whale2.dtsi | 46 +++- 1

[RECEND PATCH V7 12/12] arm64: dts: add clocks for SC9860

From: Chunyan Zhang Some clocks on SC9860 are in the same address area with syscon devices, those are what have a property of 'sprd,syscon' which would refer to syscon devices, others would have a reg property indicated their address ranges. Signed-off-by: Chunyan

[RECEND PATCH V7 12/12] arm64: dts: add clocks for SC9860

From: Chunyan Zhang Some clocks on SC9860 are in the same address area with syscon devices, those are what have a property of 'sprd,syscon' which would refer to syscon devices, others would have a reg property indicated their address ranges. Signed-off-by: Chunyan Zhang ---

Re: [PATCH 4.9 29/39] x86/kaiser: Check boottime cmdline params

On Thu, Jan 04, 2018 at 12:16:08AM +, Ben Hutchings wrote: > No such exception has been added upstream, so I don't think it's > appropriate to add it in stable. On its way: https://git.kernel.org/tip/694d99d40972f12e59a3696effee8a376b79d7c8 -- Regards/Gruss, Boris. SUSE Linux GmbH,

Re: [PATCH 4.9 29/39] x86/kaiser: Check boottime cmdline params

On Thu, Jan 04, 2018 at 12:16:08AM +, Ben Hutchings wrote: > No such exception has been added upstream, so I don't think it's > appropriate to add it in stable. On its way: https://git.kernel.org/tip/694d99d40972f12e59a3696effee8a376b79d7c8 -- Regards/Gruss, Boris. SUSE Linux GmbH,

[PATCH] thermal: Add debugfs support for cooling devices

This implements the debugfs interface for thermal cooling devices and exposes some pretty useful statistics. These statistics have proven to be quite useful specially while doing benchmarks related to the task scheduler, where we want to make sure that nothing has disrupted the test, specially the

[PATCH] thermal: Add debugfs support for cooling devices

This implements the debugfs interface for thermal cooling devices and exposes some pretty useful statistics. These statistics have proven to be quite useful specially while doing benchmarks related to the task scheduler, where we want to make sure that nothing has disrupted the test, specially the

[PATCH v4] f2fs: check segment type in __f2fs_replace_block

In some case, the node blocks has wrong blkaddr whose segment type is NODE, e.g., recover inode has missing xattr flag and the blkaddr is in the xattr range. Since fsck.f2fs does not check the recovery nodes, this will cause __f2fs_replace_block change the curseg of node and do the

[PATCH v4] f2fs: check segment type in __f2fs_replace_block

In some case, the node blocks has wrong blkaddr whose segment type is NODE, e.g., recover inode has missing xattr flag and the blkaddr is in the xattr range. Since fsck.f2fs does not check the recovery nodes, this will cause __f2fs_replace_block change the curseg of node and do the

Re: [PATCH 4.9 00/39] 4.9.75-stable review

On 4 January 2018 at 01:41, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.75 release. > There are 39 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied,

Re: [PATCH 4.9 00/39] 4.9.75-stable review

On 4 January 2018 at 01:41, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.75 release. > There are 39 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

Re: Crashes with KPTI and -rc6

* Laura Abbott wrote: > Hi, > > Fedora got a report via IRC of a double fault with KPTI > https://paste.fedoraproject.org/paste/SL~of04ZExXP6AN2gcJi7A I believe this one should be fixed by: d7732ba55c4b: x86/pti: Switch to kernel CR3 at early in entry_SYSCALL_compat()

Re: Crashes with KPTI and -rc6

* Laura Abbott wrote: > Hi, > > Fedora got a report via IRC of a double fault with KPTI > https://paste.fedoraproject.org/paste/SL~of04ZExXP6AN2gcJi7A I believe this one should be fixed by: d7732ba55c4b: x86/pti: Switch to kernel CR3 at early in entry_SYSCALL_compat() > This is on -rc6 .

Re: [PATCH v3] f2fs: check segment type in __f2fs_replace_block

On 01/04, Yunlong Song wrote: > In some case, the node blocks has wrong blkaddr whose segment type is > NODE, e.g., recover inode has missing xattr flag and the blkaddr is in > the xattr range. Since fsck.f2fs does not check the recovery nodes, this > will cause __f2fs_replace_block change the

Re: [PATCH v3] f2fs: check segment type in __f2fs_replace_block

On 01/04, Yunlong Song wrote: > In some case, the node blocks has wrong blkaddr whose segment type is > NODE, e.g., recover inode has missing xattr flag and the blkaddr is in > the xattr range. Since fsck.f2fs does not check the recovery nodes, this > will cause __f2fs_replace_block change the

Re: KASAN: use-after-free Read in __dev_queue_xmit

On Wed, 2018-01-03 at 21:13 -0800, Eric Dumazet wrote: > Note: all commands must start from beginning of the line in the email body. > > I guess skb_probe_transport_header() should be hardened to reject malicious > packets given by user space, instead of being gentle. Although bug triggered for

Re: KASAN: use-after-free Read in __dev_queue_xmit

On Wed, 2018-01-03 at 21:13 -0800, Eric Dumazet wrote: > Note: all commands must start from beginning of the line in the email body. > > I guess skb_probe_transport_header() should be hardened to reject malicious > packets given by user space, instead of being gentle. Although bug triggered for

Re: [PATCH 2/2 v2] f2fs: add reserved blocks for root user

This patch allows root to reserve some blocks via mount option. "-o reserve_root=N" means N x 4KB-sized blocks for root only. Signed-off-by: Jaegeuk Kim --- Change log from v1: - handle remount case to limit reserve_root=%u fs/f2fs/f2fs.h | 20

Re: [PATCH 2/2 v2] f2fs: add reserved blocks for root user

This patch allows root to reserve some blocks via mount option. "-o reserve_root=N" means N x 4KB-sized blocks for root only. Signed-off-by: Jaegeuk Kim --- Change log from v1: - handle remount case to limit reserve_root=%u fs/f2fs/f2fs.h | 20 fs/f2fs/super.c | 34

Re: [PATCH 4.4 00/37] 4.4.110-stable review

tp-timers-tests - pass: 12, Hikey board test results, Summary kernel: 4.4.110-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git tag: 4.4.110-rc1-hikey-20180103-95 git commit: 0769c4b4aafd63e5d73b6d67f6fe93abcf

Re: [PATCH 4.4 00/37] 4.4.110-stable review

ers-tests - pass: 12, Hikey board test results, Summary kernel: 4.4.110-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git tag: 4.4.110-rc1-hikey-20180103-95 git commit: 0769c4b4aafd63e5d73b6d67f6fe93abcff67cdc git describe

Re: [PATCH v3 00/20] arm64: Unmap the kernel whilst running in userspace (KPTI)

On Wed, Jan 03, 2018 at 09:17:26PM -0800, Florian Fainelli wrote: > On 12/11/2017 09:59 AM, Catalin Marinas wrote: > > On Wed, Dec 06, 2017 at 12:35:19PM +, Will Deacon wrote: > >> Patches are also pushed here: > >> > >> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git kpti > >>

Re: [PATCH v2 06/12] x86/retpoline/crypto: Convert xen assembler indirect jumps

> > diff --git a/arch/x86/crypto/camellia-aesni-avx2-asm_64.S > > b/arch/x86/crypto/camellia-aesni-avx2-asm_64.S > > index 1743e6850e00..9cd8450a2050 100644 > > --- a/arch/x86/crypto/camellia-aesni-avx2-asm_64.S > > +++ b/arch/x86/crypto/camellia-aesni-avx2-asm_64.S > > @@ -12,6 +12,7 @@ > > >

Re: [PATCH v3 00/20] arm64: Unmap the kernel whilst running in userspace (KPTI)

On Wed, Jan 03, 2018 at 09:17:26PM -0800, Florian Fainelli wrote: > On 12/11/2017 09:59 AM, Catalin Marinas wrote: > > On Wed, Dec 06, 2017 at 12:35:19PM +, Will Deacon wrote: > >> Patches are also pushed here: > >> > >> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git kpti > >>

Re: [PATCH v2 06/12] x86/retpoline/crypto: Convert xen assembler indirect jumps

> > diff --git a/arch/x86/crypto/camellia-aesni-avx2-asm_64.S > > b/arch/x86/crypto/camellia-aesni-avx2-asm_64.S > > index 1743e6850e00..9cd8450a2050 100644 > > --- a/arch/x86/crypto/camellia-aesni-avx2-asm_64.S > > +++ b/arch/x86/crypto/camellia-aesni-avx2-asm_64.S > > @@ -12,6 +12,7 @@ > > >

Re: [PATCH 1/2 v2] f2fs: show precise # of blocks that user/root can use

Let's show precise # of blocks that user/root can use through bavail and bfree respectively. Signed-off-by: Jaegeuk Kim --- Change log from v1: - clean up obsolete values fs/f2fs/super.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git

Re: [PATCH 1/2 v2] f2fs: show precise # of blocks that user/root can use

Let's show precise # of blocks that user/root can use through bavail and bfree respectively. Signed-off-by: Jaegeuk Kim --- Change log from v1: - clean up obsolete values fs/f2fs/super.c | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/fs/f2fs/super.c

RE: [PATCH v5 6/9] ACPI/PPTT: Add topology parsing code

Hi Jeremy > -Original Message- > From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org] > On Behalf Of Jeremy Linton > Sent: Wednesday, January 3, 2018 10:28 PM > To: vkil...@codeaurora.org > Cc: 'Mark Rutland' ; jonathan.zh...@cavium.com; >

RE: [PATCH v5 6/9] ACPI/PPTT: Add topology parsing code

Hi Jeremy > -Original Message- > From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org] > On Behalf Of Jeremy Linton > Sent: Wednesday, January 3, 2018 10:28 PM > To: vkil...@codeaurora.org > Cc: 'Mark Rutland' ; jonathan.zh...@cavium.com; >

Re: [PATCH v2 06/12] x86/retpoline/crypto: Convert xen assembler indirect jumps

On 04/01/18 03:00, Andi Kleen wrote: > From: Andi Kleen > > Convert all indirect jumps in xen inline assembler code to use > non speculative sequences. > > Based on code from David Woodhouse and Tim Chen > > Signed-off-by: Andi Kleen > --- >

Re: [PATCH v2 06/12] x86/retpoline/crypto: Convert xen assembler indirect jumps

On 04/01/18 03:00, Andi Kleen wrote: > From: Andi Kleen > > Convert all indirect jumps in xen inline assembler code to use > non speculative sequences. > > Based on code from David Woodhouse and Tim Chen > > Signed-off-by: Andi Kleen > --- > arch/x86/crypto/camellia-aesni-avx2-asm_64.S | 1 +

  1   2   3   4   5   6   7   8   9   10   >