[PATCH 4.19 008/187] f2fs: fix to avoid deadlock in f2fs_read_inline_dir()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aadcef64b22f668c1a107b86d3521d9cac915c24 ] As Jiqun Li reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=202883 sometimes, dead lock when make system call

[PATCH 4.19 009/187] tracing: kdb: Fix ftdump to not sleep

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 31b265b3baaf55f209229888b7ffea523ddab366 ] As reported back in 2016-11 [1], the "ftdump" kdb command triggers a BUG for "sleeping function called from invalid context". kdb's

[PATCH 4.19 030/187] mm/vmalloc.c: fix kernel BUG at mm/vmalloc.c:512!

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit afd07389d3f4933c7f7817a92fb5e053d59a3182 ] One of the vmalloc stress test case triggers the kernel BUG(): [60.562151] [ cut here ] [60.562154] kernel

[PATCH 4.19 018/187] scsi: hisi_sas: Set PHY linkrate when disconnected

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit efdcad62e7b8a02f5ccca57806dce1482ac8 ] When the PHY comes down, we currently do not set the negotiated linkrate: root@(none)$ pwd /sys/class/sas_phy/phy-0:0 root@(none)$ more

[PATCH 4.19 027/187] mm,oom: dont kill global init via memory.oom.group

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d342a0b38674867ea67fde47b0e1e60ffe9f17a2 ] Since setting global init process to some memory cgroup is technically possible, oom_kill_memcg_member() must check it. Tasks in /test1

Re: [RFC PATCH 0/7] Early task context tracking

On Wed, Apr 03, 2019 at 05:01:02PM -0700, Andy Lutomirski wrote: > I would much rather do the opposite: completely remove context > tracking from the asm and, instead, stick it into the C code. We'd > need to make sure that the C code is totally immune from tracing, > kprobes, etc, but it would

[PATCH 4.19 051/187] crypto: cavium/zip - fix collision with generic cra_driver_name

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 41798036430015ad45137db2d4c213cd77fd0251 ] The cavium/zip implementation of the deflate compression algorithm is incorrectly being registered under the generic driver name, which

[PATCH 4.19 049/187] mt76: fix a leaked reference by adding a missing of_node_put

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 34e022d8b780a03902d82fb3997ba7c7b1f40c81 ] The call to of_find_node_by_phandle returns a node pointer with refcount incremented thus it must be explicitly decremented after the last

[PATCH 4.19 034/187] fs/file.c: initialize init_files.resize_wait

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5704a06810682683355624923547b41540e2801a ] (Taken from https://bugzilla.kernel.org/show_bug.cgi?id=200647) 'get_unused_fd_flags' in kthread cause kernel crash. It works fine on

[PATCH 4.19 024/187] mm/cma.c: cma_declare_contiguous: correct err handling

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0d3bd18a5efd66097ef58622b898d3139790aa9d ] In case cma_init_reserved_mem failed, need to free the memblock allocated by memblock_reserve or memblock_alloc_range. Quote Catalin's

[PATCH 4.19 025/187] mm/page_ext.c: fix an imbalance with kmemleak

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0c81585499601acd1d0e1cbf424cabfaee60628c ] After offlining a memory block, kmemleak scan will trigger a crash, as it encounters a page ext address that has already been freed during

[PATCH 4.19 048/187] wil6210: check null pointer in _wil_cfg80211_merge_extra_ies

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit de77a53c2d1e8fb3621e63e8e1f0f0c9a1a99ff7 ] ies1 or ies2 might be null when code inside _wil_cfg80211_merge_extra_ies access them. Add explicit check for null and make sure ies1/ies2

[PATCH 4.19 039/187] cifs: Accept validate negotiate if server return NT_STATUS_NOT_SUPPORTED

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 969ae8e8d4ee54c99134d3895f2adf96047f5bee ] Old windows version or Netapp SMB server will return NT_STATUS_NOT_SUPPORTED since they do not allow or implement

[PATCH 4.19 070/187] IB/mlx4: Increase the timeout for CM cache

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2612d723aadcf8281f9bf8305657129bd9f3cd57 ] Using CX-3 virtual functions, either from a bare-metal machine or pass-through from a VM, MAD packets are proxied through the PF driver.

