[tip:perf/urgent] perf tools: Fix a typo in a variable name in the Documentation Makefile

Commit-ID: 89b66500f739e0033ef59011e3df694f2053679d Gitweb: https://git.kernel.org/tip/89b66500f739e0033ef59011e3df694f2053679d Author: Masanari Iida AuthorDate: Thu, 1 Aug 2019 12:28:12 +0900 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 8 Aug 2019 15:41:10 -0300 perf tools:

[tip:perf/urgent] perf cpumap: Fix writing to illegal memory in handling cpumap mask

Commit-ID: 5f5e25f1c7933a6e1673515c0b1d5acd82fea1ed Gitweb: https://git.kernel.org/tip/5f5e25f1c7933a6e1673515c0b1d5acd82fea1ed Author: He Zhe AuthorDate: Fri, 2 Aug 2019 16:29:52 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 8 Aug 2019 15:41:10 -0300 perf cpumap: Fix

[tip:perf/urgent] perf ftrace: Fix failure to set cpumask when only one cpu is present

Commit-ID: cf30ae726c011e0372fd4c2d588466c8b50a8907 Gitweb: https://git.kernel.org/tip/cf30ae726c011e0372fd4c2d588466c8b50a8907 Author: He Zhe AuthorDate: Fri, 2 Aug 2019 16:29:51 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 8 Aug 2019 15:41:10 -0300 perf ftrace: Fix

[tip:perf/urgent] perf db-export: Fix thread__exec_comm()

Commit-ID: 3de7ae0b2a1d86dbb23d0cb135150534fdb2e836 Gitweb: https://git.kernel.org/tip/3de7ae0b2a1d86dbb23d0cb135150534fdb2e836 Author: Adrian Hunter AuthorDate: Thu, 8 Aug 2019 09:48:23 +0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 8 Aug 2019 15:41:10 -0300 perf

Re: [PATCH 2/2 v2] tracing: Document the stack trace algorithm in the comments

On Wed, Aug 07, 2019 at 01:28:28PM -0400, Steven Rostedt wrote: > From: "Steven Rostedt (VMware)" > > As the max stack tracer algorithm is not that easy to understand from the > code, add comments that explain the algorithm and mentions how > ARCH_RET_ADDR_AFTER_LOCAL_VARS affects it. > > Link:

[tip:perf/urgent] perf annotate: Fix printing of unaugmented disassembled instructions from BPF

Commit-ID: 85127775a65fc58e69af0c44513937d471ccbe7b Gitweb: https://git.kernel.org/tip/85127775a65fc58e69af0c44513937d471ccbe7b Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 6 Aug 2019 11:24:09 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 8 Aug 2019 15:40:56 -0300

[tip:perf/urgent] perf bench numa: Fix cpu0 binding

Commit-ID: 6bbfe4e602691b90ac866712bd4c43c51e546a60 Gitweb: https://git.kernel.org/tip/6bbfe4e602691b90ac866712bd4c43c51e546a60 Author: Jiri Olsa AuthorDate: Thu, 1 Aug 2019 16:26:42 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 1 Aug 2019 11:34:13 -0300 perf bench numa:

Re: [PATCH] drm/i915: Remove redundant user_access_end() from __copy_from_user() error path

