[PATCH 4.14 162/164] md: free unused memory after bitmap resize

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Zdenek Kabelac [ Upstream commit 0868b99c214a3d55486c700de7c3f770b7243e7c ] When bitmap is resized, the old kalloced chunks just are not released once the resized bitmap starts to use new spa

[PATCH 4.14 146/164] xfrm: Copy policy family in clone_policy

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu [ Upstream commit 0e74aa1d79a5bbc663e03a2804399cae418a0321 ] The syzbot found an ancient bug in the IPsec code. When we cloned a socket policy (for example, for a child TCP socket

Re: [PATCH v19 1/7] xbitmap: Introduce xbitmap

Matthew, Wei, On Tue, Dec 12, 2017 at 12:55 PM, Wei Wang wrote: > From: Matthew Wilcox > > The eXtensible Bitmap is a sparse bitmap representation which is > efficient for set bits which tend to cluster. It supports up to > 'unsigned long' worth of bits, and this commit adds the bare bones -- >

[PATCH 4.14 145/164] tls: Use kzalloc for aead_request allocation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Lesokhin [ Upstream commit 61ef6da622aa7b66bf92991bd272490eea6c712e ] Use kzalloc for aead_request allocation as we don't set all the bits in the request. Fixes: 3c4d7559159b ('tls: ker

[PATCH 4.14 163/164] RDMA/cxgb4: Annotate r2 and stag as __be32

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Leon Romanovsky [ Upstream commit 7d7d065a5eec7e218174d5c64a9f53f99ffdb119 ] Chelsio cxgb4 HW is big-endian, hence there is need to properly annotate r2 and stag fields as __be32 and not __u3

[PATCH 4.14 144/164] jump_label: Invoke jump_label_test() via early_initcall()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jason Baron [ Upstream commit 92ee46efeb505ead3ab06d3c5ce695637ed5f152 ] Fengguang Wu reported that running the rcuperf test during boot can cause the jump_label_test() to hit a WARN_ON(). Th

[PATCH 4.14 161/164] dm raid: fix panic when attempting to force a raid to sync

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heinz Mauelshagen [ Upstream commit 233978449074ca7e45d9c959f9ec612d1b852893 ] Requesting a sync on an active raid device via a table reload (see 'sync' parameter in Documentation/device-mapp

Re: [PATCH v3 1/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter

Hi Viresh, On 12/12/17 17:07, Viresh Kumar wrote: [...] > From: Viresh Kumar > Date: Tue, 12 Dec 2017 15:43:26 +0530 > Subject: [PATCH] sched: Keep track of cpufreq utilization update flags > > Currently the schedutil governor overwrites the sg_cpu->flags field on > every call to the utilizati

[PATCH 4.14 158/164] nvmet-rdma: update queue list during ib_device removal

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Israel Rukshin [ Upstream commit 43b92fd27aaef0f529c9321cfebbaec1d7b8f503 ] A NULL deref happens when nvmet_rdma_remove_one() is called more than once (e.g. while connected via 2 ports). The

[PATCH 4.14 112/164] mac80211_hwsim: Fix memory leak in hwsim_new_radio_nl()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings [ Upstream commit 67bd52386125ce1159c0581cbcd2740addf33cd4 ] hwsim_new_radio_nl() now copies the name attribute in order to add a null-terminator. mac80211_hwsim_new_radio() (i

[PATCH 4.14 154/164] powerpc/powernv/idle: Round up latency and residency values

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vaidyanathan Srinivasan [ Upstream commit 8d4e10e9ed9450e18fbbf6a8872be0eac9fd4999 ] On PowerNV platforms, firmware provides exit latency and target residency for each of the idle states in n

[PATCH 4.14 152/164] afs: Connect up the CB.ProbeUuid

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit f4b3526d83c40dd8bf5948b9d7a1b2c340f0dcc8 ] The handler for the CB.ProbeUuid operation in the cache manager is implemented, but isn't listed in the switch-state

[PATCH 4.14 143/164] atm: horizon: Fix irq release error

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arvind Yadav [ Upstream commit bde533f2ea607cbbbe76ef8738b36243939a7bc2 ] atm_dev_register() can fail here and passed parameters to free irq which is not initialised. Initialization of 'dev->

[PATCH 4.14 113/164] gre6: use log_ecn_error module parameter in ip6_tnl_rcv()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 981542c526ecd846920bc500e9989da906ee9fb9 ] After commit 308edfdf1563 ("gre6: Cleanup GREv6 receive path, call common GRE functions") it's not used anywhere in

[PATCH 4.14 110/164] apparmor: fix leak of null profile name if profile allocation fails

4.14-stable review patch. If anyone has any objections, please let me know. -- From: John Johansen [ Upstream commit 4633307e5ed6128975595df43f796a10c41d11c1 ] Fixes: d07881d2edb0 ("apparmor: move new_null_profile to after profile lookup fns()") Reported-by: Seth Arnold Sig

[PATCH] x86/pti: Add pti= cmdline option and documentation

From: Borislav Petkov Keep the "nopti" for traditional reasons. Requested-by: Linus Torvalds Signed-off-by: Borislav Petkov Cc: Linus Torvalds Cc: Andy Lutomirsky Cc: Peter Zijlstra Cc: Dave Hansen Cc: Greg KH Cc: keesc...@google.com Cc: hu...@google.com Cc: Brian Gerst Cc: Josh Poimboeu

[PATCH 4.14 109/164] powerpc/perf: Fix pmu_count to count only nest imc pmus

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan [ Upstream commit de34787f1096cce38e2590be0013b44418d14546 ] "pmu_count" in opal_imc_counters_probe() is intended to hold the number of successful nest imc pmu registerati

[PATCH 4.14 140/164] clk: hi3660: fix incorrect uart3 clock freqency

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Zhong Kaihua [ Upstream commit d33fb1b9f0fcb67f2b9f8b1891465a088a9480f8 ] UART3 clock rate is doubled in previous commit. This error is not detected until recently a mezzanine board which ma

[PATCH 4.14 139/164] clk: uniphier: fix DAPLL2 clock rate of Pro5

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Masahiro Yamada [ Upstream commit 67affb78a4e4feb837953e3434c8402a5c3b272f ] The parent of DAPLL2 should be DAPLL1. Fix the clock connection. Signed-off-by: Masahiro Yamada Signed-off-by:

[PATCH 4.14 134/164] geneve: fix fill_info when link down

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hangbin Liu [ Upstream commit fd7eafd02121d6ef501ef1a4a891e6061366c952 ] geneve->sock4/6 were added with geneve_open and released with geneve_stop. So when geneve link down, we will not able

[PATCH 4.14 135/164] bpf: fix lockdep splat

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 89ad2fa3f043a1e8daae193bcb5fe34d5f8caf28 ] pcpu_freelist_pop() needs the same lockdep awareness than pcpu_freelist_populate() to avoid a false positive. [ INF

[PATCH 4.14 131/164] sctp: do not free asoc when it is already dead in sctp_sendmsg

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit ca3af4dd28cff4e7216e213ba3b671fbf9f84758 ] Now in sctp_sendmsg sctp_wait_for_sndbuf could schedule out without holding sock sk. It means the current asoc can be fre

[PATCH 4.14 132/164] sctp: use the right sk after waking up from wait_buf sleep

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit cea0cc80a6777beb6eb643d4ad53690e1ad1d4ff ] Commit dfcb9f4f99f1 ("sctp: deny peeloff operation on asocs with threads sleeping on it") fixed the race between peeloff

