[GIT PULL] seccomp fix for v4.14-rc3

Hi, Please pull this seccomp fix for v4.14-rc3. Bug was introduced in v4.4, and went unnoticed until now. Thanks! -Kees The following changes since commit e19b205be43d11bff638cad4487008c48d21c103: Linux 4.14-rc2 (2017-09-24 16:38:56 -0700) are available in the git repository at:

[GIT PULL] seccomp fix for v4.14-rc3

Hi, Please pull this seccomp fix for v4.14-rc3. Bug was introduced in v4.4, and went unnoticed until now. Thanks! -Kees The following changes since commit e19b205be43d11bff638cad4487008c48d21c103: Linux 4.14-rc2 (2017-09-24 16:38:56 -0700) are available in the git repository at:

linux-next: Tree for Sep 28

Hi all, News: I will not be doing linux-next releases from Setp 30 to Oct 30 (inclusive). Changes since 20170927: The cifs tree lost its build failure. The drm tree gained a build failure for which I applied a fix patch. The staging tree lost its build failure. The ipmi tree gained a build

linux-next: Tree for Sep 28

Hi all, News: I will not be doing linux-next releases from Setp 30 to Oct 30 (inclusive). Changes since 20170927: The cifs tree lost its build failure. The drm tree gained a build failure for which I applied a fix patch. The staging tree lost its build failure. The ipmi tree gained a build

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

On September 27, 2017 10:03:28 PM PDT, David Lin wrote: >Dmitry, > >On Fri, Sep 15, 2017 at 3:30 PM, Dmitry Torokhov > wrote: >> On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski >> wrote: >>> On 09/15/2017 08:34 PM,

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

On September 27, 2017 10:03:28 PM PDT, David Lin wrote: >Dmitry, > >On Fri, Sep 15, 2017 at 3:30 PM, Dmitry Torokhov > wrote: >> On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski >> wrote: >>> On 09/15/2017 08:34 PM, Dmitry Torokhov wrote: On Thu, Sep 14, 2017 at 1:58 PM, Pavel Machek

[tip:core/urgent] objtool: Skip unreachable warnings for GCC 4.4 and older

Commit-ID: da541b20021c781f8b65492eeaee824e729599eb Gitweb: https://git.kernel.org/tip/da541b20021c781f8b65492eeaee824e729599eb Author: Josh Poimboeuf AuthorDate: Wed, 27 Sep 2017 17:34:23 -0500 Committer: Ingo Molnar CommitDate: Thu, 28 Sep 2017

[tip:core/urgent] objtool: Support unoptimized frame pointer setup

Commit-ID: 607a4029d439cdfa258aff5da32bb9cd6ed1a66d Gitweb: https://git.kernel.org/tip/607a4029d439cdfa258aff5da32bb9cd6ed1a66d Author: Josh Poimboeuf AuthorDate: Wed, 27 Sep 2017 10:36:38 -0500 Committer: Ingo Molnar CommitDate: Thu, 28 Sep 2017

[tip:core/urgent] objtool: Skip unreachable warnings for GCC 4.4 and older

Commit-ID: da541b20021c781f8b65492eeaee824e729599eb Gitweb: https://git.kernel.org/tip/da541b20021c781f8b65492eeaee824e729599eb Author: Josh Poimboeuf AuthorDate: Wed, 27 Sep 2017 17:34:23 -0500 Committer: Ingo Molnar CommitDate: Thu, 28 Sep 2017 07:23:02 +0200 objtool: Skip

[tip:core/urgent] objtool: Support unoptimized frame pointer setup

Commit-ID: 607a4029d439cdfa258aff5da32bb9cd6ed1a66d Gitweb: https://git.kernel.org/tip/607a4029d439cdfa258aff5da32bb9cd6ed1a66d Author: Josh Poimboeuf AuthorDate: Wed, 27 Sep 2017 10:36:38 -0500 Committer: Ingo Molnar CommitDate: Thu, 28 Sep 2017 07:25:54 +0200 objtool: Support

Re: [PATCH v2 5/5] media: atmel-isc: Rework the format list

On 2017/9/27 16:03, Hans Verkuil wrote: On 09/27/2017 07:15 AM, Yang, Wenyou wrote: Hi Hans, Thank  you very much for your review. On 2017/9/25 21:24, Hans Verkuil wrote: Hi Wenyou, On 18/09/17 08:39, Wenyou Yang wrote: To improve the readability of code, split the format array into two,

Re: [PATCH v2 5/5] media: atmel-isc: Rework the format list

