Re: [Xen-devel] xen: Can't insert balloon page into VM userspace (WAS Re: [linux-linus bisection] complete test-arm64-arm64-xl-xsm)

On 12/03/2019 17:18, David Hildenbrand wrote: > On 12.03.19 18:14, Matthew Wilcox wrote: >> On Tue, Mar 12, 2019 at 05:05:39PM +, Julien Grall wrote: >>> On 3/12/19 3:59 PM, Julien Grall wrote: It looks like all the arm test for linus [1] and next [2] tree are now failing. x86 seems

[PATCH 4.14 037/135] MIPS: irq: Allocate accurate order pages for irq stack

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Liu Xiang commit 72faa7a773ca59336f3c889e878de81445c5a85c upstream. The irq_pages is the number of pages for irq stack, but not the order which is needed by __get_free_pages(). We can use

[PATCH 4.14 038/135] hugetlbfs: fix races and page leaks during migration

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Mike Kravetz commit cb6acd01e2e43fd8bad11155752b7699c3d0fb76 upstream. hugetlb pages should only be migrated if they are 'active'. The routines set/clear_page_huge_active() modify the active

[PATCH 4.19 101/149] dmaengine: dmatest: Abort test in case of mapping error

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6454368a804c4955ccd116236037536f81e5b1f1 ] In case of mapping error the DMA addresses are invalid and continuing will screw system memory or potentially something else. [

[PATCH 4.14 039/135] xtensa: fix get_wchan

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit d90b88fd3653f1fb66ecc6571b860d5a5749fa56 upstream. Stack unwinding is implemented incorrectly in xtensa get_wchan: instead of extracting a0 and a1 registers from the spill

[PATCH 4.14 064/135] gpio: vf610: Mask all GPIO interrupts

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7ae710f9f8b2cf95297e7bbfe1c09789a7dc43d4 ] On SoC reset all GPIO interrupts are disable. However, if kexec is used to boot into a new kernel, the SoC does not experience a reset.

[PATCH 4.19 107/149] s390/qeth: cancel close_dev work before removing a card

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c2780c1a3fb724560b1d44f7976e0de17bf153c7 ] A card's close_dev work is scheduled on a driver-wide workqueue. If the card is removed and freed while the work is still active, this

[PATCH] ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate

After commit fbeec965b8d1c ("ASoC: samsung: odroid: Fix 32000 sample rate handling") the audio root clock frequency is configured improperly for 44100 sample rate. Due to clock rate rounding it's 20070401 Hz instead of 22579000 Hz. This results in a too low value of the PSR clock divider in the

[PATCH 4.14 035/135] x86/CPU/AMD: Set the CPB bit unconditionally on F17h

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jiaxun Yang commit 0237199186e7a4aa5310741f0a6498a20c820fd7 upstream. Some F17h models do not have CPB set in CPUID even though the CPU supports it. Set the feature bit unconditionally on all

[PATCH 4.14 063/135] netfilter: ebtables: compat: un-break 32bit setsockopt when no rules are present

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2035f3ff8eaa29cfb5c8e2160b0f6e85eeb21a95 ] Unlike ip(6)tables ebtables only counts user-defined chains. The effect is that a 32bit ebtables binary on a 64bit kernel can do

Re: [PATCH 02/25] leds: core: Add support for composing LED class device names

On 3/10/19 1:28 PM, Jacek Anaszewski wrote: > Add public led_compose_name() API for composing LED class device > name basing on fwnode_handle data. The function composes device name > according to either a new pattern or the legacy > pattern. The decision on using the > particular pattern is

[PATCH 4.14 061/135] net: hns: Fix wrong read accesses via Clause 45 MDIO protocol

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cec8abba13e6a26729dfed41019720068eeeff2b ] When reading phy registers via Clause 45 MDIO protocol, after write address operation, the driver use another write address operation, so

[PATCH 4.14 044/135] vti4: Fix a ipip packet processing bug in IPCOMP virtual tunnel

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dd9ee3444014e8f28c0eefc9fffc9ac9c5248c12 ] Recently we run a network test over ipcomp virtual tunnel.We find that if a ipv4 packet needs fragment, then the peer can't receive it.

