Re: [PATCH v3 05/11] arm: Properly account for stack randomization and stack guard gap

On 4/18/19 1:26 AM, Kees Cook wrote: On Wed, Apr 17, 2019 at 12:28 AM Alexandre Ghiti wrote: This commit takes care of stack randomization and stack guard gap when computing mmap base address and checks if the task asked for randomization. This fixes the problem uncovered and not fixed for arm

Re: [PATCH v3 06/11] arm: Use STACK_TOP when computing mmap base address

On 4/18/19 1:27 AM, Kees Cook wrote: On Wed, Apr 17, 2019 at 12:29 AM Alexandre Ghiti wrote: mmap base address must be computed wrt stack top address, using TASK_SIZE is wrong since STACK_TOP and TASK_SIZE are not equivalent. Signed-off-by: Alexandre Ghiti --- arch/arm/mm/mmap.c | 4 ++--

Re: [PATCH v3 07/11] arm: Use generic mmap top-down layout

On 4/18/19 1:28 AM, Kees Cook wrote: On Wed, Apr 17, 2019 at 12:30 AM Alexandre Ghiti wrote: arm uses a top-down mmap layout by default that exactly fits the generic functions, so get rid of arch specific code and use the generic version by selecting ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT.

Re: [PATCH v3 08/11] mips: Properly account for stack randomization and stack guard gap

On 4/18/19 1:30 AM, Kees Cook wrote: On Wed, Apr 17, 2019 at 12:31 AM Alexandre Ghiti wrote: This commit takes care of stack randomization and stack guard gap when computing mmap base address and checks if the task asked for randomization. This fixes the problem uncovered and not fixed for

Re: [PATCH v3 09/11] mips: Use STACK_TOP when computing mmap base address

On 4/18/19 1:31 AM, Kees Cook wrote: On Wed, Apr 17, 2019 at 12:32 AM Alexandre Ghiti wrote: mmap base address must be computed wrt stack top address, using TASK_SIZE is wrong since STACK_TOP and TASK_SIZE are not equivalent. Signed-off-by: Alexandre Ghiti Acked-by: Kees Cook Thanks !

Re: [PATCH v3 10/11] mips: Use generic mmap top-down layout

On 4/18/19 1:31 AM, Kees Cook wrote: On Wed, Apr 17, 2019 at 12:33 AM Alexandre Ghiti wrote: mips uses a top-down layout by default that fits the generic functions. At the same time, this commit allows to fix problem uncovered and not fixed for mips here:

Re: [PATCH v3 11/11] riscv: Make mmap allocation top-down by default

On 4/18/19 1:31 AM, Kees Cook wrote: On Wed, Apr 17, 2019 at 12:34 AM Alexandre Ghiti wrote: In order to avoid wasting user address space by using bottom-up mmap allocation scheme, prefer top-down scheme when possible. Before: root@qemuriscv64:~# cat /proc/self/maps 0001-00016000 r-xp

Re: [PATCH v3] serial: Add Milbeaut serial control

Hi, On 2019/04/18 14:17, Greg Kroah-Hartman wrote: On Thu, Apr 18, 2019 at 11:51:56AM +0900, Sugaya Taichi wrote: Add Milbeaut serial control including earlycon and console. Signed-off-by: Sugaya Taichi --- Changes from v2: - Fix build warning. No, I only need an incremental patch fixing

Re: [PATCH] RISC-V: redefine PTRS_PER_PGD/PTRS_PER_PMD/PTRS_PER_PTE

On Thu, Apr 18, 2019 at 6:26 AM damon wrote: > > Use the number of addresses to define the relevant macros. > > Signed-off-by: damon > --- > arch/riscv/include/asm/pgtable-32.h | 2 ++ > arch/riscv/include/asm/pgtable-64.h | 3 ++- > arch/riscv/include/asm/pgtable.h| 4 ++-- > 3 files

Re: [PATCH] RDMA/cxgb4: fix spelling mistake "immedate" -> "immediate"

On Tue, Apr 16, 2019 at 03:38:04PM +0100, Colin King wrote: > From: Colin Ian King > > There is a spelling mistake in a module parameter description. Fix it. > > Signed-off-by: Colin Ian King > --- > drivers/infiniband/hw/cxgb4/qp.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

RE: [PATCH v2] mmc: core: Verify SD bus width

> > The SD Physical Layer Spec says the following: Since the SD Memory Card > shall support at least the two bus modes 1-bit or 4-bit width, then any SD > Card shall set at least bits 0 and 2 (SD_BUS_WIDTH="0101"). > > This change verifies the card has specified a bus width. > > AMD SDHC Device

[PATCH 1/1] csky: add page fault perf event support

This patch add support for page fault count, major fault count and minorfault count. Without this patch page faults are not sampled for perf event. Performance counter stats for '/usr/lib/perf-test/callchain_test': 0 page-faults #0.000 K/sec

Re: [PATCH] i2c: iproc: Change driver to use 'BIT' macro

