Re: [PATCH 3.2 085/115] veth: don???t modify ip_summed; doing so treats packets with bad checksums as good.

On Sat, Apr 30, 2016 at 03:43:51PM -0700, Ben Greear wrote: > On 04/30/2016 03:01 PM, Vijay Pandurangan wrote: > > Consider: > > > > - App A sends out corrupt packets 50% of the time and discards inbound > > data. (...) > How can you make a generic app C know how to do this? The path could be,

Re: [PATCH 3.2 085/115] veth: don???t modify ip_summed; doing so treats packets with bad checksums as good.

On Sat, Apr 30, 2016 at 03:43:51PM -0700, Ben Greear wrote: > On 04/30/2016 03:01 PM, Vijay Pandurangan wrote: > > Consider: > > > > - App A sends out corrupt packets 50% of the time and discards inbound > > data. (...) > How can you make a generic app C know how to do this? The path could be,

[PATCH RESEND 01/12] sh: Fix typo

BL is 1 in this time. Signed-off-by: Yoshinori Sato --- arch/sh/kernel/head_32.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/sh/kernel/head_32.S b/arch/sh/kernel/head_32.S index 974bc15..14da954 100644 --- a/arch/sh/kernel/head_32.S +++

[PATCH RESEND 01/12] sh: Fix typo

BL is 1 in this time. Signed-off-by: Yoshinori Sato --- arch/sh/kernel/head_32.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/sh/kernel/head_32.S b/arch/sh/kernel/head_32.S index 974bc15..14da954 100644 --- a/arch/sh/kernel/head_32.S +++ b/arch/sh/kernel/head_32.S @@

[PATCH RESEND 03/12] sh: Disable board specific code in OF mode

Board specific code conflict on of-generic. Signed-off-by: Yoshinori Sato --- arch/sh/Makefile | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/sh/Makefile b/arch/sh/Makefile index bf5b3f5..8ff943b 100644 --- a/arch/sh/Makefile +++

[PATCH RESEND 04/12] sh: Drop CPU specific setup on OF mode

CPU specific set conflict of-generic. Signed-off-by: Yoshinori Sato --- arch/sh/kernel/cpu/sh4/Makefile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/sh/kernel/cpu/sh4/Makefile b/arch/sh/kernel/cpu/sh4/Makefile index 3a1dbc7..b822c0c 100644 ---

Fail to build tools/all

Hi guys: I encountered a build error when running "make V=1 tools/all". Shall we write a patch to fix it? The following is error log. start == commit 05cf8077e54b20dddb756eaa26f3aeb5c38dd3cf Merge: cf78031 db5dd0d

[PATCH RESEND 03/12] sh: Disable board specific code in OF mode

Board specific code conflict on of-generic. Signed-off-by: Yoshinori Sato --- arch/sh/Makefile | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/sh/Makefile b/arch/sh/Makefile index bf5b3f5..8ff943b 100644 --- a/arch/sh/Makefile +++ b/arch/sh/Makefile @@ -130,6 +130,9 @@

[PATCH RESEND 04/12] sh: Drop CPU specific setup on OF mode

CPU specific set conflict of-generic. Signed-off-by: Yoshinori Sato --- arch/sh/kernel/cpu/sh4/Makefile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/sh/kernel/cpu/sh4/Makefile b/arch/sh/kernel/cpu/sh4/Makefile index 3a1dbc7..b822c0c 100644 --- a/arch/sh/kernel/cpu/sh4/Makefile +++

Fail to build tools/all

Hi guys: I encountered a build error when running "make V=1 tools/all". Shall we write a patch to fix it? The following is error log. start == commit 05cf8077e54b20dddb756eaa26f3aeb5c38dd3cf Merge: cf78031 db5dd0d

[PATCH RESEND 11/12] sh: I/O DATA HDL-U defconfig (DT mode)

Signed-off-by: Yoshinori Sato --- arch/sh/configs/landisk-dt_defconfig | 100 +++ 1 file changed, 100 insertions(+) create mode 100644 arch/sh/configs/landisk-dt_defconfig diff --git a/arch/sh/configs/landisk-dt_defconfig

[PATCH RESEND 11/12] sh: I/O DATA HDL-U defconfig (DT mode)

Signed-off-by: Yoshinori Sato --- arch/sh/configs/landisk-dt_defconfig | 100 +++ 1 file changed, 100 insertions(+) create mode 100644 arch/sh/configs/landisk-dt_defconfig diff --git a/arch/sh/configs/landisk-dt_defconfig b/arch/sh/configs/landisk-dt_defconfig

[PATCH RESEND 10/12] sh: I/O DATA HDL-U (aka landisk) support dts

