[PATCH 3.18 086/144] of/pci: Remove duplicate kfree in of_pci_get_host_bridge_resources()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit feb28979c137ba3f649ad36fc27c85c64c111f78 ] Commit d2be00c0fb5a ("of/pci: Free resources on failure in of_pci_get_host_bridge_resources()") fixed the error path so it frees

[PATCH 3.18 086/144] of/pci: Remove duplicate kfree in of_pci_get_host_bridge_resources()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit feb28979c137ba3f649ad36fc27c85c64c111f78 ] Commit d2be00c0fb5a ("of/pci: Free resources on failure in of_pci_get_host_bridge_resources()") fixed the error path so it frees

[PATCH 3.18 091/144] net/mlx4_en: Remove dependency between timestamping capability and service_task

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fc9f5ea9b4ecbe9b7839c92f0a54261809c723d3 ] Service task is responsible for other tasks in addition to timestamping overflow check. Launch it even if timestamping is not supported by

[PATCH 3.18 091/144] net/mlx4_en: Remove dependency between timestamping capability and service_task

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fc9f5ea9b4ecbe9b7839c92f0a54261809c723d3 ] Service task is responsible for other tasks in addition to timestamping overflow check. Launch it even if timestamping is not supported by

[PATCH 3.18 090/144] arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 90f6e150e44a0dc3883110eeb3ab35d1be42b6bb ] We don't hold the mmap_sem while searching for the VMAs when we try to unmap each memslot for a VM. Fix this properly to avoid unexpected

[PATCH 3.18 090/144] arm/arm64: KVM: Take mmap_sem in stage2_unmap_vm

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 90f6e150e44a0dc3883110eeb3ab35d1be42b6bb ] We don't hold the mmap_sem while searching for the VMAs when we try to unmap each memslot for a VM. Fix this properly to avoid unexpected

[PATCH 3.18 089/144] dm: fix AB-BA deadlock in __dm_destroy()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2a708cff93f1845b9239bc7d6310aef54e716c6a ] __dm_destroy() takes io_barrier SRCU lock (dm_get_live_table) and suspend_lock in reverse order. Doing so can cause AB-BA deadlock:

[PATCH 3.18 089/144] dm: fix AB-BA deadlock in __dm_destroy()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2a708cff93f1845b9239bc7d6310aef54e716c6a ] __dm_destroy() takes io_barrier SRCU lock (dm_get_live_table) and suspend_lock in reverse order. Doing so can cause AB-BA deadlock:

[PATCH 3.18 083/144] nfs: fix high load average due to callback thread sleeping

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5d05e54af3cdbb13cf19c557ff2184781b91a22c ] Chuck pointed out a problem that crept in with commit 6ffa30d3f734 (nfs: don't call blocking operations while !TASK_RUNNING). Linux counts

[PATCH 3.18 096/144] net: ethernet: davicom: fix devicetree irq resource

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b5a099c67a1c36b91356624ce86eb3f9f48a82c7 ] The dm9000 driver doesn't work in at least one device-tree configuration, spitting an error message on irq resource : [1.062495]

[PATCH 3.18 097/144] perf bench numa: Fix to show proper convergence stats

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b42b09b88c831ba4da2d669581dde371c38c2af ] With commit: e1e455f4f4d3 (perf tools: Work around lack of sched_getcpu in glibc < 2.6), perf_bench numa mem with -c or -m option is not

[PATCH 3.18 083/144] nfs: fix high load average due to callback thread sleeping

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5d05e54af3cdbb13cf19c557ff2184781b91a22c ] Chuck pointed out a problem that crept in with commit 6ffa30d3f734 (nfs: don't call blocking operations while !TASK_RUNNING). Linux counts

[PATCH 3.18 096/144] net: ethernet: davicom: fix devicetree irq resource

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b5a099c67a1c36b91356624ce86eb3f9f48a82c7 ] The dm9000 driver doesn't work in at least one device-tree configuration, spitting an error message on irq resource : [1.062495]

[PATCH 3.18 097/144] perf bench numa: Fix to show proper convergence stats

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b42b09b88c831ba4da2d669581dde371c38c2af ] With commit: e1e455f4f4d3 (perf tools: Work around lack of sched_getcpu in glibc < 2.6), perf_bench numa mem with -c or -m option is not