On 2019-04-18 01:48, Ray Jui wrote: > > > On 4/14/2019 11:56 PM, Peter Rosin wrote: >> On 2019-04-13 00:59, Peter Rosin wrote: >>> On 2019-04-03 23:05, Ray Jui wrote: Change the iProc I2C driver to use the 'BIT' macro from all '1 << XXX' bit operations to get rid of compiler warning

[PATCH] serial: Fix using plain integer instead of Null pointer

Fix build warning that using plain integer as Null pointer. This is reported by kbuild test robot. Fixes: ba44dc043004 ("serial: Add Milbeaut serial control") Signed-off-by: Sugaya Taichi --- drivers/tty/serial/milbeaut_usio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] nvme: determine the number of IO queues

On 4/18/19 1:33 AM, Maxim Levitsky wrote: > On Wed, 2019-04-17 at 20:32 +0300, Maxim Levitsky wrote: >> On Wed, 2019-04-17 at 22:12 +0800, Aaron Ma wrote: >>> Some controllers support limited IO queues, when over set >>> the number, it will return invalid field error. >>> Then NVME will be removed

Re: [PATCH] nvme: determine the number of IO queues

On 4/18/19 5:30 AM, Edmund Nadolski (Microsoft) wrote: > On 4/17/19 7:12 AM, Aaron Ma wrote: >> Some controllers support limited IO queues, when over set >> the number, it will return invalid field error. >> Then NVME will be removed by driver. >> >> Find the max number of IO queues that

Re: [PATCH v1 0/4] Add tracing for SDHCI register access

On 12/04/19 5:50 PM, Raul Rangel wrote: > On Fri, Apr 12, 2019 at 09:26:44AM +0300, Adrian Hunter wrote: >> On 12/04/19 1:08 AM, Raul E Rangel wrote: >>> I was debugging a SDHC hardware bug and got tired of having to >>> translate the register values by hand. This patch set makes it so all >>>

Re: [PATCH v2] staging: greybus: power_supply: use struct_size() helper

On Wed, Apr 17, 2019 at 01:44:40PM -0500, Gustavo A. R. Silva wrote: > Make use of the struct_size() helper instead of an open-coded version > in order to avoid any potential type mistakes, in particular in the > context in which this code is being used. > > So, replace code of the following

Re: [PATCH v2 1/2] power: reset: nvmem-reboot-mode: use NVMEM as reboot mode write interface

On 4/18/19 12:56 AM, Sebastian Reichel wrote: On Thu, Apr 11, 2019 at 05:54:09AM +, Han Nandor wrote: Add a new reboot mode write interface that is using an NVMEM cell to store the reboot mode magic. Signed-off-by: Nandor Han --- +module_platform_driver(nvmem_reboot_mode_driver); +

Re: Issues with i.MX SPI DMA transfers

Dear Robin, Hi Igor, Did you meet any issue with my latest patch? sorry, but unfortunately I have no time to test it. I have switched to PIO mode and continue other development. Maybe later I will find time to test DMA mode, but not sure when. Thank you for support! -- Igor

Re: [QUESTIONS] THP allocation in NUMA fault migration path

On Wed 17-04-19 21:15:41, Yang Shi wrote: > Hi folks, > > > I noticed that there might be new THP allocation in NUMA fault migration > path (migrate_misplaced_transhuge_page()) even when THP is disabled (set to > "never"). When THP is set to "never", there should be not any new THP > allocation,

Re: [PATCH 2/5] mmc: mtk-sd: don't hard-code interrupt trigger type

On Wed, 2019-04-17 at 08:12 +1000, NeilBrown wrote: > On Tue, Apr 16 2019, Chaotian Jing wrote: > > > On Tue, 2019-04-16 at 14:47 +1000, NeilBrown wrote: > >> When using devicetree for configuration, interrupt trigger type > >> should be described in the dts file, not hard-coded in the C code. >

Re: [PATCH 4/5] mmc: mtk-sd: enable internal card-detect logic.

On Tue, 2019-04-16 at 14:47 +1000, NeilBrown wrote: > The mtk-sd silicon has integrated card-detect logic that is > enabled, at least, on the MT7621 as used in the GNUBEE NAS. > > If the sdhci isn't marked non-removable and doesn't have a > cd-gpio configured, assume the internal cd logic should

Re: [PATCH] serial: Fix using plain integer instead of Null pointer

On Thu, Apr 18, 2019 at 03:21:25PM +0900, Sugaya Taichi wrote: > Fix build warning that using plain integer as Null pointer. > This is reported by kbuild test robot. > > Fixes: ba44dc043004 ("serial: Add Milbeaut serial control") > Signed-off-by: Sugaya Taichi > --- >

[PATCH V2 2/3] dt-bindings: regulator: add document bindings for slg51000

Add device tree binding information for slg51000 regulator driver. Example bindings for SLG51000 are added. Signed-off-by: Eric Jeong --- This patch applies against linux-next and next-20190417 v2: No changes. .../devicetree/bindings/regulator/slg51000.txt | 88

[PATCH V2 0/3] slg51000: regulator driver submission

