[PATCH v2 1/1] pwm: meson: use the spin-lock only to protect register modifications

Holding the spin-lock for all of the code in meson_pwm_apply() can result in a "BUG: scheduling while atomic". This can happen because clk_get_rate() (which is called from meson_pwm_calc()) may sleep. Only hold the spin-lock when modifying registers to solve this. The reason why we need a

[PATCH 4.19 078/134] tty: mxs-auart: fix a potential NULL pointer dereference

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Kangjie Lu commit 6734330654dac550f12e932996b868c6d0dcb421 upstream. In case ioremap fails, the fix returns -ENOMEM to avoid NULL pointer dereferences. Multiple places use port.membase.

[PATCH 4.19 122/134] x86/smp: Enforce CONFIG_HOTPLUG_CPU when SMP=y

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit bebd024e4815b1a170fcd21ead9cb23ce9e6 upstream. The SMT disable 'nosmt' command line argument is not working properly when CONFIG_HOTPLUG_CPU is disabled. The

[PATCH 4.19 111/134] mm: add support for kmem caches in DMA32 zone

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Boichat commit 6d6ea1e967a246f12cfe2f5fb743b70b2e608d4a upstream. Patch series "iommu/io-pgtable-arm-v7s: Use DMA32 zone for page tables", v6. This is a followup to the discussion in

[PATCH 4.19 126/134] staging: erofs: fix error handling when failed to read compresssed data

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Gao Xiang commit b6391ac73400eff38377a4a7364bd3df5efb5178 upstream. Complete read error handling paths for all three kinds of compressed pages: 1) For cache-managed pages, PG_uptodate will

[PATCH 4.19 129/134] drivers: base: Helpers for adding device connection descriptions

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Heikki Krogerus commit cd7753d371388e712e3ee52b693459f9b71aaac2 upstream. Introducing helpers for adding and removing multiple device connection descriptions at once. Acked-by: Hans de Goede

[PATCH 4.19 130/134] platform: x86: intel_cht_int33fe: Register all connections at once

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Heikki Krogerus commit 140a4ec4aa615b4e8e8055ca37a30c7fe5e8 upstream. We can register all device connection descriptors with a single call to device_connections_add(). Acked-by: Andy

[PATCH 4.19 134/134] platform: x86: intel_cht_int33fe: Remove the old connections for the muxes

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Heikki Krogerus commit 148b0aa78e4e1077e38f928124bbc9c2d2d24006 upstream. USB Type-C class driver now expects the muxes to be always assigned to the ports and not controllers, so the

[PATCH 4.14 021/107] mac8390: Fix mmio access size probe

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain [ Upstream commit bb9e5c5bcd76f4474eac3baf643d7a39f7bac7bb ] The bug that Stan reported is as follows. After a restart, a 16-bit NIC may be incorrectly identified as a 32-bit NIC

Re: Applied "ASoC: es8316: Add support for inverted jack detect" to the asoc tree

Hi Mark, What about the other two patches? Should I make a new patchset with these? Thanks, -Paul Le lun. 1 avril 2019 à 10:52, Mark Brown a écrit : The patch ASoC: es8316: Add support for inverted jack detect has been applied to the asoc tree at

[PATCH 4.14 022/107] tun: properly test for IFF_UP

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 4477138fa0ae4e1b699786ef0600863ea6e6c61c ] Same reasons than the ones explained in commit 4179cb5a4c92 ("vxlan: test dev->flags & IFF_UP before calling

[PATCH 4.14 012/107] net-sysfs: call dev_hold if kobject_init_and_add success

4.14-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing [ Upstream commit a3e23f719f5c4a38ffb3d30c8d7632a4ed8ccd9e ] In netdev_queue_add_kobject and rx_queue_add_kobject, if sysfs_create_group failed, kobject_put will call

[PATCH 4.14 020/107] net: aquantia: fix rx checksum offload for UDP/TCP over IPv6

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Bogdanov [ Upstream commit a7faaa0c5dc7d091cc9f72b870d7edcdd6f43f12 ] TCP/UDP checksum validity was propagated to skb only if IP checksum is valid. But for IPv6 there is no validity as

[PATCH 4.19 117/134] objtool: Query pkg-config for libelf location

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Rolf Eike Beer commit 056d28d135bca0b1d0908990338e00e9dadaf057 upstream. If it is not in the default location, compilation fails at several points. Signed-off-by: Rolf Eike Beer

[PATCH 4.14 068/107] ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit da484d00f020af3dd7cfcc6c4b69a7f856832883 upstream. Enable headset mode support for new WYSE NB platform. Signed-off-by: Kailang Yang Signed-off-by: Takashi Iwai

[PATCH 4.14 017/107] thunderx: eliminate extra calls to put_page() for pages held for recycling

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dean Nelson [ Upstream commit cd35ef91490ad8049dd180bb060aff7ee192eda9 ] For the non-XDP case, commit 773225388dae15e72790 ("net: thunderx: Optimize page recycling for XDP") added code to

[PATCH 4.14 003/107] video: fbdev: Set pixclock = 0 in goldfishfb

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ace6033ec5c356615eaa3582fb1946e9eaff6662 ] User space Android code identifies pixclock == 0 as a sign for emulation and will set the frame rate to 60 fps when reading this value,