[PATCH 4.14 130/164] slub: fix sysfs duplicate filename creation when slub_debug=O

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Miles Chen [ Upstream commit 11066386efa692f77171484c32ea30f6e5a0d729 ] When slub_debug=O is set. It is possible to clear debug flags for an "unmergeable" slab cache in kmem_cache_open(). I

[PATCH 4.14 128/164] sparc64/mm: set fields in deferred pages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Tatashin [ Upstream commit 2a20aa171071a334d80c4e5d5af719d8374702fc ] Without deferred struct page feature (CONFIG_DEFERRED_STRUCT_PAGE_INIT), flags and other fields in "struct page"es

[PATCH 4.14 126/164] dt-bindings: usb: fix reg-property port-number range

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold [ Upstream commit f42ae7b0540937e00fe005812997f126aaac4bc2 ] The USB hub port-number range for USB 2.0 is 1-255 and not 1-31 which reflects an arbitrary limit set by the current

[PATCH 4.14 124/164] nfp: fix flower offload metadata flag usage

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pieter Jansen van Vuuren [ Upstream commit 6c3ab204f4ca00374a374bc0fc9a275b64d1bcbb ] Hardware has no notion of new or last mask id, instead it makes use of the message type (i.e. add flow or

[PATCH 4.14 123/164] nfp: inherit the max_mtu from the PF netdev

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dirk van der Merwe [ Upstream commit 743ba5b47f7961fb29f2e06bb694fb4f068ac58f ] The PF netdev is used for data transfer for reprs, so reprs inherit the maximum MTU settings of the PF netdev.

[PATCH 4.14 121/164] NFS: Fix a typo in nfs_rename()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Trond Myklebust [ Upstream commit d803224c84be067754db7fa58a93f36f61566493 ] On successful rename, the "old_dentry" is retained and is attached to the "new_dir", so we need to call nfs_set_ve

[PATCH 2/2] bdisp: Fix a possible sleep-in-atomic bug in bdisp_hw_save_request

The driver may sleep under a spinlock. The function call path is: bdisp_device_run (acquire the spinlock) bdisp_hw_update bdisp_hw_save_request devm_kzalloc(GFP_KERNEL) --> may sleep To fix it, GFP_KERNEL is replaced with GFP_ATOMIC. This bug is found by my static analysis tool(DSAC)

[PATCH 1/2] bdisp: Fix a possible sleep-in-atomic bug in bdisp_hw_reset

The driver may sleep under a spinlock. The function call path is: bdisp_device_run (acquire the spinlock) bdisp_hw_reset msleep --> may sleep To fix it, msleep is replaced with mdelay. This bug is found by my static analysis tool(DSAC) and checked by my code review. Signed-off-by: Jia-Ju

Re: [PATCH] spi: s3c64xx: add SPDX identifier

On Tue, Dec 12, 2017 at 2:03 PM, Andi Shyti wrote: > Hi Krzysztof, > >> > - * Copyright (C) 2009 Samsung Electronics Ltd. >> > - * Jaswinder Singh >> > - * >> > - * This program is free software; you can redistribute it and/or modify >> > - * it under the terms of the GNU General Public Licen

[PATCH] drivers: base: power: Fix GFP_KERNEL in spinlock context

From: Shrikant Maurya As reported by Jia-Ju Bai (https://lkml.org/lkml/2017/12/11/872): API's are using GFP_KERNEL to allocate memory which may sleep. To ensure atomicity such allocations must be avoided in critical sections under spinlock. Fixed by replacing GFP_KERNEL to GFP_ATOMIC. Reported-

[PATCHv2] virtio_mmio: fix devm cleanup

Recent rework of the virtio_mmio probe/remove paths balanced a devm_ioremap() with an iounmap() rather than its devm variant. This ends up corrupting the devm datastructures, and results in the following boot-time splat on arm64 under QEMU 2.9.0: [3.450397] [ cut here ]

Re: [PATCH] x86/pti: Add pti= cmdline option and documentation

On 12/12/17 14:39, Borislav Petkov wrote: > From: Borislav Petkov > > Keep the "nopti" for traditional reasons. > > Requested-by: Linus Torvalds > Signed-off-by: Borislav Petkov Reviewed-by: Juergen Gross Juergen

[PATCH 4.14 117/164] drivers/rapidio/devices/rio_mport_cdev.c: fix resource leak in error handling path in rio_dma_transfer()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET [ Upstream commit b1402dcb5643b7a27d46a05edd7491d49ba0e248 ] If 'dma_map_sg()', we should branch to the existing error handling path to free some resources before returning

[PATCH 4.14 119/164] lib/genalloc.c: make the avail variable an atomic_long_t

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Bates [ Upstream commit 36a3d1dd4e16bcd0d2ddfb4a2ec7092f0ae0d931 ] If the amount of resources allocated to a gen_pool exceeds 2^32 then the avail atomic overflows and this causes prob

[PATCH 4.14 116/164] rsi: fix memory leak on buf and usb_reg_buf

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit d35ef8f846c72d84bfccf239c248c84f79c3a7e8 ] In the cases where len is too long, the error return path fails to kfree allocated buffers buf and usb_reg_buf. Th

[PATCH 4.14 105/164] irqchip/qcom: Fix u32 comparison with value less than zero

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King [ Upstream commit e9990d70e8a063a7b894c5cbb99f630a0f41200d ] The comparison of u32 nregs being less than zero is never true since nregs is unsigned. Fix this by making nregs a

[PATCH 4.14 118/164] pipe: match pipe_max_size data type with procfs

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Joe Lawrence [ Upstream commit 98159d977f71c3b3dee898d1c34e56f520b094e7 ] Patch series "A few round_pipe_size() and pipe-max-size fixups", v3. While backporting Michael's "pipe: fix limit ha

[PATCH 4.14 115/164] route: update fnhe_expires for redirect when the fnhe exists

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit e39d5246111399dbc6e11cd39fd8580191b86c47 ] Now when creating fnhe for redirect, it sets fnhe_expires for this new route cache. But when updating the exist one, it d