This patch adds support for the Dialog SLG51000 regulator device. In this patch set the following is provided: [PATCH V2 1/3] MAINTAINERS file update for SLG51000 [PATCH V2 2/3] SLG51000 DT binding [PATCH V2 3/3] SLG51000 regulator driver This patch applies against linux-next and

[PATCH V2 3/3] regulator: slg51000: add slg51000 regulator driver

Adding regulator driver for the device Dialog SLG51000. The SLG51000 device contains seven compact and customizable low dropout regulators and is designed for high performance camera modules and other small multi-rail applications. Signed-off-by: Eric Jeong --- This patch applies against

[PATCH V2 1/3] MAINTAINERS: slg51000 updates to the Dialog Semiconductor search terms

This patch adds the slg51000 bindings doc and driver to the Dialog Semiconductor support list. Signed-off-by: Eric Jeong --- v2: No changes. MAINTAINERS |2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 349e5d8..ae6b6f9 100644 --- a/MAINTAINERS +++

[PATCH] platform/x86: asus-wmi: Add fn-lock mode switch support

Some of latest ASUS laptops support new fn-lock mode switching. This commit detect whether if the fn-lock option is enabled in BIOS setting, and toggle the fn-lock mode via a new WMI DEVID 0x00100023 when the corresponding notify code captured. The ASUS fn-lock mode switch is activated by

Re: [PATCH v2] PCI: assign bus numbers present in EA capability for bridges

Hi Bjorn, On Thu, Apr 18, 2019 at 1:46 AM Bjorn Helgaas wrote: > > On Mon, Nov 19, 2018 at 06:44:32PM +0530, sundeep.l...@gmail.com wrote: > > From: Subbaraya Sundeep > > > > As per the spec, bridges with EA capability work > > with fixed secondary and subordinate bus numbers. > > Hence assign

[PATCH] staging: olpc_dcon: Convert all uses of old GPIO API to new descriptor API

This commit eliminate all uses of legacy integer base GPIO API in olpc_dcon_xo_1_5.c and replace them with new descriptor GPIO API like those in olpc_dcon_xo_1.c. Also pull some common code with olpc_dcon_xo_1.c to olpc_dcon.h for code sharing. Signed-off-by: Jerry Lin ---

Re: [PATCH v2] mtd: rawnand: ams-delta: Drop board specific partition info

Hi Janusz, Janusz Krzysztofik wrote on Thu, 18 Apr 2019 01:09:59 +0200: > Hi Aaro, Tony, > > On Wednesday, April 17, 2019 11:40:10 AM CEST Miquel Raynal wrote: > > Hi Janusz, > > > > Janusz Krzysztofik wrote on Sun, 24 Mar 2019 > > 23:33:44 +0100: > > > > > After recent modifications,

Re: [PATCH v5 02/02] tty: rocket: deprecate the rp_ioctl

On Thu, Apr 18, 2019 at 12:35:58PM +0800, Fuqian Huang wrote: > This patch depends on patch 01. THat's implied as it is patch 02/02, so no need to put it in the changelog text :) > > The rp_ioctl is deprecated. > Add dev_warn_ratelimited to warn the use of rp_ioctl. > > Signed-off-by: Fuqian

Re: [tip:x86/cache] x86/resctrl: Initialize a new resource group with default MBA values

Hi Boris, I found a nitpick - an unnecessary newline at the end of the patch. Please help double check. Thank you. On 4/18/2019 6:14, tip-bot for Xiaochen Shen wrote: Commit-ID: 47820e73f5b3a1fdb8ebd1219191edc96e0c85c1 Gitweb:

Re: [PATCH] serial: Fix using plain integer instead of Null pointer

Hi, On 2019/04/18 15:40, Greg Kroah-Hartman wrote: On Thu, Apr 18, 2019 at 03:21:25PM +0900, Sugaya Taichi wrote: Fix build warning that using plain integer as Null pointer. This is reported by kbuild test robot. Fixes: ba44dc043004 ("serial: Add Milbeaut serial control") Signed-off-by:

Re: [PATCH] x86: kvm: hyper-v: deal with buggy TLB flush requests from WS2012

Vitaly Kuznetsov writes: > It was reported that with some special Multi Processor Group configuration, > e.g: > bcdedit.exe /set groupsize 1 > bcdedit.exe /set maxgroup on > bcdedit.exe /set groupaware on > for a 16-vCPU guest WS2012 shows BSOD on boot when PV TLB flush mechanism > is in use.

stm class: Fix possible double free

The function stm_register_device() calls put_device(>dev) to release allocated memory (in stm_device_release()) on error paths. However, after that, the freed memory stm is released again, resulting in a double free bug. There is a similar issue in the function stm_source_register_device. This

Re: [PATCH] nvme: determine the number of IO queues

On Thu, 2019-04-18 at 14:21 +0800, Aaron Ma wrote: > On 4/18/19 1:33 AM, Maxim Levitsky wrote: > > On Wed, 2019-04-17 at 20:32 +0300, Maxim Levitsky wrote: > > > On Wed, 2019-04-17 at 22:12 +0800, Aaron Ma wrote: > > > > Some controllers support limited IO queues, when over set > > > > the number,