[PATCH 4.14 009/107] net/packet: Set __GFP_NOWARN upon allocation in alloc_pg_vec

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Paasch [ Upstream commit 398f0132c14754fcd03c1c4f8e7176d001ce8ea1 ] Since commit fc62814d690c ("net/packet: fix 4gb buffer limit due to overflow check") one can now allocate packet

[PATCH 4.14 052/107] powerpc/fsl: Update Spectre v2 reporting

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Diana Craciun commit dfa88658fb0583abb92e062c7a9cd5a5b94f2a46 upstream. Report branch predictor state flush as a mitigation for Spectre variant 2. Signed-off-by: Diana Craciun

[PATCH 4.14 036/107] powerpc/fsl: Add barrier_nospec implementation for NXP PowerPC Book3E

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Diana Craciun commit ebcd1bfc33c7a90df941df68a6e5d4018c022fba upstream. Implement the barrier_nospec as a isync;sync instruction sequence. The implementation uses the infrastructure built for

[PATCH 4.14 056/107] Btrfs: fix incorrect file size after shrinking truncate and fsync

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit bf504110bc8aa05df48b0e5f0aa84bfb81e0574b upstream. If we do a shrinking truncate against an inode which is already present in the respective log tree and then rename it,

[PATCH 4.14 041/107] powerpc/pseries: Query hypervisor for count cache flush settings

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit ba72dc171954b782a79d25e0f4b3ed91090c3b1e upstream. Use the existing hypercall to determine the appropriate settings for the count cache flush, and then call the

[PATCH 4.14 050/107] powerpc/fsl: Flush branch predictor when entering KVM

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Diana Craciun commit e7aa61f47b23afbec41031bc47ca8d6cb6516abc upstream. Switching from the guest to host is another place where the speculative accesses can be exploited. Flush the branch

[PATCH 4.14 039/107] powerpc/64s: Add new security feature flags for count cache flush

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit dc8c6cce9a26a51fc19961accb978217a3ba8c75 upstream. Add security feature flags to indicate the need for software to flush the count cache on context switch, and for the

[PATCH 4.14 042/107] powerpc/powernv: Query firmware for count cache flush settings

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 99d54754d3d5f896a8f616b0b6520662bc99d66b upstream. Look for fw-features properties to determine the appropriate settings for the count cache flush, and then call the

[PATCH 4.14 064/107] ALSA: seq: oss: Fix Spectre v1 vulnerability

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit c709f14f0616482b67f9fbcb965e1493a03ff30b upstream. dev is indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre variant 1

[PATCH 4.14 059/107] ARM: imx6q: cpuidle: fix bug that CPU might not wake up at expected time

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kohji Okuno commit 91740fc8242b4f260cfa4d4536d8551804777fae upstream. In the current cpuidle implementation for i.MX6q, the CPU that sets 'WAIT_UNCLOCKED' and the CPU that returns to

[PATCH 4.14 063/107] ALSA: rawmidi: Fix potential Spectre v1 vulnerability

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 2b1d9c8f87235f593826b9cf46ec10247741fff9 upstream. info->stream is indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.14 074/107] scsi: zfcp: fix rport unblock if deleted SCSI devices on Scsi_Host

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit fe67888fc007a76b81e37da23ce5bd8fb95890b0 upstream. An already deleted SCSI device can exist on the Scsi_Host and remain there because something still holds a reference.