On 2017/9/27 16:03, Hans Verkuil wrote: On 09/27/2017 07:15 AM, Yang, Wenyou wrote: Hi Hans, Thank  you very much for your review. On 2017/9/25 21:24, Hans Verkuil wrote: Hi Wenyou, On 18/09/17 08:39, Wenyou Yang wrote: To improve the readability of code, split the format array into two,

Re: [PATCH] sparc: Provide cmpxchg64 for 32-bit builds

From: Guenter Roeck Date: Wed, 27 Sep 2017 21:55:50 -0700 > On 09/27/2017 09:38 PM, David Miller wrote: >> From: Guenter Roeck >> Date: Sun, 24 Sep 2017 10:29:31 -0700 >> >>> Fix the following build error, seen when building >>> sparc32:allmodconfig. >>>

Re: [PATCH] sparc: Provide cmpxchg64 for 32-bit builds

From: Guenter Roeck Date: Wed, 27 Sep 2017 21:55:50 -0700 > On 09/27/2017 09:38 PM, David Miller wrote: >> From: Guenter Roeck >> Date: Sun, 24 Sep 2017 10:29:31 -0700 >> >>> Fix the following build error, seen when building >>> sparc32:allmodconfig. >>> >>>

[PATCH V2] thermal/drivers/hisi: Switch to interrupt mode

At this moment, we have both the interrupt setup and the polling enabled. The interrupt does nothing more than forcing an update while the temperature is polled every second. We can do much better than that, threshold is set to 65C in the DT and the passive cooling device enters in the dance when

[PATCH V2] thermal/drivers/hisi: Switch to interrupt mode

At this moment, we have both the interrupt setup and the polling enabled. The interrupt does nothing more than forcing an update while the temperature is polled every second. We can do much better than that, threshold is set to 65C in the DT and the passive cooling device enters in the dance when

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

Dmitry, On Fri, Sep 15, 2017 at 3:30 PM, Dmitry Torokhov wrote: > On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski > wrote: >> On 09/15/2017 08:34 PM, Dmitry Torokhov wrote: >>> On Thu, Sep 14, 2017 at 1:58 PM, Pavel Machek

Re: Vibrations in input vs. LED was Re: [PATCH v2 0/3] led: ledtrig-transient: add support for hrtimer

Dmitry, On Fri, Sep 15, 2017 at 3:30 PM, Dmitry Torokhov wrote: > On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski > wrote: >> On 09/15/2017 08:34 PM, Dmitry Torokhov wrote: >>> On Thu, Sep 14, 2017 at 1:58 PM, Pavel Machek wrote: On Thu 2017-09-14 21:31:31, Jacek Anaszewski wrote: >

Re: [PATCH net-next 0/3] support changing steering policies in tuntap

On Wed, Sep 27, 2017 at 4:25 PM, Willem de Bruijn wrote: >>> In the future, both simple and sophisticated policy like RSS or other guest >>> driven steering policies could be done on top. >> >> IMHO there should be a more practical example before adding all this

Re: [PATCH net-next 0/3] support changing steering policies in tuntap

On Wed, Sep 27, 2017 at 4:25 PM, Willem de Bruijn wrote: >>> In the future, both simple and sophisticated policy like RSS or other guest >>> driven steering policies could be done on top. >> >> IMHO there should be a more practical example before adding all this >> indirection. And it would be

Re: DMA error when sg->offset value is greater than PAGE_SIZE in Intel IOMMU

