Re: [PATCH v11 11/22] vfio iommu: Add blocking notifier to notify DMA_UNMAP

On 11/9/2016 2:58 AM, Alex Williamson wrote: > On Wed, 9 Nov 2016 01:29:19 +0530 > Kirti Wankhede wrote: > >> On 11/8/2016 11:16 PM, Alex Williamson wrote: >>> On Tue, 8 Nov 2016 21:56:29 +0530 >>> Kirti Wankhede wrote: >>> On 11/8/2016 5:15

Re: [PATCH v11 11/22] vfio iommu: Add blocking notifier to notify DMA_UNMAP

On 11/9/2016 2:58 AM, Alex Williamson wrote: > On Wed, 9 Nov 2016 01:29:19 +0530 > Kirti Wankhede wrote: > >> On 11/8/2016 11:16 PM, Alex Williamson wrote: >>> On Tue, 8 Nov 2016 21:56:29 +0530 >>> Kirti Wankhede wrote: >>> On 11/8/2016 5:15 AM, Alex Williamson wrote: > On Sat,

[GIT PULL] perf fixes

Linus, Please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus # HEAD: ce75632cc4012f1832bd56efd97c2ba75ca964bb Merge tag 'perf-hists-hierarchy-fixes-for-mingo-2016' of

[GIT PULL] perf fixes

Linus, Please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus # HEAD: ce75632cc4012f1832bd56efd97c2ba75ca964bb Merge tag 'perf-hists-hierarchy-fixes-for-mingo-2016' of

Re: [PATCH 4.8 00/35] 4.8.8-stable review

On Sun, Nov 13, 2016 at 10:18:51AM -0800, kernelci.org bot wrote: > stable-rc boot: 146 boots: 0 failed, 144 passed with 2 offline > (v4.8.7-36-g06d2f2c881c0) Nice! Thanks for testing. greg k-h

Re: [PATCH 4.8 00/35] 4.8.8-stable review

On Sun, Nov 13, 2016 at 10:18:51AM -0800, kernelci.org bot wrote: > stable-rc boot: 146 boots: 0 failed, 144 passed with 2 offline > (v4.8.7-36-g06d2f2c881c0) Nice! Thanks for testing. greg k-h

Re: [PATCH 4.4 00/34] 4.4.32-stable review

On Sun, Nov 13, 2016 at 12:58:52PM -0800, kernelci.org bot wrote: > stable-rc boot: 139 boots: 1 failed, 136 passed with 2 offline > (v4.4.31-35-g02bf66f6a361) > > Full Boot Summary: > https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.31-35-g02bf66f6a361/ > Full Build Summary: >

PLEASE VIEW THE ATTACHED FILE AND CONTACT ME.

FROM FIRST NATIONAL BANK OF SOUTH AFRICA (F.N.B)..rtf Description: MS-Word document

Re: [PATCH 4.4 00/34] 4.4.32-stable review

On Sun, Nov 13, 2016 at 12:58:52PM -0800, kernelci.org bot wrote: > stable-rc boot: 139 boots: 1 failed, 136 passed with 2 offline > (v4.4.31-35-g02bf66f6a361) > > Full Boot Summary: > https://kernelci.org/boot/all/job/stable-rc/kernel/v4.4.31-35-g02bf66f6a361/ > Full Build Summary: >

PLEASE VIEW THE ATTACHED FILE AND CONTACT ME.

FROM FIRST NATIONAL BANK OF SOUTH AFRICA (F.N.B)..rtf Description: MS-Word document

[GIT PULL] EFI fixes

Linus, Please pull the latest efi-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-urgent-for-linus # HEAD: f6697df36bdf0bf7fce984605c2918d4a7b4269f x86/efi: Prevent mixed mode boot corruption with CONFIG_VMAP_STACK=y A boot crash fix and a

[GIT PULL] EFI fixes

Linus, Please pull the latest efi-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-urgent-for-linus # HEAD: f6697df36bdf0bf7fce984605c2918d4a7b4269f x86/efi: Prevent mixed mode boot corruption with CONFIG_VMAP_STACK=y A boot crash fix and a

Re: [PATCH 4.4 00/34] 4.4.32-stable review

On Sun, Nov 13, 2016 at 04:34:46PM +0100, Philip Müller wrote: > Hi Greg, > > with inclusion of 'Fix data integrity failure for JBOD (passthrough) > devices' in v4.4.31, we currently have a regression with SCSI and macro > MEGASAS_IS_LOGICAL. > > To fix it, commit 5e5ec17[1] is needed or that

Re: [PATCH 4.4 00/34] 4.4.32-stable review