[PATCH 4.14 078/107] staging: vt6655: Remove vif check from vnt_interrupt

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Malcolm Priestley commit cc26358f89c3e493b54766b1ca56cfc6b14db78a upstream. A check for vif is made in vnt_interrupt_work. There is a small chance of leaving interrupt disabled while vif is

[PATCH 4.14 046/107] powerpc/fsl: Emulate SPRN_BUCSR register

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Diana Craciun commit 98518c4d8728656db349f875fcbbc7c126d4c973 upstream. In order to flush the branch predictor the guest kernel performs writes to the BUCSR register which is hypervisor

[PATCH 4.14 075/107] scsi: zfcp: fix scsi_eh host reset with port_forced ERP for non-NPIV FCP devices

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit 242ec1455151267fe35a0834aa9038e4c4670884 upstream. Suppose more than one non-NPIV FCP device is active on the same channel. Send I/O to storage and have some of the

[PATCH 4.14 094/107] usb: mtu3: fix EXTCON dependency

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 3d54d10c6afed34fd45b852bf76f55e8da31d8ef upstream. When EXTCON is a loadable module, mtu3 fails to link as built-in: drivers/usb/mtu3/mtu3_plat.o: In function

[PATCH 4.14 100/107] mm/migrate.c: add missing flush_dcache_page for non-mapped page migrate

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lars Persson commit d2b2c6dd227ba5b8a802858748ec9a780cb75b47 upstream. Our MIPS 1004Kc SoCs were seeing random userspace crashes with SIGILL and SIGSEGV that could not be traced back to a

Re: [PATCH v3 2/4] x86/microcode: Fix __user annotations around generic_load_microcode()

On Mon, Apr 1, 2019 at 7:30 PM Borislav Petkov wrote: > > On Fri, Mar 29, 2019 at 10:46:50PM +0100, Jann Horn wrote: > > generic_load_microcode() deals with a pointer that can be either a kernel > > pointer or a user pointer. Pass it around as a __user pointer so that it > > can't be dereferenced

[PATCH 4.14 101/107] perf intel-pt: Fix TSC slip

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Hunter commit f3b4e06b3bda759afd042d3d5fa86bea8f1fe278 upstream. A TSC packet can slip past MTC packets so that the timestamp appears to go backwards. One estimate is that can be up to

[PATCH 4.14 081/107] serial: sh-sci: Fix setting SCSCR_TIE while transferring data

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Hoan Nguyen An commit 93bcefd4c6bad4c69dbc4edcd3fbf774b24d930d upstream. We disable transmission interrupt (clear SCSCR_TIE) after all data has been transmitted (if uart_circ_empty(xmit)).

Re: [PATCHv1 5/7] vfio/mdev: Follow correct remove sequence

On Tue, 26 Mar 2019 22:45:43 -0500 Parav Pandit wrote: > mdev_remove_sysfs_files() should follow exact mirror sequence of a > create, similar to what is followed in error unwinding path of > mdev_create_sysfs_files(). > > Fixes: 6a62c1dfb5c7 ("vfio/mdev: Re-order sysfs attribute creation") >

[PATCH 4.14 104/107] KVM: Reject device ioctls from processes other than the VMs creator

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit ddba91801aeb5c160b660caed1800eb3aef403f8 upstream. KVM's API requires thats ioctls must be issued from the same process that created the VM. In other words,

[PATCH 4.14 084/107] USB: serial: mos7720: fix mos_parport refcount imbalance on error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Lin Yi commit 2908b076f5198d231de62713cb2b633a3a4b95ac upstream. The write_parport_reg_nonblock() helper takes a reference to the struct mos_parport, but failed to release it in a couple of

[PATCH 4.14 107/107] vfio: ccw: only free cp on final interrupt

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Cornelia Huck commit 50b7f1b7236bab08ebbbecf90521e84b068d7a17 upstream. When we get an interrupt for a channel program, it is not necessarily the final interrupt; for example, the issuing

[PATCH 4.14 086/107] USB: serial: option: add support for Quectel EM12

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kristian Evensen commit d1252f0237238b912c3e7a51bf237acf34c97983 upstream. The Quectel EM12 is a Cat. 12 LTE modem. It behaves in the exactly the same way as the EP06 (including the dynamic

[PATCH 4.14 088/107] Disable kgdboc failed by echo space to /sys/module/kgdboc/parameters/kgdboc

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Wentao Wang commit 3ec8002951ea173e24b466df1ea98c56b7920e63 upstream. Echo "" to /sys/module/kgdboc/parameters/kgdboc will fail with "No such device” error. This is caused by function

[PATCH 4.9 11/56] tcp: do not use ipv6 header for ipv4 flow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 89e4130939a20304f4059ab72179da81f5347528 ] When a dual stack tcp listener accepts an ipv4 flow, it should not attempt to use an ipv6 header or tcp_v6_iif()