Signed-off-by: Yoshinori Sato --- arch/sh/boot/dts/landisk.dts | 150 +++ 1 file changed, 150 insertions(+) create mode 100644 arch/sh/boot/dts/landisk.dts diff --git a/arch/sh/boot/dts/landisk.dts

[PATCH RESEND 09/12] sh: Add I/O DATA HDL-U support drivers.

PCI host fixup and external interrupt controller. Signed-off-by: Yoshinori Sato --- .../interrupt-controller/iodata-landisk.txt| 28 + drivers/irqchip/irq-io-landisk.c | 71 ++ drivers/pci/host/pci-sh7751.c

[PATCH RESEND 09/12] sh: Add I/O DATA HDL-U support drivers.

PCI host fixup and external interrupt controller. Signed-off-by: Yoshinori Sato --- .../interrupt-controller/iodata-landisk.txt| 28 + drivers/irqchip/irq-io-landisk.c | 71 ++ drivers/pci/host/pci-sh7751.c | 25

[PATCH RESEND 10/12] sh: I/O DATA HDL-U (aka landisk) support dts

Signed-off-by: Yoshinori Sato --- arch/sh/boot/dts/landisk.dts | 150 +++ 1 file changed, 150 insertions(+) create mode 100644 arch/sh/boot/dts/landisk.dts diff --git a/arch/sh/boot/dts/landisk.dts b/arch/sh/boot/dts/landisk.dts new file mode 100644

[PATCH RESEND 08/12] intc: sh: Renesas Super H INTC driver

SuperH IPR based driver. Signed-off-by: Yoshinori Sato --- .../interrupt-controller/renesas,sh7751-intc.txt | 25 drivers/irqchip/Kconfig| 5 + drivers/irqchip/Makefile | 1 +

[PATCH RESEND 06/12] clk: sh: SH7750/51 PLL and divider clock driver

Signed-off-by: Yoshinori Sato --- .../bindings/clock/renesas,sh-div-clock.txt| 24 ++ .../bindings/clock/renesas,sh7750-div-clock.txt| 27 ++ .../bindings/clock/renesas,sh7750-pll-clock.txt| 26 ++ drivers/clk/Kconfig

[PATCH RESEND 08/12] intc: sh: Renesas Super H INTC driver

SuperH IPR based driver. Signed-off-by: Yoshinori Sato --- .../interrupt-controller/renesas,sh7751-intc.txt | 25 drivers/irqchip/Kconfig| 5 + drivers/irqchip/Makefile | 1 + drivers/irqchip/irq-renesas-shipr.c|

[PATCH RESEND 06/12] clk: sh: SH7750/51 PLL and divider clock driver

Signed-off-by: Yoshinori Sato --- .../bindings/clock/renesas,sh-div-clock.txt| 24 ++ .../bindings/clock/renesas,sh7750-div-clock.txt| 27 ++ .../bindings/clock/renesas,sh7750-pll-clock.txt| 26 ++ drivers/clk/Kconfig| 1 +

[PATCH RESEND 12/12] of: Add sh support

sh fdt access in VA. But memory reservation use PA. So sh need convert to PA. Signed-off-by: Yoshinori Sato --- drivers/of/fdt.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c index 3349d2a..fb357be 100644 ---

[PATCH RESEND 05/12] sh: DeviceTree support update

Changes bellow - FDT setup timing fix. - chosen/bootargs support. - zImage support. - DT binding helper macro. Signed-off-by: Yoshinori Sato --- arch/sh/boards/of-generic.c| 23 +++--- arch/sh/boot/compressed/head_32.S

[PATCH RESEND 07/12] pci: sh: SH7751 PCI host bridge driver

Signed-off-by: Yoshinori Sato --- .../devicetree/bindings/pci/sh7751-pci.txt | 51 drivers/pci/host/Kconfig | 7 + drivers/pci/host/Makefile | 1 + drivers/pci/host/pci-sh7751.c

[PATCH RESEND 12/12] of: Add sh support

sh fdt access in VA. But memory reservation use PA. So sh need convert to PA. Signed-off-by: Yoshinori Sato --- drivers/of/fdt.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c index 3349d2a..fb357be 100644 --- a/drivers/of/fdt.c +++ b/drivers/of/fdt.c

[PATCH RESEND 05/12] sh: DeviceTree support update

Changes bellow - FDT setup timing fix. - chosen/bootargs support. - zImage support. - DT binding helper macro. Signed-off-by: Yoshinori Sato --- arch/sh/boards/of-generic.c| 23 +++--- arch/sh/boot/compressed/head_32.S | 5 +++--

[PATCH RESEND 07/12] pci: sh: SH7751 PCI host bridge driver