[PATCH 4.14 042/135] scsi: core: reset host byte in DID_NEXUS_FAILURE case

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Martin Wilck commit 4a067cf823d9d8e50d41cfb618011c0d4a969c72 upstream. Up to 4.12, __scsi_error_from_host_byte() would reset the host byte to DID_OK for various cases including

[PATCH 4.19 103/149] selftests: netfilter: add simple masq/redirect test cases

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 98bfc3414bda335dbd7fec58bde6266f991801d7 ] Check basic nat/redirect/masquerade for ipv4 and ipv6. Signed-off-by: Florian Westphal Signed-off-by: Pablo Neira Ayuso Signed-off-by:

[PATCH 4.14 065/135] selftests: timers: use LDLIBS instead of LDFLAGS

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7d4e591bc051d3382c45caaa2530969fb42ed23d ] posix_timers fails to build due to undefined reference errors: aarch64-linaro-linux-gcc --sysroot=/build/tmp-rpb-glibc/sysroots/hikey

[PATCH 4.14 066/135] nfs: Fix NULL pointer dereference of dev_name

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 80ff00172407e0aad4b10b94ef0816fc3e7813cb ] There is a NULL pointer dereference of dev_name in nfs_parse_devname() The oops looks something like: BUG: unable to handle kernel

[PATCH 4.19 140/149] staging: erofs: fix memleak of inodes shared xattr array

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Gao Xiang From: Sheng Yong commit 3b1b5291f79d040d549d7c746669fc30e8045b9b upstream. If it fails to read a shared xattr page, the inode's shared xattr array is not freed. The next time the

[PATCH 4.14 053/135] selftests: cpu-hotplug: fix case where CPUs offline > CPUs present

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b531b6137834a55857a337ac17510d6436b6fbb ] The cpu-hotplug test assumes that we can offline the maximum CPU as described by /sys/devices/system/cpu/offline. However, in the case

[PATCH 4.14 055/135] xtensa: smp_lx200_defconfig: fix vectors clash

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 306b38305c0f86de7f17c5b091a95451dcc93d7d ] Secondary CPU reset vector overlaps part of the double exception handler code, resulting in weird crashes and hangups when running user

[PATCH 4.14 067/135] qed: Fix bug in tx promiscuous mode settings

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9e71a15d8b5bbce25c637f7f8833cd3f45b65646 ] When running tx switched traffic between VNICs created via a bridge(to which VFs are added), adapter drops the unicast packets in tx flow

Re: xen: Can't insert balloon page into VM userspace (WAS Re: [Xen-devel] [linux-linus bisection] complete test-arm64-arm64-xl-xsm)

Hi David, On 3/12/19 5:18 PM, David Hildenbrand wrote: On 12.03.19 18:14, Matthew Wilcox wrote: On Tue, Mar 12, 2019 at 05:05:39PM +, Julien Grall wrote: On 3/12/19 3:59 PM, Julien Grall wrote: It looks like all the arm test for linus [1] and next [2] tree are now failing. x86 seems to

[PATCH 4.14 059/135] net: hns: Fix for missing of_node_put() after of_parse_phandle()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 263c6d75f9a544a3c2f8f6a26de4f4808d8f59cf ] In hns enet driver, we use of_parse_handle() to get hold of the device node related to "ae-handle" but we have missed to put the node

[PATCH 4.19 136/149] netfilter: xt_TEE: add missing code to get interface index in checkentry.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 18c0ab87364ac5128a152055fdcb1d27e01caf01 ] checkentry(tee_tg_check) should initialize priv->oif from dev if possible. But only netdevice notifier handler can set that. Hence

[PATCH 4.19 143/149] cifs: allow calling SMB2_xxx_free(NULL)

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ronnie Sahlberg commit 32a1fb36f6e50183871c2c1fcf5493c633e84732 upstream. Change these free functions to allow passing NULL as the argument and treat it as a no-op just like free(NULL) would.