[PATCH 4.19 054/187] scsi: core: replace GFP_ATOMIC with GFP_KERNEL in scsi_scan.c

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1749ef00f7312679f76d5e9104c5d1e22a829038 ] We had a test-report where, under memory pressure, adding LUNs to the systems would fail (the tests add LUNs strictly in sequence): [

[PATCH 4.19 044/187] jbd2: fix invalid descriptor block checksum

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6e876c3dd205d30b0db6850e97a03d75457df007 ] In jbd2_journal_commit_transaction(), if we are in abort mode, we may flush the buffer without setting descriptor block checksum by goto

Re: [PATCH] staging: rtl8192u: remove redundant null check on array 'data'

On Thu, Apr 04, 2019 at 10:32:57AM +0100, Colin King wrote: > diff --git a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c > b/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c > index 944c8894f9ff..c4a4f118f547 100644 > --- a/drivers/staging/rtl8192u/ieee80211/ieee80211_softmac.c >

[PATCH 4.19 055/187] kbuild: invoke syncconfig if include/config/auto.conf.cmd is missing

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 9390dff66a52d1a60c6e517d8fa6cdbdffc83cb1 ] If include/config/auto.conf.cmd is lost for some reasons, it is not self-healing, so the top Makefile misses to run syncconfig. Move

[PATCH 4.19 060/187] iommu/io-pgtable-arm-v7s: Only kmemleak_ignore L2 tables

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 032ebd8548c9d05e8d2bdc7a7ec2fe29454b0ad0 ] L1 tables are allocated with __get_dma_pages, and therefore already ignored by kmemleak. Without this, the kernel would print this error

[PATCH 4.19 081/187] mwifiex: dont advertise IBSS features without FW support

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6f21ab30469d670de620f758330aca9f3433f693 ] As it is, doing something like # iw phy phy0 interface add foobar type ibss on a firmware that doesn't have ad-hoc support just yields

[PATCH 4.19 058/187] serial: 8250_pxa: honor the port number from devicetree

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fe9ed6d2483fda55465f32924fb15bce0fac3fac ] Like the other OF-enabled drivers, use the port number from the firmware if the devicetree specifies an alias: aliases { ...

[PATCH 4.19 072/187] perf annotate: Fix getting source line failure

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 11db1ad4513d6205d2519e1a30ff4cef746e3243 ] The output of "perf annotate -l --stdio xxx" changed since commit 425859ff0de33 ("perf annotate: No need to calculate notes->start twice")

[PATCH 4.19 082/187] perf report: Dont shadow inlined symbol with different addr range

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7346195e8643482968f547483e0d823ec1982fab ] We can't assume inlined symbols with the same name are equal, because their address range may be different. This will cause the symbols

[PATCH 4.19 079/187] drm/amd/display: Clear stream->mode_changed after commit

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d8d2f174bcc2c26c3485c70e0c6fe22b27bce739 ] [Why] The stream->mode_changed flag can persist in the following sequence of atomic commits: Commit 1: Enable CRTC0 (mode_changed =

Re: [PATCHv3] x86/boot/KASLR: skip the specified crashkernel region

On Wed, Apr 3, 2019 at 11:10 AM Baoquan He wrote: > > On 04/03/19 at 10:58am, Pingfan Liu wrote: > > On Tue, Apr 2, 2019 at 4:08 PM Baoquan He wrote: > > > > > > > +/* handle crashkernel=x@y or =range1:size1[,range2:size2,...]@offset > > > > options */ > > > > +static void

[PATCH 4.19 099/187] iwlwifi: pcie: fix emergency path

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c6ac9f9fb98851f47b978a9476594fc3c477a34d ] Allocator swaps the pending requests with 0 when it starts working. This means that relying on it n RX path to decide if to move to

[PATCH 4.19 090/187] media: mtk-jpeg: Correct return type for mem2mem buffer helpers

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1b275e4e8b70dbff9850874b30831c1bd8d3c504 ] Fix the assigned type of mem2mem buffer handling API. Namely, these functions: v4l2_m2m_next_buf v4l2_m2m_last_buf v4l2_m2m_buf_remove

[PATCH 4.19 088/187] media: s5p-g2d: Correct return type for mem2mem buffer helpers

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 30fa627b32230737bc3f678067e2adfecf956987 ] Fix the assigned type of mem2mem buffer handling API. Namely, these functions: v4l2_m2m_next_buf v4l2_m2m_last_buf v4l2_m2m_buf_remove

[PATCH 4.19 075/187] efi: cper: Fix possible out-of-bounds access

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 45b14a4ffcc1e0b5caa246638f942cbe7eaea7ad ] When checking a generic status block, we iterate over all the generic data blocks. The loop condition only checks that the start of the

