Re: [PATCH v17 0/4] Replace PCI pool by DMA pool API

On Tue, Jan 02, 2018 at 06:53:52PM +0100, Romain Perier wrote: > The current PCI pool API are simple macro functions direct expanded to > the appropriate dma pool functions. The prototypes are almost the same > and semantically, they are very similar. I propose to use the DMA pool > API directly

Re: [PATCH v17 0/4] Replace PCI pool by DMA pool API

On Tue, Jan 02, 2018 at 06:53:52PM +0100, Romain Perier wrote: > The current PCI pool API are simple macro functions direct expanded to > the appropriate dma pool functions. The prototypes are almost the same > and semantically, they are very similar. I propose to use the DMA pool > API directly

Re: [RESEND PATCH v2 09/15] ASoC: qcom: qdsp6: Add support to Q6CORE

On Thu 14 Dec 09:33 PST 2017, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > This patch adds support to core apr service, which is used to query > status of other static and dynamic services on the dsp. > > Signed-off-by: Srinivas

Re: [RESEND PATCH v2 09/15] ASoC: qcom: qdsp6: Add support to Q6CORE

On Thu 14 Dec 09:33 PST 2017, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > This patch adds support to core apr service, which is used to query > status of other static and dynamic services on the dsp. > > Signed-off-by: Srinivas Kandagatla > --- >

Re: [ANNOUNCE] autofs 5.1.2 release

On Thu, Dec 21 2017, Ian Kent wrote: > On 21/12/17 19:06, Ian Kent wrote: >> On 21/12/17 09:09, NeilBrown wrote: >>> On Wed, Dec 20 2017, Ian Kent wrote: >>> On 20/12/17 13:52, Ian Kent wrote: > On 20/12/17 11:29, NeilBrown wrote: >> >> Hi Ian, >> I've been looking at:

Re: [ANNOUNCE] autofs 5.1.2 release

On Thu, Dec 21 2017, Ian Kent wrote: > On 21/12/17 19:06, Ian Kent wrote: >> On 21/12/17 09:09, NeilBrown wrote: >>> On Wed, Dec 20 2017, Ian Kent wrote: >>> On 20/12/17 13:52, Ian Kent wrote: > On 20/12/17 11:29, NeilBrown wrote: >> >> Hi Ian, >> I've been looking at:

Re: cgroups(7): documenting cgroup.stat

Hello, Michael! Thank you for working on this! Please, find my comments below. On Tue, Jan 02, 2018 at 07:22:33PM +0100, Michael Kerrisk (man-pages) wrote: > Hello Roman, > > I wish to add documentation to cgroups(7) for the cgroup.stat file > that you added in Linux 4.14. I wrote some text

Re: cgroups(7): documenting cgroup.stat

Hello, Michael! Thank you for working on this! Please, find my comments below. On Tue, Jan 02, 2018 at 07:22:33PM +0100, Michael Kerrisk (man-pages) wrote: > Hello Roman, > > I wish to add documentation to cgroups(7) for the cgroup.stat file > that you added in Linux 4.14. I wrote some text

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Wednesday 04 January 2017 15:37:35 Bastien Nocera wrote: > I don't doubt that the use cases should be catered for, I essentially > did that same work without kernel changes for GNOME. What I doubt is > the fuzzy semantics, the fact that the device is kept opened but no > data is sent (that's

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Wednesday 04 January 2017 15:37:35 Bastien Nocera wrote: > I don't doubt that the use cases should be catered for, I essentially > did that same work without kernel changes for GNOME. What I doubt is > the fuzzy semantics, the fact that the device is kept opened but no > data is sent (that's

Re: [PATCH] m32r: fix readl/writel prototypes

On Tue, Jan 02, 2018 at 11:56:41AM +0100, Arnd Bergmann wrote: > All other architectures use 'unsigned int' as the data in readl/write, > but m32r uses 'unsigned long', leading to lots of harmless build warnings > like: > > drivers/mmc/host/dw_mmc.c: In function 'dw_mci_regs_show': >

Re: [PATCH] m32r: fix readl/writel prototypes