[PATCH 4.14 070/135] qed: Fix system crash in ll2 xmit

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7c81626a3c37e4ac320b8ad785694ba498f24794 ] Cache number of fragments in the skb locally as in case of linear skb (with zero fragments), tx completion (or freeing of skb) may happen

[PATCH 4.19 144/149] ath9k: Avoid OF no-EEPROM quirks without qca,no-eeprom

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Daniel F. Dickinson commit ce938231bd3b1d7af3cbd8836f084801090470e1 upstream. ath9k_of_init() function[0] was initially written on the assumption that if someone had an explicit ath9k OF node

[PATCH 4.14 080/135] x86_64: increase stack size for KASAN_EXTRA

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a8e911d13540487942d53137c156bd7707f66e5d ] If the kernel is configured with KASAN_EXTRA, the stack size is increasted significantly because this option sets "-fstack-reuse" to

[PATCH 4.14 051/135] iommu/amd: Fix IOMMU page flush when detach device from a domain

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9825bd94e3a2baae1f4874767ae3a7d4c049720e ] When a VM is terminated, the VFIO driver detaches all pass-through devices from VFIO domain by clearing domain id and page table root

[PATCH 4.14 072/135] scsi: libfc: free skb when receiving invalid flogi resp

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5d8fc4a9f0eec20b6c07895022a6bea3fb6dfb38 ] The issue to be fixed in this commit is when libfc found it received a invalid FLOGI response from FC switch, it would return without

[PATCH 4.14 083/135] lib/test_kmod.c: potential double free in error handling

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit db7ddeab3ce5d64c9696e70d61f45ea9909cd196 ] There is a copy and paste bug so we set "config->test_driver" to NULL twice instead of setting "config->test_fs". Smatch complains that

[PATCH 4.19 127/149] x86/PCI: Fixup RTIT_BAR of Intel Denverton Trace Hub

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit 2e095ce7b6ecce2f3e2ff330527f12056ed1e1a1 upstream. On Denverton's integration of the Intel(R) Trace Hub (for a reference and overview see

[PATCH 4.14 086/135] autofs: fix error return in autofs_fill_super()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f585b283e3f025754c45bbe7533fc6e5c4643700 ] In autofs_fill_super() on error of get inode/make root dentry the return should be ENOMEM as this is the only failure case of the called

[PATCH 4.14 081/135] mm, memory_hotplug: is_mem_section_removable do not pass the end of a zone

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit efad4e475c312456edb3c789d0996d12ed744c13 ] Patch series "mm, memory_hotplug: fix uninitialized pages fallouts", v2. Mikhail Zaslonko has posted fixes for the two bugs quite some

[PATCH 4.19 126/149] scsi: aacraid: Fix missing break in switch statement

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 5e420fe635813e5746b296cfc8fff4853ae205a2 upstream. Add missing break statement and fix identation issue. This bug was found thanks to the ongoing efforts to enable

[PATCH 4.14 073/135] scsi: 53c700: pass correct "dev" to dma_alloc_attrs()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8437fcf14deed67e5ad90b5e8abf62fb20f30881 ] The "hostdata->dev" pointer is NULL here. We set "hostdata->dev = dev;" later in the function and we also use "hostdata->dev" when we

[PATCH 4.19 130/149] arm64: dts: hikey: Revert "Enable HS200 mode on eMMC"

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Alistair Strachan commit 8d26c1390aec795d492b8de5e4437751e8805a1d upstream. This reverts commit abd7d0972a192ee653efc7b151a6af69db58f2bb. This change was already partially reverted by John

[PATCH 4.14 097/135] net: stmmac: Send TSO packets always from Queue 0

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c5acdbee22a1b200dde07effd26fd1f649e9ab8a ] The number of TSO enabled channels in HW can be different than the number of total channels. There is no way to determined, at runtime,