On 28-09-2017 03:43, Casey Leedom wrote: > | From: Raj, Ashok > | Sent: Wednesday, September 27, 2017 12:07 PM > | > | looking at the debug output i got from Harsh it still looks like a bug in > | the code. > | > | [ 538.284589] __domain_mapping nr_pages 0x1 > | [

Re: DMA error when sg->offset value is greater than PAGE_SIZE in Intel IOMMU

On 28-09-2017 03:43, Casey Leedom wrote: > | From: Raj, Ashok > | Sent: Wednesday, September 27, 2017 12:07 PM > | > | looking at the debug output i got from Harsh it still looks like a bug in > | the code. > | > | [ 538.284589] __domain_mapping nr_pages 0x1 > | [ 538.284600] __domain_mapping

[PATCH V2] power: Use a more common logging style

Convert printks to pr_. Miscellanea: o Use pr_fmt with "PM:" and remove "PM: " from format strings o Coalesce format strings and realign format arguments o Convert an embedded incorrect function name to "%s: ", __func__ o Convert a couple multi-line formats to multiple pr_ calls Signed-off-by:

[PATCH V2] power: Use a more common logging style

Convert printks to pr_. Miscellanea: o Use pr_fmt with "PM:" and remove "PM: " from format strings o Coalesce format strings and realign format arguments o Convert an embedded incorrect function name to "%s: ", __func__ o Convert a couple multi-line formats to multiple pr_ calls Signed-off-by:

linux-next: build failure after merge of the drm tree

Hi Dave, After merging the drm tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/gpu/drm/amd/powerplay/smumgr/ci_smc.o:(.opd+0xd8): multiple definition of `ci_send_msg_to_smc' drivers/gpu/drm/radeon/ci_smc.o:(.opd+0xc0): first defined here

linux-next: build failure after merge of the drm tree

Hi Dave, After merging the drm tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/gpu/drm/amd/powerplay/smumgr/ci_smc.o:(.opd+0xd8): multiple definition of `ci_send_msg_to_smc' drivers/gpu/drm/radeon/ci_smc.o:(.opd+0xc0): first defined here

Re: [PATCH] sparc: Provide cmpxchg64 for 32-bit builds

On 09/27/2017 09:38 PM, David Miller wrote: From: Guenter Roeck Date: Sun, 24 Sep 2017 10:29:31 -0700 Fix the following build error, seen when building sparc32:allmodconfig. drivers/net/ethernet/intel/i40e/i40e_ethtool.c: In function 'i40e_set_priv_flags':

Re: [PATCH] sparc: Provide cmpxchg64 for 32-bit builds

On 09/27/2017 09:38 PM, David Miller wrote: From: Guenter Roeck Date: Sun, 24 Sep 2017 10:29:31 -0700 Fix the following build error, seen when building sparc32:allmodconfig. drivers/net/ethernet/intel/i40e/i40e_ethtool.c: In function 'i40e_set_priv_flags':

Re: [PATCH v6 05/11] dt-bindings: net: dwmac-sun8i: update documentation about integrated PHY

On 09/27/2017 12:34 AM, Corentin Labbe wrote: > This patch add documentation about the MDIO switch used on sun8i-h3-emac > for integrated PHY. > > Signed-off-by: Corentin Labbe > --- > .../devicetree/bindings/net/dwmac-sun8i.txt| 138 > +++--

Re: [PATCH v6 05/11] dt-bindings: net: dwmac-sun8i: update documentation about integrated PHY

On 09/27/2017 12:34 AM, Corentin Labbe wrote: > This patch add documentation about the MDIO switch used on sun8i-h3-emac > for integrated PHY. > > Signed-off-by: Corentin Labbe > --- > .../devicetree/bindings/net/dwmac-sun8i.txt| 138 > +++-- > 1 file changed, 126

Re: [PATCH] sparc: time: Remove unneeded linux/miscdevice.h include

From: Corentin Labbe Date: Mon, 18 Sep 2017 19:58:21 +0200 > arch/sparc/kernel/time_64.c does not contain any miscdevice so the > inclusion of linux/miscdevice.h is unnecessary. > > Signed-off-by: Corentin Labbe Applied.

Re: [PATCH] sparc64: mmu_context: Add missing include files

From: Guenter Roeck Date: Sun, 10 Sep 2017 13:44:47 -0700 > Fix the following build errors. > > In file included from arch/sparc/include/asm/mmu_context.h:4:0, > from include/linux/mmu_context.h:4, >from

Re: [PATCH] sbus: char: Move D7S_MINOR to include/linux/miscdevice.h

From: Corentin Labbe Date: Mon, 18 Sep 2017 20:10:36 +0200 > This patch move the define for D7S_MINOR to include/linux/miscdevice.h. > It's better that all minor number are in the same place. > > Signed-off-by: Corentin Labbe Applied.

Re: [PATCH] sparc: time: Remove unneeded linux/miscdevice.h include

From: Corentin Labbe Date: Mon, 18 Sep 2017 19:58:21 +0200 > arch/sparc/kernel/time_64.c does not contain any miscdevice so the > inclusion of linux/miscdevice.h is unnecessary. > > Signed-off-by: Corentin Labbe Applied.

Re: [PATCH] sparc64: mmu_context: Add missing include files

From: Guenter Roeck Date: Sun, 10 Sep 2017 13:44:47 -0700 > Fix the following build errors. > > In file included from arch/sparc/include/asm/mmu_context.h:4:0, > from include/linux/mmu_context.h:4, >from drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h:29, >

Re: [PATCH] sbus: char: Move D7S_MINOR to include/linux/miscdevice.h

From: Corentin Labbe Date: Mon, 18 Sep 2017 20:10:36 +0200 > This patch move the define for D7S_MINOR to include/linux/miscdevice.h. > It's better that all minor number are in the same place. > > Signed-off-by: Corentin Labbe Applied.

Re: [PATCH v6 11/11] of: mdio: Prevent of_mdiobus_register from scanning mdio-mux nodes

On 09/27/2017 07:12 AM, Andrew Lunn wrote: > On Wed, Sep 27, 2017 at 09:34:14AM +0200, Corentin Labbe wrote: >> Each child node of an MDIO node is scanned as a PHY when calling >> of_mdiobus_register() givint the following result: >> [ 18.175379] mdio_bus stmmac-0:

Re: [PATCH v6 11/11] of: mdio: Prevent of_mdiobus_register from scanning mdio-mux nodes

On 09/27/2017 07:12 AM, Andrew Lunn wrote: > On Wed, Sep 27, 2017 at 09:34:14AM +0200, Corentin Labbe wrote: >> Each child node of an MDIO node is scanned as a PHY when calling >> of_mdiobus_register() givint the following result: >> [ 18.175379] mdio_bus stmmac-0:

[PATCH v3 2/6] perf record: Get the first sample time and last sample time

In perf record, it's walked on all samples yet. So it's very easy to get the first/last samples and save the time to perf file header via the function write_sample_time(). In later, perf report/script will fetch the time from perf file header. Change log: --- v3: Remove the definitions

[PATCH v3 2/6] perf record: Get the first sample time and last sample time

In perf record, it's walked on all samples yet. So it's very easy to get the first/last samples and save the time to perf file header via the function write_sample_time(). In later, perf report/script will fetch the time from perf file header. Change log: --- v3: Remove the definitions

[PATCH v3 3/6] perf util: Create function to parse time percent

Current perf report/script/... have a --time option to limit the time range of output. But right now it only supports absolute time. For easy using, now it can support a percent of time usage. For example: 1. Select the second 10% time slice perf report --time 10%/2 2. Select from 0% to 10%

[PATCH v3 5/6] perf report: support time percent and multiple time ranges

perf report has a --time option to limit the time range of output. It only supports absolute time. Now this option is extended to support multiple time ranges and support the percent of time. For example: 1. Select the first and second 10% time slices perf report --time 10%/1,10%/2 2. Select

[PATCH v3 3/6] perf util: Create function to parse time percent

Current perf report/script/... have a --time option to limit the time range of output. But right now it only supports absolute time. For easy using, now it can support a percent of time usage. For example: 1. Select the second 10% time slice perf report --time 10%/2 2. Select from 0% to 10%

[PATCH v3 5/6] perf report: support time percent and multiple time ranges

perf report has a --time option to limit the time range of output. It only supports absolute time. Now this option is extended to support multiple time ranges and support the percent of time. For example: 1. Select the first and second 10% time slices perf report --time 10%/1,10%/2 2. Select

[PATCH v3 6/6] perf script: support time percent and multiple time ranges

perf script has a --time option to limit the time range of output. It only supports absolute time. Now this option is extended to support multiple time ranges and support the percent of time. For example: 1. Select the first and second 10% time slices perf script --time 10%/1,10%/2 2.

[PATCH v3 1/6] perf header: Record first sample time and last sample time in perf file header

perf report/script/... have a --time option to limit the time range of output. That's very useful to slice large traces, e.g. when processing the output of perf script for some analysis. But right now --time only supports absolute time. Also there is no fast way to get the start/end times of a

[PATCH v3 6/6] perf script: support time percent and multiple time ranges

perf script has a --time option to limit the time range of output. It only supports absolute time. Now this option is extended to support multiple time ranges and support the percent of time. For example: 1. Select the first and second 10% time slices perf script --time 10%/1,10%/2 2.

[PATCH v3 1/6] perf header: Record first sample time and last sample time in perf file header

perf report/script/... have a --time option to limit the time range of output. That's very useful to slice large traces, e.g. when processing the output of perf script for some analysis. But right now --time only supports absolute time. Also there is no fast way to get the start/end times of a

[PATCH v3 0/6] perf report/script: Support percent and multiple range in --time option

v3: --- 1. Move the definitions of first_sample_time/last_sample_time from perf_session and struct record to perf_evlist and update the related code. v2: --- 1. This patch creates a new header feature type HEADER_SAMPLE_TIME and related ops. Save the first sample time and the last sample

[PATCH v3 4/6] perf util: Create function to perform multiple time range checking

Previous patch supports the multiple time range. For example, select the first and second 10% time slices. perf report --time 10%/1,10%/2 We need a function to check if a timestamp is in the ranges of [0, 10%) and [10%, 20%]. Note that it includes the last element in [10%, 20%] but it doesn't

[PATCH v3 4/6] perf util: Create function to perform multiple time range checking

Previous patch supports the multiple time range. For example, select the first and second 10% time slices. perf report --time 10%/1,10%/2 We need a function to check if a timestamp is in the ranges of [0, 10%) and [10%, 20%]. Note that it includes the last element in [10%, 20%] but it doesn't

[PATCH v3 0/6] perf report/script: Support percent and multiple range in --time option

v3: --- 1. Move the definitions of first_sample_time/last_sample_time from perf_session and struct record to perf_evlist and update the related code. v2: --- 1. This patch creates a new header feature type HEADER_SAMPLE_TIME and related ops. Save the first sample time and the last sample

linux-next: build failure after merge of the ipmi tree

Hi Corey, After merging the ipmi tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/char/ipmi/ipmi_si_platform.c:360:1: warning: data definition has no type or storage class MODULE_DEVICE_TABLE(of, of_ipmi_match); ^ drivers/char/ipmi/ipmi_si_platform.c:360:1:

linux-next: build failure after merge of the ipmi tree

Hi Corey, After merging the ipmi tree, today's linux-next build (powerpc allyesconfig) failed like this: drivers/char/ipmi/ipmi_si_platform.c:360:1: warning: data definition has no type or storage class MODULE_DEVICE_TABLE(of, of_ipmi_match); ^ drivers/char/ipmi/ipmi_si_platform.c:360:1:

Re: [PATCH] sparc: Provide cmpxchg64 for 32-bit builds

From: Guenter Roeck Date: Sun, 24 Sep 2017 10:29:31 -0700 > Fix the following build error, seen when building sparc32:allmodconfig. > > drivers/net/ethernet/intel/i40e/i40e_ethtool.c: > In function 'i40e_set_priv_flags': >

Re: [PATCH] sparc: Provide cmpxchg64 for 32-bit builds

From: Guenter Roeck Date: Sun, 24 Sep 2017 10:29:31 -0700 > Fix the following build error, seen when building sparc32:allmodconfig. > > drivers/net/ethernet/intel/i40e/i40e_ethtool.c: > In function 'i40e_set_priv_flags': > drivers/net/ethernet/intel/i40e/i40e_ethtool.c:4150:2: error: >

[PATCH v2] irq/generic-chip: Don't replace domain's name

Currently we are replacing domain's name with irq chip's name when allocating generic chips. When the old domain's name is allocated, it would cause memory leak. Even worse the domain framework would try to free the wrong name later. Fixes: d59f6617eef0 ("genirq: Allow fwnode to carry name

[PATCH v2] irq/generic-chip: Don't replace domain's name

Currently we are replacing domain's name with irq chip's name when allocating generic chips. When the old domain's name is allocated, it would cause memory leak. Even worse the domain framework would try to free the wrong name later. Fixes: d59f6617eef0 ("genirq: Allow fwnode to carry name

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

On 2017/09/28 6:46, Yang Shi wrote: > Changelog v7 —> v8: > * Adopted Michal’s suggestion to dump unreclaim slab info when unreclaimable > slabs amount > total user memory. Not only in oom panic path. Holding slab_mutex inside dump_unreclaimable_slab() was refrained since V2 because there are

Re: [PATCH 0/2 v8] oom: capture unreclaimable slab info in oom message

On 2017/09/28 6:46, Yang Shi wrote: > Changelog v7 —> v8: > * Adopted Michal’s suggestion to dump unreclaim slab info when unreclaimable > slabs amount > total user memory. Not only in oom panic path. Holding slab_mutex inside dump_unreclaimable_slab() was refrained since V2 because there are

Re: [PATCH] irq/generic-chip: Fix memory leak of domain->name

Hi Thomas, On 09/28/2017 11:18 AM, jeffy wrote: I don't think that this is the proper thing to do. There is no reason why the domain should have the same name as the irq chip. So we rather should do: if (!d->name) d->name = name; Along with a proper comment. that is better, will

Re: [PATCH] irq/generic-chip: Fix memory leak of domain->name

Hi Thomas, On 09/28/2017 11:18 AM, jeffy wrote: I don't think that this is the proper thing to do. There is no reason why the domain should have the same name as the irq chip. So we rather should do: if (!d->name) d->name = name; Along with a proper comment. that is better, will

Re: [PATCH for-next 05/20] RDMA/hns: Add command queue support for hip08 RoCE driver

On 2017/9/27 20:41, Doug Ledford wrote: On Wed, 2017-09-27 at 08:21 -0400, Doug Ledford wrote: And if you argee, after this patchset has been accepted we will send a following up patch : In hns_roce_cmq_send function, replace usleep_range(1000, 2000); with the following

Re: [PATCH for-next 05/20] RDMA/hns: Add command queue support for hip08 RoCE driver

On 2017/9/27 20:41, Doug Ledford wrote: On Wed, 2017-09-27 at 08:21 -0400, Doug Ledford wrote: And if you argee, after this patchset has been accepted we will send a following up patch : In hns_roce_cmq_send function, replace usleep_range(1000, 2000); with the following

[PATCH for-next 8/9] RDMA/hns: Remove unused struct members in hns-abi.h

From: Lijun Ou This patch mainly deletes some unused struct members for hns_roce_ib_create_qp in order to match libhns, because the num of struct members of hns_roce_ib_create_qp must be the same with hns_roce_create_qp in libhns. Signed-off-by: Lijun Ou

[PATCH for-next 8/9] RDMA/hns: Remove unused struct members in hns-abi.h

From: Lijun Ou This patch mainly deletes some unused struct members for hns_roce_ib_create_qp in order to match libhns, because the num of struct members of hns_roce_ib_create_qp must be the same with hns_roce_create_qp in libhns. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier)