[PATCH 4.19 086/187] media: s5p-jpeg: Correct return type for mem2mem buffer helpers

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4a88f89885c7cf65c62793f385261a6e3315178a ] Fix the assigned type of mem2mem buffer handling API. Namely, these functions: v4l2_m2m_next_buf v4l2_m2m_last_buf v4l2_m2m_buf_remove

[PATCH 4.19 076/187] s390/ism: ignore some errors during deregistration

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0ff06c44efeede4acd068847d3bf8cf894b6c664 ] Prior to dma unmap/free operations the ism driver tries to ensure that the memory is no longer accessed by the HW. When errors during

[PATCH 4.19 078/187] scsi: fcoe: make use of fip_mode enum complete

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8beb90aaf334a6efa3e924339926b5f93a234dbb ] commit 1917d42d14b7 ("fcoe: use enum for fip_mode") introduces a separate enum for the fip_mode that shall be used during initialisation

Re: [PATCH v2 3/5] locking/qspinlock: Introduce CNA into the slow path of qspinlock

On Thu, Apr 04, 2019 at 07:05:24AM +0200, Juergen Gross wrote: > Without PARAVIRT_SPINLOCK this would be just an alternative() then? That could maybe work yes. This is all early enough. > Maybe the resulting code would be much more readable if we'd just > make PARAVIRT_SPINLOCK usable without

[PATCH 4.19 093/187] vfs: fix preadv64v2 and pwritev64v2 compat syscalls with offset == -1

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cc4b1242d7e3b42eed73881fc749944146493e4f ] The preadv2 and pwritev2 syscalls are supposed to emulate the readv and writev syscalls when offset == -1. Therefore the compat code

[PATCH 4.19 102/187] kprobes: Prohibit probing on bsearch()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 02106f883cd745523f7766d90a739f983f19e650 ] Since kprobe breakpoing handler is using bsearch(), probing on this routine can cause recursive breakpoint problem. int3 ->do_int3()

[PATCH 4.19 089/187] media: mx2_emmaprp: Correct return type for mem2mem buffer helpers

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8d20dcefe471763f23ad538369ec65b51993 ] Fix the assigned type of mem2mem buffer handling API. Namely, these functions: v4l2_m2m_next_buf v4l2_m2m_last_buf v4l2_m2m_buf_remove

[PATCH 4.19 096/187] jbd2: fix race when writing superblock

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 538bcaa6261b77e71d37f5596c33127c1a3ec3f7 ] The jbd2 superblock is lockless now, so there is probably a race condition between writing it so disk and modifing contents of it, which

[GIT PULL] MFD fixes for v5.1

Linus, Enjoy! The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: Linux 5.1-rc1 (2019-03-17 14:22:26 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-fixes-5.1 for you to fetch changes up to

[PATCH] usb: musb: Disable pullup in gadget setup

The pullup may be already enabled before the driver is initialized. It has to be disabled at init time, as we cannot guarantee that a gadget driver will be bound to the UDC. Signed-off-by: Paul Cercueil --- drivers/usb/musb/musb_gadget.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 4.19 117/187] iw_cxgb4: fix srqidx leak during connection abort

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f368ff188ae4b3ef6f740a15999ea0373261b619 ] When an application aborts the connection by moving QP from RTS to ERROR, then iw_cxgb4's modify_rc_qp() RTS->ERROR logic sets the

[PATCH 4.19 108/187] ath10k: fix shadow register implementation for WCN3990

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1863008369ae0407508033b4b00f98b985adeb15 ] WCN3990 supports shadow registers write operation support for copy engine for regular operation in powersave mode. Since WCN3990 is a

[PATCH 4.19 119/187] fbdev: fbmem: fix memory access if logo is bigger than the screen

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a5399db139cb3ad9b8502d8b1bd02da9ce0b9df0 ] There is no clipping on the x or y axis for logos larger that the framebuffer size. Therefore: a logo bigger than screen size leads to

[PATCH 4.19 120/187] cdrom: Fix race condition in cdrom_sysctl_register

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit f25191bb322dec8fa2979ecb8235643aa42470e1 ] The following traceback is sometimes seen when booting an image in qemu: [ 54.608293] cdrom: Uniform CD-ROM driver Revision: 3.20 [

[PATCH 4.19 134/187] sched/core: Use READ_ONCE()/WRITE_ONCE() in move_queued_task()/task_rq_lock()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit c546951d9c9300065bad253ecdf1ac59ce9d06c8 ] move_queued_task() synchronizes with task_rq_lock() as follows: move_queued_task() task_rq_lock() [S]