[PATCH 4.14 075/135] cifs: fix computation for MAX_SMB2_HDR_SIZE

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 58d15ed1203f4d858c339ea4d7dafa94bd2a56d3 ] The size of the fixed part of the create response is 88 bytes not 56. Signed-off-by: Ronnie Sahlberg Signed-off-by: Steve French

[PATCH 4.14 074/135] platform/x86: Fix unmet dependency warning for SAMSUNG_Q10

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0ee4b5f801b73b83a9fb3921d725f2162fd4a2e5 ] Add BACKLIGHT_LCD_SUPPORT for SAMSUNG_Q10 to fix the warning: unmet direct dependencies detected for BACKLIGHT_CLASS_DEVICE. SAMSUNG_Q10

[PATCH 4.14 095/135] irqchip/mmp: Only touch the PJ4 IRQ & FIQ bits on enable/disable

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2380a22b60ce6f995eac806e69c66e397b59d045 ] Resetting bit 4 disables the interrupt delivery to the "secure processor" core. This breaks the keyboard on a OLPC XO 1.75 laptop, where

[PATCH 4.14 077/135] arm64: kprobe: Always blacklist the KVM world-switch code

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f2b3d8566d81deaca31f4e3163def0bea7746e11 ] On systems with VHE the kernel and KVM's world-switch code run at the same exception level. Code that is only used on a VHE system does

[PATCH 4.14 089/135] soc: fsl: qbman: avoid race in clearing QMan interrupt

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 89857a8a5c89a406b967ab2be7bd2ccdbe75e73d ] By clearing all interrupt sources, not only those that already occurred, the existing code may acknowledge by mistake interrupts that

Re: [PATCH 1/4] drm: Add helpers for locking an array of BO reservations.

Rob Herring writes: > On Fri, Mar 8, 2019 at 10:17 AM Eric Anholt wrote: >> >> Now that we have the reservation object in the GEM object, it's easy >> to provide a helper for this common case. Noticed while reviewing >> panfrost and lima drivers. This particular version came out of v3d, >>

[PATCH 4.19 149/149] perf/x86/intel: Implement support for TSX Force Abort

4.19-stable review patch. If anyone has any objections, please let me know. -- From: "Peter Zijlstra (Intel)" commit 400816f60c543153656ac74eaf7f36f6b7202378 upstream Skylake (and later) will receive a microcode update to address a TSX errata. This microcode will, on

[PATCH 4.14 069/135] qed: Fix VF probe failure while FLR

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 327852ec64205bb651be391a069784872098a3b2 ] VFs may hit VF-PF channel timeout while probing, as in some cases it was observed that VF FLR and VF "acquire" message transaction (i.e

[PATCH 4.14 100/135] relay: check return of create_buf_file() properly

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2c1cf00eeacb784781cf1c9896b8af001246d339 ] If create_buf_file() returns an error, don't try to reference it later as a valid dentry pointer. This problem was exposed when debugfs

[PATCH 4.14 098/135] net: stmmac: Disable EEE mode earlier in XMIT callback

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e2cd682deb231ba6f80524bb84e57e7138261149 ] In stmmac xmit callback we use a different flow for TSO packets but TSO xmit callback is not disabling the EEE mode. Fix this by

[PATCH 4.14 102/135] bpf: fix lockdep false positive in percpu_freelist

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a89fac57b5d080771efd4d71feaae19877cf68f0 ] Lockdep warns about false positive: [ 12.492084] e6b28347 (>lock){+...}, at: pcpu_freelist_push+0x2a/0x40 [ 12.492696] but

[PATCH 4.14 012/135] team: Free BPF filter when unregistering netdev

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit 692c31bd4054212312396b1d303bffab2c5b93a7 ] When team is used in loadbalance mode a BPF filter can be used to provide a hash which will determine the Tx port.

[PATCH 4.14 105/135] vsock/virtio: fix kernel panic after device hot-unplug

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 22b5c0b63f32568e130fa2df4ba23efce3eb495b ] virtio_vsock_remove() invokes the vsock_core_exit() also if there are opened sockets for the AF_VSOCK protocol family. In this way the