Re: [tip:x86/cache] x86/resctrl: Initialize a new resource group with default MBA values

On Thu, Apr 18, 2019 at 03:03:35PM +0800, Xiaochen Shen wrote: > In my opinion, this newline is unnecessary. Thank you. See commit message: > [ bp: Add newlines between code blocks for better readability. ] And I didn't add enough. That code is too crammed. For example, the new

Re: linux-next: manual merge of the phy-next tree with the qcom tree

On 18/04/2019 07:29, Stephen Rothwell wrote: > Today's linux-next merge of the phy-next tree got a conflict in: > > Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt > > between commit: > > 369b89366a3d ("dt-bindings: phy-qcom-qmp: Tweak qcom,msm8998-qmp-ufs-phy") > > from the qcom

[PATCH] f2fs: Force type conversion from __le32 to u32

This patch forces type conversion from __le32 to u32 to prevent sparse warnings like: warning: restricted __le32 degrades to integer dir.c: fscrypt_fname_disk_to_usr takes a hash of type u32 as it's second arg but de->hash_code is of type __le32. node.c NULL_ADDR is of type u32 but block_addr is

Re: [PATCH] pinctrl: mediatek: Add MT8516 Pinctrl driver

Hi, Fabien After reusing the eint_regs common, the result looks good to me On Tue, Apr 16, 2019 at 1:33 AM Fabien Parent wrote: > > This commit adds the pinctrl driver for the MediaTek's MT8516 SoC. > > Signed-off-by: Fabien Parent Acked-by: Sean Wang > --- > > v2: > * Don't assign

[REGRESSION 5.0.x] Windows XP broken on KVM

Hi, we've got a regression report on the recent 5.0.x kernel, starting from 5.0.6, where Windows XP can't boot on KVM any longer. The culprit seems to be the patch KVM: x86: update %rip after emulating IO with the upstream commit 45def77ebf79e2e8942b89ed79294d97ce914fa0. Reverting this alone

[PATCH] perf stat: display cvs output for --null runs

Adding support to display CVS values for --null runs as requested by Ingo. It's only for --null run so it does not mess up with standard CVS output. For single --null run in CSV mode perf displays elapsed time: $ perf stat --null -x ';' true 0.000496 For multiple --null run in CSV mode perf

Re: [PATCH] x86/mm/mem_encrypt: fix a crash with kmemleak_scan

On Tue, Apr 16, 2019 at 08:38:30PM -0400, Qian Cai wrote: > kmemleak_init() will register the data/bss sections (only register > .data..ro_after_init if not within .data) and then kmemleak_scan() will scan > those address and dereference them looking for pointer referencing. If > free_init_pages()

Re: [PATCH v2] panic: add an option to replay all the printk message in buffer

On Thu 2019-04-18 09:00:14, Sergey Senozhatsky wrote: > I think that PANIC_PRINT_ALL_PRINTK_MSG is a debugging option; a quite > specific one. So people who ask the kernel to PANIC_PRINT_ALL_PRINTK_MSG > they know what they are doing, and we probably will not cofuse anyone. > After all, we don't

Re: [PATCH] x86_64: Disabling read-implies-exec when the stack is executable

On Wed, May 11, 2016 at 5:45 AM Hector Marco-Gisbert wrote: > > The READ_IMPLIES_EXEC personality was removed in 2005 for 64-bit processes, > (commit a3cc2546a54361b86b73557df5b85c4fc3fc27c3 form history.git). > > But it's still possible to have all readable areas with EXEC permissions by >

[PATCH] wireless: Use offsetof instead of custom macro.

Use offsetof to calculate offset of a field to take advantage of compiler built-in version when possible, and avoid UBSAN warning when compiling with Clang: == UBSAN: Undefined behaviour in net/wireless/wext-core.c:525:14 member

Re: [REGRESSION 5.0.x] Windows XP broken on KVM

On Thu, Apr 18, 2019 at 09:38:52AM +0200, Takashi Iwai wrote: > Hi, > > we've got a regression report on the recent 5.0.x kernel, starting > from 5.0.6, where Windows XP can't boot on KVM any longer. > > The culprit seems to be the patch >KVM: x86: update %rip after emulating IO > with the

Re: [RFC PATCH v2] perf/x86: make perf callchain work without CONFIG_FRAME_POINTER

On Wed, Apr 17, 2019 at 10:44:33PM +0800, Kairui Song wrote: > Despite it's hacky, it seems not necessary to dump every register. And > is there a straight way to get caller's regs in the trace point? It > seems more trouble some. Or if we just use the regs inside the > tracepoint, but it would

Re: [REGRESSION 5.0.x] Windows XP broken on KVM

On 18/04/19 09:38, Takashi Iwai wrote: > Hi, > > we've got a regression report on the recent 5.0.x kernel, starting > from 5.0.6, where Windows XP can't boot on KVM any longer. > > The culprit seems to be the patch >KVM: x86: update %rip after emulating IO > with the upstream commit

Re: [PATCH v4 2/2] x86/boot/KASLR: skip the specified crashkernel region