[PATCH 4.19 116/187] net: marvell: mvpp2: fix stuck in-band SGMII negotiation

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 316734fdcf70900a83065360cff11a5826919067 ] It appears that the mvpp22 can get stuck with SGMII negotiation. The symptoms are that in-band negotiation never completes and the

[PATCH 4.19 139/187] mt7601u: bump supported EEPROM version

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3bd1505fed71d834f45e87b32ff07157fdda47e0 ] As reported by Michael eeprom 0d is supported and work with the driver. Dump of /sys/kernel/debug/ieee80211/phy1/mt7601u/eeprom_param

Re: [PATCH] remoteproc: silence an uninitialized variable warning

On Thu, Apr 04, 2019 at 02:47:39PM +0530, Mukesh Ojha wrote: > > On 4/4/2019 2:12 PM, Dan Carpenter wrote: > > Smatch complains that "ret" might be uninitialized. I can see why it > > generates the warning, but I don't know if it's actually possible. > > Anyway initializing "ret" here is

[PATCH 4.19 127/187] platform/x86: intel_pmc_core: Fix PCH IP sts reading

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0e68eeea9894feeba2edf7ec63e4551b87f39621 ] A previous commit "platform/x86: intel_pmc_core: Make the driver PCH family agnostic " provided better abstraction to this driver but has

[PATCH 4.19 126/187] e1000e: Exclude device from suspend direct complete optimization

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 59f58708c5047289589cbf6ee95146b76cf57d1e ] e1000e sets different WoL settings in system suspend callback and runtime suspend callback. The suspend direct complete optimization

[PATCH 4.19 128/187] i2c: of: Try to find an I2C adapter matching the parent

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e814e688413aabd7b0d75e2a8ed1caa472951dec ] If an I2C adapter doesn't match the provided device tree node, also try matching the parent's device tree node. This allows finding an

[PATCH 4.19 124/187] perf/aux: Make perf_event accessible to setup_aux()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 840018668ce2d96783356204ff282d6c9b0e5f66 ] When pmu::setup_aux() is called the coresight PMU needs to know which sink to use for the session by looking up the information in the

[PATCH 4.19 130/187] iwlwifi: mvm: fix RFH config command with >=10 CPUs

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit dbf592f3d14fb7d532cb7c820b1065cf33e02aaa ] If we have >=10 (logical) CPUs, our command size exceeds the internal buffer size and the command fails; fix that by using

[PATCH 4.19 143/187] bpf: fix missing prototype warnings

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 116bfa96a255123ed209da6544f74a4f2eaca5da ] Compiling with W=1 generates warnings: CC kernel/bpf/core.o kernel/bpf/core.c:721:12: warning: no previous prototype for

[PATCH 4.19 155/187] perf script python: Add trace_context extension module to sys.modules

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit cc437642255224e4140fed1f3e3156fc8ad91903 ] In Python3, the result of PyModule_Create (called from scripts/python/Perf-Trace-Util/Context.c) is not automatically added to

Re: [PATCH v2] locking/lockdep: Zap lock classes even with lock debugging disabled

On Wed, Apr 03, 2019 at 04:35:52PM -0700, Bart Van Assche wrote: > Commit a0b0fd53e1e6 ("locking/lockdep: Free lock classes that are no longer > in use") changed the behavior of lockdep_free_key_range() from > unconditionally zapping lock classes into only zapping lock classes if > debug_lock ==

[PATCH 4.19 152/187] usb: dwc3: gadget: Fix OTG events when gadget driver isnt loaded

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 169e3b68cadb5775daca009ced4faf01ffd97dcf ] On v3.10a in dual-role mode, if port is in device mode and gadget driver isn't loaded, the OTG event interrupts don't come through. It

[PATCH 4.19 175/187] brcmfmac: Use firmware_request_nowarn for the clm_blob

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4ad0be160544ffbdafb7cec39bb8e6dd0a97317a ] The linux-firmware brcmfmac firmware files contain an embedded table with per country allowed channels and strength info. For recent