Signed-off-by: Yoshinori Sato --- .../devicetree/bindings/pci/sh7751-pci.txt | 51 drivers/pci/host/Kconfig | 7 + drivers/pci/host/Makefile | 1 + drivers/pci/host/pci-sh7751.c | 321 +

[PATCH RESEND 02/12] sh: Config update for OF mode

DeviceTreee support is use liner IRQ. And use generic function (clock / io / IRQ). Signed-off-by: Yoshinori Sato --- arch/sh/Kconfig | 26 +++--- arch/sh/boards/Kconfig | 4 arch/sh/drivers/Makefile| 2 ++

[PATCH RESEND 00/12] SH: landisk convert to devicetree

SH get devicetree support. But it not working on existing H/W. IO-DATA HDL-U (aka landisk) currentry supported. This H/W like SH7751 evalution board. It's a best to use this as a change base H/W. Yoshinori Sato (12): sh: Fix typo sh: Config update for OF mode sh: Disable board specific

[PATCH RESEND 02/12] sh: Config update for OF mode

DeviceTreee support is use liner IRQ. And use generic function (clock / io / IRQ). Signed-off-by: Yoshinori Sato --- arch/sh/Kconfig | 26 +++--- arch/sh/boards/Kconfig | 4 arch/sh/drivers/Makefile| 2 ++ arch/sh/include/asm/io.h| 6 ++

[PATCH RESEND 00/12] SH: landisk convert to devicetree

SH get devicetree support. But it not working on existing H/W. IO-DATA HDL-U (aka landisk) currentry supported. This H/W like SH7751 evalution board. It's a best to use this as a change base H/W. Yoshinori Sato (12): sh: Fix typo sh: Config update for OF mode sh: Disable board specific

2% Loan Offer! No upfront fees

We give out loans from $10,000.00 to $500,000,000.00 at 2% interest rate if interested contact us at: daviesanthony...@qq.com

2% Loan Offer! No upfront fees

We give out loans from $10,000.00 to $500,000,000.00 at 2% interest rate if interested contact us at: daviesanthony...@qq.com

Re: [PATCH V17 1/3] dmaengine: qcom_hidma: implement lower level hardware interface

On 4/28/2016 3:30 PM, Sinan Kaya wrote: > On 4/26/2016 12:24 PM, Vinod Koul wrote: >>> + + dev_err(lldev->dev, "error 0x%x, resetting...\n", + cause); >> right justify this and others as well please >> > > Can you please point me to other lines that need to be fixed

Re: [PATCH V17 1/3] dmaengine: qcom_hidma: implement lower level hardware interface

On 4/28/2016 3:30 PM, Sinan Kaya wrote: > On 4/26/2016 12:24 PM, Vinod Koul wrote: >>> + + dev_err(lldev->dev, "error 0x%x, resetting...\n", + cause); >> right justify this and others as well please >> > > Can you please point me to other lines that need to be fixed

Re: [PATCH V17 2/3] dmaengine: qcom_hidma: add debugfs hooks

On 4/27/2016 8:51 AM, ok...@codeaurora.org wrote: > On 2016-04-27 04:15, Vinod Koul wrote: >> On Tue, Apr 26, 2016 at 12:55:18PM -0400, Sinan Kaya wrote: >>> On 4/26/2016 12:25 PM, Vinod Koul wrote: >>> > On Tue, Apr 26, 2016 at 08:08:16AM -0400, ok...@codeaurora.org wrote: >>> >> On 2016-04-25

Re: [PATCH V17 2/3] dmaengine: qcom_hidma: add debugfs hooks

On 4/27/2016 8:51 AM, ok...@codeaurora.org wrote: > On 2016-04-27 04:15, Vinod Koul wrote: >> On Tue, Apr 26, 2016 at 12:55:18PM -0400, Sinan Kaya wrote: >>> On 4/26/2016 12:25 PM, Vinod Koul wrote: >>> > On Tue, Apr 26, 2016 at 08:08:16AM -0400, ok...@codeaurora.org wrote: >>> >> On 2016-04-25

[PATCH V18 3/3] dmaengine: qcom_hidma: add support for object hierarchy

In order to create a relationship model between the channels and the management object, we are adding support for object hierarchy to the drivers. This patch simplifies the userspace application development. We will not have to traverse different firmware paths based on device tree or ACPI based

[PATCH V18 3/3] dmaengine: qcom_hidma: add support for object hierarchy

In order to create a relationship model between the channels and the management object, we are adding support for object hierarchy to the drivers. This patch simplifies the userspace application development. We will not have to traverse different firmware paths based on device tree or ACPI based

[PATCH V18 2/3] dmaengine: qcom_hidma: add debugfs hooks