On Thu, Apr 18, 2019 at 12:06 AM Borislav Petkov wrote: > > On Wed, Apr 17, 2019 at 01:53:37PM +0800, Pingfan Liu wrote: > > Take __parse_crashkernel()->parse_crashkernel_simple() for example. If > > no offset given, then it still return 0, but crash_base is dangling. Sorry for misleading, I

Re: linux-next: manual merge of the phy-next tree with the qcom tree

Hi Marc, On Thu, 18 Apr 2019 09:35:44 +0200 Marc Gonzalez wrote: > > It is not clear to me what I could/should have done differently to avoid > the conflict? Nothing really, it will need to be fixed up when these trees are merged into Linus' tree (or some other tree along the way). It is not

Re: [PATCH-tip 0/2] locking/rwsem: Rwsem rearchitecture part 2 follow-up patches

* Waiman Long wrote: > As the part2 patches are still being actively modified, it doesn't look > like it will make the next merge window. I am fine with postponing it > to 5.3. However, I would like to request the merging of just patch 1 of > the part 2 patchset. It fixes a locking selftest

Re: [PATCH v2 3/3] thermal: cpu_cooling: Migrate to using the EM framework

On Thursday 18 Apr 2019 at 09:23:23 (+0530), Viresh Kumar wrote: > On 17-04-19, 10:43, Quentin Perret wrote: > > static struct thermal_cooling_device * > > __cpufreq_cooling_register(struct device_node *np, > > - struct cpufreq_policy *policy, u32 capacitance) > > +

Re: Issues with i.MX SPI DMA transfers

On 2019-04-18 at 06:30 +, Igor Plyatov wrote: > WARNING: This email was created outside of NXP. DO NOT CLICK links or > attachments unless you recognize the sender and know the content is > safe. > > > > Dear Robin, > > > > > Hi Igor, > >   Did you meet any issue with my latest patch?

Re: [REGRESSION 5.0.x] Windows XP broken on KVM

On Thu, 18 Apr 2019 09:53:28 +0200, Greg Kroah-Hartman wrote: > > On Thu, Apr 18, 2019 at 09:38:52AM +0200, Takashi Iwai wrote: > > Hi, > > > > we've got a regression report on the recent 5.0.x kernel, starting > > from 5.0.6, where Windows XP can't boot on KVM any longer. > > > > The culprit

[tip:locking/core] locking/rwsem: Prevent unneeded warning during locking selftest

Commit-ID: 26536e7c242e2b0f73c25c46fc50d2525ebe400b Gitweb: https://git.kernel.org/tip/26536e7c242e2b0f73c25c46fc50d2525ebe400b Author: Waiman Long AuthorDate: Sat, 13 Apr 2019 13:22:44 -0400 Committer: Ingo Molnar CommitDate: Sun, 14 Apr 2019 11:09:35 +0200 locking/rwsem: Prevent

Re: stm class: Fix possible double free

On 4/18/2019 12:52 PM, Pan Bian wrote: The function stm_register_device() calls put_device(>dev) to release allocated memory (in stm_device_release()) on error paths. However, after that, the freed memory stm is released again, resulting in a double free bug. There is a similar issue in the

Re: [PATCH 19/24] dt-bindings: spi: spi-mt65xx: add support for MT8516

On Tue, Apr 16, 2019 at 10:25 AM lei liu wrote: > > On Tue, 2019-04-16 at 09:55 +0200, Matthias Brugger wrote: > > > > On 23/03/2019 22:16, Fabien Parent wrote: > > > Add binding documentation of spi-mt65xx for MT8516 SoC. > > > > > > Signed-off-by: Fabien Parent > > > --- > > >

Re: [PATCH] ntp: Allow TAI-UTC offset to be set to zero

On Wed, Apr 17, 2019 at 11:00:23AM +0200, Ondrej Mosnacek wrote: > On Wed, Apr 17, 2019 at 10:48 AM Miroslav Lichvar wrote: > > Change the ADJ_TAI check to accept zero as a valid TAI-UTC offset in > > order to allow setting it back to the initial value. > Thanks for sending the patch! Maybe you

[tip:x86/asm] x86/build/vdso: Add FORCE to the build rule of %.so

Commit-ID: 3c454f47e67bf5a65dc892cd50221a7de695870f Gitweb: https://git.kernel.org/tip/3c454f47e67bf5a65dc892cd50221a7de695870f Author: Masahiro Yamada AuthorDate: Wed, 3 Apr 2019 17:30:12 +0900 Committer: Ingo Molnar CommitDate: Thu, 18 Apr 2019 10:05:34 +0200 x86/build/vdso: Add

Re: [PATCH 1/1] pinctrl: Add alternative way for specifying register bases

Hi, Light I knew your idea, but the patch really depends on a separate patch about the update of the corresponding dt-binding document for your newly added properties. You can find out dt-binding document pinctrl-mt8183.txt in linux-pinctrl.git branch for-next that is just being merged two weeks

Re: [PATCH 0/5] mm: reparent slab memory on cgroup removal