[PATCH 4.9 01/56] Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marcel Holtmann commit af3d5d1c87664a4f150fcf3534c6567cb19909b0 upstream. When doing option parsing for standard type values of 1, 2 or 4 octets, the value is converted directly into a

Re: [PATCH 4/7] dt-bindings: mfd: Document Macronix MX25F0A controller bindings

Hi Mason, Mason Yang wrote on Thu, 28 Mar 2019 18:18:35 +0800: > Document the bindings used by the Macronix MX25F0A MFD controller. > > Signed-off-by: Mason Yang > --- > .../devicetree/bindings/mfd/mxic-mx25f0a.txt | 66 > ++ > 1 file changed, 66 insertions(+) >

[PATCH 4.9 12/56] vxlan: Dont call gro_cells_destroy() before device is unregistered

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Zhiqiang Liu [ Upstream commit cc4807bb609230d8959fd732b0bf3bd4c2de8eac ] Commit ad6c9986bcb62 ("vxlan: Fix GRO cells race condition between receive and link delete") fixed a race condition

[PATCH 4.9 17/56] btrfs: remove WARN_ON in log_dir_items

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Josef Bacik commit 2cc8334270e281815c3850c3adea363c51f21e0d upstream. When Filipe added the recursive directory logging stuff in 2f2ff0ee5e430 ("Btrfs: fix metadata inconsistencies after

[PATCH 4.9 18/56] btrfs: raid56: properly unmap parity page in finish_parity_scrub()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andrea Righi commit 3897b6f0a859288c22fb793fad11ec2327e60fcd upstream. Parity page is incorrectly unmapped in finish_parity_scrub(), triggering a reference counter bug on i386, i.e.: [

[PATCH 4.9 15/56] tun: properly test for IFF_UP

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 4477138fa0ae4e1b699786ef0600863ea6e6c61c ] Same reasons than the ones explained in commit 4179cb5a4c92 ("vxlan: test dev->flags & IFF_UP before calling

Re: How to add Unicode character tables to the kernel?

On Sun, Mar 31, 2019 at 4:09 PM Theodore Ts'o wrote: > > The question is how to do this, with different tradeoffs. One is to > simply include a utf8data.h file, which will be 320k. That might > sound large, but in fs/nls there are 3544k worth of similar files. > Some are relatively small ---

[PATCH 4.9 23/56] ALSA: rawmidi: Fix potential Spectre v1 vulnerability

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gustavo A. R. Silva commit 2b1d9c8f87235f593826b9cf46ec10247741fff9 upstream. info->stream is indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre

[PATCH 4.9 26/56] ALSA: pcm: Dont suspend stream in unrecoverable PCM state

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 113ce08109f8e3b091399e7cc32486df1cff48e7 upstream. Currently PCM core sets each opened stream forcibly to SUSPENDED state via snd_pcm_suspend_all() call, and the user-space

[PATCH 4.9 06/56] dccp: do not use ipv6 header for ipv4 flow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit e0aa67709f89d08c8d8e5bdd9e0b649df61d0090 ] When a dual stack dccp listener accepts an ipv4 flow, it should not attempt to use an ipv6 header or inet6_iif()

[PATCH 4.9 30/56] scsi: zfcp: fix rport unblock if deleted SCSI devices on Scsi_Host

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Maier commit fe67888fc007a76b81e37da23ce5bd8fb95890b0 upstream. An already deleted SCSI device can exist on the Scsi_Host and remain there because something still holds a reference. A

[PATCH 4.9 00/56] 4.9.167-stable review

This is the start of the stable review cycle for the 4.9.167 release. There are 56 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 Apr 3 17:00:20 UTC 2019. Anything

[PATCH 4.9 47/56] usb: host: xhci-rcar: Add XHCI_TRUST_TX_LENGTH quirk

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Yasushi Asano commit 40fc165304f0faaae78b761f8ee30b5d216b1850 upstream. When plugging BUFFALO LUA4-U3-AGT USB3.0 to Gigabit Ethernet LAN Adapter, warning messages filled up dmesg. [

[PATCH 4.9 44/56] fs/proc/proc_sysctl.c: fix NULL pointer dereference in put_links

4.9-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing commit 23da9588037ecdd4901db76a5b79a42b529c4ec3 upstream. Syzkaller reports: kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: [#1]

Re: [PATCH] fs/open: Fix most outstanding security bugs

On Mon, Apr 1, 2019 at 4:14 PM Nikolay Borisov wrote: > On 1.04.19 г. 12:01 ч., Johannes Thumshirn wrote: > > Over the last 20 years, the Linux kernel has accumulated hundreds if not > > thousands of security vulnerabilities. > > > > One common pattern in most of these security related reports is

[PATCH 4.9 52/56] KVM: x86: Emulate MSR_IA32_ARCH_CAPABILITIES on AMD hosts

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sean Christopherson commit 0cf9135b773bf32fba9dd8e6699c1b331ee4b749 upstream. The CPUID flag ARCH_CAPABILITIES is unconditioinally exposed to host userspace for all x86 hosts, i.e. KVM

[PATCH 4.9 56/56] arm64: support keyctl() system call in 32-bit mode

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5c2a625937ba49bc691089370638223d310cda9a ] As is the case for a number of other architectures that have a 32-bit compat mode, enable KEYS_COMPAT if both COMPAT and KEYS are enabled.

[PATCH 4.9 36/56] serial: max310x: Fix to avoid potential NULL pointer dereference

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Aditya Pakki commit 3a10e3dd52e80b9a97a3346020024d17b2c272d6 upstream. of_match_device can return a NULL pointer when matching device is not found. This patch avoids a scenario causing NULL

[PATCH 4.9 40/56] USB: serial: mos7720: fix mos_parport refcount imbalance on error path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Lin Yi commit 2908b076f5198d231de62713cb2b633a3a4b95ac upstream. The write_parport_reg_nonblock() helper takes a reference to the struct mos_parport, but failed to release it in a couple of

[PATCH 4.4 001/131] mmc: pxamci: fix enum type confusion

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit e60a582bcde01158a64ff948fb799f21f5d31a11 upstream. clang points out several instances of mismatched types in this drivers, all coming from a single declaration:

[PATCH 4.9 39/56] USB: serial: ftdi_sio: add additional NovaTech products

4.9-stable review patch. If anyone has any objections, please let me know. -- From: George McCollister commit 422c2537ba9d42320f8ab6573940269f87095320 upstream. Add PIDs for the NovaTech OrionLX+ and Orion I/O so they can be automatically detected. Signed-off-by: George

[PATCH 4.4 022/131] mmc: core: fix using wrong io voltage if mmc_select_hs200 fails

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dong Aisheng commit e51534c806609c806d81bfb034f02737461f855c upstream. Currently MMC core will keep going if HS200/HS timing switch failed with -EBADMSG error by the assumption that the old

[PATCH 4.4 004/131] mips: loongson64: lemote-2f: Add IRQF_NO_SUSPEND to "cascade" irqaction.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yifeng Li commit 5f5f67da9781770df0403269bc57d7aae608fecd upstream. Timekeeping IRQs from CS5536 MFGPT are routed to i8259, which then triggers the "cascade" IRQ on MIPS CPU. Without

[PATCH 4.4 021/131] arm64: mm: Add trace_irqflags annotations to do_debug_exception()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: James Morse commit 6afedcd23cfd7ac56c011069e4a8db37b46e4623 upstream. With CONFIG_PROVE_LOCKING, CONFIG_DEBUG_LOCKDEP and CONFIG_TRACE_IRQFLAGS enabled, lockdep will compare

[PATCH 4.4 031/131] arm64: traps: disable irq in die()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Qiao Zhou commit 6f44a0bacb79a03972c83759711832b382b1b8ac upstream. In current die(), the irq is disabled for __die() handle, not including the possible panic() handling. Since the log in

[PATCH 4.4 028/131] tcp/dccp: drop SYN packets if accept queue is full

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 5ea8ea2cb7f1d0db15762c9b0bb9e7330425a071 upstream. Per listen(fd, backlog) rules, there is really no point accepting a SYN, sending a SYNACK, and dropping the following ACK

[PATCH 4.4 032/131] usb: renesas_usbhs: gadget: fix unused-but-set-variable warning

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit b7d44c36a6f6d956e1539e0dd42f98b26e5a4684 upstream. The commit b8b9c974afee ("usb: renesas_usbhs: gadget: disable all eps when the driver stops") causes the

[PATCH 4.4 035/131] USB: core: only clean up what we allocated

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Konovalov commit 32fd87b3bbf5f7a045546401dfe2894dbbf4d8c3 upstream. When cleaning up the configurations, make sure we only free the number of configurations and interfaces that we could

[PATCH 4.4 008/131] ext4: fix data corruption caused by unaligned direct AIO

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Lukas Czerner commit 372a03e01853f860560eade508794dd274e9b390 upstream. Ext4 needs to serialize unaligned direct AIO because the zeroing of partial blocks of two competing unaligned AIOs can

[PATCH 4.4 011/131] media: v4l2-ctrls.c/uvc: zero v4l2_event

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit f45f3f753b0a3d739acda8e311b4f744d82dc52a upstream. Control events can leak kernel memory since they do not fully zero the event. The same code is present in both

[PATCH 4.4 049/131] arm64: hide __efistub_ aliases from kallsyms

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 75feee3d9d51775072d3a04f47d4a439a4c4590e ] Commit e8f3010f7326 ("arm64/efi: isolate EFI stub from the kernel proper") isolated the EFI stub code from the kernel proper by prefixing

Re: [PATCH v2] writeback: use exact memcg dirty counts

On Fri, Mar 29, 2019 at 10:46:09AM -0700, Greg Thelen wrote: > Since commit a983b5ebee57 ("mm: memcontrol: fix excessive complexity in > memory.stat reporting") memcg dirty and writeback counters are managed > as: > 1) per-memcg per-cpu values in range of [-32..32] > 2) per-memcg atomic counter >