[PATCH 3.18 093/144] tty: serial: fsl_lpuart: fix clearing of receive flag

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d68827c62a105eec547945daedf4d1d3e283717d ] Commit 8e4934c6d6c6 ("tty: serial: fsl_lpuart: clear receive flag on FIFO flush") implemented clearing of the receive flag by reading the

[PATCH 3.18 081/144] quota: Fix maximum quota limit settings

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7e08da50cf706151f324349f9235ebd311226997 ] Currently quota format that supports 64-bit usage sets maximum quota limit as 2^64-1. However quota core code uses signed numbers to track

[PATCH 3.18 092/144] iommu/vt-d: Fix VM domain ID leak

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 46ebb7af7b93792de65e124e1ab8b89a108a41f2 ] This continues the attempt to fix commit fb170fb4c548 ("iommu/vt-d: Introduce helper functions to make code symmetric for readability").

[PATCH 3.18 078/144] drivers: bus: check cci device tree node status

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 896ddd600ba4a3426aeb11710ae9c28dd7ce68ce ] The arm-cci driver completes the probe sequence even if the cci node is marked as disabled. Add a check in the driver to honour the cci

[PATCH 3.18 093/144] tty: serial: fsl_lpuart: fix clearing of receive flag

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d68827c62a105eec547945daedf4d1d3e283717d ] Commit 8e4934c6d6c6 ("tty: serial: fsl_lpuart: clear receive flag on FIFO flush") implemented clearing of the receive flag by reading the

[PATCH 3.18 081/144] quota: Fix maximum quota limit settings

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7e08da50cf706151f324349f9235ebd311226997 ] Currently quota format that supports 64-bit usage sets maximum quota limit as 2^64-1. However quota core code uses signed numbers to track

[PATCH 3.18 092/144] iommu/vt-d: Fix VM domain ID leak

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 46ebb7af7b93792de65e124e1ab8b89a108a41f2 ] This continues the attempt to fix commit fb170fb4c548 ("iommu/vt-d: Introduce helper functions to make code symmetric for readability").

[PATCH 3.18 078/144] drivers: bus: check cci device tree node status

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 896ddd600ba4a3426aeb11710ae9c28dd7ce68ce ] The arm-cci driver completes the probe sequence even if the cci node is marked as disabled. Add a check in the driver to honour the cci

[PATCH 3.18 082/144] rtnl: dont account unused struct ifla_port_vsi in rtnl_port_size

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 025331df34f6722f86b467cb13a69326444ab1bc ] When allocating rtnl dump messages, struct ifla_port_vsi is never dumped, so we can save header plus payload in rtnl_port_size(). Infact,

[PATCH 3.18 079/144] ARM: dts: disable CCI on exynos5420 based arndale-octa

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 25217fef355174209eff68c0eb438a8af5d7b01c ] The arndale-octa board was giving "imprecise external aborts" during boot-up with MCPM enabled. CCI enablement of the boot cluster was

[PATCH 3.18 094/144] x86/idle: Restore trace_cpu_idle to mwait_idle() calls

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e43d0189ac02415fe4487f79fc35e8f147e9ea0d ] Commit b253149b843f ("sched/idle/x86: Restore mwait_idle() to fix boot hangs, to improve power savings and to improve performance")

[PATCH 3.18 082/144] rtnl: dont account unused struct ifla_port_vsi in rtnl_port_size

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 025331df34f6722f86b467cb13a69326444ab1bc ] When allocating rtnl dump messages, struct ifla_port_vsi is never dumped, so we can save header plus payload in rtnl_port_size(). Infact,

[PATCH 3.18 079/144] ARM: dts: disable CCI on exynos5420 based arndale-octa

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 25217fef355174209eff68c0eb438a8af5d7b01c ] The arndale-octa board was giving "imprecise external aborts" during boot-up with MCPM enabled. CCI enablement of the boot cluster was

[PATCH 3.18 094/144] x86/idle: Restore trace_cpu_idle to mwait_idle() calls

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e43d0189ac02415fe4487f79fc35e8f147e9ea0d ] Commit b253149b843f ("sched/idle/x86: Restore mwait_idle() to fix boot hangs, to improve power savings and to improve performance")

[PATCH 3.18 085/144] x86/irq: Check for valid irq descriptor in check_irq_vectors_for_cpu_disable()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d97eb8966c91f2c9d05f0a22eb89ed5b76d966d1 ] When an interrupt is migrated away from a cpu it will stay in its vector_irq array until smp_irq_move_cleanup_interrupt succeeded. The