[PATCH 4.19 161/187] hpet: Fix missing = character in the __setup() code of hpet_mmap_enable

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24d48a61f230da130cc2ec2e526eacf229e3 ] Commit '3d035f580699 ("drivers/char/hpet.c: allow user controlled mmap for user processes")' introduced a new kernel command line

[PATCH 4.19 159/187] HID: intel-ish: ipc: handle PIMR before ish_wakeup also clear PISR busy_clear bit

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2edefc056e4f0e6ec9508dd1aca2c18fa320efef ] Host driver should handle interrupt mask register earlier than wake up ish FW else there will be conditions when FW interrupt comes, host

[PATCH 4.19 170/187] pinctrl: meson: meson8b: add the eth_rxd2 and eth_rxd3 pins

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6daae00243e622dd3feec7965bfe421ad6dd317e ] Gigabit Ethernet requires the Ethernet TXD0..3 and RXD0..3 data lines. Add the missing eth_rxd2 and eth_rxd3 definitions so we don't have

[PATCH 4.19 158/187] soc/tegra: fuse: Fix illegal free of IO base address

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 51294bf6b9e897d595466dcda5a3f2751906a200 ] On cases where device tree entries for fuse and clock provider are in different order, fuse driver needs to defer probing. This leads to

[PATCH 4.19 151/187] ALSA: dice: add support for Solid State Logic Duende Classic/Mini

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b2e9e1c8810ee05c95f4d55800b8afae70ab01b4 ] Duende Classic was produced by Solid State Logic in 2006, as a first model of Duende DSP series. The following model, Duende Mini was

[PATCH 4.19 148/187] tty: increase the default flip buffer limit to 2*640K

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7ab57b76ebf632bf2231ccabe26bea33868118c6 ] We increase the default limit for buffer memory allocation by a factor of 10 to 640K to prevent data loss when using fast serial

[PATCH 4.19 173/187] x86/build: Specify elf_i386 linker emulation explicitly for i386 objects

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 927185c124d62a9a4d35878d7f6d432a166b74e3 ] The kernel uses the OUTPUT_FORMAT linker script command in it's linker scripts. Most of the time, the -m option is passed to the linker

[PATCH 4.19 149/187] powerpc/pseries: Perform full re-add of CPU for topology update post-migration

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 81b61324922c67f73813d8a9c175f3c153f6a1c6 ] On pseries systems, performing a partition migration can result in altering the nodes a CPU is assigned to on the destination system. For

[PATCH 4.19 145/187] powerpc/64s: Clear on-stack exception marker upon exception return

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit eddd0b332304d554ad6243942f87c2fcea98c56b ] The ppc64 specific implementation of the reliable stacktracer, save_stack_trace_tsk_reliable(), bails out and reports an "unreliable

[PATCH 4.19 144/187] selftests/bpf: skip verifier tests for unsupported program types

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8184d44c9a577a2f1842ed6cc844bfd4a9981d8e ] Use recently introduced bpf_probe_prog_type() to skip tests in the test_verifier() if bpf_verify_program() fails. The skipped test is

[PATCH 4.19 146/187] cgroup/pids: turn cgroup_subsys->free() into cgroup_subsys->release() to fix the accounting

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 51bee5abeab2058ea5813c5615d6197a23dbf041 ] The only user of cgroup_subsys->free() callback is pids_cgrp_subsys which needs pids_free() to uncharge the pid. However, ->free() is

[PATCH 4.19 184/187] net: stmmac: Avoid one more sometimes uninitialized Clang warning

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1f5d861f7fefa971b2c6e766f77932c86419a319 ] When building with -Wsometimes-uninitialized, Clang warns: drivers/net/ethernet/stmicro/stmmac/stmmac_ptp.c:111:2: error: variable 'ns'

[PATCH 4.19 182/187] Input: soc_button_array - fix mapping of the 5th GPIO in a PNP0C40 device

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e9eb788f9442d1b5d93efdb30c3be071ce8a22b1 ] The Microsoft documenation for the PNP0C40 device aka the "Windows-compatible button array" describes the 5th GpioInt listed in the

[PATCH 4.19 181/187] dmaengine: tegra: avoid overflow of byte tracking

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e486df39305864604b7e25f2a95d51039517ac57 ] The dma_desc->bytes_transferred counter tracks the number of bytes moved by the DMA channel. This is then used to calculate the

Re: [PATCH RFC] gpio: pca953x: Configure wake-up path when wake-up is enabled