Add debugfs hooks for debugging the execution behavior of the DMA channel. The debugfs hooks get initialized by the probe function and uninitialized by the remove function. A stats file is created in debugfs. The stats file will show the information about each HIDMA channel as well as each

[PATCH V18 1/3] dmaengine: qcom_hidma: implement lower level hardware interface

This patch implements the hardware hooks for the HIDMA channel driver. The main functions of interest are: - hidma_ll_init - hidma_ll_request - hidma_ll_queue_request - hidma_ll_hw_start OS layer calls the hidma_ll_init function during probe to set up the hardware. At this moment, the number of

[PATCH V18 2/3] dmaengine: qcom_hidma: add debugfs hooks

Add debugfs hooks for debugging the execution behavior of the DMA channel. The debugfs hooks get initialized by the probe function and uninitialized by the remove function. A stats file is created in debugfs. The stats file will show the information about each HIDMA channel as well as each

[PATCH V18 1/3] dmaengine: qcom_hidma: implement lower level hardware interface

This patch implements the hardware hooks for the HIDMA channel driver. The main functions of interest are: - hidma_ll_init - hidma_ll_request - hidma_ll_queue_request - hidma_ll_hw_start OS layer calls the hidma_ll_init function during probe to set up the hardware. At this moment, the number of

Re: efi_enabled(EFI_PARAVIRT) use

On 2016年05月01日 04:44, Matt Fleming wrote: >> While I still have a question, in this patch we use >> > efi_enabled(EFI_PARAVIRT) as a condition to make fdt_find_uefi_params() >> > and efi_get_fdt_params() execute different ways. So it needs to find a >> > new condition for that if we need to get

Re: efi_enabled(EFI_PARAVIRT) use

On 2016年05月01日 04:44, Matt Fleming wrote: >> While I still have a question, in this patch we use >> > efi_enabled(EFI_PARAVIRT) as a condition to make fdt_find_uefi_params() >> > and efi_get_fdt_params() execute different ways. So it needs to find a >> > new condition for that if we need to get

Re: [PATCH] watchdog: dw_wdt: dont build for avr32

On Sat, Apr 30, 2016 at 05:36:51PM -0700, Guenter Roeck wrote: > On Sat, Apr 30, 2016 at 07:38:28PM +0100, Sudip Mukherjee wrote: > > On Tue, Apr 12, 2016 at 11:01:28AM -0700, Guenter Roeck wrote: > > > On Tue, Apr 12, 2016 at 05:58:20PM +0300, Andy Shevchenko wrote: > > > > On Tue, Apr 12, 2016

Re: [PATCH] watchdog: dw_wdt: dont build for avr32

On Sat, Apr 30, 2016 at 05:36:51PM -0700, Guenter Roeck wrote: > On Sat, Apr 30, 2016 at 07:38:28PM +0100, Sudip Mukherjee wrote: > > On Tue, Apr 12, 2016 at 11:01:28AM -0700, Guenter Roeck wrote: > > > On Tue, Apr 12, 2016 at 05:58:20PM +0300, Andy Shevchenko wrote: > > > > On Tue, Apr 12, 2016

[PATCH RESEND 5/5] tools: hv: lsvmbus: add pci pass-through UUID

From: Vitaly Kuznetsov lsvmbus keeps its own copy of all VMBus UUIDs, add PCIe pass-through device there to not report 'Unknown' for such devices. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan ---

[PATCH RESEND 3/5] Drivers: hv: balloon: don't crash when memory is added in non-sorted order

From: Vitaly Kuznetsov When we iterate through all HA regions in handle_pg_range() we have an assumption that all these regions are sorted in the list and the 'start_pfn >= has->end_pfn' check is enough to find the proper region. Unfortunately it's not the case with WS2016

[PATCH RESEND 5/5] tools: hv: lsvmbus: add pci pass-through UUID

From: Vitaly Kuznetsov lsvmbus keeps its own copy of all VMBus UUIDs, add PCIe pass-through device there to not report 'Unknown' for such devices. Signed-off-by: Vitaly Kuznetsov Signed-off-by: K. Y. Srinivasan --- tools/hv/lsvmbus |1 + 1 files changed, 1 insertions(+), 0 deletions(-)

[PATCH RESEND 3/5] Drivers: hv: balloon: don't crash when memory is added in non-sorted order

From: Vitaly Kuznetsov When we iterate through all HA regions in handle_pg_range() we have an assumption that all these regions are sorted in the list and the 'start_pfn >= has->end_pfn' check is enough to find the proper region. Unfortunately it's not the case with WS2016 where host can hot-add

[PATCH RESEND 4/5] Drivers: hv: balloon: reset host_specified_ha_region

