Re: [PATCH] hv_netvsc: Make sure out channel is fully opened on send

On Tue, 13 Mar 2018 20:06:50 +0100 Mohammed Gamal wrote: > Dring high network traffic changes to network interface parameters > such as number of channels or MTU can cause a kernel panic with a NULL > pointer dereference. This is due to netvsc_device_remove() being > called

Re: [PATCH] hv_netvsc: Make sure out channel is fully opened on send

On Tue, 13 Mar 2018 20:06:50 +0100 Mohammed Gamal wrote: > Dring high network traffic changes to network interface parameters > such as number of channels or MTU can cause a kernel panic with a NULL > pointer dereference. This is due to netvsc_device_remove() being > called and deallocating the

Re: [PATCH 4.15 049/146] mm/page_alloc: fix memmap_init_zone pageblock alignment

On Tue, Mar 13, 2018 at 04:23:36PM +0100, Greg Kroah-Hartman wrote: > 4.15-stable review patch. If anyone has any objections, please let me know. On 4.14 and 4.15, this patch breaks booting on dragonboard 410c and hikey 620 (both arm64). The fix has been proposed and tested but is not yet in

Re: [PATCH 4.15 049/146] mm/page_alloc: fix memmap_init_zone pageblock alignment

On Tue, Mar 13, 2018 at 04:23:36PM +0100, Greg Kroah-Hartman wrote: > 4.15-stable review patch. If anyone has any objections, please let me know. On 4.14 and 4.15, this patch breaks booting on dragonboard 410c and hikey 620 (both arm64). The fix has been proposed and tested but is not yet in

[PATCH v2] staging: bcm2835-audio: Release resources on module_exit()

In the current implementation, `rmmod snd_bcm2835` does not release resources properly. It causes an oops when trying to list sound devices. This commit fixes it. The details WRT allocation / free are described below. Device structure WRT allocation: pdev \childdev[] \card \chip

[PATCH v2] staging: bcm2835-audio: Release resources on module_exit()

In the current implementation, `rmmod snd_bcm2835` does not release resources properly. It causes an oops when trying to list sound devices. This commit fixes it. The details WRT allocation / free are described below. Device structure WRT allocation: pdev \childdev[] \card \chip

Re: [PATCH] KVM: arm/arm64: replacing per-VM's per-CPU variable

On 13/03/18 13:01, Marc Zyngier wrote: [You're repeatedly posting to the kvmarm mailing list without being subscribed to it. I've flushed the queue now, but please consider subscribing to the list, it will help everyone] On 13/03/18 21:03, Peng Hao wrote: Using a global per-CPU variable

Re: [PATCH] KVM: arm/arm64: replacing per-VM's per-CPU variable

On 13/03/18 13:01, Marc Zyngier wrote: [You're repeatedly posting to the kvmarm mailing list without being subscribed to it. I've flushed the queue now, but please consider subscribing to the list, it will help everyone] On 13/03/18 21:03, Peng Hao wrote: Using a global per-CPU variable

Re: perf-core build fails on powerpc

On 13/03/2018 19:17, Sukadev Bhattiprolu wrote: Building perf on Powerpc seems broken when using Arnaldo's perf/core branch with HEAD as: 1b442ed ("perf test: Fix exit code for record+probe_libc_inet_pton.sh") It maybe related to this commit: commit d596299 Author: John

Re: perf-core build fails on powerpc

On 13/03/2018 19:17, Sukadev Bhattiprolu wrote: Building perf on Powerpc seems broken when using Arnaldo's perf/core branch with HEAD as: 1b442ed ("perf test: Fix exit code for record+probe_libc_inet_pton.sh") It maybe related to this commit: commit d596299 Author: John

Re: [PATCH 2/2] hwmon: (ucd9000) Add debugfs attributes to provide mfr_status

On Tue, Mar 13, 2018 at 02:01:51PM -0500, Eddie James wrote: > > > On 03/10/2018 10:50 AM, Guenter Roeck wrote: > >On 03/09/2018 11:19 AM, Eddie James wrote: > >>From: Christopher Bostic > >> > >>Expose the gpiN_fault fields of mfr_status as individual debugfs >

Re: [PATCH 2/2] hwmon: (ucd9000) Add debugfs attributes to provide mfr_status

On Tue, Mar 13, 2018 at 02:01:51PM -0500, Eddie James wrote: > > > On 03/10/2018 10:50 AM, Guenter Roeck wrote: > >On 03/09/2018 11:19 AM, Eddie James wrote: > >>From: Christopher Bostic > >> > >>Expose the gpiN_fault fields of mfr_status as individual debugfs > >>attributes. This provides a

Re: [PATCH V1] Input: pm8941-pwrkey: add resin key capabilities

