[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 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 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 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

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 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

[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 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

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

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

[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: [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 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,

[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 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 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 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

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 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

[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 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

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 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-

[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

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 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

[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 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 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 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 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 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 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 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 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 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 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_

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

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] 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

[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] 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

[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

Re: [PATCH v4] arm64: dts: rockchip: update mipi cells for RK3399

Hi Heiko, On Monday, 4 December 2017 15:46:32 EET Heiko Stuebner wrote: > Am Montag, 4. Dezember 2017, 15:22:07 CET schrieb Laurent Pinchart: > > On Wednesday, 29 November 2017 20:47:55 EET Brian Norris wrote: > > > From: Nickey Yang > > > > > > We might include additional ports in derivative de

replace PCI_DMA_BUS_IS_PHYS with a per-instance flag

Hi all, this small series tries to get rid of the global and misnamed PCI_DMA_BUS_IS_PHYS flag, and replace it with a setting in each struct dma_map_ops instance.

[PATCH 1/3] dma-mapping: take dma_pfn_offset into account in dma_max_pfn

This makes sure the generic version can be used with architectures / devices that have a DMA offset in the direct mapping. Signed-off-by: Christoph Hellwig --- include/linux/dma-mapping.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/dma-mapping.h b/include/li

[PATCH 2/3] arm64: don't override dma_max_pfn

The generic version now takes dma_pfn_offset into account, so there is no more need for an architecture override. Signed-off-by: Christoph Hellwig --- arch/arm64/include/asm/dma-mapping.h | 9 - 1 file changed, 9 deletions(-) diff --git a/arch/arm64/include/asm/dma-mapping.h b/arch/arm

[PATCH 4.9 10/38] nfsd: fix panic in posix_unblock_lock called from nfs4_laundromat

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Naofumi Honda commit 64ebe12494fd5d193f014ce38e1fd83cc57883c8 upstream. >From kernel 4.9, my two nfsv4 servers sometimes suffer from "panic: unable to handle kernel page request" in posix_u

[PATCH 4.4 11/27] btrfs: clear space cache inode generation always

4.4-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 o

[PATCH 1/1] x86/asm: Allow again using asm.h when building for the 'bpf' clang target

Up to f5caf621ee35 ("x86/asm: Fix inline asm call constraints for Clang") we were able to use x86 headers to build to the 'bpf' clang target, as done by the BPF code in tools/perf/. With that commit, we ended up with following failure for 'perf test LLVM', this is because "clang ... -target bpf ..

[PATCH 4.9 01/38] ARM: dts: LogicPD Torpedo: Fix camera pin mux

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adam Ford commit 56322e123235370f1449c7444e311cce857d12f5 upstream. Fix commit 05c4ffc3a266 ("ARM: dts: LogicPD Torpedo: Add MT9P031 Support") In the previous commit, I indicated that the only

[PATCH 4.4 19/27] drm/radeon: fix atombios on big endian

4.4-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 mus

[PATCH 4.4 16/27] eeprom: at24: check at24_read/write arguments

4.4-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.4 15/27] mmc: core: Do not leave the block driver in a suspended state

4.4-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: Li

[PATCH 4.4 27/27] nfsd: Fix another OPEN stateid race

4.4-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: KASAN: slab-out-of-bounds Read in strcmp

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

[PATCH 4.4 26/27] nfsd: Fix stateid races between OPEN and CLOSE

4.4-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.4 00/27] 4.4.104-stable review

This is the start of the stable review cycle for the 4.4.104 release. There are 27 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:33 UTC 2017. Anything receiv

[PATCH 4.4 22/27] NFS: revalidate "." etc correctly on "open".

4.4-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.4 04/27] x86/efi: Hoist page table switching code into efi_call_virt()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matt Fleming commit c9f2a9a65e4855b74d92cdad688f6ee4a1a323ff upstream. This change is a prerequisite for pending patches that switch to a dedicated EFI page table, instead of using 'trampoline_

[PATCH 4.4 05/27] x86/efi: Build our own page table structures

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matt Fleming commit 67a9108ed4313b85a9c53406d80dc1ae3f8c3e36 upstream. With commit e1a58320a38d ("x86/mm: Warn on W^X mappings") all users booting on 64-bit UEFI machines see the following warn

[PATCH 4.4 10/27] mm/madvise.c: fix madvise() infinite loop under special circumstances

4.4-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.4 03/27] x86/mm/pat: Ensure cpa->pfn only contains page frame numbers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matt Fleming commit edc3b9129cecd0f0857112136f5b8b1bc1d45918 upstream. The x86 pageattr code is confused about the data that is stored in cpa->pfn, sometimes it's treated as a page frame number

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

On Mon, Dec 04, 2017 at 11:34:48AM -0500, David Miller wrote: > 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_g

Re: [PATCH v3 3/5] kasan: support alloca() poisoning

I don't think we are using alloca in kernel mode code, and we shouldn't. What do I miss? Is this hidden support for on-stack VLAs? I thought we'd get rid of them as well.

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

I have no objections to adding this to 4.9-stable or 4.14-stable. Jeff Lien -Original Message- From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org] Sent: Monday, December 4, 2017 10:00 AM To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman; sta...@vger.kernel.org; Jeffrey Li

[PATCH 4.4 01/27] netlink: add a start callback for starting a netlink dump

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tom Herbert commit fc9e50f5a5a4e1fa9ba2756f745a13e693cf6a06 upstream. The start callback allows the caller to set up a context for the dump callbacks. Presumably, the context can then be destro

[PATCH 3.18 08/12] eeprom: at24: check at24_read/write arguments

3.18-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 3.18 05/12] btrfs: clear space cache inode generation always

3.18-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 3.18 03/12] mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()

3.18-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

Re: KASAN: use-after-free Read in __fput

On Thu, Nov 02, 2017 at 04:05:01AM -0700, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 3a99df9a3d14cd866b5516f8cba515a3bfd554ab > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console ou

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

On Monday 04 December 2017 10:12 PM, Russell King - ARM Linux wrote: On Mon, Dec 04, 2017 at 11:34:48AM -0500, David Miller wrote: 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

Re: [bisected] x86 boot still broken on -rc2

On 12/04/2017 08:13 AM, Prarit Bhargava wrote: > > > x86: Booting SMP configuration: > node #0, CPUs:#1 #2 #3 #4 > node #1, CPUs:#5 #6 #7 #8 #9 > node #0, CPUs: #10 #11 #12 #13 #14 > node #1, CPUs: #15 #16 #17 #18 #19 > smp: Brought up 2 nodes, 20 CP

[PATCH 3.18 10/12] NFS: revalidate "." etc correctly on "open".

3.18-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

[PATCH v2] scripts: builddeb: allow customization of "Depends:" fields

The debian packages coming out of "make *deb-pkg" lack the "Depends:" field. If one tries to install a fresh system with such a "linux-image" debootstrap or multistrap might try to install the kernel before its deps and the package hooks will fail. Different debian-based distros use different valu

Re: [PATCH v2 08/19] ASoC: tlv320aic31xx: Switch GPIO handling to use gpiod_* API

On 11/29/2017 03:32 PM, Andrew F. Davis wrote: > Move to using newer gpiod_* GPIO handling functions. This simplifies > the code and eases dropping platform data in the next patch. Also > remember GPIO are active low, so set "1" to reset. > > Signed-off-by: Andrew F. Davis > --- Kbuild bot seem

[PATCH][next] drm/i915/gvt: Add missing breaks in switch statement

From: Colin Ian King The switch statement is missing breaks for the cases of GVT_FAILSAFE_INSUFFICIENT_RESOURCE and GVT_FAILSAFE_GUEST_ERR. Add them in. Detected by CoverityScan, CID#1462416 ("Missing break in switch") Fixes: e011c6ce2b4f ("drm/i915/gvt: Add VM healthy check for workload_thread

[tip:WIP.x86/kpti 50/65] include/linux/compiler.h:319:38: error: call to '__compiletime_assert_254' declared with attribute error: BUILD_BUG_ON failed: pgd_index(EFI_VA_END) != pgd_index(MODULES_END)

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/kpti head: c7ddf30cab554658b154ee16ae5e5d577ff530bf commit: 9ebd9d9cdbc90021a5e320fb054cf48c027e6d34 [50/65] x86/fixmap: Add ldt entries to user shared fixmap config: x86_64-allmodconfig (attached as .config) compiler: g

Re: [PATCH 4.4 00/27] 4.4.104-stable review

On Mon, Dec 04, 2017 at 04:59:25PM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.4.104 release. > There are 27 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

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

>>> On 04.12.17 at 17:16, wrote: > Do you have any further comments on the current version of this patch?. No. I'm not fully understanding your most recent slot related comments, but I'll trust you and Konrad to get this into suitable shape. Jan

Re: [PATCH v2] scripts: builddeb: allow customization of "Depends:" fields

Hi, this is a simpler version that allows just the customization of "Depends:", as requested by Ben. It addresses the security issues Jim mentioned by not using eval anymore. Henning Am Mon, 4 Dec 2017 17:48:08 +0100 schrieb Henning Schild : > The debian packages coming out of "make *deb-pkg"

[patch 02/60] x86/unwinder/orc: Dont bail on stack overflow

From: Andy Lutomirski If the stack overflows into a guard page and the ORC unwinder should work well: by construction, there can't be any meaningful data in the guard page because no writes to the guard page will have succeeded. But there is a bug that prevents unwinding from working correctly:

[patch 13/60] x86/entry: Move SYSENTER_stack to the beginning of struct tss_struct

From: Andy Lutomirski SYSENTER_stack should have reliable overflow detection, which means that it needs to be at the bottom of a page, not the top. Move it to the beginning of struct tss_struct and page-align it. Also add an assertion to make sure that the fixed hardware TSS doesn't cross a page

[patch 00/60] x86/kpti: Kernel Page Table Isolation (was KAISER)

This series is a major overhaul of the KAISER patches: 1) Entry code Mostly the same, except for a handful of fixlets and delta improvements folded into the corresponding patches New: Map TSS read only into the user space visible mapping This is 64bit only, as 32bit needs the TSS