[PATCH for-next 6/9] RDMA/hns: Add return statement when checking error in hns_roce_v1_mr_free_work_fn

After the loop in hns_roce_v1_mr_free_work_fn function, it is possible that the local variable named hr_qp is NULL, the operation "hr_qp->qpn" will result in the exception. As a result, we add return statement when checking error. This patch fixes the smatch error as below:

[PATCH for-next 6/9] RDMA/hns: Add return statement when checking error in hns_roce_v1_mr_free_work_fn

After the loop in hns_roce_v1_mr_free_work_fn function, it is possible that the local variable named hr_qp is NULL, the operation "hr_qp->qpn" will result in the exception. As a result, we add return statement when checking error. This patch fixes the smatch error as below:

[PATCH for-next 5/9] RDMA/hns: Set rdma_ah_attr type for querying qp

From: Lijun Ou When querying qp, It needs to return RoCE device ah_attr type that may be specific to RoCE devices. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) Signed-off-by: Shaobo Xu ---

[PATCH for-next 5/9] RDMA/hns: Set rdma_ah_attr type for querying qp

From: Lijun Ou When querying qp, It needs to return RoCE device ah_attr type that may be specific to RoCE devices. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) Signed-off-by: Shaobo Xu --- drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 2 ++

[PATCH for-next 0/9] Bug fixes & Code improvements in hip06 and hip08 RoCE driver