From: Vitaly Kuznetsov We set host_specified_ha_region = true on certain request but this is a global state which stays 'true' forever. We need to reset it when we receive a request where ha_region is not specified. I did not see any real issues, the bug was found by code

[PATCH RESEND 1/5] Drivers: hv: kvp: fix IP Failover

From: Vitaly Kuznetsov Hyper-V VMs can be replicated to another hosts and there is a feature to set different IP for replicas, it is called 'Failover TCP/IP'. When such guest starts Hyper-V host sends it KVP_OP_SET_IP_INFO message as soon as we finish negotiation procedure.

[PATCH RESEND 2/5] Drivers: hv: vmbus: handle various crash scenarios

From: Vitaly Kuznetsov Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always delivered to the CPU which was used for initial contact or to CPU0 depending on host version. vmbus_wait_for_unload() doesn't account for the fact that in case we're crashing on some

[PATCH RESEND 4/5] Drivers: hv: balloon: reset host_specified_ha_region

From: Vitaly Kuznetsov We set host_specified_ha_region = true on certain request but this is a global state which stays 'true' forever. We need to reset it when we receive a request where ha_region is not specified. I did not see any real issues, the bug was found by code inspection.

[PATCH RESEND 1/5] Drivers: hv: kvp: fix IP Failover

From: Vitaly Kuznetsov Hyper-V VMs can be replicated to another hosts and there is a feature to set different IP for replicas, it is called 'Failover TCP/IP'. When such guest starts Hyper-V host sends it KVP_OP_SET_IP_INFO message as soon as we finish negotiation procedure. The problem is that

[PATCH RESEND 2/5] Drivers: hv: vmbus: handle various crash scenarios

From: Vitaly Kuznetsov Kdump keeps biting. Turns out CHANNELMSG_UNLOAD_RESPONSE is always delivered to the CPU which was used for initial contact or to CPU0 depending on host version. vmbus_wait_for_unload() doesn't account for the fact that in case we're crashing on some other CPU we won't get

[PATCH RESEND 0/5] Drivers: hv: Some miscellaneous fixes

Some miscellaneous fixes. All these patches are being resent. Vitaly Kuznetsov (5): Drivers: hv: kvp: fix IP Failover Drivers: hv: vmbus: handle various crash scenarios Drivers: hv: balloon: don't crash when memory is added in non-sorted order Drivers: hv: balloon: reset

[PATCH RESEND 0/5] Drivers: hv: Some miscellaneous fixes

Some miscellaneous fixes. All these patches are being resent. Vitaly Kuznetsov (5): Drivers: hv: kvp: fix IP Failover Drivers: hv: vmbus: handle various crash scenarios Drivers: hv: balloon: don't crash when memory is added in non-sorted order Drivers: hv: balloon: reset

Re: [PATCH] watchdog: dw_wdt: dont build for avr32

On Sat, Apr 30, 2016 at 07:38:28PM +0100, Sudip Mukherjee wrote: > On Tue, Apr 12, 2016 at 11:01:28AM -0700, Guenter Roeck wrote: > > On Tue, Apr 12, 2016 at 05:58:20PM +0300, Andy Shevchenko wrote: > > > On Tue, Apr 12, 2016 at 4:39 PM, Sudip Mukherjee > > > wrote: >

Re: [PATCH] watchdog: dw_wdt: dont build for avr32

On Sat, Apr 30, 2016 at 07:38:28PM +0100, Sudip Mukherjee wrote: > On Tue, Apr 12, 2016 at 11:01:28AM -0700, Guenter Roeck wrote: > > On Tue, Apr 12, 2016 at 05:58:20PM +0300, Andy Shevchenko wrote: > > > On Tue, Apr 12, 2016 at 4:39 PM, Sudip Mukherjee > > > wrote: > > > > On Tuesday 12 April

RE: [PATCH 1/8] Drivers: hv: kvp: fix IP Failover

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Saturday, April 30, 2016 2:54 PM > To: KY Srinivasan > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; > o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com; >

RE: [PATCH 1/8] Drivers: hv: kvp: fix IP Failover

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Saturday, April 30, 2016 2:54 PM > To: KY Srinivasan > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; > o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com; > jasow...@redhat.com >

Re: [PATCH] watchdog: dw_wdt: dont build for avr32

On 04/30/2016 11:38 AM, Sudip Mukherjee wrote: On Tue, Apr 12, 2016 at 11:01:28AM -0700, Guenter Roeck wrote: On Tue, Apr 12, 2016 at 05:58:20PM +0300, Andy Shevchenko wrote: On Tue, Apr 12, 2016 at 4:39 PM, Sudip Mukherjee wrote: On Tuesday 12 April 2016 06:36

Re: [PATCH] watchdog: dw_wdt: dont build for avr32