[PATCH 4.4 055/131] coresight: coresight_unregister() function cleanup

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fae54158792aec705620bdc3938d342879204f0c ] In its current form the code never frees csdev->refcnt allocated in coresight_register(). There is also a problem with csdev->conns that

[PATCH 4.4 050/131] perf: Synchronously free aux pages in case of allocation failure

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 45c815f06b80031659c63d7b93e580015d6024dd ] We are currently using asynchronous deallocation in the error path in AUX mmap code, which is unnecessary and also presents a problem for

[PATCH v2] bmp085.yaml: transform DT documentation of iio sensor into YAML

use bmp085.txt and change it into yaml format fix links to datasheets in replaced documentation Signed-off-by: Andreas Klinger --- .../devicetree/bindings/iio/pressure/bmp085.txt| 27 - .../devicetree/bindings/iio/pressure/bmp085.yaml | 70 ++ 2 files changed,

[PATCH 4.4 041/131] mmc: block: Allow more than 8 partitions per card

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 382c55f88ffeb218c446bf0c46d0fc25d2795fe2 ] It is quite common for Android devices to utilize more then 8 partitions on internal eMMC storage. The vanilla kernel can support this via

[PATCH 4.4 064/131] stm class: Fix unbalanced module/device refcounting

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f7c81c7176c72c7899390754b4b038a64b296e4d ] STM code takes references to the stm device and its module for the duration of the character device's existence or the stm_source link.