[PATCH 4.14 003/135] USB: serial: cp210x: add ID for Ingenico 3070

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ivan Mironov commit dd9d3d86b08d6a106830364879c42c78db85389c upstream. Here is how this device appears in kernel log: usb 3-1: new full-speed USB device number 18 using xhci_hcd

[PATCH 4.14 104/135] dmaengine: at_xdmac: Fix wrongfull report of a channel as in use

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dc3f595b6617ebc0307e0ce151e8f2f2b2489b95 ] atchan->status variable is used to store two different information: - pass channel interrupts status from interrupt handler to tasklet;

[PATCH 4.14 099/135] irqchip/gic-v3-its: Fix ITT_entry_size accessor

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 56841070ccc87b463ac037d2d1f2beb8e5e35f0c ] According to ARM IHI 0069C (ID070116), we should use GITS_TYPER's bits [7:4] as ITT_entry_size instead of [8:4]. Although this is pretty

[PATCH 4.14 001/135] cpufreq: Use struct kobj_attribute instead of struct global_attr

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Viresh Kumar commit 625c85a62cb7d3c79f6e16de3cfa972033658250 upstream. The cpufreq_global_kobject is created using kobject_create_and_add() helper, which assigns the kobj_type as

[PATCH 4.14 101/135] bpf, selftests: fix handling of sparse CPU allocations

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1bb54c4071f585ebef56ce8fdfe6026fa2cbcddd ] Previously, bpf_num_possible_cpus() had a bug when calculating a number of possible CPUs in the case of sparse CPU allocations, as it was

[PATCH 4.14 092/135] arm64: dts: add msm8996 compatible to gicv3

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2a81efb0de0e33f2d2c83154af0bd3ce389b3269 ] Add compatible to gicv3 node to enable quirk required to restrict writing to GICR_WAKER register which is restricted on msm8996 SoC in

[PATCH 4.14 093/135] DTS: CI20: Fix bugs in ci20s device tree.

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1ca1c87f91d9dc50d6a38e2177b2032996e7901c ] According to the Schematic, the hardware of ci20 leads to uart3, but not to uart2. Uart2 is miswritten in the original code.

[PATCH 4.14 011/135] sky2: Disable MSI on Dell Inspiron 1545 and Gateway P-79

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng [ Upstream commit b33b7cd6fd86478dd2890a9abeb6f036aa01fdf7 ] Some sky2 chips fire IRQ after S3, before the driver is fully resumed: [ 686.804877] do_IRQ: 1.37 No irq handler for

[PATCH 4.14 013/135] tipc: fix RDM/DGRAM connect() regression

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Erik Hugne [ Upstream commit 0e63208915a8d7590d0a6218dadb2a6a00ac705a ] Fix regression bug introduced in commit 365ad353c256 ("tipc: reduce risk of user starvation during link congestion")

[PATCH 4.14 009/135] net: dsa: mv88e6xxx: handle unknown duplex modes gracefully in mv88e6xxx_port_set_duplex

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heiner Kallweit [ Upstream commit c6195a8bdfc62a7cecf7df685e64847a4b700275 ] When testing another issue I faced the problem that mv88e6xxx_port_setup_mac() failed due to DUPLEX_UNKNOWN being

[PATCH 4.14 006/135] staging: wilc1000: fix to set correct value for vif_num

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ajay Singh commit dda037057a572f5c82ac2499eb4e6fb17600ba3e upstream. Set correct value in '->vif_num' for the total number of interfaces and set '->idx' value using 'i'. Fixes: 735bb39ca3be

[PATCH 4.14 008/135] ip6mr: Do not call __IP6_INC_STATS() from preemptible context

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit 87c11f1ddbbad38ad8bad47af133a8208985fbdf ] Similar to commit 44f49dd8b5a6 ("ipmr: fix possible race resulting from improper usage of IP_INC_STATS_BH() in

[PATCH 4.14 096/135] net: stmmac: Fallback to Platform Data clock in Watchdog conversion

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4ec5302fa906ec9d86597b236f62315bacdb9622 ] If we don't have DT then stmmac_clk will not be available. Let's add a new Platform Data field so that we can specify the refclk by this