On 04/30/2016 11:38 AM, Sudip Mukherjee wrote: On Tue, Apr 12, 2016 at 11:01:28AM -0700, Guenter Roeck wrote: On Tue, Apr 12, 2016 at 05:58:20PM +0300, Andy Shevchenko wrote: On Tue, Apr 12, 2016 at 4:39 PM, Sudip Mukherjee wrote: On Tuesday 12 April 2016 06:36 PM, Guenter Roeck wrote: On

Re: [PATCH] efibc: avoid stack overflow warning

On Saturday 30 April 2016 23:46:41 Matt Fleming wrote: > > > It's not something we'd have to worry about in practice, but it does > > make my patch incorrect. Should we come up with a different way to > > do it? > > Jeremy proposed a patch to dynamically allocate the memory, which I > think is

Re: [PATCH] efibc: avoid stack overflow warning

On Saturday 30 April 2016 23:46:41 Matt Fleming wrote: > > > It's not something we'd have to worry about in practice, but it does > > make my patch incorrect. Should we come up with a different way to > > do it? > > Jeremy proposed a patch to dynamically allocate the memory, which I > think is

Re: [PATCH 3.16 000/217] 3.16.35-rc1 review

On 04/30/2016 12:44 PM, Ben Hutchings wrote: On Thu, 2016-04-28 at 21:16 -0700, Guenter Roeck wrote: On 04/26/2016 04:02 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.16.35 release. There are 217 patches in this series, which will be posted as responses to

Re: [PATCH 3.16 000/217] 3.16.35-rc1 review

On 04/30/2016 12:44 PM, Ben Hutchings wrote: On Thu, 2016-04-28 at 21:16 -0700, Guenter Roeck wrote: On 04/26/2016 04:02 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.16.35 release. There are 217 patches in this series, which will be posted as responses to

Re: [PATCH] x86/efi-bgrt: Switch all pr_err() to pr_debug() for invalid BGRT

On Sat, Apr 30, 2016 at 11:35:14PM +0100, Matt Fleming wrote: > (Adding Colin and Ricardo) > > On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote: > > > > How is an end user supposed to see such a message and report it to the > > people that can fix it? They can't. So they report it in their > >

Re: [PATCH] x86/efi-bgrt: Switch all pr_err() to pr_debug() for invalid BGRT

On Sat, Apr 30, 2016 at 11:35:14PM +0100, Matt Fleming wrote: > (Adding Colin and Ricardo) > > On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote: > > > > How is an end user supposed to see such a message and report it to the > > people that can fix it? They can't. So they report it in their > >

[GIT PULL] Thermal management updates for v4.6-rc6

Hello Linus, Here are only a couple of minor fixes on thermal subsystem. Please consider pulling from git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes to receive Thermal Management updates for v4.6-rc6 with top-most 15333e3af1de37b1b214b28c85fe9a7b257fb92c:

[GIT PULL] Thermal management updates for v4.6-rc6

Hello Linus, Here are only a couple of minor fixes on thermal subsystem. Please consider pulling from git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes to receive Thermal Management updates for v4.6-rc6 with top-most 15333e3af1de37b1b214b28c85fe9a7b257fb92c:

Re: OpRegion conflicts for Skylake LPSS

Mika Westerberg writes: > On Fri, Apr 29, 2016 at 09:30:27AM +0200, Ben Gamari wrote: >> Ben Gamari writes: >> >> > [ Unknown signature status ] >> > Mika Westerberg writes: >> > >> >> On Tue, Apr 26,

Re: OpRegion conflicts for Skylake LPSS

Mika Westerberg writes: > On Fri, Apr 29, 2016 at 09:30:27AM +0200, Ben Gamari wrote: >> Ben Gamari writes: >> >> > [ Unknown signature status ] >> > Mika Westerberg writes: >> > >> >> On Tue, Apr 26, 2016 at 02:44:13AM +0200, Ben Gamari wrote: >> >>> >> > snip >> > >> >>> It looks very much

Re: [PATCH] efibc: avoid stack overflow warning

On Sun, 01 May, at 12:34:29AM, Arnd Bergmann wrote: > > The sys_restart() system call takes a mutex before calling kernel_restart() > or kernel_poweroff(). > > I've had a closer look now and found that there are a few other > callers of kernel_restart, so I guess if you restart using sysctl > at

Re: [PATCH] efibc: avoid stack overflow warning

On Sun, 01 May, at 12:34:29AM, Arnd Bergmann wrote: > > The sys_restart() system call takes a mutex before calling kernel_restart() > or kernel_poweroff(). > > I've had a closer look now and found that there are a few other > callers of kernel_restart, so I guess if you restart using sysctl > at