On Tue, Jan 02, 2018 at 11:56:41AM +0100, Arnd Bergmann wrote: > All other architectures use 'unsigned int' as the data in readl/write, > but m32r uses 'unsigned long', leading to lots of harmless build warnings > like: > > drivers/mmc/host/dw_mmc.c: In function 'dw_mci_regs_show': >

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Tuesday 03 January 2017 12:21:21 Bastien Nocera wrote: > On Mon, 2017-01-02 at 18:09 +0100, Pali Rohár wrote: > > On Monday 02 January 2017 16:27:05 Bastien Nocera wrote: > > > On Sun, 2016-12-25 at 11:04 +0100, Pali Rohár wrote: > > > > This patch allows user to disable events from any input

Re: [RFC PATCH] input: Add disable sysfs entry for every input device

On Tuesday 03 January 2017 12:21:21 Bastien Nocera wrote: > On Mon, 2017-01-02 at 18:09 +0100, Pali Rohár wrote: > > On Monday 02 January 2017 16:27:05 Bastien Nocera wrote: > > > On Sun, 2016-12-25 at 11:04 +0100, Pali Rohár wrote: > > > > This patch allows user to disable events from any input

Re: [PATCH] Support HVR-1200 analog video as a clone of HVR-1500. Tested, composite and s-video inputs.

To be honest we should probably just drop this, I no longer have the card in my machine so cannot re-test it if ever needed. On 4 December 2017 at 12:01, Hans Verkuil wrote: > Hi Nigel, > > Can you repost this as a proper patch? It doesn't apply (issues with tabs and >

Re: [PATCH] Support HVR-1200 analog video as a clone of HVR-1500. Tested, composite and s-video inputs.

To be honest we should probably just drop this, I no longer have the card in my machine so cannot re-test it if ever needed. On 4 December 2017 at 12:01, Hans Verkuil wrote: > Hi Nigel, > > Can you repost this as a proper patch? It doesn't apply (issues with tabs and > whitespace: please use

Re: PROBLEM: i915 causes complete desktop freezes in 4.15-rc5

Attached. Crashed quite a bit faster than before this time. It always seems to have something to do with opening and alt-tabbing between windows. This time what produced the crash was an attempt to open a new terminal. The hanging happened right after issuing the keyboard shortcut, before the

Re: PROBLEM: i915 causes complete desktop freezes in 4.15-rc5

Attached. Crashed quite a bit faster than before this time. It always seems to have something to do with opening and alt-tabbing between windows. This time what produced the crash was an attempt to open a new terminal. The hanging happened right after issuing the keyboard shortcut, before the

Re: [PATCH] clk: Fix debugfs_create_*() usage

Hi Stephen, On Tue, Jan 2, 2018 at 8:23 PM, Stephen Boyd wrote: > On 01/02, Geert Uytterhoeven wrote: >> When exposing data access through debugfs, the correct >> debugfs_create_*() functions must be used, depending on data type. >> >> Remove all casts from data pointers

Re: [PATCH] clk: Fix debugfs_create_*() usage

Hi Stephen, On Tue, Jan 2, 2018 at 8:23 PM, Stephen Boyd wrote: > On 01/02, Geert Uytterhoeven wrote: >> When exposing data access through debugfs, the correct >> debugfs_create_*() functions must be used, depending on data type. >> >> Remove all casts from data pointers passed to

Re: [PATCH v4 5/7] clk: Introduce davinci clocks

Forgot to cc linux-clk, so doing that now... On 12/31/2017 05:39 PM, David Lechner wrote: This introduces new drivers for arch/arm/mach-davinci. The code is based on the clock drivers from there and adapted to use the common clock framework. Signed-off-by: David Lechner

Re: [PATCH v4 5/7] clk: Introduce davinci clocks

Forgot to cc linux-clk, so doing that now... On 12/31/2017 05:39 PM, David Lechner wrote: This introduces new drivers for arch/arm/mach-davinci. The code is based on the clock drivers from there and adapted to use the common clock framework. Signed-off-by: David Lechner ---

[PATCH] netcp_ethss: Delete error messages for a failed memory allocation in three functions

From: Markus Elfring Date: Tue, 2 Jan 2018 22:08:50 +0100 Omit extra messages for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] netcp_ethss: Delete error messages for a failed memory allocation in three functions

From: Markus Elfring Date: Tue, 2 Jan 2018 22:08:50 +0100 Omit extra messages for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/net/ethernet/ti/netcp_ethss.c | 27 ++-

Re: 4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64