On Sun, Nov 13, 2016 at 04:34:46PM +0100, Philip Müller wrote: > Hi Greg, > > with inclusion of 'Fix data integrity failure for JBOD (passthrough) > devices' in v4.4.31, we currently have a regression with SCSI and macro > MEGASAS_IS_LOGICAL. > > To fix it, commit 5e5ec17[1] is needed or that

Re: [PATCH v9 00/10] MT2701 DRM support

Hi, YT On Fri, 2016-11-11 at 19:55 +0800, YT Shen wrote: > This is MT2701 DRM support PATCH v9, based on 4.9-rc1. > We add DSI interrupt control, transfer function for MIPI DSI panel support. > Most codes are the same, except some register changed. > > For example: > - DISP_OVL address offset

Re: [PATCH v9 00/10] MT2701 DRM support

Hi, YT On Fri, 2016-11-11 at 19:55 +0800, YT Shen wrote: > This is MT2701 DRM support PATCH v9, based on 4.9-rc1. > We add DSI interrupt control, transfer function for MIPI DSI panel support. > Most codes are the same, except some register changed. > > For example: > - DISP_OVL address offset

Re: [PATHCv10 0/2] USB Type-C Connector class

On Fri, Nov 11, 2016 at 01:04:24PM +0200, Heikki Krogerus wrote: > On Thu, Nov 10, 2016 at 01:36:09PM -0800, Guenter Roeck wrote: > > On Mon, Sep 19, 2016 at 02:16:55PM +0300, Heikki Krogerus wrote: > > > The USB Type-C class is meant to provide unified interface to the > > > userspace to present

Re: [PATHCv10 0/2] USB Type-C Connector class

On Fri, Nov 11, 2016 at 01:04:24PM +0200, Heikki Krogerus wrote: > On Thu, Nov 10, 2016 at 01:36:09PM -0800, Guenter Roeck wrote: > > On Mon, Sep 19, 2016 at 02:16:55PM +0300, Heikki Krogerus wrote: > > > The USB Type-C class is meant to provide unified interface to the > > > userspace to present

Re: [PATCH 4.8 00/35] 4.8.8-stable review

On Sun, Nov 13, 2016 at 12:41:54PM -0800, Guenter Roeck wrote: > On 11/13/2016 03:27 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.8 release. > > There are 35 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.4 00/34] 4.4.32-stable review

On Sun, Nov 13, 2016 at 08:45:39PM +0200, Thomas Backlund wrote: > Den 13.11.2016 kl. 17:34, skrev Philip Müller: > > Hi Greg, > > > > with inclusion of 'Fix data integrity failure for JBOD (passthrough) > > devices' in v4.4.31, we currently have a regression with SCSI and macro > >

Re: [PATCH 4.8 00/35] 4.8.8-stable review

On Sun, Nov 13, 2016 at 12:41:54PM -0800, Guenter Roeck wrote: > On 11/13/2016 03:27 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.8 release. > > There are 35 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.4 00/34] 4.4.32-stable review

On Sun, Nov 13, 2016 at 08:45:39PM +0200, Thomas Backlund wrote: > Den 13.11.2016 kl. 17:34, skrev Philip Müller: > > Hi Greg, > > > > with inclusion of 'Fix data integrity failure for JBOD (passthrough) > > devices' in v4.4.31, we currently have a regression with SCSI and macro > >

Re: [PATCH net] net: stmmac: Fix lack of link transition for fixed PHYs

On 11/14/2016 2:50 AM, Florian Fainelli wrote: Commit 52f95bbfcf72 ("stmmac: fix adjust link call in case of a switch is attached") added some logic to avoid polling the fixed PHY and therefore invoking the adjust_link callback more than once, since this is a fixed PHY and link events won't be

Re: [PATCH net] net: stmmac: Fix lack of link transition for fixed PHYs

On 11/14/2016 2:50 AM, Florian Fainelli wrote: Commit 52f95bbfcf72 ("stmmac: fix adjust link call in case of a switch is attached") added some logic to avoid polling the fixed PHY and therefore invoking the adjust_link callback more than once, since this is a fixed PHY and link events won't be

linux-next: Tree for Nov 14

Hi all, Changes since 2016: The sound tree gained conflicts against the jc_docs tree. The sound-asoc tree gained a build failure, so I used the version from next-2016. The driver-core tree gained a conflict against the pm tree. The rpmsg tree gained a conflict against the slave-dma

RE: [PATCH net 2/2] r8152: rx descriptor check

Mark Lord [mailto:ml...@pobox.com] > Sent: Monday, November 14, 2016 4:34 AM [...] > Perhaps the driver > is somehow accessing the buffer space again after doing usb_submit_urb()? > That would certainly produce this kind of behaviour. I don't think so. First, the driver only read the received