[PATCH 4.14 107/135] dmaengine: dmatest: Abort test in case of mapping error

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6454368a804c4955ccd116236037536f81e5b1f1 ] In case of mapping error the DMA addresses are invalid and continuing will screw system memory or potentially something else. [

[PATCH 4.14 119/135] qed: Consider TX tcs while deriving the max num_queues for PF.

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fb1faab74ddef9ec2d841d54e5d0912a097b3abe ] Max supported queues is derived incorrectly in the case of multi-CoS. Need to consider TCs while calculating num_queues for PF.

[PATCH 4.14 117/135] fs: ratelimit __find_get_block_slow() failure message.

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 43636c804df0126da669c261fc820fb22f62bfc2 ] When something let __find_get_block_slow() hit all_mapped path, it calls printk() for 100+ times per a second. But there is no need to

[PATCH 4.14 121/135] Input: elan_i2c - add id for touchpad found in Lenovo s21e-20

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Vincent Batts commit e154ab69321ce2c54f19863d75c77b4e2dc9d365 upstream. Lenovo s21e-20 uses ELAN0601 in its ACPI tables for the Elan touchpad. Signed-off-by: Vincent Batts Cc:

Re: [RFC PATCH v1] PCI: qcom: Use quirk to override incorrect device class

On 12/03/2019 18:18, Marc Gonzalez wrote: > On 12/03/2019 13:42, Stanimir Varbanov wrote: > >> I wonder, in case that dw_pcie_setup_rc() already has a write to >> PCI_CLASS_DEVICE configuration register to set it as a bridge do we >> still need to do the above fixup? > > I don't know, I don't

[PATCH 4.14 118/135] qed: Fix EQ full firmware assert.

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 660492bcf4a7561b5fdc13be0ae0b0c0a8c120be ] When slowpath messages are sent with high rate, the resulting events can lead to a FW assert in case they are not handled fast enough

[PATCH 4.14 032/135] tun: remove unnecessary memory barrier

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Timur Celik [ Upstream commit ecef67cb10db7b83b3b71c61dbb29aa070ab0112 ] Replace set_current_state with __set_current_state since no memory barrier is needed at this point. Signed-off-by:

[PATCH 4.14 123/135] scsi: aacraid: Fix missing break in switch statement

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 5e420fe635813e5746b296cfc8fff4853ae205a2 upstream. Add missing break statement and fix identation issue. This bug was found thanks to the ongoing efforts to enable

[PATCH 4.14 033/135] net: phy: Micrel KSZ8061: link failure after cable connect

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Rajasingh Thavamani [ Upstream commit 232ba3a51cc224b339c7114888ed7f0d4d95695e ] With Micrel KSZ8061 PHY, the link may occasionally not come up after Ethernet cable connect. The vendor's

[PATCH 4.14 120/135] Input: wacom_serial4 - add support for Wacom ArtPad II tablet

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gerecke commit 44fc95e218a09d7966a9d448941fdb003f6bb69f upstream. Tablet initially begins communicating at 9600 baud, so this command should be used to connect to the device: $

Re: [PATCH v2 2/2] mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning

Hi Adrian, On 3/6/2019 5:39 PM, Adrian Hunter wrote: > On 1/03/19 10:38 AM, Faiz Abbas wrote: >> commit 5b0d62108b46 ("mmc: sdhci-omap: Add platform specific reset >> callback") skips data resets during tuning operation. Because of this, >> a data error or data finish interrupt might still arrive

[PATCH 4.14 122/135] iscsi_ibft: Fix missing break in switch statement

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit df997abeebadaa4824271009e2d2b526a70a11cb upstream. Add missing break statement in order to prevent the code from falling through to case ISCSI_BOOT_TGT_NAME, which

[PATCH 1/4] irqchip/gic-v3-its: fix comparison logic in lpi_range_cmp