Hello Roman, On Wed, Apr 17, 2019 at 02:54:29PM -0700, Roman Gushchin wrote: > There is however a significant problem with reparenting of slab memory: > there is no list of charged pages. Some of them are in shrinker lists, > but not all. Introducing of a new list is really not an option. True,

Re: [PATCH] x86_64: Disabling read-implies-exec when the stack is executable

On Thu, 18 Apr 2019, Kees Cook wrote: > On Wed, May 11, 2016 at 5:45 AM Hector Marco-Gisbert wrote: > *thread necromancy* > > I'd still like to see this get landed. READ_IMPLIES_EXEC is way too > powerful (it impacts, for example, mmap() regions of device driver > memory, forcing drivers to not

linux-next: Tree for Apr 18

Hi all, News: there will be no linux-next release on Friday, Monday or Thursday April 25. Changes since 20190417: The bpf-next tree gained a build failure for which I applied a patch. The drm tree still had its build failure for which I disabled a driver. The fix is in the drm-misc tree where

Re: [PATCH 19/24] dt-bindings: spi: spi-mt65xx: add support for MT8516

On Thu, 2019-04-18 at 10:05 +0200, Fabien Parent wrote: > On Tue, Apr 16, 2019 at 10:25 AM lei liu wrote: > > > > On Tue, 2019-04-16 at 09:55 +0200, Matthias Brugger wrote: > > > > > > On 23/03/2019 22:16, Fabien Parent wrote: > > > > Add binding documentation of spi-mt65xx for MT8516 SoC. > > >

[PATCH 4/4] crypto: sun4i-ss: fallback when length is not multiple of blocksize

sun4i-ss does not handle requests when length are not a multiple of blocksize. This patch adds a fallback for that case. Fixes: 6298e948215f ("crypto: sunxi-ss - Add Allwinner Security System crypto accelerator") Signed-off-by: Corentin Labbe --- drivers/crypto/sunxi-ss/sun4i-ss-cipher.c | 57

Re: Support for 2D engines/blitters in V4L2 and DRM

On Wed, Apr 17, 2019 at 08:10:15PM +0200, Paul Kocialkowski wrote: > Hi Nicolas, > > I'm detaching this thread from our V4L2 stateless decoding spec since > it has drifted off and would certainly be interesting to DRM folks as > well! > > For context: I was initially talking about writing up

Re: [tip:x86/cache] x86/resctrl: Initialize a new resource group with default MBA values

Hi Boris, On 4/18/2019 15:28, Borislav Petkov wrote: On Thu, Apr 18, 2019 at 03:03:35PM +0800, Xiaochen Shen wrote: In my opinion, this newline is unnecessary. Thank you. See commit message: [ bp: Add newlines between code blocks for better readability. ] I got this commit message

Re: [PATCH v4 07/16] locking/rwsem: Implement lock handoff to prevent lock starvation