[PATCH 4.14 074/164] drm/exynos: gem: Drop NONCONTIG flag for buffers allocated without IOMMU

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit 120a264f9c2782682027d931d83dcbd22e01da80 upstream. When no IOMMU is available, all GEM buffers allocated by Exynos DRM driver are contiguous, because of the underlying

[PATCH 4.14 066/164] iwlwifi: mvm: flush queue before deleting ROC

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 6c2d49fdc5d947c5fe89935bd52e69f1f4cb upstream. Before deleting a time event (remain-on-channel instance), flush the queue so that frames cannot get stuck on it. We alr

[PATCH 4.14 072/164] md/r5cache: move mddev_lock() out of r5c_journal_mode_set()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Song Liu commit ff35f58e8f8eb520367879a0ccc6f2ec4b62b17b upstream. r5c_journal_mode_set() is called by r5c_journal_mode_store() and raid_ctr() in dm-raid. We don't need mddev_lock() when calli

[PATCH 4.14 103/164] ARM: BUG if jumping to usermode address in kernel mode

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Russell King commit 8bafae202c82dc257f649ea3c275a0f35ee15113 upstream. Detect if we are returning to usermode via the normal kernel exit paths but the saved PSR value indicates that we are in

[PATCH 4.14 102/164] crypto: talitos - fix ctr-aes-talitos

