[PATCH 3/3] dma-mapping: replace PCI_DMA_BUS_IS_PHYS with a flag in struct dma_map_ops

The current PCI_DMA_BUS_IS_PHYS decided if a dma implementation is bound by the dma mask in the device because it directly maps to a physical address range (modulo an offset in the device), or if it is virtualized by an iommu and can map any address (that includes virtual iommus like swiotlb). The

[PATCH 4.9 11/38] mfd: twl4030-power: Fix pmic for boards that need vmmc1 on reboot

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adam Ford commit ad48ed0c5763dc08931407e455dff5acdbe96e81 upstream. At least two different omap3630/3730 boards booting from MMC1 fail to reboot if the "ti,twl4030-power-idle-osc-off" or "ti,tw

Re: [PATCH] x86/mm: Rewrite sme_populate_pgd() in a more sensible way

On Mon, Dec 04, 2017 at 04:00:26PM +, Tom Lendacky wrote: > On 12/4/2017 8:57 AM, Kirill A. Shutemov wrote: > > On Mon, Dec 04, 2017 at 08:19:11AM -0600, Tom Lendacky wrote: > > > On 12/4/2017 5:23 AM, Kirill A. Shutemov wrote: > > > > sme_populate_pgd() open-codes a lot of things that are not

Re: [PATCH] drm: msm: avoid false-positive -Wmaybe-uninitialized warning

Hi Arnd, Thank you for the patch. On Monday, 4 December 2017 16:44:23 EET Arnd Bergmann wrote: > gcc-8 -fsanitize-coverage=trace-pc produces a false-positive warning: > > drivers/gpu/drm/msm/mdp/mdp5/mdp5_plane.c: In function > 'mdp5_plane_mode_set.isra.8': > drivers/gpu/drm/msm/mdp/mdp5/mdp5_pl

Re: regression: 4.13 cannot follow symlinks on some ext3 fs

On Fri 24-11-17 15:03:37, Andreas Dilger wrote: > On Nov 24, 2017, at 9:51 AM, Andi Kleen wrote: > > > >> We checked old kernels, and old e2fsprogs, and didn't see any cases > >> where fast (<= 60 chars) symlinks were created using external blocks. > >> It seems that _something_ did create them,

Re: [PATCH 03/10] net: ezchip: nps_enet: Fix platform_get_irq's error checking

From: Russell King - ARM Linux Date: Mon, 4 Dec 2017 16:24:47 + > On Mon, Dec 04, 2017 at 11:20:49AM -0500, David Miller wrote: >> From: Arvind Yadav >> Date: Sun, 3 Dec 2017 00:56:15 +0530 >> >> > The platform_get_irq() function returns negative if an error occurs. >> > zero or positive n

[PATCH 4.9 17/38] KVM: lapic: Fixup LDR on load in x2apic

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dr. David Alan Gilbert commit 12806ba937382fdfdbad62a399aa2dce65c10fcd upstream. In x2apic mode the LDR is fixed based on the ID rather than separately loadable like it was before x2. When kvm_

[PATCH 4.9 20/38] eeprom: at24: fix reading from 24MAC402/24MAC602

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit commit 644a1f19c6c8393d0c4168a5adf79056da6822eb upstream. Chip datasheet mentions that word addresses other than the actual start position of the MAC delivers undefined results.

[PATCH 4.9 24/38] bcache: Fix building error on MIPS

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen commit cf33c1ee5254c6a430bc1538232b49c3ea13e613 upstream. This patch try to fix the building error on MIPS. The reason is MIPS has already defined the PTR macro, which conflicts wit

[PATCH 4.9 23/38] i2c: i801: Fix Failed to allocate irq -2147483648 error

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 6e0c9507bf51e1517a80ad0ac171e5402528fcef upstream. On Apollo Lake devices the BIOS does not set up IRQ routing for the i801 SMBUS controller IRQ, so we end up with dev->irq

[PATCH 4.9 21/38] eeprom: at24: correctly set the size for at24mac402

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bartosz Golaszewski commit 5478e478eee3b096b8d998d4ed445da30da2dfbc upstream. There's an ilog2() expansion in AT24_DEVICE_MAGIC() which rounds down the actual size of EUI-48 byte array in at24m

[PATCH 4.9 26/38] nvme-pci: add quirk for delay before CHK RDY for WDC SN200

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Lien commit 8c97eeccf0ad8783c057830119467b877bdfced7 upstream. And increase the existing delay to cover this device as well. Signed-off-by: Jeff Lien Signed-off-by: Christoph Hellwig Si