[PATCH 3.18 076/144] perf tools: Avoid build splat for syscall numbers with uclibc

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ea1fe3a88763d4dfef7e2529ba606f96e8e6b271 ] This is due to duplicated unistd inclusion (via uClibc headers + kernel headers) Also seen on ARM uClibc based tools --- ARC build

[PATCH 3.18 099/144] dm9000: Fix irq trigger type setup on non-dt platforms

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a96d3b7593a3eefab62dd930e5c99201c3678ee4 ] Commit b5a099c67a1c36b "net: ethernet: davicom: fix devicetree irq resource" causes an interrupt storm after the ethernet interface is

[PATCH 3.18 085/144] x86/irq: Check for valid irq descriptor in check_irq_vectors_for_cpu_disable()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d97eb8966c91f2c9d05f0a22eb89ed5b76d966d1 ] When an interrupt is migrated away from a cpu it will stay in its vector_irq array until smp_irq_move_cleanup_interrupt succeeded. The

[PATCH 3.18 076/144] perf tools: Avoid build splat for syscall numbers with uclibc

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ea1fe3a88763d4dfef7e2529ba606f96e8e6b271 ] This is due to duplicated unistd inclusion (via uClibc headers + kernel headers) Also seen on ARM uClibc based tools --- ARC build

[PATCH 3.18 099/144] dm9000: Fix irq trigger type setup on non-dt platforms

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a96d3b7593a3eefab62dd930e5c99201c3678ee4 ] Commit b5a099c67a1c36b "net: ethernet: davicom: fix devicetree irq resource" causes an interrupt storm after the ethernet interface is

[PATCH 3.18 108/144] tty: audit: Fix audit source

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6b2a3d628aa752f0ab825fc6d4d07b09e274d1c1 ] The data to audit/record is in the 'from' buffer (ie., the input read buffer). Fixes: 72586c6061ab ("n_tty: Fix auditing support for

[PATCH 3.18 108/144] tty: audit: Fix audit source

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6b2a3d628aa752f0ab825fc6d4d07b09e274d1c1 ] The data to audit/record is in the 'from' buffer (ie., the input read buffer). Fixes: 72586c6061ab ("n_tty: Fix auditing support for

[PATCH 3.18 132/144] ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit ee1abcf689353f36d9322231b4320926096bdee0 ] Commit a61bbcf28a8c ("[NET]: Store skb->timestamp as offset to a base timestamp") introduces a neighbour control

[PATCH 3.18 112/144] perf: Fix PERF_EVENT_IOC_PERIOD deadlock

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 642c2d671ceff40e9453203ea0c66e991e11e249 ] Dmitry reported a fairly silly recursive lock deadlock for PERF_EVENT_IOC_PERIOD, fix this by explicitly doing the inactive part of

[PATCH 3.18 111/144] libata: blacklist Micron 500IT SSD with MU01 firmware

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 136d769e0b3475d71350aa3648a116a6ee7a8f6c ] While whitelisting Micron M500DC drives, the tweaked blacklist entry enabled queued TRIM from M500IT variants also. But these do not

[PATCH 3.18 110/144] igb: Unpair the queues when changing the number of queues

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 37a5d163fb447b39f7960d0534de30e88ad395bb ] By the commit 72ddef0506da ("igb: Fix oops caused by missing queue pairing"), the IGB_FLAG_QUEUE_PAIRS flag can now be set when changing

[GIT PULL] xfs: fixes for v4.20-rc2

Hi Linus, Here's the start of the stabilization fixes for 4.20. Let me know if there are any problems merging; I just did it against current master and saw no issues. --D The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a: Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

[PATCH 3.18 132/144] ipv6/ndisc: Preserve IPv6 control buffer if protocol error handlers are called

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefano Brivio [ Upstream commit ee1abcf689353f36d9322231b4320926096bdee0 ] Commit a61bbcf28a8c ("[NET]: Store skb->timestamp as offset to a base timestamp") introduces a neighbour control

[PATCH 3.18 112/144] perf: Fix PERF_EVENT_IOC_PERIOD deadlock

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 642c2d671ceff40e9453203ea0c66e991e11e249 ] Dmitry reported a fairly silly recursive lock deadlock for PERF_EVENT_IOC_PERIOD, fix this by explicitly doing the inactive part of