Re: [PATCH 3.2 085/115] veth: don’t modify ip_summed; doing so treats packets with bad checksums as good.

On 04/30/2016 03:01 PM, Vijay Pandurangan wrote: On Sat, Apr 30, 2016 at 5:52 PM, Ben Greear wrote: Good point, so if you had: eth0 <-> raw <-> user space-bridge <-> raw <-> vethA <-> veth B <-> userspace-stub <->eth1 and user-space hub enabled this elide flag,

Re: [PATCH 3.2 085/115] veth: don’t modify ip_summed; doing so treats packets with bad checksums as good.

On 04/30/2016 03:01 PM, Vijay Pandurangan wrote: On Sat, Apr 30, 2016 at 5:52 PM, Ben Greear wrote: Good point, so if you had: eth0 <-> raw <-> user space-bridge <-> raw <-> vethA <-> veth B <-> userspace-stub <->eth1 and user-space hub enabled this elide flag, things would work, right?

Re: [PATCH 3.2 085/115] veth: don’t modify ip_summed; doing so treats packets with bad checksums as good.

On Sat, Apr 30, 2016 at 1:59 PM, Ben Greear wrote: > > On 04/30/2016 12:54 PM, Tom Herbert wrote: >> >> We've put considerable effort into cleaning up the checksum interface >> to make it as unambiguous as possible, please be very careful to >> follow it. Broken checksum

Re: [PATCH] x86/efi-bgrt: Switch all pr_err() to pr_debug() for invalid BGRT

On 30/04/16 23:35, Matt Fleming wrote: > (Adding Colin and Ricardo) > > On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote: >> >> How is an end user supposed to see such a message and report it to the >> people that can fix it? They can't. So they report it in their >> distributions bug tracker

Re: [PATCH 3.2 085/115] veth: don’t modify ip_summed; doing so treats packets with bad checksums as good.

On Sat, Apr 30, 2016 at 1:59 PM, Ben Greear wrote: > > On 04/30/2016 12:54 PM, Tom Herbert wrote: >> >> We've put considerable effort into cleaning up the checksum interface >> to make it as unambiguous as possible, please be very careful to >> follow it. Broken checksum processing is really hard

Re: [PATCH] x86/efi-bgrt: Switch all pr_err() to pr_debug() for invalid BGRT

On 30/04/16 23:35, Matt Fleming wrote: > (Adding Colin and Ricardo) > > On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote: >> >> How is an end user supposed to see such a message and report it to the >> people that can fix it? They can't. So they report it in their >> distributions bug tracker

Re: [PATCH] x86/efi-bgrt: Switch all pr_err() to pr_debug() for invalid BGRT

(Adding Colin and Ricardo) On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote: > > How is an end user supposed to see such a message and report it to the > people that can fix it? They can't. So they report it in their > distributions bug tracker and it either gets closed as "yeah, firmware >

Re: [PATCH] x86/efi-bgrt: Switch all pr_err() to pr_debug() for invalid BGRT

(Adding Colin and Ricardo) On Wed, 27 Apr, at 01:23:55PM, Josh Boyer wrote: > > How is an end user supposed to see such a message and report it to the > people that can fix it? They can't. So they report it in their > distributions bug tracker and it either gets closed as "yeah, firmware >

Re: [PATCH] efibc: avoid stack overflow warning

On Saturday 30 April 2016 21:14:49 Matt Fleming wrote: > On Fri, 29 Apr, at 07:48:31PM, Arnd Bergmann wrote: > > gcc complains about a newly added file for the EFI Bootloader Control: > > > > drivers/firmware/efi/efibc.c: In function 'efibc_set_variable': > > drivers/firmware/efi/efibc.c:53:1:

Re: [PATCH] efibc: avoid stack overflow warning

On Saturday 30 April 2016 21:14:49 Matt Fleming wrote: > On Fri, 29 Apr, at 07:48:31PM, Arnd Bergmann wrote: > > gcc complains about a newly added file for the EFI Bootloader Control: > > > > drivers/firmware/efi/efibc.c: In function 'efibc_set_variable': > > drivers/firmware/efi/efibc.c:53:1:

Re: [PATCH 0/2] scop GFP_NOFS api

On Sat, Apr 30 2016, Dave Chinner wrote: > On Fri, Apr 29, 2016 at 03:35:42PM +1000, NeilBrown wrote: >> On Tue, Apr 26 2016, Michal Hocko wrote: >> >> > Hi, >> > we have discussed this topic at LSF/MM this year. There was a general >> > interest in the scope GFP_NOFS allocation context among

Re: [PATCH 0/2] scop GFP_NOFS api