[PATCH 4.9 31/38] drm/panel: simple: Add missing panel_simple_unprepare() calls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jonathan Liu commit f3621a8eb59a913612c8e6e37d81f16b649f8b6c upstream. During panel removal or system shutdown panel_simple_disable() is called which disables the panel backlight but the panel

[PATCH 4.9 04/38] mm/cma: fix alloc_contig_range ret code/potential leak

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mike Kravetz commit 63cd448908b5eb51d84c52f02b31b9b4ccd1cb5a upstream. If the call __alloc_contig_migrate_range() in alloc_contig_range returns -EBUSY, processing continues so that test_pages_i

[PATCH 4.9 32/38] drm/hisilicon: Ensure LDI regs are properly configured.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Griffin commit a2f042430784d86eb2b7a6d2a869f552da30edba upstream. This patch fixes the following soft lockup: BUG: soft lockup - CPU#0 stuck for 23s! [weston:307] On weston idle-timeou

[PATCH 4.9 06/38] mm/madvise.c: fix madvise() infinite loop under special circumstances

4.9-stable review patch. If anyone has any objections, please let me know. -- From: chenjie commit 6ea8d958a2c95a1d514015d4e29ba21a8c0a1a91 upstream. MADVISE_WILLNEED has always been a noop for DAX (formerly XIP) mappings. Unfortunately madvise_willneed() doesn't communicate t

[PATCH 4.9 08/38] nfsd: Fix stateid races between OPEN and CLOSE

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit 15ca08d3299682dc49bad73251677b2c5017ef08 upstream. Open file stateids can linger on the nfs4_file list of stateids even after they have been closed. In order to avoid reu

[PATCH 4.9 00/38] 4.9.67-stable review

This is the start of the stable review cycle for the 4.9.67 release. There are 38 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 Wed Dec 6 15:59:56 UTC 2017. Anything receive

Re: KASAN: slab-out-of-bounds Read in strcmp

On Mon, Dec 4, 2017 at 2:59 PM, Paul Moore wrote: > == > BUG: KASAN: slab-out-of-bounds in strcmp+0x96/0xb0 lib/string.c:328 > Read of size 1 at addr 8801cd99d2c1 by task > syzkaller242593/3087 > > CP

[PATCH 4.9 36/38] NFS: revalidate "." etc correctly on "open".

4.9-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit b688741cb06695312f18b730653d6611e1bad28d upstream. For correct close-to-open semantics, NFS must validate the change attribute of a directory (or file) on open. Since commit e

[PATCH 4.9 34/38] drm/amd/pp: fix typecast error in powerplay.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Rex Zhu commit 8d8258bdab735d9f3c4b78e091ecfbb2b2b1f2ca upstream. resulted in unexpected data truncation Reviewed-by: Alex Deucher Signed-off-by: Rex Zhu Signed-off-by: Alex Deucher Signed-

Re: [PATCH] um: Convert ubd driver to blk-mq

On Sun, Dec 03, 2017 at 10:49:23PM +0100, Richard Weinberger wrote: > Convert the driver to the modern blk-mq framework. > As byproduct we get rid of our open coded restart logic and let > blk-mq handle it. > > Signed-off-by: Richard Weinberger > --- > arch/um/drivers/ubd_kern.c | 178 > +++

[PATCH v2] perf tools: set browser mode right before setup_browser()

There are codes that print messages to the screen between assignment of the use_browser variable and setup_browser(). But since the GUI browser is not initialized during that period, all messages fail to show if the user passed the --gtk option to perf as GTK is not initialized yet. Reorder the c

[PATCH 4.14 11/95] v4l2: disable filesystem-dax mapping support

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit b70131de648c2b997d22f4653934438013f407a1 upstream. V4L2 memory registrations are incompatible with filesystem-dax that needs the ability to revoke dma access to a mapping a

[PATCH 4.14 12/95] IB/core: disable memory registration of filesystem-dax vmas

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 5f1d43de54164dcfb9bfa542fcc92c1e1a1b6c1d upstream. Until there is a solution to the dma-to-dax vs truncate problem it is not safe to allow RDMA to create long standing memo

Re: [PATCH] perf tools: set GUI mode after returning from perf_session__new()

Em Tue, Dec 05, 2017 at 01:11:49AM +0900, SeokHo Song escreveu: > Hi Arnaldo, > > 2017-12-05 0:45 GMT+09:00 Arnaldo Carvalho de Melo : > > Em Tue, Dec 05, 2017 at 12:05:18AM +0900, Namhyung Kim escreveu: > >> Hi SeokHo, > >> > >> On Sun, Dec 3, 2017 at 10:50 PM, Song Seok Ho <0xdev...@gmail.com> w