[PATCH 3.18 111/144] libata: blacklist Micron 500IT SSD with MU01 firmware

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 136d769e0b3475d71350aa3648a116a6ee7a8f6c ] While whitelisting Micron M500DC drives, the tweaked blacklist entry enabled queued TRIM from M500IT variants also. But these do not

[PATCH 3.18 110/144] igb: Unpair the queues when changing the number of queues

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 37a5d163fb447b39f7960d0534de30e88ad395bb ] By the commit 72ddef0506da ("igb: Fix oops caused by missing queue pairing"), the IGB_FLAG_QUEUE_PAIRS flag can now be set when changing

[GIT PULL] xfs: fixes for v4.20-rc2

Hi Linus, Here's the start of the stabilization fixes for 4.20. Let me know if there are any problems merging; I just did it against current master and saw no issues. --D The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a: Linux 4.20-rc1 (2018-11-04 15:37:52 -0800)

[PATCH 3.18 113/144] mm: migrate: hugetlb: putback destination hugepage to active list

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3aaa76e125c1dd58c9b599baa8c6021896874c12 ] Since commit bcc54222309c ("mm: hugetlb: introduce page_huge_active") each hugetlb page maintains its active flag to avoid a race

[PATCH 3.18 124/144] net: fix warnings in make htmldocs by moving macro definition out of field declaration

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7bbadd2d1009575dad675afc16650ebb5aa10612 ] Docbook does not like the definition of macros inside a field declaration and adds a warning. Move the definition out. Fixes:

[PATCH 3.18 116/144] PCI: Fix devfn for VPD access through function 0

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9d9240756e63dd87d6cbf5da8b98ceb8f8192b55 ] Commit 932c435caba8 ("PCI: Add dev_flags bit to access VPD through function 0") passes PCI_SLOT(devfn) for the devfn parameter of

[PATCH 3.18 113/144] mm: migrate: hugetlb: putback destination hugepage to active list

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3aaa76e125c1dd58c9b599baa8c6021896874c12 ] Since commit bcc54222309c ("mm: hugetlb: introduce page_huge_active") each hugetlb page maintains its active flag to avoid a race

[PATCH 3.18 124/144] net: fix warnings in make htmldocs by moving macro definition out of field declaration

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7bbadd2d1009575dad675afc16650ebb5aa10612 ] Docbook does not like the definition of macros inside a field declaration and adds a warning. Move the definition out. Fixes:

[PATCH 3.18 116/144] PCI: Fix devfn for VPD access through function 0

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9d9240756e63dd87d6cbf5da8b98ceb8f8192b55 ] Commit 932c435caba8 ("PCI: Add dev_flags bit to access VPD through function 0") passes PCI_SLOT(devfn) for the devfn parameter of

[PATCH 3.18 120/144] ovl: fix open in stacked overlay

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1c8a47df36d72ace8cf78eb6c228aa0f8027d3c2 ] If two overlayfs filesystems are stacked on top of each other, then we need recursion in ovl_d_select_inode(). I guess d_backing_inode()

[PATCH 4.4 002/114] xfrm6: call kfree_skb when skb is toobig

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 215ab0f021c9fea3c18b75e7d522400ee6a49990 ] After commit d6990976af7c5d8f55903bfb4289b6fb030bf754 ("vti6: fix PMTU caching and reporting on xmit"), some too big skbs might be

[PATCH 4.4 004/114] cfg80211: reg: Init wiphy_idx in regulatory_hint_core()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24f33e64fcd0d50a4b1a8e5b41bd0257aa66b0e8 ] Core regulatory hints didn't set wiphy_idx to WIPHY_IDX_INVALID. Since the regulatory request is zeroed, wiphy_idx was always implicitly

[PATCH 3.18 100/144] lib: make memzero_explicit more robust against dead store elimination

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7829fb09a2b4268b30dd9bc782fa5ebee278b137 ] In commit 0b053c951829 ("lib: memzero_explicit: use barrier instead of OPTIMIZER_HIDE_VAR"), we made memzero_explicit() more robust in

[PATCH 3.18 120/144] ovl: fix open in stacked overlay

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1c8a47df36d72ace8cf78eb6c228aa0f8027d3c2 ] If two overlayfs filesystems are stacked on top of each other, then we need recursion in ovl_d_select_inode(). I guess d_backing_inode()

[PATCH 4.4 002/114] xfrm6: call kfree_skb when skb is toobig

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 215ab0f021c9fea3c18b75e7d522400ee6a49990 ] After commit d6990976af7c5d8f55903bfb4289b6fb030bf754 ("vti6: fix PMTU caching and reporting on xmit"), some too big skbs might be