On Wed, Apr 17, 2019 at 12:39:19PM -0400, Waiman Long wrote: > On 04/17/2019 04:05 AM, Peter Zijlstra wrote: > > So what is wrong with the below? > > > > --- a/include/linux/sched/wake_q.h > > +++ b/include/linux/sched/wake_q.h > > @@ -51,6 +51,11 @@ static inline void wake_q_init(struct wa > >

Re: [tip:x86/cache] x86/resctrl: Initialize a new resource group with default MBA values

On Thu, Apr 18, 2019 at 04:20:57PM +0800, Xiaochen Shen wrote: > Should I submit a separate fixing patch for __init_one_rdt_domain()? You don't have to send a separate patch just for removing an excessive newline. Simply next time someone is touching the code around there, that newline can be

Re: [PATCH 04/12] dma-buf: add optional invalidate_mappings callback v5

Am 18.04.19 um 10:08 schrieb Daniel Vetter: > On Wed, Apr 17, 2019 at 09:13:22PM +0200, Christian König wrote: >> Am 17.04.19 um 21:07 schrieb Daniel Vetter: >>> On Tue, Apr 16, 2019 at 08:38:33PM +0200, Christian König wrote: Each importer can now provide an invalidate_mappings callback.

ext4: avoid drop reference to iloc.bh twice

The reference to iloc.bh has been dropped in ext4_mark_iloc_dirty. However, the reference is dropped again if error occurs during ext4_handle_dirty_metadata, which may result in use-after-free bugs. Fixes: fb265c9cb49e("ext4: add ext4_sb_bread() to disambiguate ENOMEM cases") Signed-off-by: Pan

[PATCH v2 2/2] arm64: dts: allwinner: a64-oceanic-5205-5inmfd: Enable GT911 CTP

Goodix GT911 CTP is bound with Oceanic 5205 5inMFD board. The CTP connected to board with, - SDA, SCK from i2c0 - GPIO-LD0 as AVDD28 supply - PH4 gpio as interrupt pin - PH11 gpio as reset pin - X axis is inverted - Y axis is inverted Signed-off-by: Jagan Teki --- Changes for v2: - drop i2c1,

[PATCH v2 1/2] arm64: dts: allwinner: a64-amarula-relic: Add GT5663 CTP node

Add Goodix GT5663 capacitive touch controller node on Amarula A64-Relic board. The CTP connected to board with, - SDA, SCK from i2c1 - GPIO-LD0 as AVDD28 supply - PH4 gpio as interrupt pin - PH8 gpio as reset pin - X axis is inverted - Y axis is inverted Signed-off-by: Jagan Teki --- Changes

[PATCH 1/2] arm64: dts: allwinner: a64: Add pinmux setting for CSI MCLK on PE1

Some camera modules have the SoC feeding a master clock to the sensor instead of having a standalone crystal. This clock signal is generated from the clock control unit and output from the CSI MCLK function of pin PE1. Add a pinmux setting for it for camera sensors to reference. Signed-off-by:

[PATCH 2/2] arm64: dts: allwinner: a64-amarula-relic: Add OV5640 camera node

Amarula A64-Relic board by default bound with OV5640 camera, so add support for it with below pin information. - PE13, PE12 via i2c-gpio bitbanging - CLK_CSI_MCLK as external clock - PE1 as external clock pin muxing - ALDO1 as AVDD supply - DLDO3 as DOVDD supply - ELDO3 as DVDD supply - PE14 gpio

Re: [PATCH v4 08/16] locking/rwsem: Make rwsem_spin_on_owner() return owner state

On Wed, Apr 17, 2019 at 02:29:02PM -0400, Waiman Long wrote: > On 04/17/2019 08:47 AM, Peter Zijlstra wrote: > >> > >> enum owner_state { > >>OWNER_NULL = 1 << 0, > >>OWNER_WRITER= 1 << 1, > >>OWNER_READER= 1 << 2, > >>OWNER_NONSPINNABLE =

[tip:x86/urgent] x86/mm/KASLR: Fix the size of the direct mapping section

Commit-ID: ec3937107ab43f3e8b2bc9dad95710043c462ff7 Gitweb: https://git.kernel.org/tip/ec3937107ab43f3e8b2bc9dad95710043c462ff7 Author: Baoquan He AuthorDate: Thu, 4 Apr 2019 10:03:13 +0800 Committer: Borislav Petkov CommitDate: Thu, 18 Apr 2019 10:42:58 +0200 x86/mm/KASLR: Fix the

Re: [PATCH v4 09/16] locking/rwsem: Ensure an RT task will not spin on reader

On Wed, Apr 17, 2019 at 02:47:07PM -0400, Waiman Long wrote: > >> @@ -566,13 +573,28 @@ static bool rwsem_optimistic_spin(struct > >> rw_semaphore *sem) > >>} > >> > >>/* > >> - * When there's no owner, we might have preempted between the > >> - *

Re: [PATCH v2 2/3] dmaengine: imx-sdma: Only check ratio on parts that support 1:1

Acked-by: Robin Gong On 2019-03-29 at 15:21 +, Angus Ainslie (Purism) wrote: > On imx8mq B0 chip, AHB/SDMA clock ratio 2:1 can't be supported, > since SDMA clock ratio has to be increased to 250Mhz, AHB can't reach > to 500Mhz, so use 1:1 instead. > > To limit this change to the imx8mq for

Re: [PATCH v4 11/16] locking/rwsem: Enable readers spinning on writer

On Wed, Apr 17, 2019 at 01:34:01PM -0400, Waiman Long wrote: > On 04/17/2019 09:56 AM, Peter Zijlstra wrote: > > On Sat, Apr 13, 2019 at 01:22:54PM -0400, Waiman Long wrote: > >> @@ -549,7 +582,7 @@ static noinline enum owner_state > >> rwsem_spin_on_owner(struct rw_semaphore *sem) > >>return

Re: [PATCH v2] panic: add an option to replay all the printk message in buffer

Hi Petr, On Thu, Apr 18, 2019 at 09:45:52AM +0200, Petr Mladek wrote: > On Thu 2019-04-18 09:00:14, Sergey Senozhatsky wrote: > > I think that PANIC_PRINT_ALL_PRINTK_MSG is a debugging option; a quite > > specific one. So people who ask the kernel to PANIC_PRINT_ALL_PRINTK_MSG > > they know what

Re: [PATCH v2] staging: greybus: power_supply: use struct_size() helper

Oi Gustavo, Thanks for the patch, and the rebasing. On Wed 17 Apr 2019 at 19:44, Gustavo A. R. Silva wrote: Make use of the struct_size() helper instead of an open-coded version in order to avoid any potential type mistakes, in particular in the context in which this code is being used. So,

Re: [PATCH v4 11/16] locking/rwsem: Enable readers spinning on writer

On Wed, Apr 17, 2019 at 01:45:10PM -0400, Waiman Long wrote: > On 04/17/2019 09:58 AM, Peter Zijlstra wrote: > > On Sat, Apr 13, 2019 at 01:22:54PM -0400, Waiman Long wrote: > >> +/* > >> + * Try to acquire read lock before the reader is put on wait queue. > >> + * Lock acquisition isn't allowed

Re: [PATCH v1] perf record: collect user registers set jointly with dwarf stacks

On 17.04.2019 21:47, Arnaldo Carvalho de Melo wrote: > Em Wed, Apr 17, 2019 at 08:45:08PM +0300, Alexey Budankov escreveu: >> Hi Arnaldo, >> >> On 17.04.2019 18:48, Arnaldo Carvalho de Melo wrote: >>> On April 17, 2019 11:40:02 AM GMT-03:00, Jiri Olsa wrote: On Wed, Apr 17, 2019 at

Re: [v2 RFC PATCH 0/9] Another Approach to Use PMEM as NUMA Node

On Wed 17-04-19 13:43:44, Yang Shi wrote: [...] > And, I'm wondering whether this optimization is also suitable to general > NUMA balancing or not. If there are convincing numbers then this should be a preferable way to deal with it. Please note that the number of promotions is not the only

[PATCH v1 3/4] Bluetooth: btmtksdio: Fix hdev->stat.byte_rx accumulation

From: Sean Wang Accumulate hdev->stat.byte_rx only for valid packets as btmtkuart doing. Signed-off-by: Sean Wang --- drivers/bluetooth/btmtksdio.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/bluetooth/btmtksdio.c b/drivers/bluetooth/btmtksdio.c index

[patch V2 19/29] lockdep: Simplify stack trace handling

Replace the indirection through struct stack_trace by using the storage array based interfaces and storing the information is a small lockdep specific data structure. Signed-off-by: Thomas Gleixner --- include/linux/lockdep.h |9 +++-- kernel/locking/lockdep.c | 44

[patch V2 27/29] lib/stackdepot: Remove obsolete functions

No more users of the struct stack_trace based interfaces. Signed-off-by: Thomas Gleixner Acked-by: Alexander Potapenko --- include/linux/stackdepot.h |4 lib/stackdepot.c | 20 2 files changed, 24 deletions(-) --- a/include/linux/stackdepot.h +++

[patch V2 15/29] dm persistent data: Simplify stack trace handling

Replace the indirection through struct stack_trace with an invocation of the storage array based interface. This results in less storage space and indirection. Signed-off-by: Thomas Gleixner Cc: dm-de...@redhat.com Cc: Mike Snitzer Cc: Alasdair Kergon ---

[patch V2 22/29] tracing: Make ftrace_trace_userstack() static and conditional

It's only used in trace.c and there is absolutely no point in compiling it in when user space stack traces are not supported. Signed-off-by: Thomas Gleixner Cc: Steven Rostedt --- kernel/trace/trace.c | 14 -- kernel/trace/trace.h |8 2 files changed, 8

[PATCH v1 4/4] Bluetooth: btmtksdio: Add runtime PM support to SDIO based Bluetooth

From: Sean Wang Add runtime PM support to btmtksdio. With this way, there will be the benefit of the device entering the more power saving state once it is been a while data traffic is idle. Signed-off-by: Sean Wang --- drivers/bluetooth/btmtksdio.c | 144 ++ 1

[patch V2 26/29] stacktrace: Remove obsolete functions

No more users of the struct stack_trace based interfaces. Remove them. Remove the macro stubs for !CONFIG_STACKTRACE as well as they are pointless because the storage on the call sites is conditional on CONFIG_STACKTRACE already. No point to be 'smart'. Signed-off-by: Thomas Gleixner ---

Re: [PATCH v3 0/3] Fix jack detection for Chromebook Pixel

On Mon, Apr 15, 2019 at 01:45:56PM -0600, Fletcher Woodruff wrote: > Headphone/mic jack detection doesn't work on the Chromebook Pixel 2015. > > This patch changes the irq implementation to support polarity flipping > and fixes the configuration code so that correct GPIO pins are read > from

[PATCH v1 0/4] Add a couple of enhancements to btmtksdio

From: Sean Wang First three are all minor changes and the final one adds a runtime pm support to enter a lower power state for decreasing power dissipation when there is idle traffic in SDIO transport for a while. Sean Wang (4): Bluetooth: btmtksdio: Drop newline with bt_dev logging macros

[PATCH v1 1/4] Bluetooth: btmtksdio: Drop newline with bt_dev logging macros

From: Sean Wang bt_dev logging macros already include a newline at each output so drop these unnecessary additional newlines in the driver. Signed-off-by: Sean Wang --- drivers/bluetooth/btmtksdio.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH v1 2/4] Bluetooth: btmtksdio: Add a bit definition for CHLPCR

From: Sean Wang Add a register bit definition about CHLPCR bit 8 because the bit is quite different in the meaning between reading and writing that bit. The patch adds a definition particularly for the bit read to avoid the confusion about using write definition to read the bit. Signed-off-by:

Re: [PATCH] ntp: Allow TAI-UTC offset to be set to zero

On Thu, 18 Apr 2019, Miroslav Lichvar wrote: > On Wed, Apr 17, 2019 at 11:00:23AM +0200, Ondrej Mosnacek wrote: > > On Wed, Apr 17, 2019 at 10:48 AM Miroslav Lichvar > > wrote: > > > Change the ADJ_TAI check to accept zero as a valid TAI-UTC offset in > > > order to allow setting it back to the

  1   2   3   4   5   6   7   8   9   10   >