4.14-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe commit 70d355ccea899dad47dc22d3a4406998f55143fd upstream. ctr-aes-talitos test fails as follows on SEC2 [0.837427] alg: skcipher: Test 1 failed (invalid result) on encryp

[PATCH 4.14 071/164] kdb: Fix handling of kallsyms_symbol_next() return value

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Thompson commit c07d35338081d107e57cf37572d8cc931a8e32e2 upstream. kallsyms_symbol_next() returns a boolean (true on success). Currently kdb_read() tests the return value with an inequa

[PATCH 4.14 096/164] IB/core: Only enforce security for InfiniBand

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Jurgens commit 315d160c5a4e034a576a13aa21e7235d5c9ec609 upstream. For now the only LSM security enforcement mechanism available is specific to InfiniBand. Bypass enforcement for non-IB

[PATCH 4.14 097/164] crypto: talitos - fix AEAD test failures

4.14-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe commit ec8c7d14acc0a477429d3a6fade5dab72c996c82 upstream. AEAD tests fail when destination SG list has more than 1 element. [2.058752] alg: aead: Test 1 failed on encrypt

[PATCH 4.14 100/164] crypto: talitos - fix AEAD for sha224 on non sha224 capable chips

4.14-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe commit 6cda075aff67a1b9b5ba1b2818091dc939643b6c upstream. sha224 AEAD test fails with: [2.803125] talitos ff02.crypto: DEUISR 0x_ [2.808743] talit

Re: [tip:x86/urgent] x86/mm/kmmio: Fix mmiotrace for page unaligned addresses