Tirupathi, On 3/13/2018 1:25 AM, Tirupathi Reddy T wrote: Hi Dmitry, On 3/10/2018 11:57 PM, Dmitry Torokhov wrote: On Wed, Mar 07, 2018 at 12:21:47PM -0800, Dmitry Torokhov wrote: Hi Tirupathi, On Wed, Mar 07, 2018 at 01:39:33PM +0530, Tirupathi Reddy wrote: Add resin key support to handle

Re: [PATCH V1] Input: pm8941-pwrkey: add resin key capabilities

Tirupathi, On 3/13/2018 1:25 AM, Tirupathi Reddy T wrote: Hi Dmitry, On 3/10/2018 11:57 PM, Dmitry Torokhov wrote: On Wed, Mar 07, 2018 at 12:21:47PM -0800, Dmitry Torokhov wrote: Hi Tirupathi, On Wed, Mar 07, 2018 at 01:39:33PM +0530, Tirupathi Reddy wrote: Add resin key support to handle

Re: [PATCH V2] Input: pm8941-pwrkey: add resin key capabilities

Hi Tirupathi, On 3/13/2018 1:35 AM, Tirupathi Reddy wrote: Add resin key support to handle different types of key events defined in different platforms. Describe "resin"  in the commit text? or just call it same as power key or different purpose? +static irqreturn_t

Re: [PATCH V2] Input: pm8941-pwrkey: add resin key capabilities

Hi Tirupathi, On 3/13/2018 1:35 AM, Tirupathi Reddy wrote: Add resin key support to handle different types of key events defined in different platforms. Describe "resin"  in the commit text? or just call it same as power key or different purpose? +static irqreturn_t

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

On 13/03/18 01:10 PM, Sinan Kaya wrote: > I was thinking of this for the pci_p2pdma_add_client() case for the > parent pointer. > > +struct pci_p2pdma_client { > + struct list_head list; > + struct pci_dev *client; > + struct pci_dev *provider; > +}; Yeah, that structure only

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

On 13/03/18 01:10 PM, Sinan Kaya wrote: > I was thinking of this for the pci_p2pdma_add_client() case for the > parent pointer. > > +struct pci_p2pdma_client { > + struct list_head list; > + struct pci_dev *client; > + struct pci_dev *provider; > +}; Yeah, that structure only

perf-core build fails on powerpc

Building perf on Powerpc seems broken when using Arnaldo's perf/core branch with HEAD as: 1b442ed ("perf test: Fix exit code for record+probe_libc_inet_pton.sh") It maybe related to this commit: commit d596299 Author: John Garry Date: Thu

perf-core build fails on powerpc

Building perf on Powerpc seems broken when using Arnaldo's perf/core branch with HEAD as: 1b442ed ("perf test: Fix exit code for record+probe_libc_inet_pton.sh") It maybe related to this commit: commit d596299 Author: John Garry Date: Thu Mar 8 18:58:29 2018

[PATCH] iio/adc/ad7291: Improve unlocking of a mutex in ad7291_read_raw()

From: Markus Elfring Date: Tue, 13 Mar 2018 20:08:40 +0100 * Add a jump target so that a call of the function "mutex_unlock" is stored only once in this function implementation. * Replace three calls by goto statements. This issue was detected by using the

[PATCH] iio/adc/ad7291: Improve unlocking of a mutex in ad7291_read_raw()

From: Markus Elfring Date: Tue, 13 Mar 2018 20:08:40 +0100 * Add a jump target so that a call of the function "mutex_unlock" is stored only once in this function implementation. * Replace three calls by goto statements. This issue was detected by using the Coccinelle software.

Re: [PATCH V2 6/7] thermal/drivers/cpu_cooling: Introduce the cpu idle cooling driver

