[PATCH] csky: Fixup libgcc unwind error

2019-06-25 Thread guoren
From: Guo Ren The struct rt_sigframe is also defined in libgcc/config/csky/linux-unwind.h of gcc. Although there is no use for the first three word space, we must keep them the same with linux-unwind.h for member position. The BUG is found in glibc test with the tst-cancel02. The BUG is from

Re: [PATCH 14/16] mm: move the powerpc hugepd code to mm/gup.c

2019-06-25 Thread Christoph Hellwig
On Tue, Jun 25, 2019 at 12:37:57PM -0700, Andrew Morton wrote: > On Tue, 25 Jun 2019 16:37:13 +0200 Christoph Hellwig wrote: > > > +static int gup_huge_pd(hugepd_t hugepd > > Naming nitlet: we have hugepd and we also have huge_pd. We have > hugepte and we also have huge_pte. It make things a

Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-25 Thread Frank Rowand
On 6/25/19 9:30 PM, Sandeep Patil wrote: > On Tue, Jun 25, 2019 at 11:53:13AM +0800, Greg Kroah-Hartman wrote: >> On Mon, Jun 24, 2019 at 03:37:07PM -0700, Sandeep Patil wrote: >>> We are trying to make sure that all (most) drivers in an Aarch64 system can >>> be kernel modules for Android, like

Re: [Intel-wired-lan] Opportunistic S0ix blocked by e1000e when ethernet is in use

2019-06-25 Thread Kai Heng Feng
at 6:25 PM, Neftin, Sasha wrote: On 6/24/2019 18:06, Kai-Heng Feng wrote: at 19:56, Neftin, Sasha wrote: [Snipped] Current HW have a limitation. Please, try follow workaround on your platform: echo 3 > /sys/kernel/debug/pmc_core/ltr_ignore Yes, this does the trick. On 4.15 based kernel

[PATCH] EDAC: Fix global-out-of-bounds write when setting edac_mc_poll_msec

2019-06-25 Thread Eiichi Tsukata
Commit 9da21b1509d8 ("EDAC: Poll timeout cannot be zero, p2") assumes edac_mc_poll_msec to be unsigned long, but the type of the variable still remained as int. Setting edac_mc_poll_msec can trigger out-of-bounds write. Reproducer: # echo 1001 >

[PATCH v2 0/2] Add MediaTek I3C master controller driver

2019-06-25 Thread Qii Wang
This series are based on 5.2-rc1, we provide two patches to support MediaTek I3C master controller. Main changes compared to v1: --remove clock-div, let clock driver handle it --let sample_cnt and step_cnt start from two Qii Wang (2): dt-bindings: i3c: Document MediaTek I3C master bindings

[PATCH v2 1/2] dt-bindings: i3c: Document MediaTek I3C master bindings

2019-06-25 Thread Qii Wang
Document MediaTek I3C master DT bindings. Signed-off-by: Qii Wang --- .../devicetree/bindings/i3c/mtk,i3c-master.txt | 47 1 file changed, 47 insertions(+) create mode 100644 Documentation/devicetree/bindings/i3c/mtk,i3c-master.txt diff --git

[PATCH v2 2/2] i3c: master: Add driver for MediaTek IP

2019-06-25 Thread Qii Wang
Add a driver for MediaTek I3C master IP. Signed-off-by: Qii Wang --- drivers/i3c/master/Kconfig | 10 + drivers/i3c/master/Makefile |1 + drivers/i3c/master/i3c-master-mtk.c | 1239 +++ 3 files changed, 1250 insertions(+) create mode

[tip:x86/urgent] x86/mm: Handle physical-virtual alignment mismatch in phys_p4d_init()

2019-06-25 Thread tip-bot for Kirill A. Shutemov
Commit-ID: 432c833218dd0f75e7b56bd5e8658b72073158d2 Gitweb: https://git.kernel.org/tip/432c833218dd0f75e7b56bd5e8658b72073158d2 Author: Kirill A. Shutemov AuthorDate: Mon, 24 Jun 2019 15:31:50 +0300 Committer: Thomas Gleixner CommitDate: Wed, 26 Jun 2019 07:25:09 +0200 x86/mm: Handle

[tip:x86/urgent] x86/boot/64: Add missing fixup_pointer() for next_early_pgt access

2019-06-25 Thread tip-bot for Kirill A. Shutemov
Commit-ID: c1887159eb48ba40e775584cfb2a443962cf1a05 Gitweb: https://git.kernel.org/tip/c1887159eb48ba40e775584cfb2a443962cf1a05 Author: Kirill A. Shutemov AuthorDate: Thu, 20 Jun 2019 14:24:22 +0300 Committer: Thomas Gleixner CommitDate: Wed, 26 Jun 2019 07:25:09 +0200 x86/boot/64:

[tip:x86/urgent] x86/boot/64: Fix crash if kernel image crosses page table boundary

2019-06-25 Thread tip-bot for Kirill A. Shutemov
Commit-ID: 81c7ed296dcd02bc0b4488246d040e03e633737a Gitweb: https://git.kernel.org/tip/81c7ed296dcd02bc0b4488246d040e03e633737a Author: Kirill A. Shutemov AuthorDate: Thu, 20 Jun 2019 14:23:45 +0300 Committer: Thomas Gleixner CommitDate: Wed, 26 Jun 2019 07:25:09 +0200 x86/boot/64:

Re: [PATCH RESEND 6/8] parisc: Use mmap_base, not mmap_legacy_base, as low_limit for bottom-up mmap

2019-06-25 Thread Alex Ghiti
On 6/25/19 10:09 AM, Helge Deller wrote: On 20.06.19 07:03, Alexandre Ghiti wrote: Bottom-up mmap scheme is used twice: - for legacy mode, in which mmap_legacy_base and mmap_base are equal. - in case of mmap failure in top-down mode, where there is no need to go through the whole address

Re: linux-next: Signed-off-by missing for commit in the tip tree

2019-06-25 Thread Thomas Gleixner
On Wed, 26 Jun 2019, Stephen Rothwell wrote: > > 53d87b37a2a4 ("arm64: compat: No need for pre-ARMv7 barriers on an ARMv8 > system") > b4b12aca00d5 ("arm64: vdso: Remove unnecessary asm-offsets.c definitions") > 4d33ebb02c45 ("vdso: Remove superfluous #ifdef __KERNEL__ in >

Re: [PATCH] perf/x86/intel: Mark expected switch fall-throughs

2019-06-25 Thread Nathan Chancellor
On Tue, Jun 25, 2019 at 08:46:26PM -0300, Arnaldo Carvalho de Melo wrote: > Em Tue, Jun 25, 2019 at 01:27:46PM -0700, Nathan Chancellor escreveu: > > On Tue, Jun 25, 2019 at 09:53:09PM +0200, Thomas Gleixner wrote: > > > On Tue, 25 Jun 2019, Nathan Chancellor wrote: > > > > On Tue, Jun 25, 2019 at

Re: [PATCH] perf/x86/intel: Mark expected switch fall-throughs

2019-06-25 Thread Nathan Chancellor
On Tue, Jun 25, 2019 at 11:47:06PM +0200, Thomas Gleixner wrote: > On Tue, 25 Jun 2019, Nathan Chancellor wrote: > > On Tue, Jun 25, 2019 at 09:53:09PM +0200, Thomas Gleixner wrote: > > > > > > But can the script please check for a minimal clang version required to > > > build that thing. > > >

[PATCH V3 0/2] sched/fair: Fallback to sched-idle CPU in absence of idle CPUs

2019-06-25 Thread Viresh Kumar
Hi, We try to find an idle CPU to run the next task, but in case we don't find an idle CPU it is better to pick a CPU which will run the task the soonest, for performance reason. A CPU which isn't idle but has only SCHED_IDLE activity queued on it should be a good target based on this criteria

[PATCH V3 2/2] sched/fair: Fallback to sched-idle CPU if idle CPU isn't found

2019-06-25 Thread Viresh Kumar
We try to find an idle CPU to run the next task, but in case we don't find an idle CPU it is better to pick a CPU which will run the task the soonest, for performance reason. A CPU which isn't idle but has only SCHED_IDLE activity queued on it should be a good target based on this criteria as any

[PATCH V3 1/2] sched: Start tracking SCHED_IDLE tasks count in cfs_rq

2019-06-25 Thread Viresh Kumar
Track how many tasks are present with SCHED_IDLE policy in each cfs_rq. This will be used by later commits. Signed-off-by: Viresh Kumar --- kernel/sched/fair.c | 14 -- kernel/sched/sched.h | 2 ++ 2 files changed, 14 insertions(+), 2 deletions(-) diff --git a/kernel/sched/fair.c

Re: [PATCH bpf-next] libbpf: fix max() type mismatch for 32bit

2019-06-25 Thread Andrii Nakryiko
On Tue, Jun 25, 2019 at 1:28 PM Ivan Khoronzhuk wrote: > > It fixes build error for 32bit caused by type mismatch > size_t/unsigned long. > > Signed-off-by: Ivan Khoronzhuk > --- Sorry, forgot to mention, this should probably have Fixes: bf82927125dd ("libbpf: refactor map initialization")

[PATCH v3] x86/tls: Fix possible spectre-v1 in do_get_thread_area()

2019-06-25 Thread Dianzhang Chen
The index to access the threads tls array is controlled by userspace via syscall: sys_ptrace(), hence leading to a potential exploitation of the Spectre variant 1 vulnerability. The idx can be controlled from: ptrace -> arch_ptrace -> do_get_thread_area. Fix this by sanitizing idx before

Re: [PATCH] rtc: Don't state that the RTC holds UTC in case it doesn't

2019-06-25 Thread Finn Thain
On Tue, 25 Jun 2019, Alexandre Belloni wrote: > On 25/06/2019 11:53:49+1000, Finn Thain wrote: > > On Mon, 24 Jun 2019, Alexandre Belloni wrote: > > > > > On 21/06/2019 11:51:26+1000, Finn Thain wrote: > > > > Some machines store local time in the Real Time Clock. The > > > > hard-coded "UTC"

Re: [PATCH v2] x86/tls: Fix possible spectre-v1 in do_get_thread_area()

2019-06-25 Thread Dianzhang Chen
On Wed, Jun 26, 2019 at 12:38 AM Thomas Gleixner wrote: > > On Wed, 26 Jun 2019, Dianzhang Chen wrote: > > > The index to access the threads tls array is controlled by userspace > > via syscall: sys_ptrace(), hence leading to a potential exploitation > > of the Spectre variant 1 vulnerability. >

Re: kernel panic: stack is corrupted in validate_chain

2019-06-25 Thread syzbot
syzbot has bisected this bug to: commit e9db4ef6bf4ca9894bb324c76e01b8f1a16b2650 Author: John Fastabend Date: Sat Jun 30 13:17:47 2018 + bpf: sockhash fix omitted bucket lock in sock_close bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11d4e129a0 start commit:

linux-next: manual merge of the keys tree with the integrity tree

2019-06-25 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the keys tree got a conflict in: security/integrity/digsig.c between commit: 8c655784e2cf ("integrity: Fix __integrity_init_keyring() section mismatch") from the integrity tree and commit: 79512db59dc8 ("keys: Replace uid/gid/perm permissions

Re: [RESEND PATCH v1 0/5] Solve postboot supplier cleanup and optimize probe ordering

2019-06-25 Thread Sandeep Patil
On Tue, Jun 25, 2019 at 11:53:13AM +0800, Greg Kroah-Hartman wrote: > On Mon, Jun 24, 2019 at 03:37:07PM -0700, Sandeep Patil wrote: > > We are trying to make sure that all (most) drivers in an Aarch64 system can > > be kernel modules for Android, like any other desktop system for > > example.

linux-next: manual merge of the keys tree with the ecryptfs tree

2019-06-25 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the keys tree got a conflict in: fs/ecryptfs/keystore.c between commit: 29a51df0609c ("ecryptfs: remove unnessesary null check in ecryptfs_keyring_auth_tok_for_sig") from the ecryptfs tree and commit: 79512db59dc8 ("keys: Replace uid/gid/perm

Re: Steam is broken on new kernels

2019-06-25 Thread Eric Dumazet
On Wed, Jun 26, 2019 at 5:43 AM Guenter Roeck wrote: > > On 6/25/19 7:29 PM, Greg Kroah-Hartman wrote: > > On Tue, Jun 25, 2019 at 07:02:20PM -0700, Guenter Roeck wrote: > >> Hi Greg, > >> > >> On Sat, Jun 22, 2019 at 09:37:53AM +0200, Greg Kroah-Hartman wrote: > >>> On Fri, Jun 21, 2019 at

[PATCH] arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly

2019-06-25 Thread Nathan Chancellor
After r363059 and r363928 in LLVM, a build using ld.lld as the linker with CONFIG_RANDOMIZE_BASE enabled fails like so: ld.lld: error: relocation R_AARCH64_ABS32 cannot be used against symbol __efistub_stext_offset; recompile with -fPIC Fangrui and Peter figured out that ld.lld is incorrectly

[PATCH 0/2] Unexport __clk_of_table

2019-06-25 Thread Stephen Boyd
I found this lying around, not sure if I sent it or not. We don't need to export this symbol anymore. And having COMMON_CLK in clk-provider.h seems to be an artifact. Here's a couple patches to clean this stuff up. Stephen Boyd (2): clk: Remove ifdef for COMMON_CLK in clk-provider.h clk:

[PATCH 2/2] clk: Unexport __clk_of_table

2019-06-25 Thread Stephen Boyd
This symbol doesn't need to be exported to clk providers anymore. Originally, it was hidden inside clk.c, but then OMAP needed to get access to it in commit 819b4861c18d ("CLK: ti: add init support for clock IP blocks"), but eventually that code also changed in commit c08ee14cc663 ("clk: ti:

[PATCH 1/2] clk: Remove ifdef for COMMON_CLK in clk-provider.h

2019-06-25 Thread Stephen Boyd
This ifdef has been there since the beginning of this file, but it doesn't really seem to serve any purpose besides obfuscating the struct definitions and #defines here from compilation units that include it. Let's always expose these function prototypes and struct definitions so that code can

Re: [PATCH 8/9] x86/tlb: Privatize cpu_tlbstate

2019-06-25 Thread Andy Lutomirski
On Tue, Jun 25, 2019 at 2:52 PM Dave Hansen wrote: > > On 6/12/19 11:48 PM, Nadav Amit wrote: > > cpu_tlbstate is mostly private and only the variable is_lazy is shared. > > This causes some false-sharing when TLB flushes are performed. > > Presumably, all CPUs doing TLB flushes read 'is_lazy'.

Re: [PATCH] linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL

2019-06-25 Thread Vinod Koul
On 25-06-19, 15:32, Andrew Morton wrote: > On Tue, 25 Jun 2019 15:29:38 -0700 Andrew Morton > wrote: > > > On Tue, 25 Jun 2019 15:35:18 +0530 Vinod Koul wrote: > > > > > DIV_ROUND_UP_ULL adds the two arguments and then invokes > > > DIV_ROUND_DOWN_ULL. But on a 32bit system the addition of

Re: [PATCH 6/9] KVM: x86: Provide paravirtualized flush_tlb_multi()

2019-06-25 Thread Andy Lutomirski
On Tue, Jun 25, 2019 at 8:41 PM Nadav Amit wrote: > > > On Jun 25, 2019, at 8:35 PM, Andy Lutomirski wrote: > > > > On Tue, Jun 25, 2019 at 7:39 PM Nadav Amit wrote: > >>> On Jun 25, 2019, at 2:40 PM, Dave Hansen wrote: > >>> > >>> On 6/12/19 11:48 PM, Nadav Amit wrote: > Support the new

[PATCH v2] pinctrl: mediatek: Update cur_mask in mask/mask ops

2019-06-25 Thread Nicolas Boichat
During suspend/resume, mtk_eint_mask may be called while wake_mask is active. For example, this happens if a wake-source with an active interrupt handler wakes the system: irq/pm.c:irq_pm_check_wakeup would disable the interrupt, so that it can be handled later on in the resume flow. However,

Re: [RFC v1] clk: core: support clocks that need to be enabled during re-parent

2019-06-25 Thread Stephen Boyd
Quoting Weiyi Lu (2019-06-25 18:05:22) > On Tue, 2019-06-25 at 15:14 -0700, Stephen Boyd wrote: > > Quoting Weiyi Lu (2019-06-09 20:44:53) > > > When using property assigned-clock-parents to assign parent clocks, > > > core clocks might still be disabled during re-parent. > > > Add flag

[PATCH AUTOSEL 5.1 11/51] ASoC: sun4i-codec: fix first delay on Speaker

2019-06-25 Thread Sasha Levin
From: Georgii Staroselskii [ Upstream commit 1f2675f6655838aaf910f911fd0abc821e3ff3df ] Allwinner DAC seems to have a delay in the Speaker audio routing. When playing a sound for the first time, the sound gets chopped. On a second play the sound is played correctly. After some time (~5s) the

[PATCH AUTOSEL 5.1 23/51] x86/CPU: Add more Icelake model numbers

2019-06-25 Thread Sasha Levin
From: Kan Liang [ Upstream commit e35faeb64146f2015f2aec14b358ae508e4066db ] Add the CPUID model numbers of Icelake (ICL) desktop and server processors to the Intel family list. [ Qiuxu: Sort the macros by model number. ] Signed-off-by: Kan Liang Signed-off-by: Borislav Petkov Cc: "H.

[PATCH AUTOSEL 5.1 06/51] spi: bitbang: Fix NULL pointer dereference in spi_unregister_master

2019-06-25 Thread Sasha Levin
From: YueHaibing [ Upstream commit 5caaf29af5ca82d5da8bc1d0ad07d9e664ccf1d8 ] If spi_register_master fails in spi_bitbang_start because device_add failure, We should return the error code other than 0, otherwise calling spi_bitbang_stop may trigger NULL pointer dereference like this: BUG:

[PATCH AUTOSEL 5.1 10/51] iommu/vt-d: Set the right field for Page Walk Snoop

2019-06-25 Thread Sasha Levin
From: Lu Baolu [ Upstream commit 66d78ad316b0e1ca5ae19663468554e2c0e31c26 ] Set the page walk snoop to the right bit, otherwise the domain id field will be overlapped. Reported-by: Dave Jiang Fixes: 6f7db75e1c469 ("iommu/vt-d: Add second level page table interface") Signed-off-by: Lu Baolu

Re: [PATCH 4/9] x86/mm/tlb: Flush remote and local TLBs concurrently

2019-06-25 Thread Andy Lutomirski
On Tue, Jun 25, 2019 at 8:48 PM Nadav Amit wrote: > > > On Jun 25, 2019, at 8:36 PM, Andy Lutomirski wrote: > > > > On Wed, Jun 12, 2019 at 11:49 PM Nadav Amit wrote: > >> To improve TLB shootdown performance, flush the remote and local TLBs > >> concurrently. Introduce flush_tlb_multi() that

[PATCH AUTOSEL 5.1 37/51] drm: panel-orientation-quirks: Add quirk for GPD MicroPC

2019-06-25 Thread Sasha Levin
From: Hans de Goede [ Upstream commit 652b8b086538c8a10de5aa5cbdaef79333b46358 ] GPD has done it again, make a nice device (good), use way too generic DMI strings (bad) and use a portrait screen rotated 90 degrees (ugly). Because of the too generic DMI strings this entry is also doing

[PATCH AUTOSEL 5.1 25/51] usb: gadget: udc: lpc32xx: allocate descriptor with GFP_ATOMIC

2019-06-25 Thread Sasha Levin
From: Alexandre Belloni [ Upstream commit fbc318afadd6e7ae2252d6158cf7d0c5a2132f7d ] Gadget drivers may queue request in interrupt context. This would lead to a descriptor allocation in that context. In that case we would hit BUG_ON(in_interrupt()) in __get_vm_area_node. Also remove the

[PATCH AUTOSEL 5.1 42/51] platform/x86: mlx-platform: Fix parent device in i2c-mux-reg device registration

2019-06-25 Thread Sasha Levin
From: Vadim Pasternak [ Upstream commit 160da20b254dd4bfc5828f12c208fa831ad4be6c ] Fix the issue found while running kernel with the option CONFIG_DEBUG_TEST_DRIVER_REMOVE. Driver 'mlx-platform' registers 'i2c_mlxcpld' device and then registers few underlying 'i2c-mux-reg' devices:

[PATCH AUTOSEL 5.1 47/51] scripts/decode_stacktrace.sh: prefix addr2line with $CROSS_COMPILE

2019-06-25 Thread Sasha Levin
From: Manuel Traut [ Upstream commit c04e32e911653442fc834be6e92e072aeebe01a1 ] At least for ARM64 kernels compiled with the crosstoolchain from Debian/stretch or with the toolchain from kernel.org the line number is not decoded correctly by 'decode_stacktrace.sh': $ echo "[ 136.513051]

[PATCH AUTOSEL 4.19 02/34] ASoC: ak4458: add return value for ak4458_probe

2019-06-25 Thread Sasha Levin
From: Viorel Suman [ Upstream commit a8dee20d792432740509237943700fbcfc230bad ] AK4458 is probed successfully even if AK4458 is not present - this is caused by probe function returning no error on i2c access failure. Return an error on probe if i2c access has failed. Signed-off-by: Shengjiu

[PATCH AUTOSEL 5.1 32/51] ALSA: hdac: fix memory release for SST and SOF drivers

2019-06-25 Thread Sasha Levin
From: Amadeusz Sławiński [ Upstream commit 6d647b736a6b1cbf2f8deab0e6a94c34a6ea9d60 ] During the integration of HDaudio support, we changed the way in which we get hdev in snd_hdac_ext_bus_device_init() to use one preallocated with devm_kzalloc(), however it still left kfree(hdev) in

[PATCH AUTOSEL 5.1 41/51] platform/x86: intel-vbtn: Report switch events when event wakes device

2019-06-25 Thread Sasha Levin
From: Mathew King [ Upstream commit cb1921b17adbe6509538098ac431033378cd7165 ] When a switch event, such as tablet mode/laptop mode or docked/undocked, wakes a device make sure that the value of the swich is reported. Without when a device is put in tablet mode from laptop mode when it is

[PATCH AUTOSEL 5.1 30/51] ASoC: Intel: cht_bsw_rt5672: fix kernel oops with platform_name override

2019-06-25 Thread Sasha Levin
From: Pierre-Louis Bossart [ Upstream commit 9bbc799318a34061703f2a980e2b6df7fc6760f0 ] The platform override code uses devm_ functions to allocate memory for the new name but the card device is not initialized. Fix by moving the init earlier. Fixes: f403906da05cd ("ASoC: Intel:

[PATCH AUTOSEL 5.1 31/51] ASoC: core: move DAI pre-links initiation to snd_soc_instantiate_card

2019-06-25 Thread Sasha Levin
From: Tzung-Bi Shih [ Upstream commit 70fc53734e71ce51f46dfcfd1a1c319e1cfe080c ] Kernel crashes when an ASoC component rebinding. The dai_link->platforms has been reset to NULL by soc_cleanup_platform() in soc_cleanup_card_resources() when un-registering component. However, it has no chance

[PATCH AUTOSEL 5.1 45/51] arm64: tlbflush: Ensure start/end of address range are aligned to stride

2019-06-25 Thread Sasha Levin
From: Will Deacon [ Upstream commit 01d57485fcdb9f9101a10a18e32d5f8b023cab86 ] Since commit 3d65b6bbc01e ("arm64: tlbi: Set MAX_TLBI_OPS to PTRS_PER_PTE"), we resort to per-ASID invalidation when attempting to perform more than PTRS_PER_PTE invalidation instructions in a single call to

[PATCH AUTOSEL 4.19 09/34] drm/mediatek: unbind components in mtk_drm_unbind()

2019-06-25 Thread Sasha Levin
From: Hsin-Yi Wang [ Upstream commit f0fd848342802bc0f74620d387eead53e8905804 ] Unbinding components (i.e. mtk_dsi and mtk_disp_ovl/rdma/color) will trigger master(mtk_drm)'s .unbind(), and currently mtk_drm's unbind won't actually unbind components. During the next bind, mtk_drm_kms_init() is

[PATCH AUTOSEL 5.1 50/51] module: Fix livepatch/ftrace module text permissions race

2019-06-25 Thread Sasha Levin
From: Josh Poimboeuf [ Upstream commit 9f255b632bf12c4dd7fc31caee89aa991ef75176 ] It's possible for livepatch and ftrace to be toggling a module's text permissions at the same time, resulting in the following panic: BUG: unable to handle page fault for address: c005b1d9 #PF:

[PATCH AUTOSEL 4.19 07/34] ASoC: sun4i-codec: fix first delay on Speaker

2019-06-25 Thread Sasha Levin
From: Georgii Staroselskii [ Upstream commit 1f2675f6655838aaf910f911fd0abc821e3ff3df ] Allwinner DAC seems to have a delay in the Speaker audio routing. When playing a sound for the first time, the sound gets chopped. On a second play the sound is played correctly. After some time (~5s) the

[PATCH AUTOSEL 5.1 51/51] ftrace: Fix NULL pointer dereference in free_ftrace_func_mapper()

2019-06-25 Thread Sasha Levin
From: Wei Li [ Upstream commit 04e03d9a616c19a47178eaca835358610e63a1dd ] The mapper may be NULL when called from register_ftrace_function_probe() with probe->data == NULL. This issue can be reproduced as follow (it may be covered by compiler optimization sometime): / # cat

Re: [PATCH 4/9] x86/mm/tlb: Flush remote and local TLBs concurrently

2019-06-25 Thread Nadav Amit
> On Jun 25, 2019, at 8:36 PM, Andy Lutomirski wrote: > > On Wed, Jun 12, 2019 at 11:49 PM Nadav Amit wrote: >> To improve TLB shootdown performance, flush the remote and local TLBs >> concurrently. Introduce flush_tlb_multi() that does so. The current >> flush_tlb_others() interface is kept,

[PATCH AUTOSEL 4.19 17/34] usb: gadget: fusb300_udc: Fix memory leak of fusb300->ep[i]

2019-06-25 Thread Sasha Levin
From: Young Xiao <92siuy...@gmail.com> [ Upstream commit 62fd0e0a24abeebe2c19fce49dd5716d9b62042d ] There is no deallocation of fusb300->ep[i] elements, allocated at fusb300_probe. The patch adds deallocation of fusb300->ep array elements. Signed-off-by: Young Xiao <92siuy...@gmail.com>

[PATCH AUTOSEL 4.19 01/34] ASoC : cs4265 : readable register too low

2019-06-25 Thread Sasha Levin
From: Matt Flax [ Upstream commit f3df05c805983427319eddc2411a2105ee1757cf ] The cs4265_readable_register function stopped short of the maximum register. An example bug is taken from : https://github.com/Audio-Injector/Ultra/issues/25 Where alsactl store fails with : Cannot read control

[PATCH AUTOSEL 4.19 05/34] spi: bitbang: Fix NULL pointer dereference in spi_unregister_master

2019-06-25 Thread Sasha Levin
From: YueHaibing [ Upstream commit 5caaf29af5ca82d5da8bc1d0ad07d9e664ccf1d8 ] If spi_register_master fails in spi_bitbang_start because device_add failure, We should return the error code other than 0, otherwise calling spi_bitbang_stop may trigger NULL pointer dereference like this: BUG:

[PATCH AUTOSEL 4.19 03/34] ASoC: soc-pcm: BE dai needs prepare when pause release after resume

2019-06-25 Thread Sasha Levin
From: Libin Yang [ Upstream commit 5087a8f17df868601cd7568299e91c28086d2b45 ] If playback/capture is paused and system enters S3, after system returns from suspend, BE dai needs to call prepare() callback when playback/capture is released from pause if RESUME_INFO flag is not set. Currently,

Re: [PATCH v3 1/3] scsi: ufs: Introduce vops for resetting device

2019-06-25 Thread Bjorn Andersson
On Tue 25 Jun 05:41 PDT 2019, Alim Akhtar wrote: > Hi Bjorn, > Are you planning to address Bean's comment on patch#2 and want to > re-spin this series? > I am ok with taking this patch as it is and take a Softreset patch as a > separate patch. > I still intend to attempt to implement a

[PATCH AUTOSEL 4.19 32/34] tracing: avoid build warning with HAVE_NOP_MCOUNT

2019-06-25 Thread Sasha Levin
From: Vasily Gorbik [ Upstream commit cbdaeaf050b730ea02e9ab4ff844ce54d85dbe1d ] Selecting HAVE_NOP_MCOUNT enables -mnop-mcount (if gcc supports it) and sets CC_USING_NOP_MCOUNT. Reuse __is_defined (which is suitable for testing CC_USING_* defines) to avoid conditional compilation and fix the

[PATCH AUTOSEL 4.19 18/34] usb: gadget: udc: lpc32xx: allocate descriptor with GFP_ATOMIC

2019-06-25 Thread Sasha Levin
From: Alexandre Belloni [ Upstream commit fbc318afadd6e7ae2252d6158cf7d0c5a2132f7d ] Gadget drivers may queue request in interrupt context. This would lead to a descriptor allocation in that context. In that case we would hit BUG_ON(in_interrupt()) in __get_vm_area_node. Also remove the

[PATCH AUTOSEL 4.19 20/34] SoC: rt274: Fix internal jack assignment in set_jack callback

2019-06-25 Thread Sasha Levin
From: Amadeusz Sławiński [ Upstream commit 04268bf2757a125616b6c2140e6250f43b7b737a ] When we call snd_soc_component_set_jack(component, NULL, NULL) we should set rt274->jack to passed jack, so when interrupt is triggered it calls snd_soc_jack_report(rt274->jack, ...) with proper value. This

[PATCH AUTOSEL 4.19 31/34] mm/mlock.c: change count_mm_mlocked_page_nr return type

2019-06-25 Thread Sasha Levin
From: swkhack [ Upstream commit 0874bb49bb21bf24deda853e8bf61b8325e24bcb ] On a 64-bit machine the value of "vma->vm_end - vma->vm_start" may be negative when using 32 bit ints and the "count >> PAGE_SHIFT"'s result will be wrong. So change the local variable and return value to unsigned long

[PATCH AUTOSEL 4.19 23/34] drm: panel-orientation-quirks: Add quirk for GPD MicroPC

2019-06-25 Thread Sasha Levin
From: Hans de Goede [ Upstream commit 652b8b086538c8a10de5aa5cbdaef79333b46358 ] GPD has done it again, make a nice device (good), use way too generic DMI strings (bad) and use a portrait screen rotated 90 degrees (ugly). Because of the too generic DMI strings this entry is also doing

[PATCH AUTOSEL 4.19 24/34] platform/x86: asus-wmi: Only Tell EC the OS will handle display hotkeys from asus_nb_wmi

2019-06-25 Thread Sasha Levin
From: Hans de Goede [ Upstream commit 401fee8195d401b2b94dee57383f627050724d5b ] Commit 78f3ac76d9e5 ("platform/x86: asus-wmi: Tell the EC the OS will handle the display off hotkey") causes the backlight to be permanently off on various EeePC laptop models using the eeepc-wmi driver (Asus EeePC

[PATCH AUTOSEL 4.19 25/34] platform/x86: intel-vbtn: Report switch events when event wakes device

2019-06-25 Thread Sasha Levin
From: Mathew King [ Upstream commit cb1921b17adbe6509538098ac431033378cd7165 ] When a switch event, such as tablet mode/laptop mode or docked/undocked, wakes a device make sure that the value of the swich is reported. Without when a device is put in tablet mode from laptop mode when it is

[PATCH AUTOSEL 4.14 08/21] drm/mediatek: call mtk_dsi_stop() after mtk_drm_crtc_atomic_disable()

2019-06-25 Thread Sasha Levin
From: Hsin-Yi Wang [ Upstream commit 2458d9d6d94be982b917e93c61a89b4426f32e31 ] mtk_dsi_stop() should be called after mtk_drm_crtc_atomic_disable(), which needs ovl irq for drm_crtc_wait_one_vblank(), since after mtk_dsi_stop() is called, ovl irq will be disabled. If drm_crtc_wait_one_vblank()

[PATCH AUTOSEL 4.14 18/21] scripts/decode_stacktrace.sh: prefix addr2line with $CROSS_COMPILE

2019-06-25 Thread Sasha Levin
From: Manuel Traut [ Upstream commit c04e32e911653442fc834be6e92e072aeebe01a1 ] At least for ARM64 kernels compiled with the crosstoolchain from Debian/stretch or with the toolchain from kernel.org the line number is not decoded correctly by 'decode_stacktrace.sh': $ echo "[ 136.513051]

[PATCH AUTOSEL 4.14 04/21] ASoC: core: lock client_mutex while removing link components

2019-06-25 Thread Sasha Levin
From: Ranjani Sridharan [ Upstream commit 34ac3c3eb8f0c07252ceddf0a22dd240e5c91ccb ] Removing link components results in topology unloading. So, acquire the client_mutex before removing components in soc_remove_link_components. This will prevent the lockdep warning seen when dai links are

[PATCH AUTOSEL 4.14 14/21] SoC: rt274: Fix internal jack assignment in set_jack callback

2019-06-25 Thread Sasha Levin
From: Amadeusz Sławiński [ Upstream commit 04268bf2757a125616b6c2140e6250f43b7b737a ] When we call snd_soc_component_set_jack(component, NULL, NULL) we should set rt274->jack to passed jack, so when interrupt is triggered it calls snd_soc_jack_report(rt274->jack, ...) with proper value. This

[PATCH AUTOSEL 4.14 01/21] ASoC : cs4265 : readable register too low

2019-06-25 Thread Sasha Levin
From: Matt Flax [ Upstream commit f3df05c805983427319eddc2411a2105ee1757cf ] The cs4265_readable_register function stopped short of the maximum register. An example bug is taken from : https://github.com/Audio-Injector/Ultra/issues/25 Where alsactl store fails with : Cannot read control

[PATCH AUTOSEL 4.14 19/21] mm/mlock.c: change count_mm_mlocked_page_nr return type

2019-06-25 Thread Sasha Levin
From: swkhack [ Upstream commit 0874bb49bb21bf24deda853e8bf61b8325e24bcb ] On a 64-bit machine the value of "vma->vm_end - vma->vm_start" may be negative when using 32 bit ints and the "count >> PAGE_SHIFT"'s result will be wrong. So change the local variable and return value to unsigned long

Re: [PATCH] docs: zh_CN: submitting-drivers.rst: Remove a duplicated Documentation/

2019-06-25 Thread Alex Shi
Thanks for catching. Reviewed-by: Alex Shi 在 2019/6/23 上午1:47, Mauro Carvalho Chehab 写道: Somehow, this file ended with Documentation/ twice. Signed-off-by: Mauro Carvalho Chehab --- Documentation/translations/zh_CN/process/submitting-drivers.rst | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH AUTOSEL 4.14 16/21] platform/x86: mlx-platform: Fix parent device in i2c-mux-reg device registration

2019-06-25 Thread Sasha Levin
From: Vadim Pasternak [ Upstream commit 160da20b254dd4bfc5828f12c208fa831ad4be6c ] Fix the issue found while running kernel with the option CONFIG_DEBUG_TEST_DRIVER_REMOVE. Driver 'mlx-platform' registers 'i2c_mlxcpld' device and then registers few underlying 'i2c-mux-reg' devices:

[PATCH AUTOSEL 4.4 3/6] ASoC: max98090: remove 24-bit format support if RJ is 0

2019-06-25 Thread Sasha Levin
From: Yu-Hsuan Hsu [ Upstream commit 5628c8979642a076f91ee86c3bae5ad251639af0 ] The supported formats are S16_LE and S24_LE now. However, by datasheet of max98090, S24_LE is only supported when it is in the right justified mode. We should remove 24-bit format if it is not in that mode to avoid

[PATCH AUTOSEL 4.9 09/11] scsi: hpsa: correct ioaccel2 chaining

2019-06-25 Thread Sasha Levin
From: Don Brace [ Upstream commit 625d7d3518875c4d303c652a198feaa13d9f52d9 ] - set ioaccel2_sg_element member 'chain_indicator' to IOACCEL2_LAST_SG for the last s/g element. - set ioaccel2_sg_element member 'chain_indicator' to IOACCEL2_CHAIN when chaining. Reviewed-by: Bader Ali - Saleh

[PATCH AUTOSEL 4.4 6/6] scsi: hpsa: correct ioaccel2 chaining

2019-06-25 Thread Sasha Levin
From: Don Brace [ Upstream commit 625d7d3518875c4d303c652a198feaa13d9f52d9 ] - set ioaccel2_sg_element member 'chain_indicator' to IOACCEL2_LAST_SG for the last s/g element. - set ioaccel2_sg_element member 'chain_indicator' to IOACCEL2_CHAIN when chaining. Reviewed-by: Bader Ali - Saleh

[PATCH AUTOSEL 4.9 10/11] scripts/decode_stacktrace.sh: prefix addr2line with $CROSS_COMPILE

2019-06-25 Thread Sasha Levin
From: Manuel Traut [ Upstream commit c04e32e911653442fc834be6e92e072aeebe01a1 ] At least for ARM64 kernels compiled with the crosstoolchain from Debian/stretch or with the toolchain from kernel.org the line number is not decoded correctly by 'decode_stacktrace.sh': $ echo "[ 136.513051]

[PATCH AUTOSEL 4.9 11/11] mm/mlock.c: change count_mm_mlocked_page_nr return type

2019-06-25 Thread Sasha Levin
From: swkhack [ Upstream commit 0874bb49bb21bf24deda853e8bf61b8325e24bcb ] On a 64-bit machine the value of "vma->vm_end - vma->vm_start" may be negative when using 32 bit ints and the "count >> PAGE_SHIFT"'s result will be wrong. So change the local variable and return value to unsigned long

[PATCH AUTOSEL 4.4 4/6] usb: gadget: fusb300_udc: Fix memory leak of fusb300->ep[i]

2019-06-25 Thread Sasha Levin
From: Young Xiao <92siuy...@gmail.com> [ Upstream commit 62fd0e0a24abeebe2c19fce49dd5716d9b62042d ] There is no deallocation of fusb300->ep[i] elements, allocated at fusb300_probe. The patch adds deallocation of fusb300->ep array elements. Signed-off-by: Young Xiao <92siuy...@gmail.com>

[PATCH AUTOSEL 4.4 2/6] spi: bitbang: Fix NULL pointer dereference in spi_unregister_master

2019-06-25 Thread Sasha Levin
From: YueHaibing [ Upstream commit 5caaf29af5ca82d5da8bc1d0ad07d9e664ccf1d8 ] If spi_register_master fails in spi_bitbang_start because device_add failure, We should return the error code other than 0, otherwise calling spi_bitbang_stop may trigger NULL pointer dereference like this: BUG:

[PATCH AUTOSEL 4.4 1/6] ASoC : cs4265 : readable register too low

2019-06-25 Thread Sasha Levin
From: Matt Flax [ Upstream commit f3df05c805983427319eddc2411a2105ee1757cf ] The cs4265_readable_register function stopped short of the maximum register. An example bug is taken from : https://github.com/Audio-Injector/Ultra/issues/25 Where alsactl store fails with : Cannot read control

[PATCH AUTOSEL 4.4 5/6] usb: gadget: udc: lpc32xx: allocate descriptor with GFP_ATOMIC

2019-06-25 Thread Sasha Levin
From: Alexandre Belloni [ Upstream commit fbc318afadd6e7ae2252d6158cf7d0c5a2132f7d ] Gadget drivers may queue request in interrupt context. This would lead to a descriptor allocation in that context. In that case we would hit BUG_ON(in_interrupt()) in __get_vm_area_node. Also remove the

[PATCH AUTOSEL 4.9 08/11] usb: gadget: udc: lpc32xx: allocate descriptor with GFP_ATOMIC

2019-06-25 Thread Sasha Levin
From: Alexandre Belloni [ Upstream commit fbc318afadd6e7ae2252d6158cf7d0c5a2132f7d ] Gadget drivers may queue request in interrupt context. This would lead to a descriptor allocation in that context. In that case we would hit BUG_ON(in_interrupt()) in __get_vm_area_node. Also remove the

[PATCH AUTOSEL 4.9 01/11] ASoC : cs4265 : readable register too low

2019-06-25 Thread Sasha Levin
From: Matt Flax [ Upstream commit f3df05c805983427319eddc2411a2105ee1757cf ] The cs4265_readable_register function stopped short of the maximum register. An example bug is taken from : https://github.com/Audio-Injector/Ultra/issues/25 Where alsactl store fails with : Cannot read control

[PATCH AUTOSEL 4.9 04/11] ASoC: sun4i-codec: fix first delay on Speaker

2019-06-25 Thread Sasha Levin
From: Georgii Staroselskii [ Upstream commit 1f2675f6655838aaf910f911fd0abc821e3ff3df ] Allwinner DAC seems to have a delay in the Speaker audio routing. When playing a sound for the first time, the sound gets chopped. On a second play the sound is played correctly. After some time (~5s) the

[PATCH AUTOSEL 4.9 07/11] usb: gadget: fusb300_udc: Fix memory leak of fusb300->ep[i]

2019-06-25 Thread Sasha Levin
From: Young Xiao <92siuy...@gmail.com> [ Upstream commit 62fd0e0a24abeebe2c19fce49dd5716d9b62042d ] There is no deallocation of fusb300->ep[i] elements, allocated at fusb300_probe. The patch adds deallocation of fusb300->ep array elements. Signed-off-by: Young Xiao <92siuy...@gmail.com>

[PATCH AUTOSEL 4.9 06/11] ASoC: max98090: remove 24-bit format support if RJ is 0

2019-06-25 Thread Sasha Levin
From: Yu-Hsuan Hsu [ Upstream commit 5628c8979642a076f91ee86c3bae5ad251639af0 ] The supported formats are S16_LE and S24_LE now. However, by datasheet of max98090, S24_LE is only supported when it is in the right justified mode. We should remove 24-bit format if it is not in that mode to avoid

[PATCH AUTOSEL 4.9 02/11] ASoC: soc-pcm: BE dai needs prepare when pause release after resume

2019-06-25 Thread Sasha Levin
From: Libin Yang [ Upstream commit 5087a8f17df868601cd7568299e91c28086d2b45 ] If playback/capture is paused and system enters S3, after system returns from suspend, BE dai needs to call prepare() callback when playback/capture is released from pause if RESUME_INFO flag is not set. Currently,

[PATCH AUTOSEL 4.14 10/21] ASoC: sun4i-i2s: Fix sun8i tx channel offset mask

2019-06-25 Thread Sasha Levin
From: Marcus Cooper [ Upstream commit 7e46169a5f35762f335898a75d1b8a242f2ae0f5 ] Although not causing any noticeable issues, the mask for the channel offset is covering too many bits. Signed-off-by: Marcus Cooper Acked-by: Maxime Ripard Acked-by: Chen-Yu Tsai Signed-off-by: Mark Brown

[PATCH AUTOSEL 4.14 21/21] ftrace: Fix NULL pointer dereference in free_ftrace_func_mapper()

2019-06-25 Thread Sasha Levin
From: Wei Li [ Upstream commit 04e03d9a616c19a47178eaca835358610e63a1dd ] The mapper may be NULL when called from register_ftrace_function_probe() with probe->data == NULL. This issue can be reproduced as follow (it may be covered by compiler optimization sometime): / # cat

[PATCH AUTOSEL 4.14 20/21] module: Fix livepatch/ftrace module text permissions race

2019-06-25 Thread Sasha Levin
From: Josh Poimboeuf [ Upstream commit 9f255b632bf12c4dd7fc31caee89aa991ef75176 ] It's possible for livepatch and ftrace to be toggling a module's text permissions at the same time, resulting in the following panic: BUG: unable to handle page fault for address: c005b1d9 #PF:

[PATCH AUTOSEL 4.9 03/11] spi: bitbang: Fix NULL pointer dereference in spi_unregister_master

2019-06-25 Thread Sasha Levin
From: YueHaibing [ Upstream commit 5caaf29af5ca82d5da8bc1d0ad07d9e664ccf1d8 ] If spi_register_master fails in spi_bitbang_start because device_add failure, We should return the error code other than 0, otherwise calling spi_bitbang_stop may trigger NULL pointer dereference like this: BUG:

[PATCH AUTOSEL 4.14 12/21] usb: gadget: fusb300_udc: Fix memory leak of fusb300->ep[i]

2019-06-25 Thread Sasha Levin
From: Young Xiao <92siuy...@gmail.com> [ Upstream commit 62fd0e0a24abeebe2c19fce49dd5716d9b62042d ] There is no deallocation of fusb300->ep[i] elements, allocated at fusb300_probe. The patch adds deallocation of fusb300->ep array elements. Signed-off-by: Young Xiao <92siuy...@gmail.com>

[PATCH AUTOSEL 4.14 11/21] ASoC: sun4i-i2s: Add offset to RX channel select

2019-06-25 Thread Sasha Levin
From: Marcus Cooper [ Upstream commit f9927000cb35f250051f0f1878db12ee2626eea1 ] Whilst testing the capture functionality of the i2s on the newer SoCs it was noticed that the recording was somewhat distorted. This was due to the offset not being set correctly on the receiver side.

[PATCH AUTOSEL 4.14 17/21] cpuset: restore sanity to cpuset_cpus_allowed_fallback()

2019-06-25 Thread Sasha Levin
From: Joel Savitz [ Upstream commit d477f8c202d1f0d4791ab1263ca7657bbe5cf79e ] In the case that a process is constrained by taskset(1) (i.e. sched_setaffinity(2)) to a subset of available cpus, and all of those are subsequently offlined, the scheduler will set tsk->cpus_allowed to the current

[PATCH AUTOSEL 4.19 27/34] platform/mellanox: mlxreg-hotplug: Add devm_free_irq call to remove flow

2019-06-25 Thread Sasha Levin
From: Vadim Pasternak [ Upstream commit 8c2eb7b6468ad4aa5600aed01aa0715f921a3f8b ] Add devm_free_irq() call to mlxreg-hotplug remove() for clean release of devices irq resource. Fix debugobjects warning triggered by rmmod It prevents of use-after-free memory, related to

[PATCH AUTOSEL 4.14 13/21] usb: gadget: udc: lpc32xx: allocate descriptor with GFP_ATOMIC

2019-06-25 Thread Sasha Levin
From: Alexandre Belloni [ Upstream commit fbc318afadd6e7ae2252d6158cf7d0c5a2132f7d ] Gadget drivers may queue request in interrupt context. This would lead to a descriptor allocation in that context. In that case we would hit BUG_ON(in_interrupt()) in __get_vm_area_node. Also remove the

  1   2   3   4   5   6   7   8   9   10   >