[PATCH 4.4 004/114] cfg80211: reg: Init wiphy_idx in regulatory_hint_core()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24f33e64fcd0d50a4b1a8e5b41bd0257aa66b0e8 ] Core regulatory hints didn't set wiphy_idx to WIPHY_IDX_INVALID. Since the regulatory request is zeroed, wiphy_idx was always implicitly

[PATCH 3.18 100/144] lib: make memzero_explicit more robust against dead store elimination

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7829fb09a2b4268b30dd9bc782fa5ebee278b137 ] In commit 0b053c951829 ("lib: memzero_explicit: use barrier instead of OPTIMIZER_HIDE_VAR"), we made memzero_explicit() more robust in

[PATCH 3.18 114/144] Revert "SCSI: Fix NULL pointer dereference in runtime PM"

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1c69d3b6eb73e466ecbb8edaf1bc7fd585b288da ] This reverts commit 49718f0fb8c9 ("SCSI: Fix NULL pointer dereference in runtime PM") The old commit may lead to a issue that

[PATCH 3.18 114/144] Revert "SCSI: Fix NULL pointer dereference in runtime PM"

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1c69d3b6eb73e466ecbb8edaf1bc7fd585b288da ] This reverts commit 49718f0fb8c9 ("SCSI: Fix NULL pointer dereference in runtime PM") The old commit may lead to a issue that

[PATCH 3.18 102/144] mtd: blkdevs: fix potential deadlock + lockdep warnings

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f3c63795e90f0c6238306883b6c72f14d5355721 ] Commit 073db4a51ee4 ("mtd: fix: avoid race condition when accessing mtd->usecount") fixed a race condition but due to poor ordering of the

[PATCH 3.18 102/144] mtd: blkdevs: fix potential deadlock + lockdep warnings

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f3c63795e90f0c6238306883b6c72f14d5355721 ] Commit 073db4a51ee4 ("mtd: fix: avoid race condition when accessing mtd->usecount") fixed a race condition but due to poor ordering of the

[PATCH 3.18 104/144] rtlwifi: rtl8821ae: Fix system lockups on boot

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 54328e64047a54b8fc2362c2e1f0fa16c90f739f ] In commit 1277fa2ab2f9 ("rtlwifi: Remove the clear interrupt routine from all drivers"), the code that cleared all interrupt enable bits

[PATCH 3.18 103/144] selftests: Introduce a new script to generate tc batch file

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7f071998474a9e5f7b98103d3058a1b8ca5887e6 ] # ./tdc_batch.py -h usage: tdc_batch.py [-h] [-n NUMBER] [-o] [-s] [-p] device file TC batch file generator positional

Re: [patch 2/2] Documentation/process: Add tip tree handbook

On Thu, 8 Nov 2018, Greg KH wrote: > On Thu, Nov 08, 2018 at 08:58:32PM +0100, Thomas Gleixner wrote: > > Fixes: 1234567890AB ("subsys/comp: Short summary") > > Backport-to: 4.14 > > Ick, no. Just stick to the "Fixes:" tag. My scripts can now track when > a patch is backported to a

[PATCH 3.18 098/144] MIPS: Fix up obsolete cpu_set usage

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7363cb7de3999e84243bca79ffea257fd86a2cc6 ] cpu_set was removed (along with a bunch of cpumask helpers) by commit 2f0f267ea072 ("cpumask: remove deprecated functions."). Fix this by

[PATCH 3.18 104/144] rtlwifi: rtl8821ae: Fix system lockups on boot

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 54328e64047a54b8fc2362c2e1f0fa16c90f739f ] In commit 1277fa2ab2f9 ("rtlwifi: Remove the clear interrupt routine from all drivers"), the code that cleared all interrupt enable bits

[PATCH 3.18 103/144] selftests: Introduce a new script to generate tc batch file

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7f071998474a9e5f7b98103d3058a1b8ca5887e6 ] # ./tdc_batch.py -h usage: tdc_batch.py [-h] [-n NUMBER] [-o] [-s] [-p] device file TC batch file generator positional

Re: [patch 2/2] Documentation/process: Add tip tree handbook