On 26/02/2018 05:30, Viresh Kumar wrote: [ ... ] + /* + * The last CPU waking up is in charge of setting the + * timer. If the CPU is hotplugged, the timer will + * move to another CPU (which may not belong to the + * same

Re: [PATCH V2 6/7] thermal/drivers/cpu_cooling: Introduce the cpu idle cooling driver

On 26/02/2018 05:30, Viresh Kumar wrote: [ ... ] + /* + * The last CPU waking up is in charge of setting the + * timer. If the CPU is hotplugged, the timer will + * move to another CPU (which may not belong to the + * same

Re: [PATCH v3 7/7] x86/kvm: use Enlightened VMCS when running on Hyper-V

2018-03-12 15:19+0100, Vitaly Kuznetsov: > Thomas Gleixner writes: > > > On Fri, 9 Mar 2018, Vitaly Kuznetsov wrote: > > > >> Enlightened VMCS is just a structure in memory, the main benefit > >> besides avoiding somewhat slower VMREAD/VMWRITE is using clean field > >> mask:

Re: [PATCH v3 7/7] x86/kvm: use Enlightened VMCS when running on Hyper-V

2018-03-12 15:19+0100, Vitaly Kuznetsov: > Thomas Gleixner writes: > > > On Fri, 9 Mar 2018, Vitaly Kuznetsov wrote: > > > >> Enlightened VMCS is just a structure in memory, the main benefit > >> besides avoiding somewhat slower VMREAD/VMWRITE is using clean field > >> mask: we tell the

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

On 3/13/2018 2:44 PM, Logan Gunthorpe wrote: >> Do you think you can keep a pointer to the parent bridge instead of querying >> it >> via get_upstream_bridge_port() here so that we can reuse your >> pci_p2pdma_disable_acs() in the future. > > Keep a pointer where? pci_p2pdma_disable_acs() and

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

On 3/13/2018 2:44 PM, Logan Gunthorpe wrote: >> Do you think you can keep a pointer to the parent bridge instead of querying >> it >> via get_upstream_bridge_port() here so that we can reuse your >> pci_p2pdma_disable_acs() in the future. > > Keep a pointer where? pci_p2pdma_disable_acs() and

[PATCH] hv_netvsc: Make sure out channel is fully opened on send

Dring high network traffic changes to network interface parameters such as number of channels or MTU can cause a kernel panic with a NULL pointer dereference. This is due to netvsc_device_remove() being called and deallocating the channel ring buffers, which can then be accessed by

[PATCH] hv_netvsc: Make sure out channel is fully opened on send

Dring high network traffic changes to network interface parameters such as number of channels or MTU can cause a kernel panic with a NULL pointer dereference. This is due to netvsc_device_remove() being called and deallocating the channel ring buffers, which can then be accessed by

Re: [PATCH 2/2] hwmon: (ucd9000) Add debugfs attributes to provide mfr_status

On 03/10/2018 10:50 AM, Guenter Roeck wrote: On 03/09/2018 11:19 AM, Eddie James wrote: From: Christopher Bostic Expose the gpiN_fault fields of mfr_status as individual debugfs attributes. This provides a way for users to be easily notified of gpi faults. Also

Re: [PATCH 2/2] hwmon: (ucd9000) Add debugfs attributes to provide mfr_status

On 03/10/2018 10:50 AM, Guenter Roeck wrote: On 03/09/2018 11:19 AM, Eddie James wrote: From: Christopher Bostic Expose the gpiN_fault fields of mfr_status as individual debugfs attributes. This provides a way for users to be easily notified of gpi faults. Also provide the whole mfr_status

Re: [PATCH v2 7/8] [PATCH 7/8] drivers/hwmon: Add a generic PECI hwmon client driver

Hi Stef, Thanks for sharing your time to test it. That is expected result in v2. Previously in v1, it used delayed creation on core temperature group so it was okay if hwmon driver is registered when client CPU is powered down, but in v2, the driver should check resolved cores at probing

Re: [PATCH v2 7/8] [PATCH 7/8] drivers/hwmon: Add a generic PECI hwmon client driver

Hi Stef, Thanks for sharing your time to test it. That is expected result in v2. Previously in v1, it used delayed creation on core temperature group so it was okay if hwmon driver is registered when client CPU is powered down, but in v2, the driver should check resolved cores at probing

RE: [PATCH v5 1/4] dt-bindings: firmware: Add bindings for ZynqMP firmware

> -Original Message- > From: Sudeep Holla [mailto:sudeep.ho...@arm.com] > Sent: Tuesday, March 13, 2018 3:16 AM > To: Jolly Shah > Cc: Sudeep Holla ; gre...@linuxfoundation.org; > m...@codeblueprint.co.uk; hkallwe...@gmail.com;

RE: [PATCH v5 1/4] dt-bindings: firmware: Add bindings for ZynqMP firmware

> -Original Message- > From: Sudeep Holla [mailto:sudeep.ho...@arm.com] > Sent: Tuesday, March 13, 2018 3:16 AM > To: Jolly Shah > Cc: Sudeep Holla ; gre...@linuxfoundation.org; > m...@codeblueprint.co.uk; hkallwe...@gmail.com; michal.si...@xilinx.com; > robh...@kernel.org;

Re: [v5 1/2] mm: disable interrupts while initializing deferred pages

On Tue, 13 Mar 2018 12:04:30 -0400 Pavel Tatashin wrote: > > > > > --- a/mm/page_alloc.c > > > +++ b/mm/page_alloc.c > > > @@ -1506,7 +1506,6 @@ static void __init deferred_free_pages(int nid, int > > > zid, unsigned long pfn, > > > } else if (!(pfn &

Re: [v5 1/2] mm: disable interrupts while initializing deferred pages

On Tue, 13 Mar 2018 12:04:30 -0400 Pavel Tatashin wrote: > > > > > --- a/mm/page_alloc.c > > > +++ b/mm/page_alloc.c > > > @@ -1506,7 +1506,6 @@ static void __init deferred_free_pages(int nid, int > > > zid, unsigned long pfn, > > > } else if (!(pfn & nr_pgmask)) { > > >

Re: [PATCH v2 5/5] iommu/amd - Add a debugfs entry to specify a IOMMU device table entry

On 03/13/2018 12:20 PM, Andy Shevchenko wrote: + oboff += OSCNPRINTF("%02x:%02x:%x (%u / %04x)\n", + PCI_BUS_NUM(amd_iommu_devid), + PCI_SLOT(amd_iommu_devid), +

Re: [PATCH v2 5/5] iommu/amd - Add a debugfs entry to specify a IOMMU device table entry

On 03/13/2018 12:20 PM, Andy Shevchenko wrote: + oboff += OSCNPRINTF("%02x:%02x:%x (%u / %04x)\n", + PCI_BUS_NUM(amd_iommu_devid), + PCI_SLOT(amd_iommu_devid), +

Re: [PATCH v2 1/5] iommu/amd - Add debugfs support

On 03/13/2018 12:16 PM, Andy Shevchenko wrote: On Fri, Mar 9, 2018 at 2:50 AM, Gary R Hook wrote: + default n Redundant Roger that. +#include +#include +#include Keep in order? What order would that be? These few needed files are listed in the same order

Re: [PATCH v2 1/5] iommu/amd - Add debugfs support

On 03/13/2018 12:16 PM, Andy Shevchenko wrote: On Fri, Mar 9, 2018 at 2:50 AM, Gary R Hook wrote: + default n Redundant Roger that. +#include +#include +#include Keep in order? What order would that be? These few needed files are listed in the same order as which they

[PATCH V2] perf/x86/intel/uncore: Querying number of CHAs from CAPID6 register

From: Kan Liang The number of CHAs is miscalculated on multi PCI domain systems on Skylake server. (From Kroening, Gary: For systems with a single PCI segment, it is sufficient to look for the bus number to change in order to determine that all of the CHa's have been

[PATCH V2] perf/x86/intel/uncore: Querying number of CHAs from CAPID6 register

From: Kan Liang The number of CHAs is miscalculated on multi PCI domain systems on Skylake server. (From Kroening, Gary: For systems with a single PCI segment, it is sufficient to look for the bus number to change in order to determine that all of the CHa's have been counted for a single

Re: [3/3] irqchip/gic-v3: Bounds check redistributor accesses

Marc, On Tue, Mar 13, 2018 at 9:21 AM, Marc Zyngier wrote: > Hi Lokesh, > > On 13/03/18 13:38, Lokesh Vutla wrote: >> Hi All, >> >> On Wednesday 11 October 2017 03:11 PM, Punit Agrawal wrote: >>> The kernel crashes while iterating over a redistributor that is >>>

Re: [3/3] irqchip/gic-v3: Bounds check redistributor accesses

Marc, On Tue, Mar 13, 2018 at 9:21 AM, Marc Zyngier wrote: > Hi Lokesh, > > On 13/03/18 13:38, Lokesh Vutla wrote: >> Hi All, >> >> On Wednesday 11 October 2017 03:11 PM, Punit Agrawal wrote: >>> The kernel crashes while iterating over a redistributor that is >>> in-correctly sized by the

Re: [PATCH v4 1/6] sysctl: Add flags to support min/max range clamping

On 03/13/2018 01:46 PM, Eric W. Biederman wrote: > Waiman Long writes: > >> When minimum/maximum values are specified for a sysctl parameter in >> the ctl_table structure with proc_dointvec_minmax() handler, update >> to that parameter will fail with error if the given value

Re: [PATCH v4 1/6] sysctl: Add flags to support min/max range clamping

On 03/13/2018 01:46 PM, Eric W. Biederman wrote: > Waiman Long writes: > >> When minimum/maximum values are specified for a sysctl parameter in >> the ctl_table structure with proc_dointvec_minmax() handler, update >> to that parameter will fail with error if the given value is outside >> of the

Re: [PATCH v3 3/3] arm64: dts: renesas: Add LVDS decoder to R-Car V3M Eagle

On Tue, Mar 13, 2018 at 03:30:25PM +0100, Jacopo Mondi wrote: > The R-Car V3M Eagle board includes a transparent THC63LVD1024 LVDS > decoder, connected to the on-chip LVDS encoder output on one side > and to HDMI encoder ADV7511w on the other one. > > As the decoder does not need any

Re: [PATCH v3 3/3] arm64: dts: renesas: Add LVDS decoder to R-Car V3M Eagle

On Tue, Mar 13, 2018 at 03:30:25PM +0100, Jacopo Mondi wrote: > The R-Car V3M Eagle board includes a transparent THC63LVD1024 LVDS > decoder, connected to the on-chip LVDS encoder output on one side > and to HDMI encoder ADV7511w on the other one. > > As the decoder does not need any

[GIT PULL] auxdisplay for v4.16-rc6

Hi Linus, Please pull these small changes to silence a few warnings in auxdisplay. This is my first pull request, so if there is anything wrong, please let me know! Also, note that for the moment my PGP/GPG key is only signed by 2 other kernel maintainers and that we did it over email/Skype. I

[GIT PULL] auxdisplay for v4.16-rc6

Hi Linus, Please pull these small changes to silence a few warnings in auxdisplay. This is my first pull request, so if there is anything wrong, please let me know! Also, note that for the moment my PGP/GPG key is only signed by 2 other kernel maintainers and that we did it over email/Skype. I

Re: [GIT PULL] bcm2835-dt-next-2018-03-13

On 03/13/2018 10:30 AM, Eric Anholt wrote: > Hi Florian, > > The following changes since commit bcc76c4014dce4e3834dbd5b7f6593cbcfbfebe0: > > ARM: dts: bcm2835-rpi-zero-w: Enable OTG mode (2018-02-26 15:02:23 -0800) > > are available in the Git repository at: > >

Re: [GIT PULL] bcm2835-dt-next-2018-03-13

On 03/13/2018 10:30 AM, Eric Anholt wrote: > Hi Florian, > > The following changes since commit bcc76c4014dce4e3834dbd5b7f6593cbcfbfebe0: > > ARM: dts: bcm2835-rpi-zero-w: Enable OTG mode (2018-02-26 15:02:23 -0800) > > are available in the Git repository at: > >

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

On 13/03/18 11:49 AM, Sinan Kaya wrote: And there's also the ACS problem which means if you want to use P2P on the root ports you'll have to disable ACS on the entire system. (Or preferably, the IOMMU groups need to get more sophisticated to allow for dynamic changes). Do you think you

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

On 13/03/18 11:49 AM, Sinan Kaya wrote: And there's also the ACS problem which means if you want to use P2P on the root ports you'll have to disable ACS on the entire system. (Or preferably, the IOMMU groups need to get more sophisticated to allow for dynamic changes). Do you think you

[RT PATCH 2/2] block: blk-mq: move blk_queue_usage_counter_release() into process context

| BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914 | in_atomic(): 1, irqs_disabled(): 0, pid: 255, name: kworker/u257:6 | 5 locks held by kworker/u257:6/255: | #0: ("events_unbound"){.+.+.+}, at: [] process_one_work+0x171/0x5e0 | #1: ((>work)){+.+.+.}, at:

[RT PATCH 2/2] block: blk-mq: move blk_queue_usage_counter_release() into process context

| BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:914 | in_atomic(): 1, irqs_disabled(): 0, pid: 255, name: kworker/u257:6 | 5 locks held by kworker/u257:6/255: | #0: ("events_unbound"){.+.+.+}, at: [] process_one_work+0x171/0x5e0 | #1: ((>work)){+.+.+.}, at:

[RT PATCH 1/2] Revert "block: blk-mq: Use swait"

This reverts commit "block: blk-mq: Use swait". The issue remains but will be fixed differently. Signed-off-by: Sebastian Andrzej Siewior --- block/blk-core.c | 6 +++--- block/blk-mq.c | 8 include/linux/blkdev.h | 2 +- 3 files changed, 8

[RT PATCH 1/2] Revert "block: blk-mq: Use swait"

This reverts commit "block: blk-mq: Use swait". The issue remains but will be fixed differently. Signed-off-by: Sebastian Andrzej Siewior --- block/blk-core.c | 6 +++--- block/blk-mq.c | 8 include/linux/blkdev.h | 2 +- 3 files changed, 8 insertions(+), 8 deletions(-)

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

On 12/03/18 09:28 PM, Sinan Kaya wrote: Maybe, dev parameter should also be struct pci_dev so that you can get rid of all to_pci_dev() calls in this code including find_parent_pci_dev() function. No, this was mentioned in v2. find_parent_pci_dev is necessary because the calling drivers

Re: [PATCH v3 01/11] PCI/P2PDMA: Support peer-to-peer memory

On 12/03/18 09:28 PM, Sinan Kaya wrote: Maybe, dev parameter should also be struct pci_dev so that you can get rid of all to_pci_dev() calls in this code including find_parent_pci_dev() function. No, this was mentioned in v2. find_parent_pci_dev is necessary because the calling drivers

[PATCH v3 1/3] arm64: dts: apq8096-db820c: enable bluetooth node

Add a new serial node for the Qualcomm BT controller QCA6174. This allows automatic probing and hci registration through the serdev framework instead of relying on the userspace helpers. Signed-off-by: Thierry Escande ---

[PATCH v3 1/3] arm64: dts: apq8096-db820c: enable bluetooth node

Add a new serial node for the Qualcomm BT controller QCA6174. This allows automatic probing and hci registration through the serdev framework instead of relying on the userspace helpers. Signed-off-by: Thierry Escande --- arch/arm64/boot/dts/qcom/apq8096-db820c-pins.dtsi | 14 ++

RE: [PATCH 2/3] dt-bindings: clock: Add bindings for ZynqMP clock driver

Hi Rob, > -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: Wednesday, March 07, 2018 5:20 PM > To: Jolly Shah > Cc: mturque...@baylibre.com; sb...@codeaurora.org; > michal.si...@xilinx.com; mark.rutl...@arm.com; linux-...@vger.kernel.org; >

RE: [PATCH 2/3] dt-bindings: clock: Add bindings for ZynqMP clock driver

Hi Rob, > -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: Wednesday, March 07, 2018 5:20 PM > To: Jolly Shah > Cc: mturque...@baylibre.com; sb...@codeaurora.org; > michal.si...@xilinx.com; mark.rutl...@arm.com; linux-...@vger.kernel.org; >

Re: [PATCH v4 4/6] ipc: Clamp msgmni and shmmni to the real IPCMNI limit

On 03/13/2018 02:17 PM, Eric W. Biederman wrote: > Waiman Long writes: > >> A user can write arbitrary integer values to msgmni and shmmni sysctl >> parameters without getting error, but the actual limit is really >> IPCMNI (32k). This can mislead users as they think they can

Re: [PATCH v4 4/6] ipc: Clamp msgmni and shmmni to the real IPCMNI limit

On 03/13/2018 02:17 PM, Eric W. Biederman wrote: > Waiman Long writes: > >> A user can write arbitrary integer values to msgmni and shmmni sysctl >> parameters without getting error, but the actual limit is really >> IPCMNI (32k). This can mislead users as they think they can get a >> value that

[PATCH v3 2/3] dt-bindings: net: bluetooth: Add qualcomm-bluetooth

Add binding document for serial bluetooth chips using Qualcomm protocol. Signed-off-by: Thierry Escande --- .../devicetree/bindings/net/qualcomm-bluetooth.txt | 34 ++ 1 file changed, 34 insertions(+) create mode 100644

[PATCH v3 2/3] dt-bindings: net: bluetooth: Add qualcomm-bluetooth

Add binding document for serial bluetooth chips using Qualcomm protocol. Signed-off-by: Thierry Escande --- .../devicetree/bindings/net/qualcomm-bluetooth.txt | 34 ++ 1 file changed, 34 insertions(+) create mode 100644

[PATCH v3 3/3] Bluetooth: hci_qca: Add serdev support

Add support for Qualcomm serial slave devices. Probe the serial device, retrieve its maximum speed and register a new hci uart device. Signed-off-by: Thierry Escande --- v3: - Remove redundant call to gpiod_set_value() after devm_gpiod_get() - Check returned values

[PATCH v3 3/3] Bluetooth: hci_qca: Add serdev support

Add support for Qualcomm serial slave devices. Probe the serial device, retrieve its maximum speed and register a new hci uart device. Signed-off-by: Thierry Escande --- v3: - Remove redundant call to gpiod_set_value() after devm_gpiod_get() - Check returned values for clk_set_rate() and

[PATCH v3 0/3] Bluetooth: hci_qca: Add serdev support

Hi, This patchset enables the Qualcomm BT controller QCA6174 node in the device tree of the db820c board. This allows the bluetooth chipset to be probed and registered against the hci layer by using the serdev framework. This patchset also contains the documentation for the compatible string

[PATCH v3 0/3] Bluetooth: hci_qca: Add serdev support

Hi, This patchset enables the Qualcomm BT controller QCA6174 node in the device tree of the db820c board. This allows the bluetooth chipset to be probed and registered against the hci layer by using the serdev framework. This patchset also contains the documentation for the compatible string

[PATCH] spi: bcm-qspi: fIX some error handling paths

For some reason, commit c0368e4db4a3 ("spi: bcm-qspi: Fix use after free in bcm_qspi_probe() in error path") has updated some gotos, but not all of them. This looks spurious, so fix it. Fixes: fa236a7ef240 ("spi: bcm-qspi: Add Broadcom MSPI driver") Signed-off-by: Christophe JAILLET

Re: [PATCH 2/2] mm: Add kvmalloc_ab_c and kvzalloc_struct

On Tue, Mar 13, 2018 at 06:19:51PM +0100, Julia Lawall wrote: > On Thu, 8 Mar 2018, Matthew Wilcox wrote: > > On Thu, Mar 08, 2018 at 07:24:47AM +0100, Julia Lawall wrote: > > > Thanks. So it's OK to replace kmalloc and kzalloc, even though they > > > didn't previously consider vmalloc and even

[PATCH RFC 2/8] powerpc: Use barrier_nospec in copy_from_user

Coopypasta from x86. Signed-off-by: Michal Suchanek --- arch/powerpc/include/asm/uaccess.h | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/arch/powerpc/include/asm/uaccess.h b/arch/powerpc/include/asm/uaccess.h index 51bfeb8777f0..af9b0e731f46

[PATCH] spi: bcm-qspi: fIX some error handling paths

For some reason, commit c0368e4db4a3 ("spi: bcm-qspi: Fix use after free in bcm_qspi_probe() in error path") has updated some gotos, but not all of them. This looks spurious, so fix it. Fixes: fa236a7ef240 ("spi: bcm-qspi: Add Broadcom MSPI driver") Signed-off-by: Christophe JAILLET --- I've

Re: [PATCH 2/2] mm: Add kvmalloc_ab_c and kvzalloc_struct

On Tue, Mar 13, 2018 at 06:19:51PM +0100, Julia Lawall wrote: > On Thu, 8 Mar 2018, Matthew Wilcox wrote: > > On Thu, Mar 08, 2018 at 07:24:47AM +0100, Julia Lawall wrote: > > > Thanks. So it's OK to replace kmalloc and kzalloc, even though they > > > didn't previously consider vmalloc and even

[PATCH RFC 2/8] powerpc: Use barrier_nospec in copy_from_user

Coopypasta from x86. Signed-off-by: Michal Suchanek --- arch/powerpc/include/asm/uaccess.h | 11 ++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/arch/powerpc/include/asm/uaccess.h b/arch/powerpc/include/asm/uaccess.h index 51bfeb8777f0..af9b0e731f46 100644 ---

[PATCH RFC 0/8] powerpc barrier_nospec

Hello, this is patchset adding barrier_nospec on powerpc. It is based on the out-of-tree gmb() patch and the existing rfi patches. I do not have the tests for the Spectre/Meltdown issues available so this is untested. Feedback on the general approach as well as actual effectivity is welcome.

[PATCH RFC 0/8] powerpc barrier_nospec

Hello, this is patchset adding barrier_nospec on powerpc. It is based on the out-of-tree gmb() patch and the existing rfi patches. I do not have the tests for the Spectre/Meltdown issues available so this is untested. Feedback on the general approach as well as actual effectivity is welcome.

Re: [PATCH 2/2] mm: Add kvmalloc_ab_c and kvzalloc_struct

On Tue, 13 Mar 2018, Matthew Wilcox wrote: > On Tue, Mar 13, 2018 at 06:19:51PM +0100, Julia Lawall wrote: > > On Thu, 8 Mar 2018, Matthew Wilcox wrote: > > > On Thu, Mar 08, 2018 at 07:24:47AM +0100, Julia Lawall wrote: > > > > Thanks. So it's OK to replace kmalloc and kzalloc, even though

Re: [PATCH 2/2] mm: Add kvmalloc_ab_c and kvzalloc_struct

On Tue, 13 Mar 2018, Matthew Wilcox wrote: > On Tue, Mar 13, 2018 at 06:19:51PM +0100, Julia Lawall wrote: > > On Thu, 8 Mar 2018, Matthew Wilcox wrote: > > > On Thu, Mar 08, 2018 at 07:24:47AM +0100, Julia Lawall wrote: > > > > Thanks. So it's OK to replace kmalloc and kzalloc, even though

Re: [PATCH 00/11] RISC-V: Resolve the issue of loadable module on 64-bit

On Tue, 13 Mar 2018 01:35:05 PDT (-0700), z...@andestech.com wrote: These patches resolve the some issues of loadable module. - symbol out of ranges - unknown relocation types The reference of external variable and function symbols cannot exceed 32-bit offset ranges in kernel module. The

Re: [PATCH 00/11] RISC-V: Resolve the issue of loadable module on 64-bit

On Tue, 13 Mar 2018 01:35:05 PDT (-0700), z...@andestech.com wrote: These patches resolve the some issues of loadable module. - symbol out of ranges - unknown relocation types The reference of external variable and function symbols cannot exceed 32-bit offset ranges in kernel module. The

Re: [bug, bisected] pfifo_fast causes packet reordering

On Tue, Mar 13, 2018 at 11:24 AM, Jakob Unterwurzacher wrote: > During stress-testing our "ucan" USB/CAN adapter SocketCAN driver on Linux > v4.16-rc4-383-ged58d66f60b3 we observed that a small fraction of packets are > delivered out-of-order. > > We

Re: [bug, bisected] pfifo_fast causes packet reordering

On Tue, Mar 13, 2018 at 11:24 AM, Jakob Unterwurzacher wrote: > During stress-testing our "ucan" USB/CAN adapter SocketCAN driver on Linux > v4.16-rc4-383-ged58d66f60b3 we observed that a small fraction of packets are > delivered out-of-order. > > We have tracked the problem down to the driver

Re: [PATCH 0/3] irqchip: GIC kexec/kdump improvement and workarounds

On 13/03/18 17:51, Mark Rutland wrote: > On Tue, Mar 13, 2018 at 05:21:00PM +, Marc Zyngier wrote: >> As kexec and kdump are getting used a bit more intensively, I've been >> made aware of a number of shortcomings. >> >> The main gripe is from folks trying to launch a kdump kernel from >>

Re: [PATCH 0/3] irqchip: GIC kexec/kdump improvement and workarounds

On 13/03/18 17:51, Mark Rutland wrote: > On Tue, Mar 13, 2018 at 05:21:00PM +, Marc Zyngier wrote: >> As kexec and kdump are getting used a bit more intensively, I've been >> made aware of a number of shortcomings. >> >> The main gripe is from folks trying to launch a kdump kernel from >>

[PATCH RFC 4/8] powerpc/64s: Add support for ori barrier_nospec

Copypasta from rfi implementation Signed-off-by: Michal Suchanek --- arch/powerpc/include/asm/barrier.h| 4 ++-- arch/powerpc/include/asm/feature-fixups.h | 9 + arch/powerpc/include/asm/setup.h | 8 arch/powerpc/kernel/setup_64.c

[PATCH RFC 4/8] powerpc/64s: Add support for ori barrier_nospec

Copypasta from rfi implementation Signed-off-by: Michal Suchanek --- arch/powerpc/include/asm/barrier.h| 4 ++-- arch/powerpc/include/asm/feature-fixups.h | 9 + arch/powerpc/include/asm/setup.h | 8 arch/powerpc/kernel/setup_64.c| 29

[PATCH RFC 1/8] powerpc: Add barrier_nospec

Copypasta from original gmb() and rfi implementation Signed-off-by: Michal Suchanek --- arch/powerpc/include/asm/barrier.h | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/powerpc/include/asm/barrier.h b/arch/powerpc/include/asm/barrier.h index

[PATCH RFC 1/8] powerpc: Add barrier_nospec

Copypasta from original gmb() and rfi implementation Signed-off-by: Michal Suchanek --- arch/powerpc/include/asm/barrier.h | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/powerpc/include/asm/barrier.h b/arch/powerpc/include/asm/barrier.h index 10daa1d56e0a..8e47b3abe405

[PATCH RFC 5/8] powerpc/64: Patch barrier_nospec in modules

Copypasta from lwsync patching. Note that unlike RFI which is patched only in kernel the nospec state reflects settings at the time the module was loaded. Iterating all modules and re-patching every time the settings change is not implemented. Signed-off-by: Michal Suchanek

[PATCH RFC 5/8] powerpc/64: Patch barrier_nospec in modules

Copypasta from lwsync patching. Note that unlike RFI which is patched only in kernel the nospec state reflects settings at the time the module was loaded. Iterating all modules and re-patching every time the settings change is not implemented. Signed-off-by: Michal Suchanek ---

[PATCH RFC 6/8] powerpc/64: barrier_nospec: Add debugfs trigger

Copypasta from rfi implementation Signed-off-by: Michal Suchanek --- arch/powerpc/kernel/setup_64.c | 35 +++ 1 file changed, 35 insertions(+) diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c index

[PATCH RFC 6/8] powerpc/64: barrier_nospec: Add debugfs trigger

Copypasta from rfi implementation Signed-off-by: Michal Suchanek --- arch/powerpc/kernel/setup_64.c | 35 +++ 1 file changed, 35 insertions(+) diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c index d1d9f047161e..4b67b7b877d9 100644

[PATCH v4] dmaengine: pl330: flush before wait, and add dev burst support.

Do DMAFLUSHP _before_ the first DMAWFP to ensure controller and peripheral are in agreement about dma request state before first transfer. Add support for burst transfers to/from peripherals. In the new scheme, the controller does as many burst transfers as it can then transfers the remaining

[PATCH RFC 3/8] powerpc/64: Use barrier_nospec in syscall entry

Signed-off-by: Michal Suchanek --- arch/powerpc/kernel/entry_64.S | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/powerpc/kernel/entry_64.S b/arch/powerpc/kernel/entry_64.S index 2cb5109a7ea3..7bfc4cf48af2 100644 --- a/arch/powerpc/kernel/entry_64.S +++

<    3   4   5   6   7   8   9   10   11   12   >