On Tue, Jan 02, 2018 at 10:49:16PM +0200, Meelis Roos wrote: > This is on a socket 939 Athlon64 3500+, with PTI enabled. LOL. > [ 316.384669] mce: [Hardware Error]: Machine check events logged > [ 316.384698] [Hardware Error]: Corrected error, no action required. > [ 316.384719] [Hardware

Re: 4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64

On Tue, Jan 02, 2018 at 10:49:16PM +0200, Meelis Roos wrote: > This is on a socket 939 Athlon64 3500+, with PTI enabled. LOL. > [ 316.384669] mce: [Hardware Error]: Machine check events logged > [ 316.384698] [Hardware Error]: Corrected error, no action required. > [ 316.384719] [Hardware

[net-next v2] ipv6: sr: export some functions of seg6local

Some functions of seg6local are very useful to process SRv6 encapsulated packets This patch exports some functions of seg6local that are useful and can be re-used at different parts of the kernel. The set of exported functions are: (1) seg6_get_srh() (2) seg6_advance_nextseg() (3)

[net-next v2] ipv6: sr: export some functions of seg6local

Some functions of seg6local are very useful to process SRv6 encapsulated packets This patch exports some functions of seg6local that are useful and can be re-used at different parts of the kernel. The set of exported functions are: (1) seg6_get_srh() (2) seg6_advance_nextseg() (3)

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

On Sat, 30 Dec 2017, 10:28am, Himanshu Jha wrote: > Use dma_zalloc_coherent instead of dma_alloc_coherent followed by > memset 0. > > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > > Suggested-by: Luis R. Rodriguez > Signed-off-by: Himanshu Jha

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

On Sat, 30 Dec 2017, 10:28am, Himanshu Jha wrote: > Use dma_zalloc_coherent instead of dma_alloc_coherent followed by > memset 0. > > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > > Suggested-by: Luis R. Rodriguez > Signed-off-by: Himanshu Jha > --- >

Re: [PATCH] net: ipv4: emulate READ_ONCE() on ->hdrincl bit-field in raw_sendmsg()

Hi, On Tue, 2 Jan 2018 17:30:20 +0100 Nicolai Stange wrote: > [...] > > diff --git a/net/ipv4/raw.c b/net/ipv4/raw.c > index 5b9bd5c33d9d..e84290c28c0c 100644 > --- a/net/ipv4/raw.c > +++ b/net/ipv4/raw.c > @@ -513,16 +513,18 @@ static int raw_sendmsg(struct sock *sk, struct

Re: [PATCH] net: ipv4: emulate READ_ONCE() on ->hdrincl bit-field in raw_sendmsg()

Hi, On Tue, 2 Jan 2018 17:30:20 +0100 Nicolai Stange wrote: > [...] > > diff --git a/net/ipv4/raw.c b/net/ipv4/raw.c > index 5b9bd5c33d9d..e84290c28c0c 100644 > --- a/net/ipv4/raw.c > +++ b/net/ipv4/raw.c > @@ -513,16 +513,18 @@ static int raw_sendmsg(struct sock *sk, struct msghdr > *msg,

Re: [PATCH 2/3] x86/tsc: Fix erroneous TSC rate on Skylake Xeon

On Tue, Jan 2, 2018 at 10:36 AM, Prarit Bhargava wrote: > > > On 12/22/2017 12:27 AM, Len Brown wrote: >> From: Len Brown >> >> Linux-4.9 added INTEL_FAM6_SKYLAKE_X to native_calibrate_tsc(): > > Sorry, Len I didn't realize you had sent this multiple

Re: [PATCH 2/3] x86/tsc: Fix erroneous TSC rate on Skylake Xeon

On Tue, Jan 2, 2018 at 10:36 AM, Prarit Bhargava wrote: > > > On 12/22/2017 12:27 AM, Len Brown wrote: >> From: Len Brown >> >> Linux-4.9 added INTEL_FAM6_SKYLAKE_X to native_calibrate_tsc(): > > Sorry, Len I didn't realize you had sent this multiple times. > > I lifted this code directly from

Re: Linux 4.15-rc6

On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote: > > I thought it'd be interesting to run a short benchmark to be able to > estimate the impact of the PTI work on postgres workloads (which I work > on). On my skylake laptop, a memory resident, OLTP workload with 16 >

Re: Linux 4.15-rc6

On Tue, Jan 2, 2018 at 12:28 PM, Andres Freund wrote: > > I thought it'd be interesting to run a short benchmark to be able to > estimate the impact of the PTI work on postgres workloads (which I work > on). On my skylake laptop, a memory resident, OLTP workload with 16 > connections results in:

Re: [PATCH] IB/ocrdma: Use zeroing memory allocator than allocator/memset

On Sat, Dec 30, 2017 at 09:09:56PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] IB/ocrdma: Use zeroing memory allocator than allocator/memset

On Sat, Dec 30, 2017 at 09:09:56PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] IB/mthca: Use zeroing memory allocator than allocator/memset

On Sun, Dec 31, 2017 at 06:04:10PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] RDMA/vmw_pvrdma: Use zeroing memory allocator than allocator/memset

On Sun, Dec 31, 2017 at 05:59:00PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] IB/mthca: Use zeroing memory allocator than allocator/memset