RE: [PATCH net 2/2] r8152: rx descriptor check

Mark Lord [mailto:ml...@pobox.com] > Sent: Monday, November 14, 2016 4:34 AM [...] > Perhaps the driver > is somehow accessing the buffer space again after doing usb_submit_urb()? > That would certainly produce this kind of behaviour. I don't think so. First, the driver only read the received

linux-next: Tree for Nov 14

Hi all, Changes since 2016: The sound tree gained conflicts against the jc_docs tree. The sound-asoc tree gained a build failure, so I used the version from next-2016. The driver-core tree gained a conflict against the pm tree. The rpmsg tree gained a conflict against the slave-dma

Re: [patch v3 1/1] platform/x86: move module mlx-platform from arch/x86 to drivers/platform/x86

On Tue, Nov 8, 2016 at 8:19 AM, Vadim Pasternak wrote: > Hi, > > Could this patch be merged to for-next for 4.10? > When it's merged I'd like to submit another small patch on top of it. First of all, please avoid top posting. I will process the pdx86 mailing list and queue

Re: [patch v3 1/1] platform/x86: move module mlx-platform from arch/x86 to drivers/platform/x86

On Tue, Nov 8, 2016 at 8:19 AM, Vadim Pasternak wrote: > Hi, > > Could this patch be merged to for-next for 4.10? > When it's merged I'd like to submit another small patch on top of it. First of all, please avoid top posting. I will process the pdx86 mailing list and queue this week. P.S. Are

Re: [PATCH v9 00/10] MT2701 DRM support

Hi, YT: On Fri, 2016-11-11 at 19:55 +0800, YT Shen wrote: > This is MT2701 DRM support PATCH v9, based on 4.9-rc1. > We add DSI interrupt control, transfer function for MIPI DSI panel support. > Most codes are the same, except some register changed. > > For example: > - DISP_OVL address offset

Re: [PATCH v9 00/10] MT2701 DRM support

Hi, YT: On Fri, 2016-11-11 at 19:55 +0800, YT Shen wrote: > This is MT2701 DRM support PATCH v9, based on 4.9-rc1. > We add DSI interrupt control, transfer function for MIPI DSI panel support. > Most codes are the same, except some register changed. > > For example: > - DISP_OVL address offset

Re: Linux 4.8.6

On Mon, Oct 31, 2016 at 04:26:39PM -0400, Levin, Alexander wrote: > On Mon, Oct 31, 2016 at 06:47:10AM -0600, Greg KH wrote: > > I'm announcing the release of the 4.8.6 kernel. > > Hey Greg, > > I've put more work into improving my filters to find stable commits upstream. > > The list below,

Re: Linux 4.8.6

On Mon, Oct 31, 2016 at 04:26:39PM -0400, Levin, Alexander wrote: > On Mon, Oct 31, 2016 at 06:47:10AM -0600, Greg KH wrote: > > I'm announcing the release of the 4.8.6 kernel. > > Hey Greg, > > I've put more work into improving my filters to find stable commits upstream. > > The list below,

[PATCH] perf symbol: Print symbol offsets conditionally

The __symbol__fprintf_symname_offs() always shows symbol offsets. So there's no difference between 'perf script -F ip,sym' and 'perf script -F ip,sym,symoff'. I don't think it's a desired behavior.. Signed-off-by: Namhyung Kim --- tools/perf/util/evsel_fprintf.c | 6

[PATCH] perf symbol: Print symbol offsets conditionally

The __symbol__fprintf_symname_offs() always shows symbol offsets. So there's no difference between 'perf script -F ip,sym' and 'perf script -F ip,sym,symoff'. I don't think it's a desired behavior.. Signed-off-by: Namhyung Kim --- tools/perf/util/evsel_fprintf.c | 6 --

Re: [PATCH 4.4 10/34] net/sched: act_vlan: Push skb->data to mac_header prior calling skb_vlan_*() functions

On Sun, 13 Nov 2016 12:24:42 +0100 Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. > Looks ok, thanks. Reviewed-by: Shmulik Ladkani

Re: [PATCH 4.4 10/34] net/sched: act_vlan: Push skb->data to mac_header prior calling skb_vlan_*() functions

On Sun, 13 Nov 2016 12:24:42 +0100 Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. > Looks ok, thanks. Reviewed-by: Shmulik Ladkani

[PATCH v2 0/2] phy: rockchip-inno-usb2: correct 480MHz clk_ops callbacks and stable time

This series try to correct the 480MHz output clock of USB2 PHY clk_ops callback and fix the delay time. It aims to make the 480MHz clock more sensible and stable. Tested on rk3366/rk3399 EVB board. William Wu (2): phy: rockchip-inno-usb2: correct clk_ops callback phy: rockchip-inno-usb2:

RE: [PATCH net 2/2] r8152: rx descriptor check

David Miller [mailto:da...@davemloft.net] > Sent: Monday, November 14, 2016 1:40 AM [...] > If you add this patch now, there is a much smaller likelyhood that you > will work with a high priority to figure out _why_ this is happening. > > For all we know this could be a platform bug in the DMA

[PATCH v2 0/2] phy: rockchip-inno-usb2: correct 480MHz clk_ops callbacks and stable time

This series try to correct the 480MHz output clock of USB2 PHY clk_ops callback and fix the delay time. It aims to make the 480MHz clock more sensible and stable. Tested on rk3366/rk3399 EVB board. William Wu (2): phy: rockchip-inno-usb2: correct clk_ops callback phy: rockchip-inno-usb2:

RE: [PATCH net 2/2] r8152: rx descriptor check

David Miller [mailto:da...@davemloft.net] > Sent: Monday, November 14, 2016 1:40 AM [...] > If you add this patch now, there is a much smaller likelyhood that you > will work with a high priority to figure out _why_ this is happening. > > For all we know this could be a platform bug in the DMA

Re: [PATCH v2] cpufreq: conservative: Decrease frequency faster when the update deferred

On 12-11-16, 23:04, Stratos Karafotis wrote: > diff --git a/drivers/cpufreq/cpufreq_conservative.c > b/drivers/cpufreq/cpufreq_conservative.c > index fa5ece3..d787772 100644 > --- a/drivers/cpufreq/cpufreq_conservative.c > +++ b/drivers/cpufreq/cpufreq_conservative.c > @@ -73,7 +73,19 @@ static

Re: [PATCH v2] cpufreq: conservative: Decrease frequency faster when the update deferred

On 12-11-16, 23:04, Stratos Karafotis wrote: > diff --git a/drivers/cpufreq/cpufreq_conservative.c > b/drivers/cpufreq/cpufreq_conservative.c > index fa5ece3..d787772 100644 > --- a/drivers/cpufreq/cpufreq_conservative.c > +++ b/drivers/cpufreq/cpufreq_conservative.c > @@ -73,7 +73,19 @@ static

[PATCH v2 2/2] phy: rockchip-inno-usb2: correct 480MHz output clock stable time

We found that the system crashed due to 480MHz output clock of USB2 PHY was unstable after clock had been enabled by gpu module. Theoretically, 1 millisecond is a critical value for 480MHz output clock stable time, so we try to change the delay time to 1.2 millisecond to avoid this issue. And

[PATCH v2 1/2] phy: rockchip-inno-usb2: correct clk_ops callback

Since we needs to delay ~1ms to wait for 480MHz output clock of USB2 PHY to become stable after turn on it, the delay time is pretty long for something that's supposed to be "atomic" like a clk_enable(). Consider that clk_enable() will disable interrupt and that a 1ms interrupt latency is not

[PATCH v2 2/2] phy: rockchip-inno-usb2: correct 480MHz output clock stable time

We found that the system crashed due to 480MHz output clock of USB2 PHY was unstable after clock had been enabled by gpu module. Theoretically, 1 millisecond is a critical value for 480MHz output clock stable time, so we try to change the delay time to 1.2 millisecond to avoid this issue. And

[PATCH v2 1/2] phy: rockchip-inno-usb2: correct clk_ops callback

Since we needs to delay ~1ms to wait for 480MHz output clock of USB2 PHY to become stable after turn on it, the delay time is pretty long for something that's supposed to be "atomic" like a clk_enable(). Consider that clk_enable() will disable interrupt and that a 1ms interrupt latency is not

[PATCH] cpufreq: conservative: Rename get_freq_target() to get_freq_step()

What's returned from this function is the delta by which the frequency must be increased or decreased and not the final frequency that should be selected. Name it properly to match its purpose. Also update the variables used to store that value. Signed-off-by: Viresh Kumar

[PATCH] cpufreq: conservative: Rename get_freq_target() to get_freq_step()

What's returned from this function is the delta by which the frequency must be increased or decreased and not the final frequency that should be selected. Name it properly to match its purpose. Also update the variables used to store that value. Signed-off-by: Viresh Kumar ---

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

On Mon, 14 Nov 2016 14:12:51 +0800 Jisheng Zhang wrote: > Hi Pankaj, > > On Mon, 14 Nov 2016 10:31:56 +0530 Pankaj Dubey wrote: > > > Many platforms are duplicating code for enabling SCU, lets add > > common code to enable SCU by parsing SCU device node so the duplication > > in each platform

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