Hi Ulf, On Thu, Apr 4, 2019 at 10:55 AM Ulf Hansson wrote: > On Wed, 20 Mar 2019 at 11:39, Geert Uytterhoeven > wrote: > > If a device is part of the wake-up path, it should indicate this by > > setting its power.wakeup_path field. This allows the genpd core code to > > keep the device enabled

Re: [PATCH] axxia-i2c: use auto cmd for last message

Hello Wolfram, On 03/04/2019 22:54, Wolfram Sang wrote: >> Some recent commits to this driver were trying to make sure the TSS >> interrupt is not generated on busy system due to 25ms timer expiring >> between commands. It can still happen, however if STOP command is not >> issued on time at the

[PATCH 4.19 179/187] clk: meson: clean-up clock registration

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8d9981efbcab066d17af4d3c85c169200f6f78df ] Order, ids and size between the table of regmap clocks and the onecell data table could be different. Set regmap pointer in all the

[PATCH 4.19 162/187] cpu/hotplug: Mute hotplug lockdep during init

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ce48c457b95316b9a01b5aa9d4456ce820df94b4 ] Since we've had: commit cb538267ea1e ("jump_label/lockdep: Assert we hold the hotplug lock for _cpuslocked() operations") we've been

[PATCH 4.19 168/187] media: s5p-jpeg: Check for fmt_ver_flag when doing fmt enumeration

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 49710c32cd9d6626a77c9f5f978a5f58cb536b35 ] Previously when doing format enumeration, it was returning all formats supported by driver, even if they're not supported by hw. Add

[PATCH 5.0 008/246] apparmor: fix double free when unpack of secmark rules fails

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d8dbb581d4f86a2ac669c056fc71a28ebeb367f4 ] if secmark rules fail to unpack a double free happens resulting in the following oops [ 1295.584074] audit: type=1400

[PATCH 5.0 011/246] net/mlx5: Avoid panic when setting vport rate

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 24319258660a84dd77f4be026a55b10a12524919 ] If we try to set VFs rate on a VF (not PF) net device, the kernel will be crash. The commands are show as below: $ echo 2 >

[PATCH 5.0 002/246] CIFS: fix POSIX lock leak and invalid ptr deref

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bc31d0cdcfbadb6258b45db97e93b1c83822ba33 ] We have a customer reporting crashes in lock_get_status() with many "Leaked POSIX lock" messages preceeding the crash. Leaked POSIX lock

[PATCH 5.0 007/246] f2fs: fix to avoid deadlock in f2fs_read_inline_dir()

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aadcef64b22f668c1a107b86d3521d9cac915c24 ] As Jiqun Li reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=202883 sometimes, dead lock when make system call

[PATCH 5.0 004/246] nvme-loop: init nvmet_ctrl fatal_err_work when allocate

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d11de63f2b519f0a162b834013b6d3a46dbf3886 ] After commit 4d43d395fe (workqueue: Try to catch flush_work() without INIT_WORK()), it can cause warning when delete nvme-loop device,

[PATCH 5.0 009/246] tracing: kdb: Fix ftdump to not sleep

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 31b265b3baaf55f209229888b7ffea523ddab366 ] As reported back in 2016-11 [1], the "ftdump" kdb command triggers a BUG for "sleeping function called from invalid context". kdb's

[PATCH 5.0 024/246] x86/hyperv: Fix kernel panic when kexec on HyperV

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 179fb36abb097976997f50733d5b122a29158cba ] After commit 68bb7bfb7985 ("X86/Hyper-V: Enable IPI enlightenments"), kexec fails with a kernel panic: kexec_core: Starting new kernel

[PATCH 5.0 021/246] scsi: hisi_sas: Set PHY linkrate when disconnected

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit efdcad62e7b8a02f5ccca57806dce1482ac8 ] When the PHY comes down, we currently do not set the negotiated linkrate: root@(none)$ pwd /sys/class/sas_phy/phy-0:0 root@(none)$ more

[PATCH] staging: rtl8192u: remove redundant null check on array 'data'

From: Colin Ian King The NULL check on ram->u.wpa_ie.data is redudant as data is zero-length array and is not a pointer, so it can't be null. Remove the check. Addresses-Coverity: ("Array compared against 0") Signed-off-by: Colin Ian King ---

[PATCH 5.0 027/246] mm/cma.c: cma_declare_contiguous: correct err handling

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0d3bd18a5efd66097ef58622b898d3139790aa9d ] In case cma_init_reserved_mem failed, need to free the memblock allocated by memblock_reserve or memblock_alloc_range. Quote Catalin's