[PATCH 4.14 17/95] fs/fat/inode.c: fix sb_rdonly() change

4.14-stable review patch. If anyone has any objections, please let me know. -- From: OGAWA Hirofumi commit b6e8e12c0aeb5fbf1bf46c84d58cc93aedede385 upstream. Commit bc98a42c1f7d ("VFS: Convert sb->s_flags & MS_RDONLY to sb_rdonly(sb)") converted fat_remount():new_rdonly from a

[PATCH 4.14 16/95] mm, memcg: fix mem_cgroup_swapout() for THPs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Shakeel Butt commit d08afa149acfd00871484ada6dabc3880524cd1c upstream. Commit d6810d730022 ("memcg, THP, swap: make mem_cgroup_swapout() support THP") changed mem_cgroup_swapout() to support t

[PATCH 4.14 14/95] mm/madvise.c: fix madvise() infinite loop under special circumstances

4.14-stable review patch. If anyone has any objections, please let me know. -- From: chenjie commit 6ea8d958a2c95a1d514015d4e29ba21a8c0a1a91 upstream. MADVISE_WILLNEED has always been a noop for DAX (formerly XIP) mappings. Unfortunately madvise_willneed() doesn't communicate

[PATCH 4.14 02/95] mm, memory_hotplug: do not back off draining pcp free pages from kworker context

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michal Hocko commit 4b81cb2ff69c8a8e297a147d2eb4d9b5e8d7c435 upstream. drain_all_pages backs off when called from a kworker context since commit 0ccce3b92421 ("mm, page_alloc: drain per-cpu pa

[PATCH 4.14 21/95] btrfs: clear space cache inode generation always

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Josef Bacik commit 8e138e0d92c6c9d3d481674fb14e3439b495be37 upstream. We discovered a box that had double allocations, and suspected the space cache may be to blame. While auditing the write

[PATCH 4.14 23/95] nfsd: Fix another OPEN stateid race

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust commit d8a1a000555ecd1b824ac1ed6df8fe364df0 upstream. If nfsd4_process_open2() is initialising a new stateid, and yet the call to nfs4_get_vfs_file() fails for some reason,

Re: [PATCH] leds: trigger: Introduce a NETDEV trigger

Hi Jacek, Thank you for the review, trimmed and comments inline. On 3 December 2017 at 21:09, Jacek Anaszewski wrote: >> + * link - LED's normal state reflects whether the link is up >> + * (has carrier) or not >> + * tx - LED blinks on transmitted data >> + * rx - LED blinks on recei

[PATCH 4.14 25/95] crypto: algif_aead - skip SGL entries with NULL page

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stephan Mueller commit 8e1fa89aa8bc2870009b4486644e4a58f2e2a4f5 upstream. The TX SGL may contain SGL entries that are assigned a NULL page. This may happen if a multi-stage AIO operation is pe

Re: [PATCHv5 1/1] ima: re-introduce own integrity cache lock

On 04/12/17 17:40, Dmitry Kasatkin wrote: On 04/12/17 15:42, Roberto Sassu wrote: On 12/4/2017 1:06 PM, Mimi Zohar wrote: Hi Dmitry, On Fri, 2017-12-01 at 20:40 +0200, Dmitry Kasatkin wrote: The original design was discussed 3+ years ago, but was never completed/upstreamed. Based on the

Re: [PATCH 03/10] net: ezchip: nps_enet: Fix platform_get_irq's error checking

On Mon, Dec 04, 2017 at 11:20:49AM -0500, David Miller wrote: > From: Arvind Yadav > Date: Sun, 3 Dec 2017 00:56:15 +0530 > > > The platform_get_irq() function returns negative if an error occurs. > > zero or positive number on success. platform_get_irq() error checking > > for zero is not corre

[PATCH 4.14 03/95] mm, oom_reaper: gather each vma to prevent leaking TLB entry

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Wang Nan commit 687cb0884a714ff484d038e9190edc874edcf146 upstream. tlb_gather_mmu(&tlb, mm, 0, -1) means gathering the whole virtual memory space. In this case, tlb->fullmm is true. Some arc

[PATCH 4.14 04/95] mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit a8f97366452ed491d13cf1e44241bc0b5740b1f0 upstream. Currently, we unconditionally make page table dirty in touch_pmd(). It may result in false-positive can_follow_writ

[PATCH 4.14 06/95] mm: fix device-dax pud write-faults triggered by get_user_pages()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 1501899a898dfb5477c55534bdfd734c046da06d upstream. Currently only get_user_pages_fast() can safely handle the writable gup case due to its use of pud_access_permitted() to

[PATCH 4.14 07/95] mm, hugetlbfs: introduce ->split() to vm_operations_struct

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dan Williams commit 31383c6865a578834dd953d9dbc88e6b19fe3997 upstream. Patch series "device-dax: fix unaligned munmap handling" When device-dax is operating in huge-page mode we want it to be

Re: [PATCH V5 4/7] OF: properties: Implement get_match_data() callback

On Fri, Dec 1, 2017 at 10:27 PM, Sinan Kaya wrote: > Now that we have a get_match_data() callback as part of the firmware node, > implement the OF specific piece for it. > > Signed-off-by: Sinan Kaya > --- > drivers/of/property.c | 17 + > 1 file changed, 17 insertions(+) > > dif

[PATCH 4.14 41/95] KVM: lapic: Fixup LDR on load in x2apic

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dr. David Alan Gilbert commit 12806ba937382fdfdbad62a399aa2dce65c10fcd upstream. In x2apic mode the LDR is fixed based on the ID rather than separately loadable like it was before x2. When kvm

[PATCH 4.14 40/95] KVM: lapic: Split out x2apic ldr calculation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dr. David Alan Gilbert commit e872fa94662d0644057c7c80b3071bdb9249e5ab upstream. Split out the ldr calculation from kvm_apic_set_x2apic_id since we're about to reuse it in the following patch.

[PATCH 4.14 42/95] mmc: sdhci: Avoid swiotlb buffer being full

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ulf Hansson commit 250dcd11466e06df64b92520e2c56bdae453581b upstream. The commit de3ee99b097d ("mmc: Delete bounce buffer handling") deletes the bounce buffer handling, but also causes the max

[PATCH 4.14 44/95] mmc: block: Check return value of blk_get_request()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit fb8e456e547ed2c699f64665bd8a3b9bde7b9728 upstream. blk_get_request() can fail, always check the return value. Fixes: 0493f6fe5bde ("mmc: block: Move boot partition lockin

[PATCH 4.14 45/95] mmc: core: Do not leave the block driver in a suspended state

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit ebe7dd45cf49e3b49cacbaace17f9f878f21fbea upstream. The block driver must be resumed if the mmc bus fails to suspend the card. Signed-off-by: Adrian Hunter Reviewed-by: L

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

On Wed, Nov 29, 2017 at 08:18:09PM +0100, Christian Borntraeger wrote: > Works fine under KVM with virtio-blk, but still hangs during boot in an LPAR. > FWIW, the system not only has scsi disks via fcp but also DASDs as a boot > disk. > Seems that this is the place where the system stops. (see the

[PATCH 4.14 47/95] mmc: core: prepend 0x to pre_eol_info entry in sysfs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bastian Stender commit 80a780a167d9267c72867b806142bd6ec69ba123 upstream. The sysfs entry "pre_eol_info" was missing the 0x prefix to identify it as hex formatted. Fixes: 46bc5c408e4e ("mmc:

Re: [PATCH 03/10] net: ezchip: nps_enet: Fix platform_get_irq's error checking

From: Arvind Yadav Date: Sun, 3 Dec 2017 00:56:15 +0530 > The platform_get_irq() function returns negative if an error occurs. > zero or positive number on success. platform_get_irq() error checking > for zero is not correct. And remove unnecessary check for free_netdev(). > > Signed-off-by: Ar

Re: [PATCH v4.1] phylib: Add device reset GPIO support

On 12/04/2017 01:35 PM, Geert Uytterhoeven wrote: > From: Sergei Shtylyov > > The PHY devices sometimes do have their reset signal (maybe even power > supply?) tied to some GPIO and sometimes it also does happen that a boot > loader does not leave it deasserted. So far this issue has been attack

[PATCH 4.14 49/95] ACPI / EC: Fix regression related to PM ops support in ECDT device

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lv Zheng commit a64a62ce9a380213dc9e192f762266d70c9b40ec upstream. On platforms (ASUS X550ZE and possibly all ASUS X series) with valid ECDT EC but invalid DSDT EC, EC PM ops won't be invoked

[PATCH 4.14 30/95] drm: omapdrm: Fix DPI on platforms using the DSI VDDS

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Pinchart commit bf25dac38f71d392a31ec074f55cbc941f1eaf1d upstream. Commit d178e034d565 ("drm: omapdrm: Move FEAT_DPI_USES_VDDS_DSI feature to dpi code") replaced usage of platform data

[PATCH 4.14 54/95] cxl: Check if vphb exists before iterating over AFU devices

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vaibhav Jain commit 12841f87b7a8ceb3d54f171660f72a86941bfcb3 upstream. During an eeh a kernel-oops is reported if no vPHB is allocated to the AFU. This happens as during AFU init, an error in

[PATCH 4.14 52/95] eeprom: at24: check at24_read/write arguments

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit commit d9bcd462daf34aebb8de9ad7f76de0198bb5a0f0 upstream. So far we completely rely on the caller to provide valid arguments. To be on the safe side perform an own sanity check

[PATCH 4.14 48/95] mmc: core: prepend 0x to OCR entry in sysfs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Bastian Stender commit c892b0d81705c566f575e489efc3c50762db1bde upstream. The sysfs entry "ocr" was missing the 0x prefix to identify it as hex formatted. Fixes: 5fb06af7a33b ("mmc: core: Ext

[PATCH 4.14 53/95] i2c: i801: Fix Failed to allocate irq -2147483648 error

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 6e0c9507bf51e1517a80ad0ac171e5402528fcef upstream. On Apollo Lake devices the BIOS does not set up IRQ routing for the i801 SMBUS controller IRQ, so we end up with dev->ir

Re: [PATCH resend v2] mux: core: Fix double get_device()

On 2017-11-28 10:05, Hans de Goede wrote: > class_find_device already does a get_device on the returned device. > So the device returned by of_find_mux_chip_by_node is already referenced > and we should not reference it again (and unref it on error). > > Also rename of_find_mux_chip_by_node to of_

[PATCH 4.14 31/95] omapdrm: hdmi4: Correct the SoC revision matching

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi commit 23970e150a0a49f9a966c46e5d22fed06226098f upstream. I believe the intention of the commit 2c9fc9bf45f8 ("drm: omapdrm: Move FEAT_HDMI_* features to hdmi4 driver") was to i

[PATCH 4.14 58/95] hwmon: (jc42) optionally try to disable the SMBUS timeout

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Peter Rosin commit 68615eb01f82256c19e41967bfb3eef902f77033 upstream. With a nxp,se97 chip on an atmel sama5d31 board, the I2C adapter driver is not always capable of avoiding the 25-35 ms tim

Re: [Xen-devel] [PATCH V2] Xen/pciback: Implement PCI slot or bus reset with 'do_flr' SysFS attribute

Jan, Do you have any further comments on the current version of this patch?. Otherwise, I will work on the review comments and publish next version of this patch later this week. Please let me know. Thanks. Cheers GOVINDA On 12/1/2017 10:16 AM, Govinda Tatti wrote: On 11/30/2017 8:46 AM, Ja

[PATCH 4.14 34/95] arm64: ftrace: emit ftrace-mod.o contents through code

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit be0f272bfc83797f70d44faca86954df62e2bbc0 upstream. When building the arm64 kernel with both CONFIG_ARM64_MODULE_PLTS and CONFIG_DYNAMIC_FTRACE enabled, the ftrace-mod.o o

[PATCH 4.14 32/95] apparmor: fix oops in audit_signal_cb hook

4.14-stable review patch. If anyone has any objections, please let me know. -- From: John Johansen commit b12cbb21586277f72533769832c24cc6c1d60ab3 upstream. The apparmor_audit_data struct ordering got messed up during a merge conflict, resulting in the signal integer and peer

[PATCH 4.14 35/95] powerpc/powernv: Fix kexec crashes caused by tlbie tracing

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mahesh Salgaonkar commit a3961f824cdbe7eb431254dc7d8f6f6767f474aa upstream. Rebooting into a new kernel with kexec fails in trace_tlbie() which is called from native_hpte_clear(). This happens

Re: [PATCH net-next v2] net: dsa: Allow compiling out legacy support

From: Florian Fainelli Date: Fri, 1 Dec 2017 19:31:41 -0800 > Introduce a configuration option: CONFIG_NET_DSA_LEGACY allowing to compile > out > support for the old platform device and Device Tree binding registration. > Support for these configurations is scheduled to be removed in 4.17. > >

[PATCH 4.14 36/95] powerpc/kexec: Fix kexec/kdump in P9 guest kernels

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 2621e945fbf1d6df5f3f0ba7be5bae3d2cf9b6a5 upstream. The code that cleans up the IAMR/AMOR before kexec'ing failed to remember that when we're running as a guest AMOR is

[PATCH 4.14 28/95] lockd: lost rollback of set_grace_period() in lockd_down_net()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vasily Averin commit 3a2b19d1ee5633f76ae8a88da7bc039a5d1732aa upstream. Commit efda760fe95ea ("lockd: fix lockd shutdown race") is incorrect, it removes lockd_manager and disarm grace_period_e

RE: [PATCH 1/1] gianfar: fix a flooded alignment reports because of padding issue.

>-Original Message- >From: Zumeng Chen [mailto:zumeng.c...@gmail.com] >Sent: Monday, December 04, 2017 5:22 AM >To: net...@vger.kernel.org; linux-kernel@vger.kernel.org >Cc: Claudiu Manoil ; da...@davemloft.net >Subject: [PATCH 1/1] gianfar: fix a flooded alignment reports because of >padd

Re: [PATCH v2 00/31] Replacing net_mutex with rw_semaphore

On 04.12.2017 19:10, David Miller wrote: > From: Kirill Tkhai > Date: Mon, 4 Dec 2017 18:54:51 +0300 > >> Still no comments :( >> >> Ping, ping, ping. > > You cannot force people to prioritize reviewing your patch submission. > > Screaming "ping ping ping" doesn't help, in fact is hinders. > >

[PATCH v13 1/5] serdev: Make .remove in struct serdev_device_driver optional

Using devres infrastructure it is possible to write a serdev driver that doesn't have any code that needs to be called as a part of .remove. Add code to make .remove optional. Cc: linux-kernel@vger.kernel.org Cc: linux-ser...@vger.kernel.org Cc: Rob Herring Cc: cphe...@gmail.com Cc: Guenter Roeck

[PATCH 5/5] blkcg: Add cgroup file to configure blkcg::blkg_aio_max_nr

Add a file to configure per-cgroup maximum number of available aio requests. Allow write the values, which are less then currently allocated numbers of requests. Show numbers of currently allocated and maximum available requests. Signed-off-by: Kirill Tkhai --- block/blk-cgroup.c | 40 ++

[PATCH 4/5] blkcg: Charge aio requests in blkio cgroup hierarchy

This patch adds accounting of number of requests of allocated aio contexts per blkio cgroup, and aggregates child cgroups requests up the hierarhy. This may be used to limit aio requests available for containers. By default, newly allocated blkcg::blkg_aio_max_nr is set to "unlimited" value (see b

[PATCH 3/5] blkcg: Add blkcg::blkg_aio_nr and blkcg::blkg_aio_max_nr

This adds new members of struct blkcg, which will be used to account numbers of cgroup's aio requests. Also, blkcg_root is used to store sysctl variables aio_nr and aio_max_nr. Signed-off-by: Kirill Tkhai --- block/blk-cgroup.c |4 fs/aio.c |2 ++ include/

[PATCH 2/5] aio: Export aio_nr_lock and aio_max_nr initial value to include/linux/aio.h

Next patch will use the values in more files, so let's make them visible external. Signed-off-by: Kirill Tkhai --- fs/aio.c|4 ++-- include/linux/aio.h |4 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/fs/aio.c b/fs/aio.c index 04209c0561b2..9dc98a29077

[PATCH 0/5] blkcg: Limit maximum number of aio requests available for cgroup

Hi, this patch set introduces accounting aio_nr and aio_max_nr per blkio cgroup. It may be used to limit number of aio requests, which are available for a cgroup, and could be useful for containers. The accounting is hierarchical, and aio contexts, allocated in child cgroup, are accounted in pare

[PATCH 1/5] aio: Move aio_nr increment to separate function

There is no functional changes, only a preparation for next patches. Signed-off-by: Kirill Tkhai --- fs/aio.c | 44 1 file changed, 32 insertions(+), 12 deletions(-) diff --git a/fs/aio.c b/fs/aio.c index e6de7715228c..04209c0561b2 100644 --- a/fs/

[PATCH v13 2/5] serdev: Introduce devm_serdev_device_open()

Add code implementing managed version of serdev_device_open() for serdev device drivers that "open" the device during driver's lifecycle only once (e.g. opened in .probe() and closed in .remove()). Cc: linux-kernel@vger.kernel.org Cc: linux-ser...@vger.kernel.org Cc: Rob Herring Cc: cphe...@gmail

[PATCH v13 3/5] mfd: Add driver for RAVE Supervisory Processor

Add a driver for RAVE Supervisory Processor, an MCU implementing various bits of housekeeping functionality (watchdoging, backlight control, LED control, etc) on RAVE family of products by Zodiac Inflight Innovations. This driver implementes core MFD/serdev device as well as communication subrouti

[PATCH v13 4/5] watchdog: Add RAVE SP watchdog driver

This driver provides access to RAVE SP watchdog functionality. Cc: linux-kernel@vger.kernel.org Cc: linux-watch...@vger.kernel.org Cc: cphe...@gmail.com Cc: Lucas Stach Cc: Nikita Yushchenko Cc: Lee Jones Cc: Greg Kroah-Hartman Cc: Pavel Machek Cc: Andy Shevchenko Cc: Guenter Roeck Cc: Rob

Re: [PATCH] perf tools: set GUI mode after returning from perf_session__new()

Hi Arnaldo, 2017-12-05 0:45 GMT+09:00 Arnaldo Carvalho de Melo : > Em Tue, Dec 05, 2017 at 12:05:18AM +0900, Namhyung Kim escreveu: >> Hi SeokHo, >> >> On Sun, Dec 3, 2017 at 10:50 PM, Song Seok Ho <0xdev...@gmail.com> wrote: >> > If perf_session__new() returns NULL with use_browser set to 2 via -

[PATCH v13 5/5] dt-bindings: watchdog: Add bindings for RAVE SP watchdog driver

Add Device Tree bindings for RAVE SP watchdog drvier - an MFD cell of parent RAVE SP driver (documented in Documentation/devicetree/bindings/mfd/zii,rave-sp.txt). Cc: linux-kernel@vger.kernel.org Cc: devicet...@vger.kernel.org Cc: linux-watch...@vger.kernel.org Cc: cphe...@gmail.com Cc: Lucas Stac

Re: [PATCH v3 2/5] kasan/Makefile: Support LLVM style asan parameters.

On 12/02/2017 12:36 AM, Paul Lawrence wrote: > Missing: From: Andrey Ryabinin Please, don't change authorship of the patches. > LLVM doesn't understand GCC-style paramters ("--param asan-foo=bar"), > thus we currently we don't use inline/globals/stack instrumentation > when building th

[PATCH 4.14 78/95] drm/amd/pp: fix typecast error in powerplay.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rex Zhu commit 8d8258bdab735d9f3c4b78e091ecfbb2b2b1f2ca upstream. resulted in unexpected data truncation Reviewed-by: Alex Deucher Signed-off-by: Rex Zhu Signed-off-by: Alex Deucher Signed

[PATCH 4.14 75/95] drm/panel: simple: Add missing panel_simple_unprepare() calls

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jonathan Liu commit f3621a8eb59a913612c8e6e37d81f16b649f8b6c upstream. During panel removal or system shutdown panel_simple_disable() is called which disables the panel backlight but the panel

Re: [PATCH tip/core/rcu 02/20] torture: Prepare scripting for shift from %p to %pK

On Mon, Dec 04, 2017 at 02:13:38PM +, David Laight wrote: > From: Paul E. McKenney > > Sent: 04 December 2017 13:42 > > On Mon, Dec 04, 2017 at 12:32:30PM +, David Laight wrote: > > > From: Paul E. McKenney > > > > Sent: 01 December 2017 20:09 > > > > > > > > Because %p prints "(null)" and

[PATCH 4.14 84/95] include/linux/compiler-clang.h: handle randomizable anonymous structs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sandipan Das commit 4ca59b14e588f873795a11cdc77a25c686a29d23 upstream. The GCC randomize layout plugin can randomize the member offsets of sensitive kernel data structures. To use this featur

Re: [PATCH v2 00/31] Replacing net_mutex with rw_semaphore

From: Kirill Tkhai Date: Mon, 4 Dec 2017 18:54:51 +0300 > Still no comments :( > > Ping, ping, ping. You cannot force people to prioritize reviewing your patch submission. Screaming "ping ping ping" doesn't help, in fact is hinders. > What will we do next? Be patient.

[PATCH 4.14 85/95] IB/core: Do not warn on lid conversions for OPA

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Don Hiatt commit 6588e412fe872ed81f3fb8d9b4561a66ecb763d0 upstream. On OPA devices the user_mad recv_handler can receive 32Bit LIDs (e.g. OPA_PERMISSIVE_LID) and it is okay to lose the upper 1

[PATCH 4.14 87/95] e1000e: fix the use of magic numbers for buffer overrun issue

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sasha Neftin commit c0f4b163a03e73055dd734eaca64b9580e72e7fb upstream. This is a follow on to commit b10effb92e27 ("fix buffer overrun while the I219 is processing DMA transactions") to addre

[PATCH 4.14 89/95] drm/i915: Fix false-positive assert_rpm_wakelock_held in i915_pmic_bus_access_notifier v2

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit f4359cedfb43b934f38c50d1604db21333abe57b upstream. assert_rpm_wakelock_held is triggered from i915_pmic_bus_access_notifier even though it gets unregistered on (runtime) s

[PATCH 4.14 91/95] drm/i915/fbdev: Serialise early hotplug events with async fbdev config

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Chris Wilson commit a45b30a6c5db631e2ba680304bd5edd0cd1f9643 upstream. As both the hotplug event and fbdev configuration run asynchronously, it is possible for them to run concurrently. If con

Re: [PATCH 0/4] Move DP phy switch to PHY driver

Hi, On Sun, Dec 3, 2017 at 11:46 PM, Heiko Stübner wrote: > Hi Chris, > > Am Montag, 4. Dezember 2017, 10:47:08 CET schrieb Chris Zhong: >> On 2017年12月02日 05:58, Heiko Stuebner wrote: >> > Am Freitag, 1. Dezember 2017, 13:42:46 CET schrieb Doug Anderson: >> >> Hi, >> >> >> >> On Wed, Nov 29, 2017

[PATCH 4.14 74/95] drm/radeon: fix atombios on big endian

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Roman Kapl commit 4f626a4ac8f57ddabf06d03870adab91e463217f upstream. The function for byteswapping the data send to/from atombios was buggy for num_bytes not divisible by four. The function mu

[PATCH 4.14 65/95] drm/amdgpu: Properly allocate VM invalidate eng v2

4.14-stable review patch. If anyone has any objections, please let me know. -- From: ozeng commit c5066129af4436ab0da8eefe4289774a5409706d upstream. v1: Properly allocate TLB invalidation engine to avoid conflict. v2: Added comments to codes Signed-off-by: Oak Zeng Reviewed-

[PATCH 4.14 73/95] drm/tilcdc: Precalculate total frametime in tilcdc_crtc_set_mode()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jyri Sarha commit ce99f7206c9105851d97202ed08c058af6f11ac4 upstream. We need the total frame refresh time to check if we are too close to vertical sync when updating the two framebuffer DMA re

[PATCH 4.14 90/95] drm/i915: Re-register PMIC bus access notifier on runtime resume

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 294cf1af8cf2eb0d1eced377fdfb9a2d3f0e8b42 upstream. intel_uncore_suspend() unregisters the uncore code's PMIC bus access notifier and gets called on both normal and runtime

[PATCH 4.14 95/95] Revert "x86/entry/64: Add missing irqflags tracing to native_load_gs_index()"

4.14-stable review patch. If anyone has any objections, please let me know. -- This reverts commit f9a64e23a9da528e7d8aa1bd2c7bb92be4ebb724 which is commit 0d794d0d018f23fb09c50f6ae26868bd6ae343d6 upstream. Andy writes: I think the thing to do is to revert the patch fro

[PATCH 4.14 92/95] drm/i915/gvt: Correct ADDR_4K/2M/1G_MASK definition

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Xiong Zhang commit b721b65af4eb46df6a1d9e34b14003225e403565 upstream. For ADDR_4K_MASK, bit[45..12] should be 1, all other bits should be 0. The current definition wrongly set bit[46] as 1 als

[PATCH 4.14 88/95] md: forbid a RAID5 from having both a bitmap and a journal.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: NeilBrown commit 230b55fa8d64007339319539f8f8e68114d08529 upstream. Having both a bitmap and a journal is pointless. Attempting to do so can corrupt the bitmap if the journal replay happens be

[PATCH 4.14 86/95] IB/hfi1: Do not warn on lid conversions for OPA

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Don Hiatt commit 4988be5813ff2afdc0d8bfa315ef34a577d3efbf upstream. On OPA devices opa_local_smp_check will receive 32Bit LIDs when the LID is Extended. In such cases, it is okay to lose the u

[PATCH 4.14 80/95] drm/fsl-dcu: Dont set connector DPMS property

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Pinchart commit daee54263c1202cbdab85c5e15ae30b417602efb upstream. Since commit 4a97a3da420b ("drm: Don't update property values for atomic drivers") atomic drivers must not update pro

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