On Mon, 14 Nov 2016 14:12:51 +0800 Jisheng Zhang wrote: > Hi Pankaj, > > On Mon, 14 Nov 2016 10:31:56 +0530 Pankaj Dubey wrote: > > > Many platforms are duplicating code for enabling SCU, lets add > > common code to enable SCU by parsing SCU device node so the duplication > > in each platform

Re: [PATCH] i.MX: Kconfig: Drop errata 769419 for Vybrid

On 2016-11-09 17:44, Andrey Smirnov wrote: > According to the datasheet, VF610 uses revision r3p2 of the L2C-310 > block, same as i.MX6Q+, which does not require a software workaround for > ARM errata 769419. FWIW, r3p2 is also the revision according to the cache registers... Acked-by: Stefan

Re: [PATCH] i.MX: Kconfig: Drop errata 769419 for Vybrid

On 2016-11-09 17:44, Andrey Smirnov wrote: > According to the datasheet, VF610 uses revision r3p2 of the L2C-310 > block, same as i.MX6Q+, which does not require a software workaround for > ARM errata 769419. FWIW, r3p2 is also the revision according to the cache registers... Acked-by: Stefan

Re: [PATCH v5] USB hub_probe: rework ugly goto-into-compound-statement

On Sun, Nov 13, 2016 at 03:53:58PM +0300, Eugene Korenevsky wrote: > Rework smelling code (goto inside compound statement). Perhaps this is > legacy. Anyway such code is not appropriate for Linux kernel. > > Signed-off-by: Eugene Korenevsky > --- > Changes in v5: make

Re: [PATCH v5] USB hub_probe: rework ugly goto-into-compound-statement

On Sun, Nov 13, 2016 at 03:53:58PM +0300, Eugene Korenevsky wrote: > Rework smelling code (goto inside compound statement). Perhaps this is > legacy. Anyway such code is not appropriate for Linux kernel. > > Signed-off-by: Eugene Korenevsky > --- > Changes in v5: make `bool` a return type of

Re: [PATCH v5] USB hub_probe: rework ugly goto-into-compound-statement

On Sun, Nov 13, 2016 at 03:53:58PM +0300, Eugene Korenevsky wrote: > Rework smelling code (goto inside compound statement). Perhaps this is > legacy. Anyway such code is not appropriate for Linux kernel. > > Signed-off-by: Eugene Korenevsky > --- > Changes in v5: make

Re: [PATCH v5] USB hub_probe: rework ugly goto-into-compound-statement

On Sun, Nov 13, 2016 at 03:53:58PM +0300, Eugene Korenevsky wrote: > Rework smelling code (goto inside compound statement). Perhaps this is > legacy. Anyway such code is not appropriate for Linux kernel. > > Signed-off-by: Eugene Korenevsky > --- > Changes in v5: make `bool` a return type of

Re: Long delays creating a netns after deleting one (possibly RCU related)

On Fri, Nov 11, 2016 at 4:55 PM, Cong Wang wrote: > On Fri, Nov 11, 2016 at 4:23 PM, Paul E. McKenney > wrote: >> >> Ah! This net_mutex is different than RTNL. Should synchronize_net() be >> modified to check for net_mutex being held in

Re: Long delays creating a netns after deleting one (possibly RCU related)

On Fri, Nov 11, 2016 at 4:55 PM, Cong Wang wrote: > On Fri, Nov 11, 2016 at 4:23 PM, Paul E. McKenney > wrote: >> >> Ah! This net_mutex is different than RTNL. Should synchronize_net() be >> modified to check for net_mutex being held in addition to the current >> checks for RTNL being held? >>

Re: [PATCH RESEND] drm/ast: free correct pointer in astfb_create() error paths

On Mon, Nov 14, 2016 at 02:03:59PM +1100, Andrew Donnellan wrote: > In the err_free_vram and err_release_fbi error paths in astfb_create(), we > attempt to free afbdev->sysram. The only jumps to these error paths occur > before we assign afbdev->sysram = sysram. Free sysram instead. > >

Re: [PATCH RESEND] drm/ast: free correct pointer in astfb_create() error paths

On Mon, Nov 14, 2016 at 02:03:59PM +1100, Andrew Donnellan wrote: > In the err_free_vram and err_release_fbi error paths in astfb_create(), we > attempt to free afbdev->sysram. The only jumps to these error paths occur > before we assign afbdev->sysram = sysram. Free sysram instead. > >

Re: [PATCH] i.MX: Kconfig: Drop errata 769419 for Vybrid

On Wed, Nov 09, 2016 at 08:44:10AM -0800, Andrey Smirnov wrote: > According to the datasheet, VF610 uses revision r3p2 of the L2C-310 > block, same as i.MX6Q+, which does not require a software workaround for > ARM errata 769419. > > Signed-off-by: Andrey Smirnov I