On Tue, Aug 6, 2019 at 5:59 AM Josh Poimboeuf wrote: > > On Mon, Aug 05, 2019 at 09:29:53PM +0200, Sedat Dilek wrote: > > On Wed, Jul 31, 2019 at 2:25 PM Sedat Dilek wrote: > > > > > > On Fri, Jul 26, 2019 at 9:30 PM Chris Wilson > > > wrote: > > > > > > > > Quoting Thomas Gleixner (2019-07-26

Re: [PATCH RFC v1 1/2] rcu/tree: Add basic support for kfree_rcu batching

On Thu, Aug 08, 2019 at 11:11:12AM -0700, Paul E. McKenney wrote: > On Thu, Aug 08, 2019 at 07:26:10PM +0900, Byungchul Park wrote: > > On Wed, Aug 07, 2019 at 05:45:04AM -0400, Joel Fernandes wrote: > > > On Tue, Aug 06, 2019 at 04:56:31PM -0700, Paul E. McKenney wrote: > > > > [snip] > > > > >

Re: [PATCH V2 09/10] x86/resctrl: Pseudo-lock portions of multiple resources

Hi Borislav, On 8/8/2019 1:44 AM, Borislav Petkov wrote: > On Wed, Aug 07, 2019 at 12:23:29PM -0700, Reinette Chatre wrote: >> I do not fully understand this proposal. All those goto labels take care >> of the the different failures that can be encountered during the >> initialization of the

Re: [PATCH] HID: apple: Fix stuck function keys when using FN

Hi Benjamin, On Mon, 8 Jul 2019 at 22:35, João Moreno wrote: > > Hi Benjamin, > > No worries, also pretty busy over here. Didn't mean to press. > > On Mon, 1 Jul 2019 at 10:32, Benjamin Tissoires > wrote: > > > > Hi João, > > > > On Sun, Jun 30, 2019 at 10:15 PM João Moreno wrote: > > > > > >

Re: [PATCH V2 01/10] x86/CPU: Expose if cache is inclusive of lower level caches

Hi Borislav, On 8/8/2019 1:13 AM, Borislav Petkov wrote: > On Thu, Aug 08, 2019 at 10:08:41AM +0200, Borislav Petkov wrote: >> Ok, tglx and I talked it over a bit on IRC: so your 1/10 patch is pretty >> close - just leave out the generic struct cacheinfo bits and put the >> cache inclusivity

Re: BUG: soft lockup in tcp_delack_timer

On Thu, 8 Aug 2019, syzbot wrote: Cc+ Eric, net-dev > Hello, > > syzbot found the following crash on: > > HEAD commit:0d8b3265 Add linux-next specific files for 20190729 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=1101fdc860 > kernel config:

Re: [PATCH] mm/oom: Add killed process selection information

[please do not top-post] On Thu 08-08-19 12:21:30, Edward Chron wrote: > It is helpful to the admin that looks at the kill message and records this > information. OOMs can come in bunches. > Knowing how much resource the oom selected process was using at the time of > the OOM event is very

[ANNOUNCE] 4.4.188-rt185

Hello RT Folks! I'm pleased to announce the 4.4.188-rt185 stable release. This release is just an update to the new stable 4.4.188 version and no RT specific changes have been made. The know issue from last time is now resolved. The missing patch for -rt has is now also part of stable

RE: [PATCH v2 2/2] nvme-pci: Allow PCI bus-level PM to be used if ASPM is disabled

> This is more meaningful to you than to most people because "applying > the standard PCI PM" doesn't tell us what that means in terms of the > device. Presumably it has something to do with a D-state transition? > I *assume* a suspend might involve the D0 -> D3hot transition you > mention below?

Re: [PATCH] arch/x86/kernel/cpu/umwait.c - remove unused variable

Valdis, On Thu, 8 Aug 2019, Valdis Klētnieks wrote: I really appreciate your work, but can you please refrain from using file names as prefixes? git log $FILE gives you usually a pretty good hint what the proper prefix is: bd9a0c97e53c ("x86/umwait: Add sysfs interface to control umwait

Re: [PATCH v2 2/2] nvme-pci: Allow PCI bus-level PM to be used if ASPM is disabled

On Thu, Aug 08, 2019 at 01:39:54PM -0500, Bjorn Helgaas wrote: > On Thu, Aug 08, 2019 at 04:47:45PM +0200, Rafael J. Wysocki wrote: > > On Thu, Aug 8, 2019 at 3:43 PM Bjorn Helgaas wrote: > > > > > IIUC the NVMe device will go to the desired package idle state if > > > the link is in L0s or L1,

Re: i2c: imx: support slave mode for imx I2C driver

On Thu, Aug 08, 2019 at 11:53:43AM +0800, Biwen Li wrote: > The patch supports slave mode for imx I2C driver > > Signed-off-by: Biwen Li Wow, this is much simpler than the other approach flying around: http://patchwork.ozlabs.org/patch/1124048/ Can this one be master and slave on the same

Re: [PATCH net] net: phy: rtl8211f: do a double read to get real time link status

On 08.08.2019 21:40, Andrew Lunn wrote: >> @@ -568,6 +568,11 @@ int phy_start_aneg(struct phy_device *phydev) >> if (err < 0) >> goto out_unlock; >> >> +/* The PHY may not yet have cleared aneg-completed and link-up bit >> + * w/o this delay when the following read is

Re: [PATCH 1/2] genirq: introduce update_irq_devid()

On Thu, 8 Aug 2019, Ben Luo wrote: > +int update_irq_devid(unsigned int irq, void *dev_id, void *new_dev_id) > +{ > + struct irq_desc *desc = irq_to_desc(irq); > + struct irqaction *action, **action_ptr; > + unsigned long flags; > + > + WARN(in_interrupt(), > +

Re: [PATCH v2] pci: Kconfig: select PCI_MSI_IRQ_DOMAIN by default on RISC-V

Hi Paul, Wesley, On Thu, Jul 25, 2019 at 02:28:07PM -0700, Paul Walmsley wrote: > From: Wesley Terpstra > > This is part of adding support for RISC-V systems with PCIe host > controllers that support message-signaled interrupts. > > Signed-off-by: Wesley Terpstra > [paul.walms...@sifive.com:

[PATCH RT 08/19] arm: imx6: cpuidle: Use raw_spinlock_t

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit 40d0332ec8312e9c090f0a5414d9c90e12b13611 ] The idle call back is invoked with disabled interrupts and requires raw_spinlock_t locks to work.

[PATCH RT 05/19] locking/rwsem: Rename rwsem_rt.h to rwsem-rt.h

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit fc7a6bdcce83ce162c32d991f0ac8e56ea260f5b ] Rename rwsem_rt.h to rwsem-rt.h to remain consistent with rwsem-rt.c. Signed-off-by: Sebastian

[PATCH RT 03/19] genirq: Do not invoke the affinity callback via a workqueue on RT

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit 2122adbe011cdc0eb62ad62494e181005b23c76a ] Joe Korty reported, that __irq_set_affinity_locked() schedules a workqueue while holding a

[PATCH RT 06/19] sched/completion: Fix a lockup in wait_for_completion()

From: Corey Minyard v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit f0837746a7e258abb35e65defc432ca66786347f ] Consider following race: T0T1 T2 wait_for_completion()

Re: [PATCH] rtc: bd70528: fix link error

Hello All, On Thu, 2019-08-08 at 10:29 +0800, Yuehaibing wrote: > On 2019/7/9 13:25, Vaittinen, Matti wrote: > > Hello Arnd, > > > > (Added Randy who also sent a patch to fix this) > > > > On Mon, 2019-07-08 at 18:10 +0200, Arnd Bergmann wrote: > > > On Mon, Jul 8, 2019 at 3:24 PM Vaittinen,

[PATCH RT 10/19] pci/switchtec: fix stream_open.cocci warnings

From: kbuild test robot v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit 9462c69e29307adc95c289f50839d5d683973891 ] drivers/pci/switch/switchtec.c:395:1-17: ERROR: switchtec_fops: .read() can deadlock .write(); change

[PATCH RT 00/19] Linux v4.14.137-rt65-rc1

From: Tom Zanussi Dear RT Folks, This is the RT stable review cycle of patch 4.14.137-rt65-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review

[PATCH RT 14/19] Revert "rtmutex: Handle the various new futex race conditions"

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit 9e0265c21af4d6388d47dcd5ce20f76ec3a2e468 ] Drop the RT fixup, the futex code will be changed to avoid the need for the workaround.

[PATCH RT 18/19] mm/zswap: Do not disable preemption in zswap_frontswap_store()

From: "Luis Claudio R. Goncalves" v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit 4e4cf4be79635e67144632d9135286381acbc95a ] Zswap causes "BUG: scheduling while atomic" by blocking on a rt_spin_lock() with preemption

Re: [PATCH 01/26] drm/dp_mst: Move link address dumping into a function

On Wed, Jul 17, 2019 at 09:42:24PM -0400, Lyude Paul wrote: > Since we're about to be calling this from multiple places. Also it makes > things easier to read! > > Cc: Juston Li > Cc: Imre Deak > Cc: Ville Syrjälä > Cc: Harry Wentland > Signed-off-by: Lyude Paul Reviewed-by: Daniel Vetter

[PATCH RT 12/19] Revert "futex: Ensure lock/unlock symetry versus pi_lock and hash bucket lock"

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit 6a773b70cf105b46298ed3b44e77c102ce31d9ec ] Drop the RT fixup, the futex code will be changed to avoid the need for the workaround.

[PATCH RT 11/19] sched/core: Drop a preempt_disable_rt() statement

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit 761126efdcbe3fa3e99c9079fa0ad6eca2f251f2 ] The caller holds a lock which already disables preemption. Drop the preempt_disable_rt()

[PATCH RT 15/19] Revert "futex: workaround migrate_disable/enable in different context"

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit a71221d81cc4873891ae44f3aa02df596079b786 ] Drop the RT fixup, the futex code will be changed to avoid the need for the workaround.

[PATCH RT 07/19] locking/lockdep: Don't complain about incorrect name for no validate class

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit 978315462d3ea3cf6cfacd34c563ec1eb02a3aa5 ] It is possible to ignore the validation for a certain lock by using:

[PATCH RT 09/19] rcu: Don't allow to change rcu_normal_after_boot on RT

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit c6c058c10577815a2491ce661876cff00a4c3b15 ] On RT rcu_normal_after_boot is enabled by default. Don't allow to disable it on RT because the

[PATCH RT 19/19] Linux 4.14.137-rt65-rc1

From: Tom Zanussi v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- Signed-off-by: Tom Zanussi --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index

[PATCH RT 16/19] futex: Make the futex_hash_bucket lock raw

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit f646521aadedab78801c9befe193e2e8a0c99298 ] Since commit 1a1fb985f2e2b ("futex: Handle early deadlock return correctly") we can deadlock

[PATCH RT 17/19] futex: Delay deallocation of pi_state

From: Thomas Gleixner v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit d7c7cf8cb68b7df17e6e50be1f25f35d83e686c7 ] On -RT we can't invoke kfree() in a non-preemptible context. Defer the deallocation of pi_state to

[PATCH RT 13/19] Revert "futex: Fix bug on when a requeued RT task times out"

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit f1a170cb3289a48df26cae3c60d77608f7a988bb ] Drop the RT fixup, the futex code will be changed to avoid the need for the workaround.

[PATCH RT 02/19] kthread: add a global worker thread.

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit 0532e87d9d44795221aa921ba7024bde689cc894 ] Add kthread_schedule_work() which uses a global kthread for all its jobs. Split the cgroup

[PATCH RT 04/19] genirq: Handle missing work_struct in irq_set_affinity_notifier()

From: Sebastian Andrzej Siewior v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- [ Upstream commit bbc4d2a7d6ff54ba923640d9a42c7bef7185fe98 ] The backported stable commit 59c39840f5abf ("genirq: Prevent use-after-free and work list

[PATCH v4 2/2] sched/topology: Improve load balancing on AMD EPYC

SD_BALANCE_{FORK,EXEC} and SD_WAKE_AFFINE are stripped in sd_init() for any sched domains with a NUMA distance greater than 2 hops (RECLAIM_DISTANCE). The idea being that it's expensive to balance across domains that far apart. However, as is rather unfortunately explained in commit

[PATCH 1/2] ia64: Make NUMA select SMP

While it does make sense to allow CONFIG_NUMA and !CONFIG_SMP in theory, it doesn't make much sense in practice. Follow other architectures and make CONFIG_NUMA select CONFIG_SMP. The motivation for this patch is to allow a new NUMA variable to be initialised in kernel/sched/topology.c.

[PATCH RT 01/19] kthread: Use __RAW_SPIN_LOCK_UNLOCK to initialize kthread_worker lock

From: Tom Zanussi v4.14.137-rt65-rc1 stable review patch. If anyone has any objections, please let me know. --- commit 2a9060beefcf (kthread: convert worker lock to raw spinlock) forgot to update KTHREAD_WORKER_INIT() to use __RAW_SPIN_LOCK_UNLOCKED() instead of just

Re: [PATCH v2 1/4] dt-bindings: soundwire: add slave bindings

On Thu, Aug 08, 2019 at 05:48:56PM +0100, Srinivas Kandagatla wrote: > On 08/08/2019 16:58, Pierre-Louis Bossart wrote: > > > +- sdw-instance-id: Should be ('Instance ID') from SoundWire > > > +  Enumeration Address. Instance ID is for the cases > > > +  where multiple Devices of

[PATCH v4 0/2] sched: Improve load balancing on AMD EPYC

This is another version of the AMD EPYC load balancing patch. The difference with this one is that now it fixes the following ia64 build error, reported by 0day: mm/page_alloc.o: In function `get_page_from_freelist': page_alloc.c:(.text+0x7850): undefined reference to

Re: [PATCH] clk: fix devm_platform_ioremap_resource.cocci warnings

On Thu, 8 Aug 2019, Stephen Boyd wrote: > Quoting Julia Lawall (2019-08-08 09:10:53) > > From: kbuild test robot > > > > drivers/clk/bcm/clk-bcm63xx-gate.c:174:1-9: WARNING: Use > > devm_platform_ioremap_resource for hw -> regs > > > > Use devm_platform_ioremap_resource helper which wraps >

Re: [PATCH] clk: fix devm_platform_ioremap_resource.cocci warnings

Quoting Julia Lawall (2019-08-08 09:10:53) > From: kbuild test robot > > drivers/clk/bcm/clk-bcm63xx-gate.c:174:1-9: WARNING: Use > devm_platform_ioremap_resource for hw -> regs > > Use devm_platform_ioremap_resource helper which wraps > platform_get_resource() and devm_ioremap_resource()

Re: [PATCH v2 2/6] thermal: amlogic: Add thermal driver to support G12 SoCs

Hi Kevin, On Thu, Aug 8, 2019 at 4:59 AM Kevin Hilman wrote: > > Martin Blumenstingl writes: > > > Hi Guillaume, > > > > On Mon, Aug 5, 2019 at 2:48 PM guillaume La Roque > > wrote: > >> > >> Hi Martin, > >> > >> again thanks for your review. > > you're welcome - thank you for working on the

[ANNOUNCE] 4.14.137-rt64

Hello RT Folks! I'm pleased to announce the 4.14.137-rt64 stable release. This release is just an update to the new stable 4.14.137 version and no RT specific changes have been made. You can get this release via the git tree at:

[RFC PATCH] hugetlbfs: Add hugetlb_cgroup reservation limits

Problem: Currently tasks attempting to allocate more hugetlb memory than is available get a failure at mmap/shmget time. This is thanks to Hugetlbfs Reservations [1]. However, if a task attempts to allocate hugetlb memory only more than its hugetlb_cgroup limit allows, the kernel will allow the

Re: [PATCH net] net: phy: rtl8211f: do a double read to get real time link status

> @@ -568,6 +568,11 @@ int phy_start_aneg(struct phy_device *phydev) > if (err < 0) > goto out_unlock; > > + /* The PHY may not yet have cleared aneg-completed and link-up bit > + * w/o this delay when the following read is done. > + */ > +

Re: [PATCH v2 13/15] net: phy: adin: configure downshift on config_init

On 08.08.2019 14:30, Alexandru Ardelean wrote: > Down-speed auto-negotiation may not always be enabled, in which case the > PHY won't down-shift to 100 or 10 during auto-negotiation. > > This change enables downshift and configures the number of retries to > default 8 (maximum supported value). >

Re: [PATCH v2 02/15] net: phy: adin: hook genphy_read_abilities() to get_features

On 08.08.2019 17:24, Andrew Lunn wrote: > On Thu, Aug 08, 2019 at 03:30:13PM +0300, Alexandru Ardelean wrote: >> The ADIN PHYs can operate with Clause 45, however they are not typical for >> how phylib considers Clause 45 PHYs. >> >> If the `features` field & the `get_features` hook are

[PATCH] coresight: tmc-etr: Remove perf_data check.

When tracing etm data of multiple threads on multiple cpus through perf interface, each cpu has a unique etr_perf_buffer while sharing the same etr device. There is no guarantee that the last cpu starts etm tracing also stops last. So the perf_data check is no longer valid. Signed-off-by: Yabin

Re: [PATCH] ASoC: soc-core: remove error due to probe deferral

On Thu, Aug 08, 2019 at 03:16:53PM +0200, Stefan Agner wrote: > On 2019-08-08 15:14, Takashi Iwai wrote: > > Mark Brown wrote: > > I guess we can use dev_printk() with the conditional level choice. > How about use dev_info always? We get a dev_err message from > soc_init_dai_link in error

Re: [PATCH net] net: phy: rtl8211f: do a double read to get real time link status

On 08.08.2019 08:21, Yonglong Liu wrote: > > > On 2019/8/8 14:11, Heiner Kallweit wrote: >> On 08.08.2019 03:15, Yonglong Liu wrote: >>> >>> >>> On 2019/8/8 0:47, Heiner Kallweit wrote: On 07.08.2019 15:16, Yonglong Liu wrote: > [ 27.232781] hns3 :bd:00.3 eth7: net open > [

Re: [PATCH 1/3] mm/mlock.c: convert put_page() to put_user_page*()

On 8/8/19 4:09 AM, Vlastimil Babka wrote: > On 8/8/19 8:21 AM, Michal Hocko wrote: >> On Wed 07-08-19 16:32:08, John Hubbard wrote: >>> On 8/7/19 4:01 AM, Michal Hocko wrote: On Mon 05-08-19 15:20:17, john.hubb...@gmail.com wrote: > From: John Hubbard >>> Actually, I think

Re: [bonding][patch] Regarding a bonding lacp issue

Felix wrote: >Dear Mainteners, > >Recently I hit a packet drop issue in bonding driver on Linux 4.9. Please >see details below. Please take a look to see if my understanding is >correct. Many thanks. > >What is the problem? >The bonding driver starts to send packets even if the Partner(Switch)'s

[PATCH] coresight: Serialize enabling/disabling a link device.

When tracing etm data of multiple threads on multiple cpus through perf interface, some link devices are shared between paths of different cpus. It creates race conditions when different cpus wants to enable/disable the same link device at the same time. Example 1: Two cpus want to enable

[PATCH 5.2 15/56] mlxsw: spectrum: Fix error path in mlxsw_sp_module_init()

From: Jiri Pirko [ Upstream commit 28fe79000e9b0a6f99959869947f1ca305f14599 ] In case of sp2 pci driver registration fail, fix the error path to start with sp1 pci driver unregister. Fixes: c3ab435466d5 ("mlxsw: spectrum: Extend to support Spectrum-2 ASIC") Signed-off-by: Jiri Pirko

[PATCH 5.2 11/56] ife: error out when nla attributes are empty

From: Cong Wang [ Upstream commit c8ec4632c6ac9cda0e8c3d51aa41eeab66585bd5 ] act_ife at least requires TCA_IFE_PARMS, so we have to bail out when there is no attribute passed in. Reported-by: syzbot+fbb5b288c9cb6a2ee...@syzkaller.appspotmail.com Fixes: ef6980b6becb ("introduce IFE action") Cc:

[PATCH 5.2 22/56] net/mlx5e: always initialize frag->last_in_page

From: Qian Cai [ Upstream commit 60d60c8fbd8d1acf25b041ecd72ae4fa16e9405b ] The commit 069d11465a80 ("net/mlx5e: RX, Enhance legacy Receive Queue memory scheme") introduced an undefined behaviour below due to "frag->last_in_page" is only initialized in mlx5e_init_frags_partition() when, if

[PATCH 5.2 21/56] net: fix ifindex collision during namespace removal

From: Jiri Pirko [ Upstream commit 55b40dbf0e76b4bfb9d8b3a16a0208640a9a45df ] Commit aca51397d014 ("netns: Fix arbitrary net_device-s corruptions on net_ns stop.") introduced a possibility to hit a BUG in case device is returning back to init_net and two following conditions are met: 1)

[PATCH 5.2 27/56] net: phy: mscc: initialize stats array

From: Andreas Schwab [ Upstream commit f972037e71246c5e0916eef835174d58ffc517e4 ] The memory allocated for the stats array may contain arbitrary data. Fixes: e4f9ba642f0b ("net: phy: mscc: add support for VSC8514 PHY.") Fixes: 00d70d8e0e78 ("net: phy: mscc: add support for VSC8574 PHY") Fixes:

[PATCH 5.2 30/56] net sched: update vlan action for batched events operations

From: Roman Mashak [ Upstream commit b35475c5491a14c8ce7a5046ef7bcda8a860581a ] Add get_fill_size() routine used to calculate the action size when building a batch of events. Fixes: c7e2b9689 ("sched: introduce vlan action") Signed-off-by: Roman Mashak Signed-off-by: David S. Miller

[PATCH 5.2 32/56] net/smc: do not schedule tx_work in SMC_CLOSED state

From: Ursula Braun [ Upstream commit f9cedf1a9b1cdcfb0c52edb391d01771e43994a4 ] The setsockopts options TCP_NODELAY and TCP_CORK may schedule the tx worker. Make sure the socket is not yet moved into SMC_CLOSED state (for instance by a shutdown SHUT_RDWR call). Reported-by:

[PATCH 5.2 07/56] HID: Add quirk for HP X1200 PIXART OEM mouse

From: Sebastian Parschauer commit 49869d2ea9eecc105a10724c1abf035151a3c4e2 upstream. The PixArt OEM mice are known for disconnecting every minute in runlevel 1 or 3 if they are not always polled. So add quirk ALWAYS_POLL for this one as well. Jonathan Teh (@jonathan-teh) reported and tested

[PATCH 5.2 28/56] net: qualcomm: rmnet: Fix incorrect UL checksum offload logic

From: Subash Abhinov Kasiviswanathan [ Upstream commit a7cf3d24ee6081930feb4c830a7f6f16ebe31c49 ] The udp_ip4_ind bit is set only for IPv4 UDP non-fragmented packets so that the hardware can flip the checksum to 0x if the computed checksum is 0 per RFC768. However, this bit had to be set

[PATCH 5.2 29/56] net: sched: Fix a possible null-pointer dereference in dequeue_func()

From: Jia-Ju Bai [ Upstream commit 051c7b39be4a91f6b7d8c4548444e4b850f1f56c ] In dequeue_func(), there is an if statement on line 74 to check whether skb is NULL: if (skb) When skb is NULL, it is used on line 77: prefetch(>end); Thus, a possible null-pointer dereference may occur. To

[PATCH 5.2 36/56] tipc: compat: allow tipc commands without arguments

From: Taras Kondratiuk [ Upstream commit 4da5f0018eef4c0de31675b670c80e82e13e99d1 ] Commit 2753ca5d9009 ("tipc: fix uninit-value in tipc_nl_compat_doit") broke older tipc tools that use compat interface (e.g. tipc-config from tipcutils package): % tipc-config -p operation not supported The

[PATCH 5.2 04/56] ALSA: usb-audio: Sanity checks for each pipe and EP types

[ Upstream commit 801ebf1043ae7b182588554cc9b9ad3c14bc2ab5 ] The recent USB core code performs sanity checks for the given pipe and EP types, and it can be hit by manipulated USB descriptors by syzbot. For making syzbot happier, this patch introduces a local helper for a sanity check in the

[PATCH 5.2 37/56] tipc: fix unitilized skb list crash

From: Jon Maloy [ Upstream commit 2948a1fcd77a8bb11604387e3fc52f0ebf5729e9 ] Our test suite somtimes provokes the following crash: Description of problem: [ 1092.597234] BUG: unable to handle kernel NULL pointer dereference at 00e8 [ 1092.605072] PGD 0 P4D 0 [ 1092.607620] Oops:

[PATCH 5.2 00/56] 5.2.8-stable review

This is the start of the stable review cycle for the 5.2.8 release. There are 56 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat 10 Aug 2019 07:03:19 PM UTC. Anything

[PATCH 5.2 39/56] net/mlx5: Fix modify_cq_in alignment

From: Edward Srouji [ Upstream commit 7a32f2962c56d9d8a836b4469855caeee8766bd4 ] Fix modify_cq_in alignment to match the device specification. After this fix the 'cq_umem_valid' field will be in the right offset. Cc: # 4.19 Fixes: bd37197554eb ("net/mlx5: Update mlx5_ifc with DEVX UID bits")

[PATCH 5.2 08/56] atm: iphase: Fix Spectre v1 vulnerability

From: "Gustavo A. R. Silva" [ Upstream commit ea443e5e98b5b74e317ef3d26bcaea54931ccdee ] board is controlled by user-space, hence leading to a potential exploitation of the Spectre variant 1 vulnerability. This issue was detected with the help of Smatch: drivers/atm/iphase.c:2765 ia_ioctl()

[PATCH 5.2 51/56] net/mlx5: Add missing RDMA_RX capabilities

From: Maor Gottlieb [ Upstream commit 987f6c69dd923069d443f6a37225f5b1630a30f2 ] New flow table type RDMA_RX was added but the MLX5_CAP_FLOW_TABLE_TYPE didn't handle this new flow table type. This means that MLX5_CAP_FLOW_TABLE_TYPE returns an empty capability to this flow table type. Update

Re: [RFC PATCH v4 9/9] printk: use a new ringbuffer implementation

On Wed, Aug 7, 2019 at 3:27 PM John Ogness wrote: > > 2. For the CONFIG_PPC_POWERNV powerpc platform, kernel log buffer >registration is no longer available because there is no longer >a single contigous block of memory to represent all of the >ringbuffer. So this is tangential, but

[PATCH 5.2 43/56] selftests/bpf: add wrapper scripts for test_xdp_vlan.sh

From: Jesper Dangaard Brouer [ Upstream commit d35661fcf95d8818c1f9acc818a1bad23dda4e1c ] In-order to test both native-XDP (xdpdrv) and generic-XDP (xdpgeneric) create two wrapper test scripts, that start the test_xdp_vlan.sh script with these modes. Signed-off-by: Jesper Dangaard Brouer

[PATCH 5.2 42/56] bpf: fix XDP vlan selftests test_xdp_vlan.sh

From: Jesper Dangaard Brouer [ Upstream commit 4de9c89a4982431c4a02739743fd360dc5581f22 ] Change BPF selftest test_xdp_vlan.sh to (default) use generic XDP. This selftest was created together with a fix for generic XDP, in commit 297249569932 ("net: fix generic XDP to handle if eth header was

[PATCH 5.2 45/56] net: fix bpf_xdp_adjust_head regression for generic-XDP

From: Jesper Dangaard Brouer [ Upstream commit 065af355470519bd184019a93ac579f22b036045 ] When generic-XDP was moved to a later processing step by commit 458bf2f224f0 ("net: core: support XDP generic on stacked devices.") a regression was introduced when using bpf_xdp_adjust_head. The issue is

[PATCH 5.2 47/56] net: phy: fix race in genphy_update_link

From: Heiner Kallweit [ Upstream commit aa6b1956158f1afc52761137620d4b3f8a058d24 ] In phy_start_aneg() autoneg is started, and immediately after that link and autoneg status are read. As reported in [0] it can happen that at time of this read the PHY has reset the "aneg complete" bit but not

[PATCH 4.19 01/45] scsi: fcoe: Embed fc_rport_priv in fcoe_rport structure

From: Hannes Reinecke commit 023358b136d490ca91735ac6490db3741af5a8bd upstream. Gcc-9 complains for a memset across pointer boundaries, which happens as the code tries to allocate a flexible array on the stack. Turns out we cannot do this without relying on gcc-isms, so with this patch we'll

[PATCH 4.19 03/45] driver core: Establish order of operations for device_add and device_del via bitflag

commit 3451a495ef244a88ed6317a035299d835554d579 upstream. Add an additional bit flag to the device_private struct named "dead". This additional flag provides a guarantee that when a device_del is executed on a given interface an async worker will not attempt to attach the driver following the

[PATCH 5.2 46/56] hv_sock: Fix hang when a connection is closed

From: Dexuan Cui [ Upstream commit 8c7885e5690be9a27231ebebf82ef29fbf46c4e4 ] There is a race condition for an established connection that is being closed by the guest: the refcnt is 4 at the end of hvs_release() (Note: here the 'remove_sock' is false): 1 for the initial value; 1 for the sk

[PATCH 4.19 00/45] 4.19.66-stable review

This is the start of the stable review cycle for the 4.19.66 release. There are 45 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat 10 Aug 2019 07:03:19 PM UTC. Anything

[PATCH 4.19 08/45] libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock

commit ca6bf264f6d856f959c4239cda1047b587745c67 upstream. A multithreaded namespace creation/destruction stress test currently deadlocks with the following lockup signature: INFO: task ndctl:2924 blocked for more than 122 seconds. Tainted: G OE 5.2.0-rc4+ #3382

[PATCH 4.19 07/45] libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant

commit 6de5d06e657acdbcf9637dac37916a4a5309e0f4 upstream. In preparation for not holding a lock over the execution of nd_ioctl(), update the implementation to allow multiple threads to be attempting ioctls at the same time. The bus lock still prevents multiple in-flight ->ndctl() invocations from

[PATCH 4.19 15/45] ip6_gre: reload ipv6h in prepare_ip6gre_xmit_ipv6

From: Haishuang Yan [ Upstream commit 3bc817d665ac6d9de89f59df522ad86f5b5dfc03 ] Since ip6_tnl_parse_tlv_enc_lim() can call pskb_may_pull() which may change skb->data, so we need to re-load ipv6h at the right place. Fixes: 898b29798e36 ("ip6_gre: Refactor ip6gre xmit codes") Cc: William Tu

[PATCH 4.19 05/45] libnvdimm/bus: Prevent duplicate device_unregister() calls

commit 8aac0e2338916e273ccbd438a2b7a1e8c61749f5 upstream. A multithreaded namespace creation/destruction stress test currently fails with signatures like the following: sysfs group 'power' not found for kobject 'dax1.1' RIP: 0010:sysfs_remove_group+0x76/0x80 Call Trace:

[PATCH 4.19 27/45] net: qualcomm: rmnet: Fix incorrect UL checksum offload logic

From: Subash Abhinov Kasiviswanathan [ Upstream commit a7cf3d24ee6081930feb4c830a7f6f16ebe31c49 ] The udp_ip4_ind bit is set only for IPv4 UDP non-fragmented packets so that the hardware can flip the checksum to 0x if the computed checksum is 0 per RFC768. However, this bit had to be set

[PATCH 4.19 31/45] net/smc: do not schedule tx_work in SMC_CLOSED state

From: Ursula Braun [ Upstream commit f9cedf1a9b1cdcfb0c52edb391d01771e43994a4 ] The setsockopts options TCP_NODELAY and TCP_CORK may schedule the tx worker. Make sure the socket is not yet moved into SMC_CLOSED state (for instance by a shutdown SHUT_RDWR call). Reported-by:

[PATCH 4.19 26/45] net: phylink: Fix flow control for fixed-link

From: "Ren� van Dorst" [ Upstream commit 8aace4f3eba2a3ceb431e18683ea0e1ecbade5cd ] In phylink_parse_fixedlink() the pl->link_config.advertising bits are AND with pl->supported, pl->supported is zeroed and only the speed/duplex modes and MII bits are set. So pl->link_config.advertising always

[PATCH 4.19 38/45] r8169: dont use MSI before RTL8168d

From: Heiner Kallweit [ Upstream commit 003bd5b4a7b4a94b501e3a1e2e7c9df6b2a94ed4 ] It was reported that after resuming from suspend network fails with error "do_IRQ: 3.38 No irq handler for vector", see [0]. Enabling WoL can work around the issue, but the only actual fix is to disable MSI. So

[PATCH 4.19 36/45] net/mlx5: Fix modify_cq_in alignment

From: Edward Srouji [ Upstream commit 7a32f2962c56d9d8a836b4469855caeee8766bd4 ] Fix modify_cq_in alignment to match the device specification. After this fix the 'cq_umem_valid' field will be in the right offset. Cc: # 4.19 Fixes: bd37197554eb ("net/mlx5: Update mlx5_ifc with DEVX UID bits")

[PATCH 4.14 13/33] ife: error out when nla attributes are empty

From: Cong Wang [ Upstream commit c8ec4632c6ac9cda0e8c3d51aa41eeab66585bd5 ] act_ife at least requires TCA_IFE_PARMS, so we have to bail out when there is no attribute passed in. Reported-by: syzbot+fbb5b288c9cb6a2ee...@syzkaller.appspotmail.com Fixes: ef6980b6becb ("introduce IFE action") Cc:

[PATCH 4.19 22/45] net: bridge: mcast: dont delete permanent entries when fast leave is enabled

From: Nikolay Aleksandrov [ Upstream commit 5c725b6b65067909548ac9ca9bc777098ec9883d ] When permanent entries were introduced by the commit below, they were exempt from timing out and thus igmp leave wouldn't affect them unless fast leave was enabled on the port which was added before permanent

[PATCH 4.19 41/45] cgroup: Implement css_task_iter_skip()

From: Tejun Heo commit b636fd38dc40113f853337a7d2a6885ad23b8811 upstream. When a task is moved out of a cset, task iterators pointing to the task are advanced using the normal css_task_iter_advance() call. This is fine but we'll be tracking dying tasks on csets and thus moving tasks from

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