On Tue, Dec 12, 2017 at 02:55:30AM -0800, tip-bot for Karol Herbst wrote: > Commit-ID: 6d60ce384d1d5ca32b595244db4077a419acc687 > Gitweb: > https://git.kernel.org/tip/6d60ce384d1d5ca32b595244db4077a419acc687 > Author: Karol Herbst > AuthorDate: Mon, 27 Nov 2017 08:51:39 +0100 > Committer

[PATCH 4.14 098/164] crypto: talitos - fix memory corruption on SEC2

4.14-stable review patch. If anyone has any objections, please let me know. -- From: LEROY Christophe commit e04a61bebc5da1535b6f194b464295b8d558e2fc upstream. On SEC2, when using the old descriptors type (hmac snoop no afeu) for doing IPsec, the CICV out pointeur points out o

[PATCH 4.14 069/164] iwlwifi: mvm: enable RX offloading with TKIP and WEP

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Spinadel commit 9d0fc5a50a0548f8e5d61243e5e5f26d5c405aef upstream. Set the flag that indicates that ICV was stripped on if this option was enabled in the HW. [this is needed for the 900

[PATCH 4.14 094/164] bus: arm-ccn: fix module unloading Error: Removing state 147 which has instances left.

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kim Phillips commit b69f63ebf553504739cc8534cbed31bd530c6f0b upstream. Unregistering the driver before calling cpuhp_remove_multi_state() removes any remaining hotplug cpu instances so __cpuhp

[PATCH 4.14 092/164] bus: arm-ccn: Check memory allocation failure

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christophe JAILLET commit 24771179c5c138f0ea3ef88b7972979f62f2d5db upstream. Check memory allocation failures and return -ENOMEM in such cases This avoids a potential NULL pointer dereference

[PATCH 4.14 091/164] bus: arm-cci: Fix use of smp_processor_id() in preemptible context

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 4608af8aa53e7f3922ddee695d023b7bcd5cb35b upstream. The ARM CCI driver seem to be using smp_processor_id() in a preemptible context, which is likely to make a DEBUG_PREMPT k

[PATCH 4.14 086/164] KVM: arm/arm64: vgic-its: Check result of allocation before use

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 686f294f2f1ae40705283dd413ca1e4c14f20f93 upstream. We miss a test against NULL after allocation. Fixes: 6d03a68f8054 ("KVM: arm64: vgic-its: Turn device_id validation into

[PATCH 4.14 087/164] arm64: fpsimd: Prevent registers leaking from dead tasks

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dave Martin commit 071b6d4a5d343046f253a5a8835d477d93992002 upstream. Currently, loading of a task's fpsimd state into the CPU registers is skipped if that task's state is already present in t

[PATCH 4.14 068/164] iwlwifi: mvm: fix packet injection

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit b13f43a48571f0cd0fda271b5046b65f1f268db5 upstream. We need to have a station and a queue for the monitor interface to be able to inject traffic. We used to have this t

[PATCH 4.14 084/164] KVM: arm/arm64: vgic-irqfd: Fix MSI entry allocation

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 150009e2c70cc3c6e97f00e7595055765d32fb85 upstream. Using the size of the structure we're allocating is a good idea and avoids any surprise... In this case, we're happilly c

[PATCH 4.14 083/164] KVM: arm/arm64: Fix broken GICH_ELRSR big endian conversion

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christoffer Dall commit fc396e066318c0a02208c1d3f0b62950a7714999 upstream. We are incorrectly rearranging 32-bit words inside a 64-bit typed value for big endian systems, which would result in

[PATCH 4.14 078/164] media: rc: sir_ir: detect presence of port

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sean Young commit 30b4e122d71cbec2944a5f8b558b88936ee42f10 upstream. Without this test, sir_ir clumsy claims resources for a device which does not exist. The 0-day kernel test robot reports t

[PATCH 4.14 081/164] arm: KVM: Fix VTTBR_BADDR_MASK BUG_ON off-by-one

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 5553b142be11e794ebc0805950b2e8313f93d718 upstream. VTTBR_BADDR_MASK is used to sanity check the size and alignment of the VTTBR address. It seems to currently be off by one

[PATCH 4.14 080/164] arm64: KVM: fix VTTBR_BADDR_MASK BUG_ON off-by-one

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kristina Martsenko commit 26aa7b3b1c0fb3f1a6176a0c1847204ef4355693 upstream. VTTBR_BADDR_MASK is used to sanity check the size and alignment of the VTTBR address. It seems to currently be off

[PATCH 4.14 035/164] scsi: dma-mapping: always provide dma_get_cache_alignment

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 860dd4424f344400b491b212ee4acb3a358ba9d9 upstream. Provide the dummy version of dma_get_cache_alignment that always returns 1 even if CONFIG_HAS_DMA is not set, so tha

[PATCH 4.14 077/164] media: dvb: i2c transfers over usb cannot be done from stack

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Laurent Caumont commit 6d33377f2abbf9f0e561b116dd468d1c3ff36a6a upstream. Signed-off-by: Laurent Caumont Signed-off-by: Sean Young Signed-off-by: Mauro Carvalho Chehab Signed-off-by: Greg K

[PATCH 4.14 036/164] scsi: use dma_get_cache_alignment() as minimum DMA alignment

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen commit 90addc6b3c9cda0146fbd62a08e234c2b224a80c upstream. In non-coherent DMA mode, kernel uses cache flushing operations to maintain I/O coherency, so scsi's block queue should be

[PATCH 4.14 028/164] Drivers: hv: vmbus: Fix a rescind issue

4.14-stable review patch. If anyone has any objections, please let me know. -- From: K. Y. Srinivasan commit 7fa32e5ec28b1609abc0b797b58267f725fc3964 upstream. The current rescind processing code will not correctly handle the case where the host immediately rescinds a channel

[PATCH 4.14 076/164] drm: safely free connectors from connector_iter

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit a703c55004e1c5076d57e43771b3e7796ea0 upstream. In commit 613051dac40da1751ab269572766d3348d45a197 Author: Daniel Vetter Date: Wed Dec 14 00:08:06 2016 +0100 d

[PATCH 4.14 037/164] scsi: libsas: align sata_devices rps_resp on a cacheline

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Huacai Chen commit c2e8fbf908afd81ad502b567a6639598f92c9b9d upstream. The rps_resp buffer in ata_device is a DMA target, but it isn't explicitly cacheline aligned. Due to this, adjacent fields

[PATCH 4.14 033/164] firmware: vpd: Fix platform driver and device registration/unregistration

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 0631fb8b027f5968c2f5031f0b3ff7be3e4bebcc upstream. The driver exit function needs to unregister both platform device and driver. Also, during registration, register driver

[PATCH 4.14 065/164] iwlwifi: mvm: dont use transmit queue hang detection when it is not possible

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 0b9832b712d6767d6c7b01965fd788d1ca84fc92 upstream. When we act as an AP, new firmware versions handle internally the power saving clients and the driver doesn't know t

[PATCH 4.14 063/164] powerpc/64s: Initialize ISAv3 MMU registers before setting partition table

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit 371b80447ff33ddac392c189cf884a5a3e18faeb upstream. kexec can leave MMU registers set when booting into a new kernel, the PIDR (Process Identification Register) in partic

[PATCH 4.14 061/164] KVM: s390: Fix skey emulation permission check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Janosch Frank commit ca76ec9ca871e67d8cd0b6caba24aca3d3ac4546 upstream. All skey functions call skey_check_enable at their start, which checks if we are in the PSTATE and injects a privileged

[PATCHv6 1/4] x86/boot/compressed/64: Rename pagetable.c to kaslr_64.c

The name of the file -- pagetable.c -- is misleading: it only contains helpers used for KASLR in 64-bit mode. Let's rename the file to reflect its content. Signed-off-by: Kirill A. Shutemov --- arch/x86/boot/compressed/Makefile| 2 +- arch/x86/boot/compressed/{pagetable.c =>

[PATCHv6 3/4] x86/boot/compressed/64: Prepare trampoline memory

If a bootloader enables 64-bit mode with 4-level paging, we might need to switch over to 5-level paging. The switching requires the disabling paging. It works fine if kernel itself is loaded below 4G. But if the bootloader put the kernel above 4G (not sure if anybody does this), we would lose cont

[PATCHv6 4/4] x86/boot/compressed/64: Handle 5-level paging boot if kernel is above 4G

This patch addresses a shortcoming in current boot process on machines that supports 5-level paging. If a bootloader enables 64-bit mode with 4-level paging, we might need to switch over to 5-level paging. The switching requires the disabling paging. It works fine if kernel itself is loaded below

[PATCH 4.14 031/164] firmware: vpd: Destroy vpd sections in remove function

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 811d7e0215fb738fb9a9f0bcb1276516ad161ed1 upstream. vpd sections are initialized during probe and thus should be destroyed in the remove function. Fixes: 049a59db34eb ("fi

[PATCH 4.14 059/164] s390/mm: fix off-by-one bug in 5-level page table handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens commit 8d306f53b63099fec2d56300149e400d181ba4f5 upstream. Martin Cermak reported that setting a uprobe doesn't work. Reason for this is that the common uprobes code tries to get

[PATCHv6 0/4] x86: 5-level related changes into decompression code

Here's few changes to x86 decompression code. The first patch is pure cosmetic change: it gives file with KASLR helpers a proper name. The last three patches bring support of booting into 5-level paging mode if a bootloader put the kernel above 4G. Patch 2/4 Renames l5_paging_required() into pag

[PATCH 4.14 058/164] s390: always save and restore all registers on context switch

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Carstens commit fbbd7f1a51965b50dd12924841da0d478f3da71b upstream. The switch_to() macro has an optimization to avoid saving and restoring register contents that aren't needed for kernel

[PATCHv6 2/4] x86/boot/compressed/64: Introduce paging_prepare()

This patch renames l5_paging_required() into paging_prepare() and changes the interface of the function. This is a preparation for the next patch, which would make the function also allocate memory for the 32-bit trampoline. The function now returns a 128-bit structure. RAX would return trampolin

[PATCH 4.14 056/164] iommu/vt-d: Fix scatterlist offset handling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Robin Murphy commit 29a90b70893817e2f2bb3cea40a29f5308e21b21 upstream. The intel-iommu DMA ops fail to correctly handle scatterlists where sg->offset is greater than PAGE_SIZE - the IOVA alloc

Re: AF_ALG: skb limits

On Fri, 8 Dec 2017 13:43:20 +0100 Stephan Mueller wrote: > Am Freitag, 8. Dezember 2017, 12:39:06 CET schrieb Jonathan Cameron: > > Hi Jonathan, > > > > > As a heads up, the other nasties we've found so far are around hitting > > limits on the various socket buffers. When you run into those y

[PATCH 4.14 054/164] ALSA: usb-audio: Fix out-of-bound error

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jaejoong Kim commit 251552a2b0d454badc8f486e6d79100970c744b0 upstream. The snd_usb_copy_string_desc() retrieves the usb string corresponding to the index number through the usb_string(). The p

Re: [PATCH] KVM: X86: Reduce the overhead when lapic_timer_advance is disabled

On 01/12/2017 09:15, Wanpeng Li wrote: > When I run ebizzy in a 32 vCPUs guest on a 32 pCPUs Xeon box, I can observe > ~8000 kvm_wait_lapic_expire CurAvg/s through kvm_stat tool even if the > advance > tscdeadline hrtimer expiration is disabled. Each call to wait_lapic_expire() > will consume ~

Re: mmots test error: WARNING in __wake_up_common

On Fri, Dec 8, 2017 at 7:05 PM, Dmitry Vyukov wrote: > On Fri, Dec 1, 2017 at 6:05 PM, Christoph Hellwig wrote: >> Ok, more epoll fun. We already have a discussion on it on lkml.. > > Need to tell the bot what fixed it: > > #syz fix: epoll: use proper wake_up variant in ep_poll_callback The rig

[PATCH 4.14 051/164] ALSA: hda/realtek - New codec support for ALC257

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit f429e7e494afaded76e62c6f98211a635aa03098 upstream. Add new support for ALC257 codec. [ It's supposed to be almost equivalent with other ALC25x variants, just adding anot

[PATCH 4.14 049/164] btrfs: fix missing error return in btrfs_drop_snapshot

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Mahoney commit e19182c0fff451e3744c1107d98f072e7ca377a0 upstream. If btrfs_del_root fails in btrfs_drop_snapshot, we'll pick up the error but then return 0 anyway due to mixing err and re

[PATCH 4.14 030/164] firmware: cleanup FIRMWARE_IN_KERNEL message

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Robin H. Johnson commit 0946b2fb38fdb6585a5ac3ca84ac73924f645952 upstream. The help for FIRMWARE_IN_KERNEL still references the firmware_install command that was recently removed by commit 562

[PATCH 4.14 053/164] ALSA: seq: Remove spurious WARN_ON() at timer check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 43a3542870328601be02fcc9d27b09db467336ef upstream. The use of snd_BUG_ON() in ALSA sequencer timer may lead to a spurious WARN_ON() when a slave timer is deployed as its ba

[PATCH 4.14 047/164] x86/PCI: Make broadcom_postcore_init() check acpi_disabled

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit ddec3bdee05b06f1dda20ded003c3e10e4184cab upstream. acpi_os_get_root_pointer() may return a valid address even if acpi_disabled is set, but the host bridge information

[PATCH 4.14 044/164] X.509: reject invalid BIT STRING for subjectPublicKey

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 0f30cbea005bd3077bd98cd29277d7fc2699c1da upstream. Adding a specially crafted X.509 certificate whose subjectPublicKey ASN.1 value is zero-length caused x509_extract_key_da

Re: [PATCH 1/2] KVM: MMU: Fix infinite loop when there is no available mmu page

On 05/12/2017 07:21, Wanpeng Li wrote: > From: Wanpeng Li > > The below test case can cause infinite loop in kvm when ept=0. > > #include > #include > #include > #include > #include > #include > #include > > long r[5]; > int main() > { >

[PATCH 4.14 043/164] KEYS: reject NULL restriction string when type is specified

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 18026d866801d0c52e5550210563222bd6c7191d upstream. keyctl_restrict_keyring() allows through a NULL restriction when the "type" is non-NULL, which causes a NULL pointer dere

[PATCH 4.14 042/164] KEYS: add missing permission check for request_key() destination

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 4dca6ea1d9432052afb06baf2e3ae78188a4410b upstream. When the request_key() syscall is not passed a destination keyring, it links the requested key (if constructed) into the

[PATCH 4.14 041/164] ASN.1: check for error from ASN1_OP_END__ACT actions

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 81a7be2cd69b412ab6aeacfe5ebf1bb6e5bce955 upstream. asn1_ber_decoder() was ignoring errors from actions associated with the opcodes ASN1_OP_END_SEQ_ACT, ASN1_OP_END_SET_ACT,

Re: [tip:x86/urgent] x86/mm/kmmio: Fix mmiotrace for page unaligned addresses

* Peter Zijlstra wrote: > On Tue, Dec 12, 2017 at 02:55:30AM -0800, tip-bot for Karol Herbst wrote: > > Commit-ID: 6d60ce384d1d5ca32b595244db4077a419acc687 > > Gitweb: > > https://git.kernel.org/tip/6d60ce384d1d5ca32b595244db4077a419acc687 > > Author: Karol Herbst > > AuthorDate: Mon,

Re: [PATCH V3 09/29] drm/i915: deprecate pci_get_bus_and_slot()

Hi, I sent this individual i915 patch to our CI, and it is passing on all platforms: https://patchwork.freedesktop.org/series/34822/ Is it ok if I merge this to drm-tip already? Regards, Joonas On Mon, 2017-11-27 at 13:50 -0500, Sinan Kaya wrote: > +dri-de...@lists.freedesktop.org > > On 11/2

[PATCH 4.14 040/164] ASN.1: fix out-of-bounds read when parsing indefinite length item

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit e0058f3a874ebb48b25be7ff79bc3b4e59929f90 upstream. In asn1_ber_decoder(), indefinitely-sized ASN.1 items were being passed to the action functions before their lengths had

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