[patch 11/60] x86/entry: Fix assumptions that the HW TSS is at the beginning of cpu_tss

From: Andy Lutomirski A future patch will move SYSENTER_stack to the beginning of cpu_tss to help detect overflow. Before this can happen, fix several code paths that hardcode assumptions about the old layout. Signed-off-by: Andy Lutomirski Signed-off-by: Ingo Molnar Signed-off-by: Thomas Gle

[patch 10/60] x86/kasan/64: Teach KASAN about the cpu_entry_area

From: Andy Lutomirski The cpu_entry_area will contain stacks. Make sure that KASAN has appropriate shadow mappings for them. Signed-off-by: Andy Lutomirski Signed-off-by: Andrey Ryabinin Signed-off-by: Ingo Molnar Signed-off-by: Thomas Gleixner Cc: Rik van Riel Cc: Denys Vlasenko Cc: Pete

[patch 43/60] x86/fixmap: Add debugstore entries to cpu_entry_area

From: Thomas Gleixner The intel PEBS/BTS debug store is a design trainwreck as is expects virtual addresses which must be visible in any execution context. So it is required to make these mappings visible to user space when kernel page table isolation is active. Provide enough room for the buff

[patch 46/60] x86/ldt: Rename ldt_struct->entries member

From: Thomas Gleixner To support user shared LDT entry mappings it's required to change the LDT related code so that the kernel side only references the real page mapping of the LDT. When the LDT is loaded then the entries are alias mapped in the per cpu fixmap. To catch all users rename ldt_stru