On Thu, 8 Nov 2018, Greg KH wrote: > On Thu, Nov 08, 2018 at 08:58:32PM +0100, Thomas Gleixner wrote: > > Fixes: 1234567890AB ("subsys/comp: Short summary") > > Backport-to: 4.14 > > Ick, no. Just stick to the "Fixes:" tag. My scripts can now track when > a patch is backported to a

[PATCH 3.18 098/144] MIPS: Fix up obsolete cpu_set usage

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7363cb7de3999e84243bca79ffea257fd86a2cc6 ] cpu_set was removed (along with a bunch of cpumask helpers) by commit 2f0f267ea072 ("cpumask: remove deprecated functions."). Fix this by

[PATCH 3.18 134/144] net: socket: fix a missing-check bug

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit b6168562c8ce2bd5a30e213021650422e08764dc ] In ethtool_ioctl(), the ioctl command 'ethcmd' is checked through a switch statement to see whether it is necessary to

[PATCH 3.18 136/144] r8169: fix NAPI handling under high load

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ] rtl_rx() and rtl_tx() are called only if the respective bits are set in the interrupt status register. Under high

[PATCH 3.18 134/144] net: socket: fix a missing-check bug

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang [ Upstream commit b6168562c8ce2bd5a30e213021650422e08764dc ] In ethtool_ioctl(), the ioctl command 'ethcmd' is checked through a switch statement to see whether it is necessary to

[PATCH 3.18 136/144] r8169: fix NAPI handling under high load

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ] rtl_rx() and rtl_tx() are called only if the respective bits are set in the interrupt status register. Under high

[PATCH 3.18 131/144] ipv6: mcast: fix a use-after-free in inet6_mc_check

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit dc012f3628eaecfb5ba68404a5c30ef501daf63d ] syzbot found a use-after-free in inet6_mc_check [1] The problem here is that inet6_mc_check() uses rcu and

[PATCH 3.18 133/144] net/ipv6: Fix index counter for unicast addresses in in6_dump_addrs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 4ba4c566ba8448a05e6257e0b98a21f1a0d55315 ] The loop wants to skip previously dumped addresses, so loops until current index >= saved index. If the message fills

[PATCH 3.18 127/144] fs/fat/fatent.c: add cond_resched() to fat_count_free_clusters()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ac081c3be3fae6d0cc3e1862507fca3862d30b67 ] On non-preempt kernels this loop can take a long time (more than 50 ticks) processing through entries. Link:

[PATCH 3.18 131/144] ipv6: mcast: fix a use-after-free in inet6_mc_check

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit dc012f3628eaecfb5ba68404a5c30ef501daf63d ] syzbot found a use-after-free in inet6_mc_check [1] The problem here is that inet6_mc_check() uses rcu and

[PATCH 3.18 133/144] net/ipv6: Fix index counter for unicast addresses in in6_dump_addrs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 4ba4c566ba8448a05e6257e0b98a21f1a0d55315 ] The loop wants to skip previously dumped addresses, so loops until current index >= saved index. If the message fills

[PATCH 3.18 127/144] fs/fat/fatent.c: add cond_resched() to fat_count_free_clusters()

3.18-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ac081c3be3fae6d0cc3e1862507fca3862d30b67 ] On non-preempt kernels this loop can take a long time (more than 50 ticks) processing through entries. Link:

[PATCH 4.4 001/114] xfrm: Validate address prefix lengths in the xfrm selector.

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07bf7908950a8b14e81aa1807e3c667eab39287a ] We don't validate the address prefix lengths in the xfrm selector we got from userspace. This can lead to undefined behaviour in the

[PATCH 3.18 144/144] sched/fair: Fix throttle_list starvation with low CFS quota

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Phil Auld commit baa9be4ffb55876923dc9716abc0a448e510ba30 upstream. With a very low cpu.cfs_quota_us setting, such as the minimum of 1000, distribute_cfs_runtime may not empty the

[PATCH 3.18 142/144] cdc-acm: correct counting of UART states in serial state notification

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Herzog commit f976d0e5747ca65ccd0fb2a4118b193d70aa1836 upstream. The usb standard ("Universal Serial Bus Class Definitions for Communication Devices") distiguishes between "consistent

Re: [PATCH stable 4.9] posix-timers: Sanitize overrun handling

