[PATCH 4.19 119/139] ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit a182ecd3809c8d5a2da80c520f3602e301c5317e upstream. Some boards such as the Swanky model Chromebooks use pmc_plt_clk_0 for the mclk instead of pmc_plt_clk_3. This commit

[PATCH 4.19 120/139] ASoC: pcm186x: Fix device reset-registers trigger value

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Dannenberg commit 5277715639ff6f75c729e657690751a831112c4b upstream. According to the current device datasheet (TI Lit # SLAS831D, revised March 2018) the value written to the

[PATCH 4.19 132/139] Revert "usb: dwc3: gadget: skip Set/Clear Halt when invalid"

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Felipe Balbi commit 38317f5c0f2faae5110854f36edad810f841d62f upstream. This reverts commit ffb80fc672c3a7b6afd0cefcb1524fb99917b2f3. Turns out that commit is wrong. Host controllers are

[PATCH 4.19 115/139] function_graph: Reverse the order of pushing the ret_stack and the callback

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 7c6ea35ef50810aa12ab26f21cb858d980881576 upstream. The function graph profiler uses the ret_stack to store the "subtime" and reuse it by nested functions and

[PATCH 4.19 137/139] mm: use swp_offset as key in shmem_replace_page()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Yu Zhao commit c1cb20d43728aa9b5393bd8d489bc85c142949b2 upstream. We changed the key of swap cache tree from swp_entry_t.val to swp_offset. We need to do so in shmem_replace_page() as well.

[PATCH 4.19 138/139] Drivers: hv: vmbus: check the creation_status in vmbus_establish_gpadl()

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Dexuan Cui commit eceb05965489784f24bbf4d61ba60e475a983016 upstream. This is a longstanding issue: if the vmbus upper-layer drivers try to consume too many GPADLs, the host may return with an

[PATCH 4.19 139/139] misc: mic/scif: fix copy-paste error in scif_create_remote_lookup

4.19-stable review patch. If anyone has any objections, please let me know. -- From: YueHaibing commit 6484a677294aa5d08c0210f2f387ebb9be646115 upstream. gcc '-Wunused-but-set-variable' warning: drivers/misc/mic/scif/scif_rma.c: In function 'scif_create_remote_lookup':

[PATCH 4.19 116/139] binder: fix race that allows malicious free of live buffer

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Todd Kjos commit 7bada55ab50697861eee6bb7d60b41e68a961a9c upstream. Malicious code can attempt to free buffers using the BC_FREE_BUFFER ioctl to binder. There are protections against a user

[PATCH 4.19 113/139] function_graph: Have profiler use curr_ret_stack and not depth

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit b1b35f2e218a5b57d03bbc3b0667d5064570dc60 upstream. The profiler uses trace->depth to find its entry on the ret_stack, but the depth may not match the actual

[PATCH 4.19 134/139] iio:st_magn: Fix enable device after trigger

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Martin Kelly commit fe5192ac81ad0d4dfe1395d11f393f0513c15f7f upstream. Currently, we enable the device before we enable the device trigger. At high frequencies, this can cause interrupts that

[PATCH 4.14 142/146] lib/test_kmod.c: fix rmmod double free

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Luis Chamberlain commit 5618cf031fecda63847cafd1091e7b8bd626cdb1 upstream. We free the misc device string twice on rmmod; fix this. Without this we cannot remove the module without crashing.

[PATCH 4.14 139/146] usb: core: quirks: add RESET_RESUME quirk for Cherry G230 Stream series

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Michael Niewöhner commit effd14f66cc1ef6701a19c5a56e39c35f4d395a5 upstream. Cherry G230 Stream 2.0 (G85-231) and 3.0 (G85-232) need this quirk to function correctly. This fixes a but where

[PATCH 4.14 106/146] x86/speculation: Enable prctl mode for spectre_v2_user

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner t...@linutronix.de commit 7cc765a67d8e04ef7d772425ca5a2a1e2b894c15 upstream Now that all prerequisites are in place: - Add the prctl command line option - Default the

[PATCH 4.14 109/146] kvm: mmu: Fix race in emulated page table writes

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Junaid Shahid commit 0e0fee5c539b61fdd098332e0e2cc375d9073706 upstream. When a guest page table is updated via an emulated write, kvm_mmu_pte_write() is called to update the shadow PTE using

[PATCH 4.14 131/146] ext2: fix potential use after free

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pan Bian commit ecebf55d27a11538ea84aee0be643dd953f830d5 upstream. The function ext2_xattr_set calls brelse(bh) to drop the reference count of bh. After that, bh may be freed. However,

[PATCH 4.14 103/146] x86/speculation: Prevent stale SPEC_CTRL msr content

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner t...@linutronix.de commit 6d991ba509ebcfcc908e009d1db51972a4f7a064 upstream The seccomp speculation control operates on all tasks of a process, but only the current task of a

[PATCH 4.14 140/146] Revert "usb: dwc3: gadget: skip Set/Clear Halt when invalid"

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Felipe Balbi commit 38317f5c0f2faae5110854f36edad810f841d62f upstream. This reverts commit ffb80fc672c3a7b6afd0cefcb1524fb99917b2f3. Turns out that commit is wrong. Host controllers are

Re: [PATCH 4.14 098/146] x86/process: Consolidate and simplify switch_to_xtra() code

On Tue, 4 Dec 2018, Greg Kroah-Hartman wrote: > --- a/arch/x86/kernel/process_32.c > +++ b/arch/x86/kernel/process_32.c > @@ -234,7 +234,6 @@ __switch_to(struct task_struct *prev_p, > struct fpu *prev_fpu = >fpu; > struct fpu *next_fpu = >fpu; > int cpu = smp_processor_id(); > -

[PATCH 4.14 129/146] ALSA: hda/realtek - Support ALC300

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kailang Yang commit 1078bef0cd9291355a20369b21cd823026ab8eaa upstream. This patch will enable ALC300. [ It's almost equivalent with other ALC269-compatible ones, and apparently has no

[PATCH 4.14 133/146] dmaengine: at_hdmac: fix memory leak in at_dma_xlate()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Richard Genoud commit 98f5f932254b88ce828bc8e4d1642d14e5854caa upstream. The leak was found when opening/closing a serial port a great number of time, increasing kmalloc-32 in slabinfo. Each

[PATCH 4.14 127/146] ALSA: control: Fix race between adding and removing a user element

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit e1a7bfe3807974e66f971f2589d4e0197ec0fced upstream. The procedure for adding a user control element has some window opened for race against the concurrent removal of a user

[PATCH 4.14 004/146] mm/huge_memory: fix lockdep complaint on 32-bit i_size_read()

4.14-stable review patch. If anyone has any objections, please let me know. -- commit 006d3ff27e884f80bd7d306b041afc415f63598f upstream. Huge tmpfs testing, on 32-bit kernel with lockdep enabled, showed that __split_huge_page() was using i_size_read() while holding the irq-safe

[PATCH 4.14 020/146] tls: Add function to update the TLS socket configuration

4.14-stable review patch. If anyone has any objections, please let me know. -- commit 6d88207fcfddc002afe3e2e4a455e5201089d5d9 upstream. The tx configuration is now stored in ctx->tx_conf. And sk->sk_prot is updated trough a function This will simplify things when we add rx and

[PATCH 4.14 016/146] libceph: factor out encrypt_authorizer()

4.14-stable review patch. If anyone has any objections, please let me know. -- commit 149cac4a50b0b4081b38b2f38de6ef71c27eaa85 upstream. Will be used for encrypting both the initial and updated authorizers. Signed-off-by: Ilya Dryomov Reviewed-by: Sage Weil Signed-off-by:

[PATCH 4.14 019/146] bpf: Prevent memory disambiguation attack

4.14-stable review patch. If anyone has any objections, please let me know. -- commit af86ca4e3088fe5eacf2f7e58c01fa68ca067672 upstream. Detect code patterns where malicious 'speculative store bypass' can be used and sanitize such patterns. 39: (bf) r3 = r10 40: (07) r3 +=

[PATCH 4.14 015/146] libceph: factor out __ceph_x_decrypt()

4.14-stable review patch. If anyone has any objections, please let me know. -- commit c571fe24d243bfe7017f0e67fe800b3cc2a1d1f7 upstream. Will be used for decrypting the server challenge which is only preceded by ceph_x_encrypt_header. Drop struct_v check to allow for extending

[PATCH 4.14 014/146] libceph: factor out __prepare_write_connect()

4.14-stable review patch. If anyone has any objections, please let me know. -- commit c0f56b483aa09c99bfe97409a43ad786f33b8a5a upstream. Will be used for sending ceph_msg_connect with an updated authorizer, after the server challenges the initial authorizer. Signed-off-by:

[PATCH 4.14 013/146] libceph: store ceph_auth_handshake pointer in ceph_connection

4.14-stable review patch. If anyone has any objections, please let me know. -- commit 262614c4294d33b1f19e0d18c0091d9c329b544a upstream. We already copy authorizer_reply_buf and authorizer_reply_buf_len into ceph_connection. Factoring out __prepare_write_connect() requires two

[PATCH 1/1] iommu/arm-smmu: Add support to use Last level cache

Qualcomm SoCs have an additional level of cache called as System cache, aka. Last level cache (LLC). This cache sits right before the DDR, and is tightly coupled with the memory controller. The cache is available to all the clients present in the SoC system. The clients request their slices from

[PATCH 4.19 111/139] function_graph: Make ftrace_push_return_trace() static

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit d125f3f866df88da5a85df00291f88f0baa89f7c upstream. As all architectures now call function_graph_enter() to do the entry work, no architecture should ever call

[tip:x86/timers] x86/hpet: Remove unused FSEC_PER_NSEC define

Commit-ID: d999c0ec2498e54b9328db6b2c1037710025add1 Gitweb: https://git.kernel.org/tip/d999c0ec2498e54b9328db6b2c1037710025add1 Author: Roland Dreier AuthorDate: Fri, 30 Nov 2018 13:14:50 -0800 Committer: Borislav Petkov CommitDate: Tue, 4 Dec 2018 12:17:21 +0100 x86/hpet: Remove

Re: [PATCH 11/14] pinctrl: milbeaut: Add Milbeaut M10V pinctrl

Hi Sugaya-san On Mon, Nov 19, 2018 at 10:01 AM Sugaya Taichi wrote: > > Add Milbeaut M10V pinctrl. > The M10V has the pins that can be used GPIOs or take multiple other > functions. > > Signed-off-by: Sugaya Taichi This patch was sent to: linux-...@vger.kernel.org,

[PATCH 4.14 012/146] ubi: Initialize Fastmap checkmapping correctly

4.14-stable review patch. If anyone has any objections, please let me know. -- commit 25677478474a91fa1b46f19a4a591a9848bca6fb upstream We cannot do it last, otherwithse it will be skipped for dynamic volumes. Reported-by: Lachmann, Juergen Fixes: 34653fd8c46e ("ubi: fastmap:

[PATCH 4.14 011/146] media: em28xx: Fix use-after-free when disconnecting

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 910b0797fa9e8af09c44a3fa36cb310ba7a7218d ] Fix bug by moving the i2c_unregister_device calls after deregistration of dvb frontend. The new style i2c drivers already destroys the

Re: [PATCH v3 2/4] drivers: thermal: tsens: Add generic support for TSENS v1 IP

On Thu, Nov 29, 2018 at 10:26 PM Eduardo Valentin wrote: > > On Tue, Nov 27, 2018 at 09:59:05PM +0530, Amit Kucheria wrote: > > + qfprom_cdata = (u32 *)qfprom_read(tmdev->dev, "calib"); > > + if (IS_ERR(qfprom_cdata)) > > + return PTR_ERR(qfprom_cdata); > > + > > + mode

[PATCH 4.19 117/139] ext2: initialize opts.s_mount_opt as zero before using it

4.19-stable review patch. If anyone has any objections, please let me know. -- From: xingaopeng commit e5f5b717983bccfa033282e9886811635602510e upstream. We need to initialize opts.s_mount_opt as zero before using it, else we may get some unexpected mount options. Fixes:

[PATCH 4.19 136/139] mm: cleancache: fix corruption on missed inode invalidation

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Tikhomirov commit 6ff38bd40230af35e446239396e5fc8ebd6a5248 upstream. If all pages are deleted from the mapping by memory reclaim and also moved to the cleancache:

[PATCH 4.19 127/139] staging: mt7621-pinctrl: fix uninitialized variable ngroups

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit cd56a5141331abfe218d744a3d66e1788135d482 upstream. Currently the for_each_node_with_property loop us incrementing variable ngroups however it was not initialized and

Re: [PATCH] Revert "exec: make de_thread() freezable (was: Re: Linux 4.20-rc4)

* Rafael J. Wysocki wrote: > > Note that I haven't tested the revert yet, but the code and the breakage > > looks pretty obvious. (I'll boot the revert, will follow up if that > > didn't solve the problem.) > > I can queue up a revert unless anyone beats me to that. Thanks! I have 1+ days

Re: [PATCH 1/2] mm: add probe_user_read() and probe_user_address()

Christophe Leroy writes: > In the powerpc, there are several places implementing safe ^ code ? > access to user data. This is sometimes implemented using > probe_kernel_address() with additional access_ok() verification, > sometimes with get_user() enclosed in a

Re: [PATCH] mm/alloc: fallback to first node if the wanted node offline

On Tue, Dec 4, 2018 at 4:40 PM Wei Yang wrote: > > On Tue, Dec 04, 2018 at 04:20:32PM +0800, Pingfan Liu wrote: > >On Tue, Dec 4, 2018 at 3:22 PM Michal Hocko wrote: > >> > >> On Tue 04-12-18 11:05:57, Pingfan Liu wrote: > >> > During my test on some AMD machine, with kexec -l nr_cpus=x option,

RE: [LINUX PATCH v12 3/3] mtd: rawnand: arasan: Add support for Arasan NAND Flash Controller

Hi Boris, > -Original Message- > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com] > Sent: Tuesday, November 20, 2018 9:55 PM > To: Naga Sureshkumar Relli > Cc: miquel.ray...@bootlin.com; rich...@nod.at; dw...@infradead.org; > computersforpe...@gmail.com; marek.va...@gmail.com;

Re: [patch V2 27/28] x86/speculation: Add seccomp Spectre v2 user space protection mode

On processors with enhanced IBRS support, we recommend setting IBRS to 1 and left set. Then why doesn't CPU with EIBRS support acutally *default* to '1', with opt-out possibility for OS? (slightly longer answer) you can pretty much assume that on these CPUs, IBRS doesn't actually do anything

Re: [PATCH v2 1/2] dt-bindings: gpio: add SAMA5D2 PIOBU support

Hello Rob, Could you please tell me if there are any improvements to be made to the patch? Best regards, Andrei On 20.11.2018 10:08, Andrei Stefanescu - M50506 wrote: > This patch describes the compatible and the device tree > bindings necessary for the SAMA5D2 PIOBU GPIO. > > Signed-off-by:

Re: [patch 0/2 for-4.20] mm, thp: fix remote access and allocation regressions

On 12/4/18 12:50 AM, David Rientjes wrote: > This fixes a 13.9% of remote memory access regression and 40% remote > memory allocation regression on Haswell when the local node is fragmented > for hugepage sized pages and memory is being faulted with either the thp > defrag setting of "always" or

Re: [PATCH v6 2/2] PCI: amlogic: Add the Amlogic Meson PCIe controller driver

On 2018/12/4 6:57, Bjorn Helgaas wrote: > On Mon, Dec 03, 2018 at 04:41:50PM +, Lorenzo Pieralisi wrote: >> On Thu, Nov 22, 2018 at 04:53:54PM +0800, Hanjie Lin wrote: >> >> [...] >> >>> +static int meson_pcie_rd_own_conf(struct pcie_port *pp, int where, int >>> size, >>> +

[PATCH 4.14 122/146] perf/x86/intel: Move branch tracing setup to the Intel-specific source file

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa commit ed6101bbf6266ee83e620b19faa7c6ad56bb41ab upstream. Moving branch tracing setup to Intel core object into separate intel_pmu_bts_config function, because it's Intel specific.

[PATCH 4.14 128/146] ALSA: sparc: Fix invalid snd_free_pages() at error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 9a20332ab373b1f8f947e0a9c923652b32dab031 upstream. Some spurious calls of snd_free_pages() have been overlooked and remain in the error paths of sparc cs4231 driver code.

[PATCH 4.14 121/146] x86/fpu: Disable bottom halves while loading FPU registers

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit 68239654acafe6aad5a3c1dc7237e60accfebc03 upstream. The sequence fpu->initialized = 1; /* step A */ preempt_disable();/* step B */

[PATCH 4.14 134/146] dmaengine: at_hdmac: fix module unloading

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Richard Genoud commit 77e75fda94d2ebb86aa9d35fb1860f6395bf95de upstream. of_dma_controller_free() was not called on module onloading. This lead to a soft lockup: watchdog: BUG: soft lockup -

[PATCH 4.14 132/146] ARM: dts: rockchip: Remove @0 from the veyron memory node

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Heiko Stuebner commit 672e60b72bbe7aace88721db55b380b6a51fb8f9 upstream. The Coreboot version on veyron ChromeOS devices seems to ignore memory@0 nodes when updating the available memory and

[PATCH 4.14 130/146] ALSA: hda/realtek - fix headset mic detection for MSI MS-B171

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Anisse Astier commit 8cd65271f8e545ddeed10ecc2e417936bdff168e upstream. MSI Cubi N 8GL (MS-B171) needs the same fixup as its older model, the MS-B120, in order for the headset mic to be

[PATCH 4.14 135/146] btrfs: release metadata before running delayed refs

4.14-stable review patch. If anyone has any objections, please let me know. -- We want to release the unused reservation we have since it refills the delayed refs reserve, which will make everything go smoother when running the delayed refs if we're short on our reservation.

[PATCH 4.14 126/146] ALSA: ac97: Fix incorrect bit shift at AC97-SPSA control write

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 7194eda1ba0872d917faf3b322540b4f57f11ba5 upstream. The function snd_ac97_put_spsa() gets the bit shift value from the associated private_value, but it extracts too much;

[PATCH 4.14 108/146] x86/speculation: Provide IBPB always command line options

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner t...@linutronix.de commit 55a974021ec952ee460dc31ca08722158639de72 upstream Provide the possibility to enable IBPB always in combination with 'prctl' and 'seccomp'. Add the

[PATCH 4.14 141/146] iio:st_magn: Fix enable device after trigger

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Martin Kelly commit fe5192ac81ad0d4dfe1395d11f393f0513c15f7f upstream. Currently, we enable the device before we enable the device trigger. At high frequencies, this can cause interrupts that

[PATCH 4.14 143/146] mm: use swp_offset as key in shmem_replace_page()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Yu Zhao commit c1cb20d43728aa9b5393bd8d489bc85c142949b2 upstream. We changed the key of swap cache tree from swp_entry_t.val to swp_offset. We need to do so in shmem_replace_page() as well.

[PATCH 4.14 138/146] USB: usb-storage: Add new IDs to ums-realtek

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng commit a84a1bcc992f0545a51d2e120b8ca2ef20e2ea97 upstream. There are two new Realtek card readers require ums-realtek to work correctly. Add the new IDs to support them.

[PATCH 4.14 125/146] ALSA: wss: Fix invalid snd_free_pages() at error path

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 7b69154171b407844c273ab4c10b5f0ddcd6aa29 upstream. Some spurious calls of snd_free_pages() have been overlooked and remain in the error paths of wss driver code. Since

[PATCH 4.14 124/146] fs: fix lost error code in dio_complete

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Maximilian Heyne commit 41e817bca3acd3980efe5dd7d28af0e6f4ab9247 upstream. commit e259221763a40403d5bb232209998e8c45804ab8 ("fs: simplify the generic_write_sync prototype") reworked callers

[PATCH 4.14 117/146] btrfs: relocation: set trans to be NULL after ending transaction

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Pan Bian commit 42a657f57628402c73237547f0134e083e2f6764 upstream. The function relocate_block_group calls btrfs_end_transaction to release trans when update_backref_cache returns 1, and then

[PATCH 4.14 116/146] Btrfs: ensure path name is null terminated at btrfs_control_ioctl

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Filipe Manana commit f505754fd6599230371cb01b9332754ddc104be1 upstream. We were using the path name received from user space without checking that it is null terminated. While btrfs-progs is

[PATCH 4.9 22/50] xtensa: enable coprocessors that are being flushed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit 2958b66694e018c552be0b60521fec27e8d12988 upstream. coprocessor_flush_all may be called from a context of a thread that is different from the thread being flushed. In that

[PATCH 4.9 23/50] xtensa: fix coprocessor context offset definitions

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit 03bc996af0cc71c7f30c384d8ce7260172423b34 upstream. Coprocessor context offsets are used by the assembly code that moves coprocessor context between the individual fields of

[PATCH 4.9 15/50] net: skb_scrub_packet(): Scrub offload_fwd_mark

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Petr Machata [ Upstream commit b5dd186d10ba59e6b5ba60e42b3b083df56df6f3 ] When a packet is trapped and the corresponding SKB marked as already-forwarded, it retains this marking even after it

[PATCH 4.14 144/146] Drivers: hv: vmbus: check the creation_status in vmbus_establish_gpadl()

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Dexuan Cui commit eceb05965489784f24bbf4d61ba60e475a983016 upstream. This is a longstanding issue: if the vmbus upper-layer drivers try to consume too many GPADLs, the host may return with an

[PATCH 4.9 01/50] mm/huge_memory: rename freeze_page() to unmap_page()

4.9-stable review patch. If anyone has any objections, please let me know. -- commit 906f9cdfc2a0800f13683f9e4ebdfd08c12ee81b upstream. The term "freeze" is used in several ways in the kernel, and in mm it has the particular meaning of forcing page refcount temporarily to 0.

[PATCH 4.9 11/50] mm/khugepaged: collapse_shmem() without freezing new_page

4.9-stable review patch. If anyone has any objections, please let me know. -- commit 87c460a0bded56195b5eb497d44709777ef7b415 upstream. khugepaged's collapse_shmem() does almost all of its work, to assemble the huge new_page from 512 scattered old pages, with the new_page's

[PATCH 4.9 19/50] kvm: mmu: Fix race in emulated page table writes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Junaid Shahid commit 0e0fee5c539b61fdd098332e0e2cc375d9073706 upstream. When a guest page table is updated via an emulated write, kvm_mmu_pte_write() is called to update the shadow PTE using

Re: [PATCH 3/3] arm64: ftrace: add cond_resched() to func ftrace_make_(call|nop)

Hi Steve, Arnd, On Tue, Dec 04, 2018 at 12:50:12AM -0500, Steven Rostedt wrote: > On Mon, 3 Dec 2018 22:51:52 +0100 > Arnd Bergmann wrote: > > On Mon, Dec 3, 2018 at 8:22 PM Will Deacon wrote: > > > On Fri, Nov 30, 2018 at 04:09:56PM +0100, Anders Roxell wrote: > > > > Both of those functions

[PATCH 4.9 16/50] rapidio/rionet: do not free skb before reading its length

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Pan Bian [ Upstream commit cfc435198f53a6fa1f656d98466b24967ff457d0 ] skb is freed via dev_kfree_skb_any, however, skb->len is read then. This may result in a use-after-free bug. Fixes:

[PATCH 4.9 25/50] perf/x86/intel: Move branch tracing setup to the Intel-specific source file

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa commit ed6101bbf6266ee83e620b19faa7c6ad56bb41ab upstream. Moving branch tracing setup to Intel core object into separate intel_pmu_bts_config function, because it's Intel specific.

[PATCH 4.9 17/50] s390/qeth: fix length check in SNMP processing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 9a764c1e59684c0358e16ccaafd870629f2cfe67 ] The response for a SNMP request can consist of multiple parts, which the cmd callback stages into a kernel buffer

[PATCH 4.9 03/50] mm/huge_memory: splitting set mapping+index before unfreeze

4.9-stable review patch. If anyone has any objections, please let me know. -- commit 173d9d9fd3ddae84c110fea8aedf1f26af6be9ec upstream. Huge tmpfs stress testing has occasionally hit shmem_undo_range()'s VM_BUG_ON_PAGE(page_to_pgoff(page) != index, page). Move the setting of

[PATCH 4.9 26/50] perf/x86/intel: Add generic branch tracing check to intel_pmu_has_bts()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Olsa commit 67266c1080ad56c31af72b9c18355fde8ccc124a upstream. Currently we check the branch tracing only by checking for the PERF_COUNT_HW_BRANCH_INSTRUCTIONS event of PERF_TYPE_HARDWARE

[PATCH 4.14 054/146] f2fs: fix to do sanity check with block address in main area

4.14-stable review patch. If anyone has any objections, please let me know. -- commit c9b60788fc760d136211853f10ce73dc152d1f4a upstream. This patch add to do sanity check with below field: - cp_pack_total_block_count - blkaddr of data/node - extent info - Overview BUG() in

[PATCH 4.14 049/146] f2fs: fix to do sanity check with secs_per_zone

4.14-stable review patch. If anyone has any objections, please let me know. -- commit 42bf546c1fe3f3654bdf914e977acbc2b80a5be5 upstream. As Wen Xu reported in below link: https://bugzilla.kernel.org/show_bug.cgi?id=200183 - Overview Divide zero in reset_curseg() when mounting

[PATCH 4.14 048/146] f2fs: introduce and spread verify_blkaddr

4.14-stable review patch. If anyone has any objections, please let me know. -- commit e1da7872f6eda977bd812346bf588c35e4495a1e upstream. This patch introduces verify_blkaddr to check meta/data block address with valid range to detect bug earlier. In addition, once we encounter

[PATCH 4.14 053/146] f2fs: fix to do sanity check with node footer and iblocks

4.14-stable review patch. If anyone has any objections, please let me know. -- commit e34438c903b653daca2b2a7de95aed46226f8ed3 upstream. This patch adds to do sanity check with below fields of inode to avoid reported panic. - node footer - iblocks

[PATCH v2 2/2] soc: fsl: dpio: use a cpumask to identify which cpus are unused

The current implementation of the dpio driver uses a static next_cpu variable to keep track of the index of the next cpu available. This approach does not handle well unbinding and binding dpio devices in a random order. For example, unbinding a dpio and then binding it again with the driver, will

[PATCH 4.14 059/146] net: skb_scrub_packet(): Scrub offload_fwd_mark

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Petr Machata [ Upstream commit b5dd186d10ba59e6b5ba60e42b3b083df56df6f3 ] When a packet is trapped and the corresponding SKB marked as already-forwarded, it retains this marking even after it

[PATCH v2 1/2] soc: fsl: dpio: cleanup the cpu array on dpaa2_io_down

The dpio_by_cpu array should not contain a reference to a freed dpaa2_io object. This patch adds the necessary cleanup in dpaa2_io_down. Signed-off-by: Ioana Ciornei --- Changes in v2: - none drivers/soc/fsl/dpio/dpio-service.c | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH 4.14 026/146] wil6210: missing length check in wmi_set_ie

4.14-stable review patch. If anyone has any objections, please let me know. -- commit b5a8ffcae4103a9d823ea3aa3a761f65779fbe2a upstream. Add a length check in wmi_set_ie to detect unsigned integer overflow. Signed-off-by: Lior David Signed-off-by: Maya Erez Signed-off-by:

[PATCH 4.14 044/146] f2fs: check blkaddr more accuratly before issue a bio

4.14-stable review patch. If anyone has any objections, please let me know. -- commit 0833721ec3658a4e9d5e58b6fa82cf9edc431e59 upstream. This patch check blkaddr more accuratly before issue a write or read bio. Signed-off-by: Yunlei He Reviewed-by: Chao Yu Signed-off-by:

[PATCH 4.14 046/146] f2fs: enhance sanity_check_raw_super() to avoid potential overflow

4.14-stable review patch. If anyone has any objections, please let me know. -- commit 0cfe75c5b011994651a4ca6d74f20aa997bfc69a upstream. In order to avoid the below overflow issue, we should have checked the boundaries in superblock before reaching out to allocation. As Linus

[PATCH 4.14 050/146] f2fs: Add sanity_check_inode() function

4.14-stable review patch. If anyone has any objections, please let me know. -- This was done as part of commit 5d64600d4f33 "f2fs: avoid bug_on on corrupted inode" upstream, but the specific check that commit added is not applicable to 4.14. Cc: Jaegeuk Kim Cc: Chao Yu

Re: [PATCH AUTOSEL 4.14 25/35] iomap: sub-block dio needs to zeroout beyond EOF

On Mon, Dec 03, 2018 at 11:22:46PM +0159, Thomas Backlund wrote: Den 2018-12-03 kl. 11:22, skrev Sasha Levin: This is a case where theory collides with the real world. Yes, our QA is lacking, but we don't have the option of not doing the current process. If we stop backporting until a future

RE: [PATCH v3 0/4] Correct dma pool for imx-sdma

Hello Vinod, This patch set test by Lucas and no any other comment received yet, do you have comments and help to push it on 4.19 stable tree? > -Original Message- > From: Robin Gong > Sent: 2018年11月20日 17:09 > To: 'Lucas Stach' ; vk...@kernel.org > Cc: dmaeng...@vger.kernel.org;

Re: [PATCH] mm/alloc: fallback to first node if the wanted node offline

On Tue, Dec 4, 2018 at 3:22 PM Michal Hocko wrote: > > On Tue 04-12-18 11:05:57, Pingfan Liu wrote: > > During my test on some AMD machine, with kexec -l nr_cpus=x option, the > > kernel failed to bootup, because some node's data struct can not be > > allocated, > > e.g, on x86, initialized by

Re: [PATCH v6 3/9] spi: Add a driver for the Freescale/NXP QuadSPI controller

Hi Han, On 03.12.18 21:54, Han Xu wrote: [...] >>> >>> Hi Schrempf, I am reviewing and testing on some i.MX platforms, please >> hold on for a while for the result. >> >> Okay, thanks! I'm looking forward to see the results. > > Hi Schrempf, I am good with the patch set(with warning fix) and it

Re: [PATCH] dt-bindings: ti-tsc-adc: Add new compatible for AM654 SoCs

Hi, On 19/11/18 3:15 PM, Vignesh R wrote: > AM654 SoCs has ADC IP which is similar to AM335x. Add new compatible to > handle AM654 SoCs. Also, it seems that existing compatible strings used > in the kernel DTs were never documented. So, document them now. > > Signed-off-by: Vignesh R > ---

Re: [PATCH 2/3] mm/vmscan: Enable kswapd to reclaim low-protected memory

On 2018/12/4 PM 3:25, Michal Hocko wrote: > On Tue 04-12-18 10:40:29, Xunlei Pang wrote: >> On 2018/12/4 AM 1:22, Michal Hocko wrote: >>> On Mon 03-12-18 23:20:31, Xunlei Pang wrote: On 2018/12/3 下午7:56, Michal Hocko wrote: > On Mon 03-12-18 16:01:18, Xunlei Pang wrote: >> There may

Re: [PATCH] cpufreq: nforce2: Remove meaningless return

On Tue, Dec 4, 2018 at 2:15 AM Frank Lee wrote: > > On Mon, Dec 3, 2018 at 5:14 PM Rafael J. Wysocki wrote: > > > > On Fri, Nov 30, 2018 at 3:26 PM Yangtao Li wrote: > > > > > > In a function whose return type is void, returning on the last line is > > > not required.So remove it.Also move the

Re: [PATCH] mm/alloc: fallback to first node if the wanted node offline

On Tue 04-12-18 16:20:32, Pingfan Liu wrote: > On Tue, Dec 4, 2018 at 3:22 PM Michal Hocko wrote: > > > > On Tue 04-12-18 11:05:57, Pingfan Liu wrote: > > > During my test on some AMD machine, with kexec -l nr_cpus=x option, the > > > kernel failed to bootup, because some node's data struct can

[PATCH] ARM: dts: imx6qdl-sabresd: add egalax touch screen support on i2c2 bus

Add egalax touch screen support on i2c2 bus. Signed-off-by: Anson Huang --- arch/arm/boot/dts/imx6qdl-sabresd.dtsi | 16 1 file changed, 16 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi index 6e46a19..d7389b5 100644

[PATCH] platform/x86: touchscreen_dmi: Add info for the Mediacom Flexbook Edge 11

Add a DMI match for the Mediacom Flexbook Edge 11, this is the same hw as the Trekstor Primebook C11, so we use the same settings. Reported-by: rmbg Signed-off-by: Hans de Goede --- drivers/platform/x86/touchscreen_dmi.c | 8 1 file changed, 8 insertions(+) diff --git

Re: [PATCH v3 2/8] mfd / platform: cros_ec: move lightbar attributes to its own driver.

On Mon, 03 Dec 2018, Enric Balletbo i Serra wrote: > On 3/12/18 11:36, Lee Jones wrote: > > On Tue, 27 Nov 2018, Enric Balletbo i Serra wrote: > > > >> The entire way how cros sysfs attibutes are created is broken. > >> cros_ec_lightbar should be its own driver and its attributes should be > >>

Re: [PATCH 00/13 v2] Regulator ena_gpiod fixups

Hi Marek, first, thanks a *lot* for testing this, it is is much, much appreciated! On Mon, Dec 3, 2018 at 3:35 PM Marek Szyprowski wrote: > The idea is good imho, but it looks that there are some missing cases in > the code. Here are some logs from the boards I have access to: OK let's fix

Re: [PATCH] Revert "exec: make de_thread() freezable (was: Re: Linux 4.20-rc4)

* Michal Hocko wrote: > I dunno. I do not use hibernation. I am a heavy user of the suspend > though. I s2ram all the time. And I have certainly experienced cases > where suspend has failed and I onlyi found out later when I've picked > up my laptop from my heat up bag. Nothing fatal has

Re: [PATCH 05/12] PCI: aardvark: add suspend to RAM support

On Mon, Dec 03, 2018 at 11:00:20PM +0100, Rafael J. Wysocki wrote: > On Monday, December 3, 2018 4:38:46 PM CET Miquel Raynal wrote: > > Hi Lorenzo, > > > > Lorenzo Pieralisi wrote on Mon, 3 Dec 2018 > > 10:27:08 +: > > > > > [+Rafael, Sudeep] > > > > > > On Fri, Nov 23, 2018 at 03:18:24PM

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