[patch 48/60] x86/mm: Move the CR3 construction functions to tlbflush.h

From: Dave Hansen For flushing the TLB, the ASID which has been programmed into the hardware must be known. That differs from what is in 'cpu_tlbstate'. Add functions to transform the 'cpu_tlbstate' values into to the one programmed into the hardware (CR3). It's not easy to include mmu_context

[patch 51/60] x86/mm: Allow flushing for future ASID switches

From: Dave Hansen If changing the page tables in such a way that an invalidation of all contexts (aka. PCIDs / ASIDs) is required, they can be actively invalidated by: 1. INVPCID for each PCID (works for single pages too). 2. Load CR3 with each PCID without the NOFLUSH bit set 3. Load CR3 w

[patch 49/60] x86/mm: Remove hard-coded ASID limit checks

From: Dave Hansen First, it's nice to remove the magic numbers. Second, KERNEL_PAGE_TABLE_ISOLATION is going to consume half of the available ASID space. The space is currently unused, but add a comment to spell out this new restriction. Signed-off-by: Dave Hansen Signed-off-by: Ingo Molnar

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

On 12/04/2017 07:20 PM, Paul Lawrence wrote: > > > +   # -fasan-shadow-offset fails without -fsanitize > > +   CFLAGS_KASAN_SHADOW := $(call cc-option, -fsanitize=kernel-address \ > > +                     -fasan-shadow-offset=$(KASAN_SHADOW_OFFSET), \ > > +                     $(

[PATCH v3 0/3] perf tools: perf tools: Clarify overwrite and backward, bugfix

Simplify patch 1/3 following Namhyung's suggestion. Context adjustment for patch 2 and 3. Wang Nan (3): perf mmap: Fix perf backward recording perf tools: Don't discard prev in backward mode perf tools: Replace 'backward' to 'overwrite' in evlist. mmap and record tools/perf/builtin-re

[PATCH v3 1/3] perf mmap: Fix perf backward recording

perf record backward recording doesn't work as we expected: it never overwrite when ring buffer full. Test: (Run a busy python printing task background like this: while True: print 123 send SIGUSR2 to perf to capture snapshot.) # ./perf record --overwrite -e raw_syscalls:sys_enter -e ra

[PATCH v3 2/3] perf tools: Don't discard prev in backward mode

Perf record can switch output. The new output should only store the data after switching. However, in overwrite backward mode, the new output still have the data from old output. That also brings extra overhead. At the end of mmap_read, the position of processed ring buffer is saved in md->prev. N

[PATCH v3 3/3] perf tools: Replace 'backward' to 'overwrite' in evlist. mmap and record

Remove the backward/forward concept to make it uniform with user interface (the '--overwrite' option). Signed-off-by: Wang Nan --- tools/perf/builtin-record.c | 14 +++--- tools/perf/tests/backward-ring-buffer.c | 4 ++-- tools/perf/util/evlist.c| 30

[patch 47/60] x86/ldt: Map LDT entries into fixmap

From: Thomas Gleixner LDT is not really commonly used on 64bit so the overhead of populating the fixmap entries on context switch for the rare LDT syscall users is a reasonable trade off vs. having extra dynamically managed mapping space per process. Signed-off-by: Thomas Gleixner --- arch/x86

Re: [PATCH v3 3/5] kasan: support alloca() poisoning

On 12/04/2017 07:42 PM, Christoph Hellwig wrote: > I don't think we are using alloca in kernel mode code, and we shouldn't. > What do I miss? Is this hidden support for on-stack VLAs? I thought > we'd get rid of them as well. > Yes, this is for on-stack VLA. Last time I checked, we still had

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