This patch-set introduces some bug fixes and code improvements for hip06 and hip08 RoCE driver. It includes a patch for fixing the assign algorithm of qp_attr->max_rd_atomic and qp_attr->max_dest_rd_atomic, three patches for static check errors, one for setting attr mask, one for returning RoCE

[PATCH for-next 0/9] Bug fixes & Code improvements in hip06 and hip08 RoCE driver

This patch-set introduces some bug fixes and code improvements for hip06 and hip08 RoCE driver. It includes a patch for fixing the assign algorithm of qp_attr->max_rd_atomic and qp_attr->max_dest_rd_atomic, three patches for static check errors, one for setting attr mask, one for returning RoCE

[PATCH for-next 9/9] RDMA/hns: Replace usleep_range with udelay when checking command status

From: Lijun Ou It replaces usleep_range with udelay to avoid using usleep_range function in spin_lock_bh spin region, because it probably cause calltrace. BUG: scheduling while atomic: insmod/1428/0x0002 Modules linked in: hns-roce-hw-v2(+) hns_roce rdma_ucm rdma_cm

[PATCH for-next 9/9] RDMA/hns: Replace usleep_range with udelay when checking command status

From: Lijun Ou It replaces usleep_range with udelay to avoid using usleep_range function in spin_lock_bh spin region, because it probably cause calltrace. BUG: scheduling while atomic: insmod/1428/0x0002 Modules linked in: hns-roce-hw-v2(+) hns_roce rdma_ucm rdma_cm iw_cm ib_uverbs ib_cm