[PATCH 5.0 019/246] enic: fix build warning without CONFIG_CPUMASK_OFFSTACK

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 43d281662fdb46750d49417559b71069f435298d ] The enic driver relies on the CONFIG_CPUMASK_OFFSTACK feature to dynamically allocate a struct member, but this is normally intended for

[PATCH 5.0 017/246] sysctl: handle overflow for file-max

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 32a5ad9c22852e6bd9e74bdec5934ef9d1480bc5 ] Currently, when writing echo 18446744073709551616 > /proc/sys/fs/file-max /proc/sys/fs/file-max will overflow and be set to 0. That

[PATCH 5.0 014/246] clk: ti: clkctrl: Fix clkdm_name regression for TI_CLK_CLKCTRL_COMPAT

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d17a718db40df2548e99a62dc3d7e5e2b38143cc ] Commit a72d785021cb ("clk: ti: Prepare for remove of OF node name") changed the code to use kasprintf() for provider->clkdm_name but also

[PATCH 5.0 015/246] gpio: gpio-omap: fix level interrupt idling

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d01849f7deba81f4959fd9e51bf20dbf46987d1c ] Tony notes that the GPIO module does not idle when level interrupts are in use, as the wakeup appears to get stuck. After extensive

[PATCH 5.0 018/246] net: stmmac: Avoid sometimes uninitialized Clang warnings

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit df103170854e87124ee7bdd2bca64b178e653f97 ] When building with -Wsometimes-uninitialized, Clang warns: drivers/net/ethernet/stmicro/stmmac/stmmac_main.c:495:3: warning: variable 'ns'

[PATCH 5.0 042/246] cifs: use correct format characters

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 259594bea574e515a148171b5cd84ce5cbdc028a ] When compiling with -Wformat, clang emits the following warnings: fs/cifs/smb1ops.c:312:20: warning: format specifies type 'unsigned

[PATCH 5.0 030/246] docs/core-api/mm: fix user memory accessors formatting

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bc8ff3ca6589d63c6d10f5ee8bed38f74851b469 ] The descriptions of userspace memory access functions had minor issues with formatting that made kernel-doc unable to properly detect the

Re: [PATCH v2] Staging: rtlwifi: Remove unwanted parentheses

You should probably update the subject line because now it's not just about parentheses any more. [PATCH v2] Staging: rtlwifi: clean up crc16_ccitt() So the one thing per patch rule is a little bit about selling your patch. We never allow "Clean up whole_file.c" but we do sometimes allow "Clean

[PATCH 5.0 039/246] fs/file.c: initialize init_files.resize_wait

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5704a06810682683355624923547b41540e2801a ] (Taken from https://bugzilla.kernel.org/show_bug.cgi?id=200647) 'get_unused_fd_flags' in kthread cause kernel crash. It works fine on

[PATCH 5.0 041/246] kasan: fix kasan_check_read/write definitions

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bcf6f55a0d05eedd8ebb6ecc60ae3f93205ad833 ] Building little-endian allmodconfig kernels on arm64 started failing with the generated atomic.h implementation, since we now try to call

[PATCH 5.0 033/246] mm, mempolicy: fix uninit memory access

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2e25644e8da4ed3a27e7b8315aaae74660be72dc ] Syzbot with KMSAN reports (excerpt): == BUG: KMSAN: uninit-value in

[PATCH 5.0 058/246] PCI/PME: Fix hotplug/sysfs remove deadlock in pcie_pme_remove()

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 95c80bc6952b6a5badc7b702d23e5bf14d251e7c ] Dongdong reported a deadlock triggered by a hotplug event during a sysfs "remove" operation: pciehp :00:0c.0:pcie004: Slot(0-1):

[PATCH 5.0 045/246] cifs: Accept validate negotiate if server return NT_STATUS_NOT_SUPPORTED

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 969ae8e8d4ee54c99134d3895f2adf96047f5bee ] Old windows version or Netapp SMB server will return NT_STATUS_NOT_SUPPORTED since they do not allow or implement

[PATCH 5.0 028/246] mm/page_ext.c: fix an imbalance with kmemleak

5.0-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0c81585499601acd1d0e1cbf424cabfaee60628c ] After offlining a memory block, kmemleak scan will trigger a crash, as it encounters a page ext address that has already been freed during

<    3   4   5   6   7   8   9   10   11   12   >