Re: [PATCH] i.MX: Kconfig: Drop errata 769419 for Vybrid

On Wed, Nov 09, 2016 at 08:44:10AM -0800, Andrey Smirnov wrote: > According to the datasheet, VF610 uses revision r3p2 of the L2C-310 > block, same as i.MX6Q+, which does not require a software workaround for > ARM errata 769419. > > Signed-off-by: Andrey Smirnov I updated subject prefix a bit

RE: [PATCH net 2/2] r8152: rx descriptor check

Francois Romieu [mailto:rom...@fr.zoreil.com] > Sent: Friday, November 11, 2016 8:13 PM [...] > Invalid packet size corrupted receive descriptors in Realtek's device > reminds of CVE-2009-4537. Do you mean that the driver would get a packet exceed the size which is set to RxMaxSize? I check it

RE: [PATCH net 2/2] r8152: rx descriptor check

Francois Romieu [mailto:rom...@fr.zoreil.com] > Sent: Friday, November 11, 2016 8:13 PM [...] > Invalid packet size corrupted receive descriptors in Realtek's device > reminds of CVE-2009-4537. Do you mean that the driver would get a packet exceed the size which is set to RxMaxSize? I check it

Re: [PATCH] ARM: dts: imx7d-pinfunc: fix UART pinmux defines

On Tue, Nov 08, 2016 at 06:44:56PM -0800, Stefan Agner wrote: > The UART pinmux defines for the pins which are part of the LPSR > pinmux controller are wrong: Output signals configure the input > sel value and the pinmux defines allow not to distinguish between > DCE/DTE mode. Follow the usual

Re: [PATCH] ARM: dts: imx7d-pinfunc: fix UART pinmux defines

On Tue, Nov 08, 2016 at 06:44:56PM -0800, Stefan Agner wrote: > The UART pinmux defines for the pins which are part of the LPSR > pinmux controller are wrong: Output signals configure the input > sel value and the pinmux defines allow not to distinguish between > DCE/DTE mode. Follow the usual

Re: [PATCH 2/3] cpufreq: schedutil: move slow path from workqueue to SCHED_FIFO task

On 13-11-16, 23:44, Rafael J. Wysocki wrote: > To a minimum, there should be a comment regarding that in the patches. Wanted to get the comment written properly before sending that in the patch. Can you please rectify this based on what you are looking for ? diff --git

Re: [PATCH 2/3] cpufreq: schedutil: move slow path from workqueue to SCHED_FIFO task

On 13-11-16, 23:44, Rafael J. Wysocki wrote: > To a minimum, there should be a comment regarding that in the patches. Wanted to get the comment written properly before sending that in the patch. Can you please rectify this based on what you are looking for ? diff --git

Re: [PATCH] x86/topology: Document cpu_llc_id

On Wed, Sep 07, 2016 at 12:36:41PM +0200, Peter Zijlstra wrote: > On Wed, Sep 07, 2016 at 11:22:19AM +0200, Borislav Petkov wrote: > > From: Borislav Petkov > > > > It means different things on Intel and AMD so write it down so that > > there's no confusion. > > > > Signed-off-by:

Re: [PATCH] x86/topology: Document cpu_llc_id

On Wed, Sep 07, 2016 at 12:36:41PM +0200, Peter Zijlstra wrote: > On Wed, Sep 07, 2016 at 11:22:19AM +0200, Borislav Petkov wrote: > > From: Borislav Petkov > > > > It means different things on Intel and AMD so write it down so that > > there's no confusion. > > > > Signed-off-by: Borislav

Re: [PATCH] genetlink: fix unsigned int comparison with less than zero

On Sun, Nov 13, 2016 at 9:15 AM, David Miller wrote: > I've commited the following to net-next: > > > [PATCH] genetlink: Make family a signed integer. > > The idr_alloc(), idr_remove(), et al. routines all expect IDs to be > signed integers. Therefore

Re: [PATCH] genetlink: fix unsigned int comparison with less than zero

On Sun, Nov 13, 2016 at 9:15 AM, David Miller wrote: > I've commited the following to net-next: > > > [PATCH] genetlink: Make family a signed integer. > > The idr_alloc(), idr_remove(), et al. routines all expect IDs to be > signed integers. Therefore make the genl_family

Re: [RFC PATCH] x86/debug: Dump more detailed segfault info

On Sun, Nov 13, 2016 at 08:15:01AM -0800, Andy Lutomirski wrote: > How about dropping the __ in front of the copy? In front of __copy_from_user_inatomic()? If so, is there even a global helper by that name? $ git grep -E "[^_]copy_from_user_inatomic" drivers/gpu/drm/msm/msm_gem_submit.c:98:

Re: [RFC PATCH] x86/debug: Dump more detailed segfault info

On Sun, Nov 13, 2016 at 08:15:01AM -0800, Andy Lutomirski wrote: > How about dropping the __ in front of the copy? In front of __copy_from_user_inatomic()? If so, is there even a global helper by that name? $ git grep -E "[^_]copy_from_user_inatomic" drivers/gpu/drm/msm/msm_gem_submit.c:98:

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

Hi Pankaj, On Mon, 14 Nov 2016 10:31:56 +0530 Pankaj Dubey wrote: > Many platforms are duplicating code for enabling SCU, lets add > common code to enable SCU by parsing SCU device node so the duplication > in each platform can be avoided. > > CC: Krzysztof Kozlowski > CC:

Re: [PATCH 01/16] ARM: scu: Provide support for parsing SCU device node to enable SCU

Hi Pankaj, On Mon, 14 Nov 2016 10:31:56 +0530 Pankaj Dubey wrote: > Many platforms are duplicating code for enabling SCU, lets add > common code to enable SCU by parsing SCU device node so the duplication > in each platform can be avoided. > > CC: Krzysztof Kozlowski > CC: Jisheng Zhang > CC:

[PATCH v3] module: extend 'rodata=off' boot cmdline parameter to module mappings

The current "rodata=off" parameter disables read-only kernel mappings under CONFIG_DEBUG_RODATA: commit d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter to disable read-only kernel mappings") This patch is a logical extension to module mappings ie. read-only mappings at

[PATCH v3] module: extend 'rodata=off' boot cmdline parameter to module mappings

The current "rodata=off" parameter disables read-only kernel mappings under CONFIG_DEBUG_RODATA: commit d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter to disable read-only kernel mappings") This patch is a logical extension to module mappings ie. read-only mappings at

Re: [PATCH 09/16] ARM: BCM: use generic API for enabling SCU

Le 13/11/2016 à 21:02, Pankaj Dubey a écrit : > Now as we have of_scu_enable which takes care of mapping > scu base from DT, lets use it. > > CC: Florian Fainelli > CC: Ray Jui > CC: Scott Branden > CC:

Re: [PATCH 09/16] ARM: BCM: use generic API for enabling SCU

Le 13/11/2016 à 21:02, Pankaj Dubey a écrit : > Now as we have of_scu_enable which takes care of mapping > scu base from DT, lets use it. > > CC: Florian Fainelli > CC: Ray Jui > CC: Scott Branden > CC: bcm-kernel-feedback-l...@broadcom.com > Signed-off-by: Pankaj Dubey Reviewed-by: Florian