[PATCH for-next 3/9] RDMA/hns: Add return statement when kzalloc return NULL in hns_roce_v1_recreate_lp_qp

From: Lijun Ou When lp_qp_work is NULL, it should be returned ENOMEM. This patch mainly fixes it. Ihis patch fixes the smatch error as below: drivers/infiniband/hw/hns/hns_roce_hw_v1.c:918 hns_roce_v1_recreate_lp_qp() error: potential null dereference 'lp_qp_work'. (kzalloc

[PATCH for-next 3/9] RDMA/hns: Add return statement when kzalloc return NULL in hns_roce_v1_recreate_lp_qp

From: Lijun Ou When lp_qp_work is NULL, it should be returned ENOMEM. This patch mainly fixes it. Ihis patch fixes the smatch error as below: drivers/infiniband/hw/hns/hns_roce_hw_v1.c:918 hns_roce_v1_recreate_lp_qp() error: potential null dereference 'lp_qp_work'. (kzalloc returns null)

[PATCH for-next 2/9] RDMA/hns: Factor out the code for checking sdb status into a new function

From: Lijun Ou It mainly places the lines for checking send doorbell status into a special functions. As a result, we can directly call it in check_qp_db_process_status function and keep consistent indenting style. It fixes: 5f110ac4bed8 ("IB/hns: Fix for checkpatch.pl

[PATCH for-next 1/9] RDMA/hns: Modify the value with rd_rd of qp_attr

From: Lijun Ou The value of max_rd_atomic and max_dest_rd_atomic in query_qp are incorrect. It should be assigned by left shifting of the bit in hip06 SoC. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) ---

[PATCH for-next 2/9] RDMA/hns: Factor out the code for checking sdb status into a new function

From: Lijun Ou It mainly places the lines for checking send doorbell status into a special functions. As a result, we can directly call it in check_qp_db_process_status function and keep consistent indenting style. It fixes: 5f110ac4bed8 ("IB/hns: Fix for checkpatch.pl comment style) The

[PATCH for-next 1/9] RDMA/hns: Modify the value with rd_rd of qp_attr

From: Lijun Ou The value of max_rd_atomic and max_dest_rd_atomic in query_qp are incorrect. It should be assigned by left shifting of the bit in hip06 SoC. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) --- drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 4 ++-- 1 file changed, 2

Re: [PATCH v2 3/5] clk: aspeed: Add platform driver and register PLLs

On Wed, Sep 27, 2017 at 5:34 PM, Andrew Jeffery wrote: > On Wed, 2017-09-27 at 16:13 +1000, Joel Stanley wrote: >> > > + div_table, >> > >> > This doesn't seem to be correct. There's the problem of 0b000 and 0b001 >> > mapping >> > the same value of 2 for the

Re: [PATCH v2 3/5] clk: aspeed: Add platform driver and register PLLs

On Wed, Sep 27, 2017 at 5:34 PM, Andrew Jeffery wrote: > On Wed, 2017-09-27 at 16:13 +1000, Joel Stanley wrote: >> > > + div_table, >> > >> > This doesn't seem to be correct. There's the problem of 0b000 and 0b001 >> > mapping >> > the same value of 2 for the AST2500, whose

[PATCH for-next 7/9] RDMA/hns: Remove unnecessarily calling unregister_inetaddr_notifier function

From: Lijun Ou When the driver doesn't call register_inetaddr_notifier function, it need not call unregister_inetaddr_notifier to unregister inet addr. This patch fixes it. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier)

[PATCH for-next 7/9] RDMA/hns: Remove unnecessarily calling unregister_inetaddr_notifier function

From: Lijun Ou When the driver doesn't call register_inetaddr_notifier function, it need not call unregister_inetaddr_notifier to unregister inet addr. This patch fixes it. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) Signed-off-by: Shaobo Xu ---

[PATCH for-next 4/9] RDMA/hns: Set mask for destination qp field of qp context assignment

From: Lijun Ou When only set IB_QP_DEST_QPN flag for attr_mask, the operation of assigning the dest_qp_num for dest_qp field of qp context is valid. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) Signed-off-by: Shaobo Xu