On Sun, Dec 31, 2017 at 06:04:10PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] RDMA/vmw_pvrdma: Use zeroing memory allocator than allocator/memset

On Sun, Dec 31, 2017 at 05:59:00PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] RDMA/bnxt_re: Use zeroing memory allocator than allocator/memset

On Sun, Dec 31, 2017 at 06:02:38PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] RDMA/bnxt_re: Use zeroing memory allocator than allocator/memset

On Sun, Dec 31, 2017 at 06:02:38PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] RDMA/qedr: Use zeroing memory allocator than allocator/memset

On Sun, Dec 31, 2017 at 06:01:03PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] RDMA/qedr: Use zeroing memory allocator than allocator/memset

On Sun, Dec 31, 2017 at 06:01:03PM +0530, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > >

Re: [PATCH] Documentation: security/credentials.rst: explain need to sort group_list

On Wed, Jan 03, 2018 at 08:01:15AM +1100, NeilBrown wrote: > > +When replacing the group list, the new list must be sorted before it > +is added to the credential, as a binary search is used to test for > +membership. In practice, this means ``groups_sort()`` should be For a .rst file,

Re: [PATCH] Documentation: security/credentials.rst: explain need to sort group_list

On Wed, Jan 03, 2018 at 08:01:15AM +1100, NeilBrown wrote: > > +When replacing the group list, the new list must be sorted before it > +is added to the credential, as a binary search is used to test for > +membership. In practice, this means ``groups_sort()`` should be For a .rst file,

[PATCH] Documentation: security/credentials.rst: explain need to sort group_list

This patch updates the documentation with the observations that led to commit bdcf0a423ea1 ("kernel: make groups_sort calling a responsibility group_info allocators") and the new behaviour required. Specifically that groups_sort() should be called on a new group_list before set_groups() or

[PATCH] Documentation: security/credentials.rst: explain need to sort group_list

This patch updates the documentation with the observations that led to commit bdcf0a423ea1 ("kernel: make groups_sort calling a responsibility group_info allocators") and the new behaviour required. Specifically that groups_sort() should be called on a new group_list before set_groups() or

RE: [PATCH v5 2/5] iommu/vt-d: Add debugfs support to show context internals

> -Original Message- > From: Andy Shevchenko [mailto:andriy.shevche...@linux.intel.com] > Sent: Thursday, December 28, 2017 12:52 AM > To: Mehta, Sohil ; Joerg Roedel ; > Alex Williamson > Cc: David Woodhouse

RE: [PATCH v5 2/5] iommu/vt-d: Add debugfs support to show context internals

> -Original Message- > From: Andy Shevchenko [mailto:andriy.shevche...@linux.intel.com] > Sent: Thursday, December 28, 2017 12:52 AM > To: Mehta, Sohil ; Joerg Roedel ; > Alex Williamson > Cc: David Woodhouse ; Raj, Ashok > ; io...@lists.linux-foundation.org; linux- >

Re: [PATCH] swiotlb: suppress warning when __GFP_NOWARN is set v2

On Tue, Jan 02, 2018 at 01:13:58PM +0100, Christian König wrote: > TTM tries to allocate coherent memory in chunks of 2MB first to improve > TLB efficiency and falls back to allocating 4K pages if that fails. > > Suppress the warning when the 2MB allocations fails since there is a > valid fall

Re: [PATCH] swiotlb: suppress warning when __GFP_NOWARN is set v2