The lpi_range_list is supposed to be sorted in ascending order of ->base_id (at least if the range merging is to work), but the current comparison function returns a positive value if rb->base_id > ra->base_id, which means that list_sort() will put A after B in that case - and vice versa, of

[PATCH 2/4] irqchip/gic-v3-its: move allocation outside mutex

There's no reason to do the allocation of the new lpi_range inside the lpi_range_lock. One could change the code to avoid the allocation altogether in case the freed range can be merged with one or two existing ranges (in which case the allocation would naturally be done under the lock), but it's

[PATCH 4.14 124/135] arm64: dts: hikey: Give wifi some time after power-on

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kiszka commit 83b944174ad79825ae84a47af1a0354485b24602 upstream. Somewhere along recent changes to power control of the wl1835, power-on became very unreliable on the hikey, failing like

[PATCH 3/4] irqchip/gic-v3-its: drop redundant initialization in mk_lpi_range

There's no reason to ask kmalloc() to zero the allocation, since all the fields get initialized immediately afterwards. Except that there's also not any reason to initialize the ->entry member, since the element gets added to the lpi_range_list immediately. Signed-off-by: Rasmus Villemoes ---

[PATCH 4.14 108/135] selftests: netfilter: fix config fragment CONFIG_NF_TABLES_INET

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 952b72f89ae23b316da8c1021b18d0c388ad6cc4 ] In selftests the config fragment for netfilter was added as NF_TABLES_INET=y and this patch correct it as CONFIG_NF_TABLES_INET=y

[PATCH 4.14 023/135] net: socket: set sock->sk to NULL after calling proto_ops::release()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers [ Upstream commit ff7b11aa481f682e0e9711abfeb7d03f5cd612bf ] Commit 9060cb719e61 ("net: crypto set sk to NULL when af_alg_release.") fixed a use-after-free in sockfs_setattr()

[PATCH 4/4] irqchip/gic-v3-its: make free_lpi_range a little cheaper

Using list_add + list_sort to insert an element and keeping the list sorted is a somewhat blunt instrument; one can find the right place to insert in fewer lines of code than the cmp callback uses. Moreover, walking the entire list afterwards to merge adjacent ranges is overkill, since we know

Re: [PATCH v9 perf,bpf 09/15] perf, bpf: save btf information as headers to perf.data

> On Mar 12, 2019, at 10:05 AM, Arnaldo Carvalho de Melo > wrote: > > Em Tue, Mar 12, 2019 at 04:26:17PM +, Song Liu escreveu: >> >> >>> On Mar 12, 2019, at 8:16 AM, Arnaldo Carvalho de Melo >>> wrote: >>> >>> Em Tue, Mar 12, 2019 at 12:14:05PM -0300, Arnaldo Carvalho de Melo

[PATCH 0/4] irqchip/gic-v3-its: free_lpi_range tweaks

I noticed that the O(n log n) behaviour of free_lpi_range could easily be made O(n) (patch 4), though I don't suppose n is ever large enough to actually matter. While there, I also stumbled on two other micro-optimizations (2 and 3). Then while writing the commit log for the last patch, I noticed

[PATCH 4.14 126/135] ARM: dts: exynos: Add minimal clkout parameters to Exynos3250 PMU

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marek Szyprowski commit a66352e005488ecb4b534ba1af58a9f671eba9b8 upstream. Add minimal parameters needed by the Exynos CLKOUT driver to Exynos3250 PMU node. This fixes the following warning

[PATCH 1/2] arm64/mmap: handle worst-case heap randomization in mmap_base

Increase mmap_base by the worst-case brk randomization so that the stack and heap remain apart. In Linux 4.13 a change was committed that special cased the kernel ELF loader when the loader is invoked directly (eab09532d400; binfmt_elf: use ELF_ET_DYN_BASE only for PIE). Generally, the loader

[PATCH 4.14 109/135] selftests: netfilter: add simple masq/redirect test cases

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 98bfc3414bda335dbd7fec58bde6266f991801d7 ] Check basic nat/redirect/masquerade for ipv4 and ipv6. Signed-off-by: Florian Westphal Signed-off-by: Pablo Neira Ayuso Signed-off-by:

Building and cross-compiling kernel source on Mac OS

Hi, I have a Mac Book Pro with macOS High Sierra 10.13.x installed (with Mac OS Extended (Journaled, Encrypted)). I also have the Xcode installed so I can compile a C program using gcc. Now, I wanted to build linux kernel code (cross compile for arm or risc-v) on Mac OS. I know this is possible,

[PATCH 4.14 111/135] s390/qeth: fix use-after-free in error path

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit afa0c5904ba16d59b0454f7ee4c807dae350f432 ] The error path in qeth_alloc_qdio_buffers() that takes care of cleaning up the Output Queues is buggy. It first frees the queue, but then

[PATCH 4.14 113/135] perf trace: Support multiple "vfs_getname" probes

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6ab3bc240ade47a0f52bc16d97edd9accbe0024e ] With a suitably defined "probe:vfs_getname" probe, 'perf trace' can "beautify" its output, so syscalls like open() or openat() can print

[PATCH 0/2] handle worst-case heap randomization in mmap_base

Increase mmap_base by the worst-case brk randomization so that the stack and heap remain apart. In Linux 4.13 a change was committed that special cased the kernel ELF loader when the loader is invoked directly (eab09532d400; binfmt_elf: use ELF_ET_DYN_BASE only for PIE). Generally, the loader

[PATCH 4.14 110/135] netfilter: nf_nat: skip nat clash resolution for same-origin entries

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 ] It is possible that two concurrent packets originating from the same socket of a connection-less protocol (e.g. UDP) can end up having

[PATCH 2/2] x86/mmap: handle worst-case heap randomization in mmap_base

Increase mmap_base by the worst-case brk randomization so that the stack and heap remain apart. In Linux 4.13 a change was committed that special cased the kernel ELF loader when the loader is invoked directly (eab09532d400; binfmt_elf: use ELF_ET_DYN_BASE only for PIE). Generally, the loader

[PATCH 4.14 114/135] MIPS: Loongson: Introduce and use loongson_llsc_mb()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e02e07e3127d8aec1f4bcdfb2fc52a2d99b4859e ] On the Loongson-2G/2H/3A/3B there is a hardware flaw that ll/sc and lld/scd is very weak ordering. We should add sync instructions "before

[PATCH 4.14 115/135] MIPS: Remove function size check in get_frame_info()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b424cfc69728224fcb5fad138ea7260728e0901 ] Patch (b6c7a324df37b "MIPS: Fix get_frame_info() handling of microMIPS function size.") introduces additional function size check for

Re: [PATCH v2 2/3] dt-bindings: mmc: Add a new property disable-cqe-dcmd.

> On 12.03.2019, at 18:10, Heiko Stübner wrote: > > Hi Christoph, > > Am Dienstag, 12. März 2019, 15:46:44 CET schrieb Christoph Müllner: >>> On 12.03.2019, at 14:17, Heiko Stuebner wrote: >>> >>> Am Freitag, 8. März 2019, 14:10:45 CET schrieb Christoph Müllner: > On 08.03.2019, at

[PATCH 4.14 106/135] vsock/virtio: reset connected sockets on device removal

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 85965487abc540368393a15491e6e7fcd230039d ] When the virtio transport device disappear, we should reset all connected sockets in order to inform the users. Signed-off-by: Stefano

[PATCH 4.14 028/135] ipv4: Return error for RTA_VIA attribute

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit b6e9e5df4ecf100f6a10ab2ade8e46d47a4b9779 ] IPv4 currently does not support nexthops outside of the AF_INET family. Specifically, it does not handle RTA_VIA

[PATCH 4.14 128/135] ARM: 8781/1: Fix Thumb-2 syscall return for binutils 2.29+

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit afc9f65e01cd114cb2cedf544d22239116ce0cc6 ] When building the kernel as Thumb-2 with binutils 2.29 or newer, if the assembler has seen the .type directive (via ENDPROC()) for a

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