[PATCH for-next 4/9] RDMA/hns: Set mask for destination qp field of qp context assignment

From: Lijun Ou When only set IB_QP_DEST_QPN flag for attr_mask, the operation of assigning the dest_qp_num for dest_qp field of qp context is valid. Signed-off-by: Lijun Ou Signed-off-by: Wei Hu (Xavier) Signed-off-by: Shaobo Xu --- drivers/infiniband/hw/hns/hns_roce_hw_v1.c | 9 +

Re: [PATCH V2] PM / OPP: Move the OPP directory out of power/

On 27-09-17, 19:49, Rafael J. Wysocki wrote: > Actually, it is even listed in that MAINTAINERS entry already, unless > you prefer to use a different one that is. :-) Yeah, that will remain the same. Thanks. -- viresh

Re: [PATCH V2] PM / OPP: Move the OPP directory out of power/

On 27-09-17, 19:49, Rafael J. Wysocki wrote: > Actually, it is even listed in that MAINTAINERS entry already, unless > you prefer to use a different one that is. :-) Yeah, that will remain the same. Thanks. -- viresh

[PATCH 1/2] ARM: dts: Fix I2C repeated start issue on Armada-38x

All the Armada 38x(380, 385, 388) have a silicon issue in the I2C controller which violates the I2C repeated start timing (errata FE-8471889). i2c-mv64xxx driver handles this errata based on the compatible string "marvell,mv78230-a0-i2c". This patch activates the "marvell,mv78230-a0-i2c"