linux-next: manual merge of the akpm-current tree with the tip tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: mm/memcontrol.c between commit: 308167fcb330 ("mm/memcg: Convert to hotplug state machine") from the tip tree and commit: 2558c318449d ("mm: memcontrol: use special workqueue for creating per-memcg

linux-next: manual merge of the akpm-current tree with the tip tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got a conflict in: mm/memcontrol.c between commit: 308167fcb330 ("mm/memcg: Convert to hotplug state machine") from the tip tree and commit: 2558c318449d ("mm: memcontrol: use special workqueue for creating per-memcg

Re: [PATCH V3 1/2] mm: move vma_is_anonymous check within pmd_move_must_withdraw

On 14/11/16 02:00, Aneesh Kumar K.V wrote: > Architectures like ppc64 want to use page table deposit/withraw > even with huge pmd dax entries. Allow arch to override the > vma_is_anonymous check by moving that to pmd_move_must_withdraw > function > I think the changelog can be reworded a bit

Re: [PATCH V3 1/2] mm: move vma_is_anonymous check within pmd_move_must_withdraw

On 14/11/16 02:00, Aneesh Kumar K.V wrote: > Architectures like ppc64 want to use page table deposit/withraw > even with huge pmd dax entries. Allow arch to override the > vma_is_anonymous check by moving that to pmd_move_must_withdraw > function > I think the changelog can be reworded a bit

Re: [PATCH v2] inotify: Convert to using per-namespace limits

On Tue, Oct 11, 2016 at 10:36:22AM +0300, Nikolay Borisov wrote: > This patchset converts inotify to using the newly introduced > per-userns sysctl infrastructure. > > Currently the inotify instances/watches are being accounted in the > user_struct structure. This means that in setups where

Re: [PATCH v2] inotify: Convert to using per-namespace limits

On Tue, Oct 11, 2016 at 10:36:22AM +0300, Nikolay Borisov wrote: > This patchset converts inotify to using the newly introduced > per-userns sysctl infrastructure. > > Currently the inotify instances/watches are being accounted in the > user_struct structure. This means that in setups where

Re: module: extend 'rodata=off' boot cmdline parameter to module mappings

On Sat, Nov 12, 2016 at 07:04:22PM -0800, Jessica Yu wrote: > +++ AKASHI Takahiro [21/10/16 10:13 +0900]: > >The current "rodata=off" parameter disables read-only kernel mappings > >under CONFIG_DEBUG_RODATA: > > commit d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter > > to

Re: module: extend 'rodata=off' boot cmdline parameter to module mappings

On Sat, Nov 12, 2016 at 07:04:22PM -0800, Jessica Yu wrote: > +++ AKASHI Takahiro [21/10/16 10:13 +0900]: > >The current "rodata=off" parameter disables read-only kernel mappings > >under CONFIG_DEBUG_RODATA: > > commit d2aa1acad22f ("mm/init: Add 'rodata=off' boot cmdline parameter > > to

Re: [PATCH v2 1/2] arm64: dts: Add level for cpu dt node for exynos7

Hi Krzysztof, On 11/13/2016 12:43 AM, Krzysztof Kozlowski wrote: On Sat, Nov 12, 2016 at 6:00 PM, Alim Akhtar wrote: Hi Javier, On Sat, Nov 12, 2016 at 7:54 PM, Javier Martinez Canillas wrote: Hello Alim, On 11/12/2016 07:17 AM, Alim Akhtar

Re: [PATCH] IB/usnic: simplify IS_ERR_OR_NULL to IS_ERR

On Fri, Nov 11, 2016 at 08:04:26PM +0100, Julia Lawall wrote: > The function usnic_ib_qp_grp_get_chunk only returns an ERR_PTR value or a > valid pointer, never NULL. The same is true of get_qp_res_chunk, which > just returns the result of calling usnic_ib_qp_grp_get_chunk. Simplify >

Re: [PATCH v2 1/2] arm64: dts: Add level for cpu dt node for exynos7

Hi Krzysztof, On 11/13/2016 12:43 AM, Krzysztof Kozlowski wrote: On Sat, Nov 12, 2016 at 6:00 PM, Alim Akhtar wrote: Hi Javier, On Sat, Nov 12, 2016 at 7:54 PM, Javier Martinez Canillas wrote: Hello Alim, On 11/12/2016 07:17 AM, Alim Akhtar wrote: This patch adds level for cpu dt node,

Re: [PATCH] IB/usnic: simplify IS_ERR_OR_NULL to IS_ERR

On Fri, Nov 11, 2016 at 08:04:26PM +0100, Julia Lawall wrote: > The function usnic_ib_qp_grp_get_chunk only returns an ERR_PTR value or a > valid pointer, never NULL. The same is true of get_qp_res_chunk, which > just returns the result of calling usnic_ib_qp_grp_get_chunk. Simplify >

Re: [PATCH v6 3/3] x86/kvm: Add AVX512_4VNNIW and AVX512_4FMAPS support

On Mon, Nov 14, 2016 at 09:41:04AM +0800, He Chen wrote: > Yep, Luwei wrote it and I send it on behalf of him. Then it needs to have the following format so that tools can pick up the proper author: "From: Luwei ... Signed-off-by: He Chen... Signed-off-by: Luwei... ... " git format-patch

Re: [PATCH v6 3/3] x86/kvm: Add AVX512_4VNNIW and AVX512_4FMAPS support

On Mon, Nov 14, 2016 at 09:41:04AM +0800, He Chen wrote: > Yep, Luwei wrote it and I send it on behalf of him. Then it needs to have the following format so that tools can pick up the proper author: "From: Luwei ... Signed-off-by: He Chen... Signed-off-by: Luwei... ... " git format-patch

[PATCH] [STYLE]staging:xgifb:vb_util.h No space after cast

Make suggested modification from checkpatch in reference to: CHECK: No space is necessary after a cast Signed-off-by: Walt Feasel --- drivers/staging/xgifb/vb_util.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/xgifb/vb_util.h

[PATCH] [STYLE]staging:xgifb:vb_util.h No space after cast

Make suggested modification from checkpatch in reference to: CHECK: No space is necessary after a cast Signed-off-by: Walt Feasel --- drivers/staging/xgifb/vb_util.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/xgifb/vb_util.h

Re: [PATCH 3.16 000/346] 3.16.39-rc1 review

On 11/13/2016 04:14 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.16.39 release. There are 346 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 3.16 000/346] 3.16.39-rc1 review

On 11/13/2016 04:14 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.16.39 release. There are 346 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be

  1   2   3   4   5   6   7   8   9   10   >