On 11/8/18 7:46 AM, Sasha Levin wrote: > On Thu, Nov 08, 2018 at 07:48:16AM +0100, Thomas Gleixner wrote: >> Florian, >> >> On Wed, 7 Nov 2018, Florian Fainelli wrote: >>> On 11/1/18 1:02 PM, Florian Fainelli wrote: >>> > From: Thomas Gleixner >>> > >>> > [ Upstream commit

[PATCH 4.4 001/114] xfrm: Validate address prefix lengths in the xfrm selector.

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 07bf7908950a8b14e81aa1807e3c667eab39287a ] We don't validate the address prefix lengths in the xfrm selector we got from userspace. This can lead to undefined behaviour in the

[PATCH 3.18 144/144] sched/fair: Fix throttle_list starvation with low CFS quota

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Phil Auld commit baa9be4ffb55876923dc9716abc0a448e510ba30 upstream. With a very low cpu.cfs_quota_us setting, such as the minimum of 1000, distribute_cfs_runtime may not empty the

[PATCH 3.18 142/144] cdc-acm: correct counting of UART states in serial state notification

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Herzog commit f976d0e5747ca65ccd0fb2a4118b193d70aa1836 upstream. The usb standard ("Universal Serial Bus Class Definitions for Communication Devices") distiguishes between "consistent

Re: [PATCH stable 4.9] posix-timers: Sanitize overrun handling

On 11/8/18 7:46 AM, Sasha Levin wrote: > On Thu, Nov 08, 2018 at 07:48:16AM +0100, Thomas Gleixner wrote: >> Florian, >> >> On Wed, 7 Nov 2018, Florian Fainelli wrote: >>> On 11/1/18 1:02 PM, Florian Fainelli wrote: >>> > From: Thomas Gleixner >>> > >>> > [ Upstream commit

Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected

On Thu, Nov 08, 2018 at 02:01:17PM -0800, Greg Kroah-Hartman wrote: > On Thu, Nov 08, 2018 at 02:09:17PM -0600, Bjorn Helgaas wrote: > > I'm having second thoughts about this. One thing I'm uncomfortable > > with is that sprinkling pci_dev_is_disconnected() around feels ad hoc > > instead of

[PATCH 4.4 000/114] 4.4.163-stable review

This is the start of the stable review cycle for the 4.4.163 release. There are 114 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 Nov 10 21:50:28 UTC 2018. Anything

Re: [PATCH v2] PCI/MSI: Don't touch MSI bits when the PCI device is disconnected

On Thu, Nov 08, 2018 at 02:01:17PM -0800, Greg Kroah-Hartman wrote: > On Thu, Nov 08, 2018 at 02:09:17PM -0600, Bjorn Helgaas wrote: > > I'm having second thoughts about this. One thing I'm uncomfortable > > with is that sprinkling pci_dev_is_disconnected() around feels ad hoc > > instead of

[PATCH 4.4 000/114] 4.4.163-stable review

This is the start of the stable review cycle for the 4.4.163 release. There are 114 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 Nov 10 21:50:28 UTC 2018. Anything

[PATCH 4.4 012/114] lan78xx: Check for supported Wake-on-LAN modes

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit eb9ad088f96653a26b340f7c447c44cf023d5cdc ] The driver supports a fair amount of Wake-on-LAN modes, but is not checking that the user specified one that is supported. Fixes:

[PATCH 4.4 024/114] ARM: dts: apq8064: add ahci ports-implemented mask

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bb4add2ce991e4ec891b5a0287fd1ab77b631979 ] This patch adds new ports-implemented mask, which is required to get achi working on the mainline. Without this patch value read from

[PATCH 4.4 021/114] net: drop write-only stack variable

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3575dbf2cbbc8e598f17ec441aed526dbea0e1bd ] Remove a write-only stack variable from unix_attach_fds(). This is a left-over from the security fix in: commit

[PATCH 4.4 022/114] ser_gigaset: use container_of() instead of detour

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8d2c3ab4445640957d136caa3629857d63544a2a ] The purpose of gigaset_device_release() is to kfree() the struct ser_cardstate that contains our struct device. This is done via a bit of a

[PATCH 4.4 012/114] lan78xx: Check for supported Wake-on-LAN modes

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit eb9ad088f96653a26b340f7c447c44cf023d5cdc ] The driver supports a fair amount of Wake-on-LAN modes, but is not checking that the user specified one that is supported. Fixes:

[PATCH 4.4 024/114] ARM: dts: apq8064: add ahci ports-implemented mask

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bb4add2ce991e4ec891b5a0287fd1ab77b631979 ] This patch adds new ports-implemented mask, which is required to get achi working on the mainline. Without this patch value read from

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