[PATCH 1/2] ARM: dts: Fix I2C repeated start issue on Armada-38x

All the Armada 38x(380, 385, 388) have a silicon issue in the I2C controller which violates the I2C repeated start timing (errata FE-8471889). i2c-mv64xxx driver handles this errata based on the compatible string "marvell,mv78230-a0-i2c". This patch activates the "marvell,mv78230-a0-i2c"

[PATCH 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c"

This commit modifies the documentation for "marvell,mv78230-a0-i2c" compatible string. The "marvell,mv78230-a0-i2c" compatible string enables the workaround for an i2c repeated start timing violation, but unlike "marvell,mv78230-i2c" it disables the i2c offload support. This is applicable to a

[PATCH 2/2] dt-bindings: i2c: Update documentation for "mv78230-a0-i2c"

This commit modifies the documentation for "marvell,mv78230-a0-i2c" compatible string. The "marvell,mv78230-a0-i2c" compatible string enables the workaround for an i2c repeated start timing violation, but unlike "marvell,mv78230-i2c" it disables the i2c offload support. This is applicable to a

[PATCH v3 3/8] platform/x86: dell-wmi-smbios: Use Dell WMI descriptor check

The Dell WMI descriptor check is used as an indication that WMI calls are safe to run both when used with the notification ASL/GUID pair as well as the SMBIOS calling ASL/GUID pair. As some code in dell-wmi-smbios is already a prerequisite for dell-wmi, move the code for performing the descriptor

[PATCH 0/2] Fix I2C repeated start timing violation on Armada-38x.

All the Armada 38x(380, 385, 388) have a silicon issue in the I2C controller which violates the I2C repeated start timing (errata FE-8471889). Activate the compatible string "marvell,mv78230-a0-i2c" in the device tree file of Armada-38x to fx this errata (FE-8471889). Updated the Documentation

[PATCH v3 3/8] platform/x86: dell-wmi-smbios: Use Dell WMI descriptor check

The Dell WMI descriptor check is used as an indication that WMI calls are safe to run both when used with the notification ASL/GUID pair as well as the SMBIOS calling ASL/GUID pair. As some code in dell-wmi-smbios is already a prerequisite for dell-wmi, move the code for performing the descriptor

[PATCH 0/2] Fix I2C repeated start timing violation on Armada-38x.

All the Armada 38x(380, 385, 388) have a silicon issue in the I2C controller which violates the I2C repeated start timing (errata FE-8471889). Activate the compatible string "marvell,mv78230-a0-i2c" in the device tree file of Armada-38x to fx this errata (FE-8471889). Updated the Documentation

[PATCH v3 7/8] platform/x86: Kconfig: Change the default settings for dell-wmi-smbios

The dell-wmi-smbios driver should be enabled by default when ACPI_WMI is enabled (like many other WMI drivers). Signed-off-by: Mario Limonciello --- drivers/platform/x86/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/platform/x86/Kconfig

[PATCH v3 0/8] Introduce support for Dell SMBIOS over WMI

The existing way that the dell-smbios helper module and associated other drivers (dell-laptop, dell-wmi) communicate with the platform really isn't secure. It requires creating a buffer in physical DMA32 memory space and passing that to the platform via SMM. Since the platform got a physical

[PATCH v3 2/8] platform/x86: dell-smbios: Introduce a WMI-ACPI interface

The driver currently uses an SMI interface which grants direct access to physical memory to the firmware SMM methods via a pointer. Now add a WMI-ACPI interface that is detected by WMI probe and preferred over the SMI interface. Changing this to operate over WMI-ACPI will use an ACPI

[PATCH v3 4/8] platform/x86: wmi: create character devices when requested by drivers

For WMI operations that are only Set or Query read or write sysfs attributes created by WMI vendor drivers make sense. For other WMI operations that are run on Method, there needs to be a way to guarantee to userspace that the results from the method call belong to the data request to the method

  1   2   3   4   5   6   7   8   9   10   >