[PATCH 4.4 062/131] stm class: Fix unlocking braino in the error path

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1810f2c44817c74ca3d05d1e3981e3a2e2ceb6f5 ] If an illegal attempt is made to unlink stm source device from an stm device, the stm device's link spinlock mistakenly remains locked.

[PATCH 4.4 063/131] stm class: Guard output assignment against concurrency

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cde4ad8368840e414ecf67db258fe1dabaa5fd2e ] It is possible to concurrently assign the same output (a character device writer or an stm_source device) to different stm devices, which

[PATCH 4.4 060/131] stm class: Prevent user-controllable allocations

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f08b18266c7116e2ec6885dd53a928f580060a71 ] Currently, the character device write method allocates a temporary buffer for user's data, but the user's data size is not sanitized and

Re: [PATCH v2 0/5] pid: add pidfd_open()

On Mon, Apr 1, 2019 at 9:45 AM Daniel Colascione wrote: > > But doesn't the CSIGNAL approach still require that libraries somehow > coordinate which non-SIGCHLD signal they use? Yes. As mentioned, this was seldom used. In some cases it's ok, eg aio would just specify the signal in sigev_signo

Re: [PATCH] usb: musb: Force-disable pullup on shutdown

Le lun. 1 avril 2019 à 19:17, Bin Liu a écrit : On Thu, Mar 21, 2019 at 03:42:46PM +0100, Paul Cercueil wrote: When the musb is shutdown, for instance when the driver is unloaded, force-disable the pullup. Otherwise, the host will still see the gadget device even after the shutdown.