On Tue, Jan 02, 2018 at 01:13:58PM +0100, Christian König wrote: > TTM tries to allocate coherent memory in chunks of 2MB first to improve > TLB efficiency and falls back to allocating 4K pages if that fails. > > Suppress the warning when the 2MB allocations fails since there is a > valid fall

Re: [PATCH v5] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

On Wed, Jan 03, 2018 at 04:49:42AM +0800, kbuild test robot wrote: > Hi Jia, > > Thank you for the patch! Yet something to improve: > > [auto build test ERROR on v4.15-rc5] > [also build test ERROR on next-20180102] > [cannot apply to tip/x86/core] > [if your patch is

Re: [PATCH v5] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

On Wed, Jan 03, 2018 at 04:49:42AM +0800, kbuild test robot wrote: > Hi Jia, > > Thank you for the patch! Yet something to improve: > > [auto build test ERROR on v4.15-rc5] > [also build test ERROR on next-20180102] > [cannot apply to tip/x86/core] > [if your patch is

[nouveau] grumble/gripe ... fifo: read fault ... channel 12 killed! (eternal freeze-frame)

Twice now with v4.15-rc6, my display has gone belly up. Note: swiotlb: suppress warning when __GFP_NOWARN is set v2 is applied, but I don't _think_ it was the first time it happened. [ 3729.558261] nouveau :01:00.0: gr: TRAP ch 2 [00ff842000 Xorg[3413]] [ 3729.558269] nouveau :01:00.0:

[nouveau] grumble/gripe ... fifo: read fault ... channel 12 killed! (eternal freeze-frame)

Twice now with v4.15-rc6, my display has gone belly up. Note: swiotlb: suppress warning when __GFP_NOWARN is set v2 is applied, but I don't _think_ it was the first time it happened. [ 3729.558261] nouveau :01:00.0: gr: TRAP ch 2 [00ff842000 Xorg[3413]] [ 3729.558269] nouveau :01:00.0:

Re: thinkpad x60: sound problems in 4.15-rc1 was Re: thinkpad x60: sound problems in 4.14.0-next-20171114

Hi! > > > > > > pavel@amd:~$ > > > > > > > > > > > > Again, mplayer has problems, mpg123 works. This time mplayer started > > > > > > playing video (w/o sound) after long delay. > > > > > > > > > > > > Uh. huh. And now problems appeared in mpg123, too, and then went > > > > > > away > > > > >

Re: [BISECTED] tpm CLKRUN breaks PS/2 keyboard and touchpad on Braswell system

> diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c > index e7bd2e750f69..0858c08b3b89 100644 > --- a/drivers/char/tpm/tpm_tis_core.c > +++ b/drivers/char/tpm/tpm_tis_core.c > @@ -688,7 +688,7 @@ static void tpm_tis_clkrun_enable(struct tpm_chip *chip, > bool value)

Re: thinkpad x60: sound problems in 4.15-rc1 was Re: thinkpad x60: sound problems in 4.14.0-next-20171114

Hi! > > > > > > pavel@amd:~$ > > > > > > > > > > > > Again, mplayer has problems, mpg123 works. This time mplayer started > > > > > > playing video (w/o sound) after long delay. > > > > > > > > > > > > Uh. huh. And now problems appeared in mpg123, too, and then went > > > > > > away > > > > >

Re: [BISECTED] tpm CLKRUN breaks PS/2 keyboard and touchpad on Braswell system

> diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c > index e7bd2e750f69..0858c08b3b89 100644 > --- a/drivers/char/tpm/tpm_tis_core.c > +++ b/drivers/char/tpm/tpm_tis_core.c > @@ -688,7 +688,7 @@ static void tpm_tis_clkrun_enable(struct tpm_chip *chip, > bool value)

Re: [PATCH v5] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

Hi Jia, Thank you for the patch! Yet something to improve: [auto build test ERROR on v4.15-rc5] [also build test ERROR on next-20180102] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH v5] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

Hi Jia, Thank you for the patch! Yet something to improve: [auto build test ERROR on v4.15-rc5] [also build test ERROR on next-20180102] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64

This is on a socket 939 Athlon64 3500+, with PTI enabled. [ 316.384669] mce: [Hardware Error]: Machine check events logged [ 316.384698] [Hardware Error]: Corrected error, no action required. [ 316.384719] [Hardware Error]: CPU:0 (f:2f:2) MC1_STATUS[-|CE|-|-|AddrV]: 0x94010011 [

[PATCH] ethernet: cpsw-phy-sel: Delete an error message for a failed memory allocation in cpsw_phy_sel_probe()

From: Markus Elfring Date: Tue, 2 Jan 2018 21:41:25 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

4.15-rc6 PTI regression: L1 TLB mismatch MCE on Athlon64

This is on a socket 939 Athlon64 3500+, with PTI enabled. [ 316.384669] mce: [Hardware Error]: Machine check events logged [ 316.384698] [Hardware Error]: Corrected error, no action required. [ 316.384719] [Hardware Error]: CPU:0 (f:2f:2) MC1_STATUS[-|CE|-|-|AddrV]: 0x94010011 [

[PATCH] ethernet: cpsw-phy-sel: Delete an error message for a failed memory allocation in cpsw_phy_sel_probe()

From: Markus Elfring Date: Tue, 2 Jan 2018 21:41:25 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/net/ethernet/ti/cpsw-phy-sel.c | 4 +--- 1 file changed, 1

[PATCH] misc: rtsx: release IRQ during shutdown

'Commit cc27b735ad3a ("PCI/portdrv: Turn off PCIe services during shutdown")' revealed a resource leak in rtsx_pci driver during shutdown. Issue shows up as a warning during the shutdown step as follows: remove_proc_entry: removing non-empty directory 'irq/17', leaking at least 'rtsx_pci'

[PATCH] misc: rtsx: release IRQ during shutdown

'Commit cc27b735ad3a ("PCI/portdrv: Turn off PCIe services during shutdown")' revealed a resource leak in rtsx_pci driver during shutdown. Issue shows up as a warning during the shutdown step as follows: remove_proc_entry: removing non-empty directory 'irq/17', leaking at least 'rtsx_pci'

Re: [PATCH] Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops

Hi John, John Stultz reports a boot time crash with the HiKey board (which uses hci_serdev) occurring in hci_uart_tx_wakeup(). That function is contained in hci_ldisc.c, but also called from the newer hci_serdev.c. It acquires the proto_lock in struct hci_uart and it turns

Re: [PATCH] Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops

Hi John, John Stultz reports a boot time crash with the HiKey board (which uses hci_serdev) occurring in hci_uart_tx_wakeup(). That function is contained in hci_ldisc.c, but also called from the newer hci_serdev.c. It acquires the proto_lock in struct hci_uart and it turns

Re: [PATCH 01/33] clk_ops: change round_rate() to return unsigned long

On 02/01/18 19:01, Stephen Boyd wrote: On 12/31, Bryan O'Donoghue wrote: On 30/12/17 16:36, Mikko Perttunen wrote: FWIW, we had this problem some years ago with the Tegra CPU clock - then it was determined that a simpler solution was to have the determine_rate callback support unsigned long

Re: [PATCH 01/33] clk_ops: change round_rate() to return unsigned long

On 02/01/18 19:01, Stephen Boyd wrote: On 12/31, Bryan O'Donoghue wrote: On 30/12/17 16:36, Mikko Perttunen wrote: FWIW, we had this problem some years ago with the Tegra CPU clock - then it was determined that a simpler solution was to have the determine_rate callback support unsigned long

Re: [PATCH] xfs: destroy mutex qi_tree_lock before free xfs_quotainfo_t object

On Sun, Dec 24, 2017 at 08:34:47PM +0800, Xiongwei Song wrote: > The mutex qi_tree_lock of xfs_quotainfo_t object was initialized when > calling xfs_qm_init_quotainfo, but it was not destroyed before free > xfs_quotainfo_t object when calling xfs_qm_destroy_quotainfo, this was > incorrect, so

Re: [PATCH] xfs: destroy mutex qi_tree_lock before free xfs_quotainfo_t object

On Sun, Dec 24, 2017 at 08:34:47PM +0800, Xiongwei Song wrote: > The mutex qi_tree_lock of xfs_quotainfo_t object was initialized when > calling xfs_qm_init_quotainfo, but it was not destroyed before free > xfs_quotainfo_t object when calling xfs_qm_destroy_quotainfo, this was > incorrect, so

Re: [PATCH] Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops

On Mon, Dec 11, 2017 at 1:49 PM, John Stultz wrote: > On Thu, Nov 16, 2017 at 10:07 PM, Marcel Holtmann wrote: >> Hi Lukas, >> >>> John Stultz reports a boot time crash with the HiKey board (which uses >>> hci_serdev) occurring in

Re: [PATCH] Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops

On Mon, Dec 11, 2017 at 1:49 PM, John Stultz wrote: > On Thu, Nov 16, 2017 at 10:07 PM, Marcel Holtmann wrote: >> Hi Lukas, >> >>> John Stultz reports a boot time crash with the HiKey board (which uses >>> hci_serdev) occurring in hci_uart_tx_wakeup(). That function is >>> contained in

[PATCH] usercopy: Remove pointer from overflow report

Using %p was already mostly useless in the usercopy overflow reports, so this removes it entirely to avoid confusion now that %p-hashing is enabled. Fixes: ad67b74d2469d9b8 ("printk: hash addresses printed with %p") Signed-off-by: Kees Cook --- I have follow-ups to this

[PATCH] usercopy: Remove pointer from overflow report

Using %p was already mostly useless in the usercopy overflow reports, so this removes it entirely to avoid confusion now that %p-hashing is enabled. Fixes: ad67b74d2469d9b8 ("printk: hash addresses printed with %p") Signed-off-by: Kees Cook --- I have follow-ups to this that include the offset

Re: [net-next] netfilter: add segment routing header 'srh' match

On Fri, 29 Dec 2017 12:07:52 +0100 Ahmed Abdelsalam wrote: > It allows matching packets based on Segment Routing Header > (SRH) information. > The implementation considers revision 7 of the SRH draft. > https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-07 >

Re: [net-next] netfilter: add segment routing header 'srh' match

On Fri, 29 Dec 2017 12:07:52 +0100 Ahmed Abdelsalam wrote: > It allows matching packets based on Segment Routing Header > (SRH) information. > The implementation considers revision 7 of the SRH draft. > https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-07 > > Currently

[patch] fs/nfs: Add a resched point to nfs_commit_release_pages()

On Mon, 2017-12-18 at 17:24 +, Trond Myklebust wrote: > On Mon, 2017-12-18 at 18:00 +0100, Mike Galbraith wrote: > > On Mon, 2017-12-18 at 11:35 -0500, J. Bruce Fields wrote: > > > > > > Like I say, I don't really understand the issues here, so it's more > > > a > > > question than an

[patch] fs/nfs: Add a resched point to nfs_commit_release_pages()

On Mon, 2017-12-18 at 17:24 +, Trond Myklebust wrote: > On Mon, 2017-12-18 at 18:00 +0100, Mike Galbraith wrote: > > On Mon, 2017-12-18 at 11:35 -0500, J. Bruce Fields wrote: > > > > > > Like I say, I don't really understand the issues here, so it's more > > > a > > > question than an

Re: Linux 4.15-rc6

On 2017-12-31 14:57:51 -0800, Linus Torvalds wrote: > With all the x86 pti work coming in late in the rc like this, I'm by > now almost guaranteed to do an rc8 this release, not because there are > any known problems, but simply because of the timing of the patches. > > Go forth and test, I

Re: Linux 4.15-rc6

On 2017-12-31 14:57:51 -0800, Linus Torvalds wrote: > With all the x86 pti work coming in late in the rc like this, I'm by > now almost guaranteed to do an rc8 this release, not because there are > any known problems, but simply because of the timing of the patches. > > Go forth and test, I

Re: Bluetooth: Prevent stack info leak from the EFS element.

On Fri, Dec 08, 2017 at 03:14:47PM +0100, gre...@linuxfoundation.org wrote: > From: Ben Seri > > In the function l2cap_parse_conf_rsp and in the function > l2cap_parse_conf_req the following variable is declared without > initialization: > > struct l2cap_conf_efs efs; > > In

Re: Bluetooth: Prevent stack info leak from the EFS element.

On Fri, Dec 08, 2017 at 03:14:47PM +0100, gre...@linuxfoundation.org wrote: > From: Ben Seri > > In the function l2cap_parse_conf_rsp and in the function > l2cap_parse_conf_req the following variable is declared without > initialization: > > struct l2cap_conf_efs efs; > > In addition, when

Re: Prototype patch for Linux-kernel memory model

On Sat, Dec 23, 2017 at 11:44:18AM +0530, afzal mohammed wrote: > Hi, > > On Fri, Dec 22, 2017 at 09:41:32AM +0530, afzal mohammed wrote: > > On Thu, Dec 21, 2017 at 08:15:02AM -0800, Paul E. McKenney wrote: > > > > Have you installed and run the herd tool? Doing so would allow you > > > to

Re: Prototype patch for Linux-kernel memory model

On Sat, Dec 23, 2017 at 11:44:18AM +0530, afzal mohammed wrote: > Hi, > > On Fri, Dec 22, 2017 at 09:41:32AM +0530, afzal mohammed wrote: > > On Thu, Dec 21, 2017 at 08:15:02AM -0800, Paul E. McKenney wrote: > > > > Have you installed and run the herd tool? Doing so would allow you > > > to

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Thu, Dec 28, 2017 at 04:27:11PM +0100, Thomas Gleixner wrote: > Add a file to the Documentation directory to describe how file licenses > should be described in all kernel files, using the SPDX identifier, as well > as where all licenses should be in the kernel source tree for people to > refer

Re: [patch V5 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Thu, Dec 28, 2017 at 04:27:11PM +0100, Thomas Gleixner wrote: > Add a file to the Documentation directory to describe how file licenses > should be described in all kernel files, using the SPDX identifier, as well > as where all licenses should be in the kernel source tree for people to > refer

Re: [PATCH] Move kfree_call_rcu() to slab_common.c

On Thu, Dec 21, 2017 at 07:17:35PM -0800, Rao Shoaib wrote: > > > On 12/21/2017 05:39 PM, Paul E. McKenney wrote: > >>I left it out on purpose because the call in tiny is a little different > >> > >>rcutiny.h: > >> > >>static inline void kfree_call_rcu(struct rcu_head *head, > >>                

Re: [PATCH] Move kfree_call_rcu() to slab_common.c

On Thu, Dec 21, 2017 at 07:17:35PM -0800, Rao Shoaib wrote: > > > On 12/21/2017 05:39 PM, Paul E. McKenney wrote: > >>I left it out on purpose because the call in tiny is a little different > >> > >>rcutiny.h: > >> > >>static inline void kfree_call_rcu(struct rcu_head *head, > >>                

[PATCH 1/2] Move kfree_call_rcu() to slab_common.c

From: Rao Shoaib Signed-off-by: Rao Shoaib --- include/linux/rcupdate.h | 43 +++ include/linux/rcutree.h | 2 -- include/linux/slab.h | 44

[PATCH 1/2] Move kfree_call_rcu() to slab_common.c

From: Rao Shoaib Signed-off-by: Rao Shoaib --- include/linux/rcupdate.h | 43 +++ include/linux/rcutree.h | 2 -- include/linux/slab.h | 44 kernel/rcu/tree.c| 24 ++--

[PATCH 2/2] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures

From: Rao Shoaib Signed-off-by: Rao Shoaib --- include/linux/mm.h | 5 ++ include/linux/rcutiny.h | 8 ++- kernel/sysctl.c | 40 mm/slab.h | 23 +++ mm/slab_common.c| 161

[PATCH 2/2] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures

From: Rao Shoaib Signed-off-by: Rao Shoaib --- include/linux/mm.h | 5 ++ include/linux/rcutiny.h | 8 ++- kernel/sysctl.c | 40 mm/slab.h | 23 +++ mm/slab_common.c| 161 +++- 5 files

Re: [PATCH v2 4/6] clk: ingenic: Add JZ47xx TCU clocks driver

Hi, [...] + +static void __init ingenic_tcu_init(struct device_node *np, + enum ingenic_version id) +{ + struct ingenic_tcu *tcu; + size_t i, nb_clks; + int ret = -ENOMEM; + + if (id >= ID_JZ4770) + nb_clks = (JZ4770_CLK_LAST -

Re: [PATCH v2 4/6] clk: ingenic: Add JZ47xx TCU clocks driver

Hi, [...] + +static void __init ingenic_tcu_init(struct device_node *np, + enum ingenic_version id) +{ + struct ingenic_tcu *tcu; + size_t i, nb_clks; + int ret = -ENOMEM; + + if (id >= ID_JZ4770) + nb_clks = (JZ4770_CLK_LAST -

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