On Sat, Apr 30 2016, Dave Chinner wrote: > On Fri, Apr 29, 2016 at 03:35:42PM +1000, NeilBrown wrote: >> On Tue, Apr 26 2016, Michal Hocko wrote: >> >> > Hi, >> > we have discussed this topic at LSF/MM this year. There was a general >> > interest in the scope GFP_NOFS allocation context among

[PATCH] efi/capsule: Make efi_capsule_pending() lockless

Taking a mutex in the reboot path is bogus because we cannot sleep with interrupts disabled, such as when rebooting due to panic(), [ 18.069005] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:97 [ 18.071639] in_atomic(): 0, irqs_disabled(): 1, pid: 7, name:

[PATCH] efi/capsule: Make efi_capsule_pending() lockless

Taking a mutex in the reboot path is bogus because we cannot sleep with interrupts disabled, such as when rebooting due to panic(), [ 18.069005] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:97 [ 18.071639] in_atomic(): 0, irqs_disabled(): 1, pid: 7, name:

Re: [BUG] x86/efi: MMRs no longer properly mapped after switch to isolated page table

On Fri, 29 Apr, at 10:41:19AM, Alex Thorlton wrote: > > You can see here that we've made it past the MMR read in uv_system_init, > but we die inside of our first EFI callback. In this example, it looks > like we're using the kernel page table at the time of the failure, and I > believe that the

Re: [BUG] x86/efi: MMRs no longer properly mapped after switch to isolated page table

On Fri, 29 Apr, at 10:41:19AM, Alex Thorlton wrote: > > You can see here that we've made it past the MMR read in uv_system_init, > but we die inside of our first EFI callback. In this example, it looks > like we're using the kernel page table at the time of the failure, and I > believe that the

Re: [PATCH 3.2 085/115] veth: don’t modify ip_summed; doing so treats packets with bad checksums as good.

On Sat, Apr 30, 2016 at 5:52 PM, Ben Greear wrote: >> >> Good point, so if you had: >> >> eth0 <-> raw <-> user space-bridge <-> raw <-> vethA <-> veth B <-> >> userspace-stub <->eth1 >> >> and user-space hub enabled this elide flag, things would work, right? >> Then, it

Re: [PATCH 3.2 085/115] veth: don’t modify ip_summed; doing so treats packets with bad checksums as good.

On Sat, Apr 30, 2016 at 5:52 PM, Ben Greear wrote: >> >> Good point, so if you had: >> >> eth0 <-> raw <-> user space-bridge <-> raw <-> vethA <-> veth B <-> >> userspace-stub <->eth1 >> >> and user-space hub enabled this elide flag, things would work, right? >> Then, it seems like what we need

Re: [PATCH] Cleanup __pvclock_read_cycles to remove useless variables

On Apr 30, 2016 12:17 PM, "Borislav Petkov" wrote: > > On Sat, Apr 30, 2016 at 10:47:49AM -0700, Andy Lutomirski wrote: > > Take a look at vread_pvclock. I decided that __pvclock_read_cycles > > was too ugly to use and was very slow and I just gave up and rewrote > > it. > > Should

Re: [PATCH] Cleanup __pvclock_read_cycles to remove useless variables

On Apr 30, 2016 12:17 PM, "Borislav Petkov" wrote: > > On Sat, Apr 30, 2016 at 10:47:49AM -0700, Andy Lutomirski wrote: > > Take a look at vread_pvclock. I decided that __pvclock_read_cycles > > was too ugly to use and was very slow and I just gave up and rewrote > > it. > > Should we kill

Re: [PATCH 0/2] scop GFP_NOFS api

On Fri, Apr 29 2016, Michal Hocko wrote: > > One think I have learned is that shrinkers can be really complex and > getting rid of GFP_NOFS will be really hard so I would really like to > start the easiest way possible and remove the direct usage and replace > it by scope one which would at least

Re: [PATCH 0/2] scop GFP_NOFS api

On Fri, Apr 29 2016, Michal Hocko wrote: > > One think I have learned is that shrinkers can be really complex and > getting rid of GFP_NOFS will be really hard so I would really like to > start the easiest way possible and remove the direct usage and replace > it by scope one which would at least

Re: [PATCH 1/8] Drivers: hv: kvp: fix IP Failover

On Sat, Apr 30, 2016 at 09:43:09PM +, KY Srinivasan wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Saturday, April 30, 2016 2:05 PM > > To: KY Srinivasan > > Cc: linux-kernel@vger.kernel.org;

Re: [PATCH 1/8] Drivers: hv: kvp: fix IP Failover

On Sat, Apr 30, 2016 at 09:43:09PM +, KY Srinivasan wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Saturday, April 30, 2016 2:05 PM > > To: KY Srinivasan > > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; > >

  1   2   3   4   >