[PATCH 4.4 046/131] android: unconditionally remove callbacks in sync_fence_free()

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 699f685569434510d944e419f4048c4e3ba8d631 ] Using fence->status to determine whether or not there are callbacks remaining on the sync_fence is racy since fence->status may have been

[PATCH 4.4 078/131] PM / Hibernate: Call flush_icache_range() on pages restored in-place

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f6cf0545ec697ddc278b7457b7d0c0d86a2ea88e ] Some architectures require code written to memory as if it were data to be 'cleaned' from any data caches before the processor can fetch

Re: WARNING in cma_exit_net

On Mon, Apr 01, 2019 at 10:36:05AM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:e3ecb83e Add linux-next specific files for 20190401 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=13

[PATCH 4.4 093/131] net: rose: fix a possible stack overflow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit e5dcc0c3223c45c94100f05f28d8ef814db3d82c ] rose_write_internal() uses a temp buffer of 100 bytes, but a manual inspection showed that given arbitrary input,

[PATCH 4.4 080/131] stm class: Fix stm device initialization order

4.4-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 389b6699a2aa0b457aa69986e9ddf39f3b4030fd ] Currently, stm_register_device() makes the device visible and then proceeds to initializing spinlocks and other properties, which leaves a

[RFC PATCH 4/5] dt-bindings: leds: Add LED_COLOR_ID and COLOR_NAME definitions

This patch is being added to demonstrate reuse of Jacek's patch https://lore.kernel.org/patchwork/patch/1056726/ I have added color name definitions to the above patch. I do not claim authorship and the intent of this patch to strictly for demonstration. Signed-off-by: Dan Murphy ---

[RFC PATCH 1/5] leds: multicolor: Add sysfs interface definition

Add a documentation of LED Multicolor LED class specific sysfs attributes. Signed-off-by: Dan Murphy --- .../ABI/testing/sysfs-class-led-multicolor| 91 +++ 1 file changed, 91 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-class-led-multicolor diff --git

[RFC PATCH 2/5] dt: bindings: Add multicolor class dt bindings documention

Add DT bindings for the LEDs multicolor class framework. Signed-off-by: Dan Murphy --- .../bindings/leds/leds-class-multicolor.txt | 140 ++ 1 file changed, 140 insertions(+) create mode 100644 Documentation/devicetree/bindings/leds/leds-class-multicolor.txt diff --git

[PATCH 4.4 095/131] packets: Always register packet sk in the same order

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maxime Chevallier [ Upstream commit a4dc6a49156b1f8d6e17251ffda17c9e6a5db78a ] When using fanouts with AF_PACKET, the demux functions such as fanout_demux_cpu will return an index in the

[RFC PATCH 5/5] leds: multicolor: Introduce a multicolor class definition

Introduce a multicolor class that groups colored LEDs within a LED node. The framework allows for dynamically setting individual LEDs or setting brightness levels of LEDs and updating them virtually simultaneously. Signed-off-by: Dan Murphy --- drivers/leds/Kconfig | 10 +

[RFC PATCH 0/5] MultiColor LED framework Documentation

I am RFCing these patches to start this Multicolor framework as it appears we have a few devices that need to leverage a framework like this. I have attempted to create as much documentation as possible and have no issue in combining documents into a single document but I think this patchset is

[PATCH 4.4 094/131] Add hlist_add_tail_rcu() (Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net)

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David S. Miller commit 1602f49b58abcb0d34a5f0a29d68e7c1769547aa upstream. [This commit was a merge, but it added hlist_add_tail_rcu(), which is what we need in this stable tree, so I've

[PATCH 4.4 096/131] tcp: do not use ipv6 header for ipv4 flow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 89e4130939a20304f4059ab72179da81f5347528 ] When a dual stack tcp listener accepts an ipv4 flow, it should not attempt to use an ipv6 header or tcp_v6_iif()

[PATCH 4.4 101/131] btrfs: raid56: properly unmap parity page in finish_parity_scrub()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andrea Righi commit 3897b6f0a859288c22fb793fad11ec2327e60fcd upstream. Parity page is incorrectly unmapped in finish_parity_scrub(), triggering a reference counter bug on i386, i.e.: [

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