Re: [PATCH v2] mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB

On Tue, 28 Aug 2018 21:21:16 +0800 Liu Xiang wrote: > If the size of spi-nor flash is larger than 16MB, the read_opcode > is set to SPINOR_OP_READ_1_1_4_4B, and fsl_qspi_get_seqid() will > return -EINVAL when cmd is SPINOR_OP_READ_1_1_4_4B. This can > cause read operation fail. > > --- > v2: >

Re: [RFC PATCH v2 2/2] mtd: rawnand: meson: add support for Amlogic NAND flash controller

On Tue, 28 Aug 2018 21:21:48 +0800 Liang Yang wrote: > Hi Boris, > > On 8/24/2018 8:48 PM, Boris Brezillon wrote: > > On Wed, 22 Aug 2018 22:08:42 +0800 > > Liang Yang wrote: > > > >>> You have to wait tWB, that's for sure. > >>> > >> we have a maximum 32 commands fifo. when command is

gpiolib: GPIO_GET_LINEHANDLE_IOCTL and GPIO_GET_LINEEVENT_IOCTL at the same time

It seems gpiolib only allows user to request either the line handle descriptor or the line event descriptor, but not both at the same time. gpiohandle_request hr; gpioevent_request er; ... ioctl(fd, GPIO_GET_LINEHANDLE_IOCTL, &hr); // so far so good ioctl(fd, GPIO_GET_LINEEVENT_IOCTL, &er);

[PATCH] MAINTAINERS: Move entry for Cirrus Logic Madera codecs

To preserve alphabetical sort order. Fixes: 97c2b5cba2044f1c ("mfd: madera: Add register definitions for Cirrus Logic Madera codecs") Signed-off-by: Geert Uytterhoeven --- MAINTAINERS | 32 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/MAINTAIN

Re: linux-next: manual merge of the mfd tree with Linus' tree

Hi Stephen, On Tue, Aug 21, 2018 at 10:31 AM Stephen Rothwell wrote: > On Tue, 21 Aug 2018 10:08:54 +0200 Geert Uytterhoeven > wrote: > > To obey sorting rules, the CIRRUS LOGIC entry should be before the CLANG > > entry. > > Upon closer look, it should be inserted before the CISCO entries, too

[PATCH v2 00/11] Another round of tsens cleanups

This is another series of tsens cleanups before we add interrupt support. This applies on top of 4.19-rc1. In this series, we have the following: - splitup 8916 and 8974 register address spaces for SROT and TM - cleanups: move to spdx, dead code removal, removal of id field - Add support to map t

[PATCH v2 01/11] arm/arm64: dts: msm8974/msm8916: thermal: Split address space into two

We've earlier added support to split the register address space into TM and SROT regions. Split up the regmap address space into two for the remaining platforms that have a similar register layout and make corresponding changes to the get_temp_common() function used by these platforms. Since tsen

[PATCH v2 02/11] arm/arm64: dts: msm8974/msm8916: thermal: Add "qcom,sensors" property

This new property allows the number of sensors to be configured from DT instead of being hardcoded in platform data. Use it. Signed-off-by: Amit Kucheria Reviewed-by: Matthias Kaehlcke --- arch/arm/boot/dts/qcom-msm8974.dtsi | 1 + arch/arm64/boot/dts/qcom/msm8916.dtsi | 1 + 2 files changed,

[PATCH v2 06/11] thermal: tsens: Rename map field in order to add a second address map

The TSENS driver currently only uses a limited set of registers from the TM address space. So it was ok to map just that set of registers and call it "map". We'd now like to map a second set: SROT registers to introduce new functionality. Rename the "map" field to a more appropriate "tm_map". The

[PATCH v2 07/11] thermal: tsens: Add the SROT address map

On platforms whose device trees specify two address spaces for TSENS, the second one points to the SROT registers. Initialise the SROT map on those platforms. Signed-off-by: Amit Kucheria Reviewed-by: Matthias Kaehlcke --- drivers/thermal/qcom/tsens-common.c | 14 -- drivers/thermal

[PATCH v2 05/11] thermal: tsens: Get rid of dead code

hw_id is dynamically allocated but not used anywhere. Get rid of dead code. Signed-off-by: Amit Kucheria Reviewed-by: Matthias Kaehlcke --- drivers/thermal/qcom/tsens.c | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/thermal/qcom/tsens.c b/drivers/thermal/qcom/tsens.c index 90bb

[PATCH v2 04/11] thermal: tsens: Add SPDX license identifiers

The TSENS drivers use a GPL-2.0 license. Replace with equivalent SPDX tags and delete the full license text. Signed-off-by: Amit Kucheria Reviewed-by: Matthias Kaehlcke --- drivers/thermal/qcom/tsens-8916.c | 11 +-- drivers/thermal/qcom/tsens-8960.c | 11 +-- drivers/therma

[PATCH v2 09/11] thermal: tsens: Get rid of 'id' field

The hw_id field in 'struct tsens_sensor' can do the job of tracking unique ids for each sensor connected to each tsens device instance. It also allows hw_ids to be overridden (e.g. 8916) in cases where some sensors in a sequence are disabled on a particular platform. Use the hw_id field instead of

[PATCH v2 03/11] dt-bindings: thermal: Fix a typo in documentation

c(1) + x(1) was actually meant to be c(1) * x(1). Signed-off-by: Amit Kucheria Reviewed-by: Matthias Kaehlcke Acked-by: Rob Herring --- Documentation/devicetree/bindings/thermal/thermal.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/th

[PATCH v2 08/11] thermal: tsens: Check if the IP is correctly enabled by firmware

The SROT registers are initialised by the secure firmware at boot. We don't have write access to the registers. Check if the block is enabled before continuing. Signed-off-by: Amit Kucheria Reviewed-by: Matthias Kaehlcke --- drivers/thermal/qcom/tsens-common.c | 17 + 1 file cha

[PATCH v2 10/11] arm64: dts: qcom: Add reg-names for all tsens nodes

Instead of showing up as thermal-sensor@, the nodes will show up as tsens0_tm, tsen1_tm, tsens1_srot, etc. in /proc/iomem making it easier to read. IOW, 0c222000-0c2221fe : thermal-sensor@c263000 0c223000-0c2231fe : thermal-sensor@c265000 0c263000-0c2631fe : thermal-sensor@c263000 0c265000-0c2651

[PATCH v2 11/11] MAINTAINERS: Add entry for Qualcomm TSENS thermal drivers

Create an entry for the TSENS drivers and mark them as maintained Signed-off-by: Amit Kucheria Reviewed-by: Matthias Kaehlcke Acked-by: Rajendra Nayak --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index a5b256b25905..b8c96e0699c9 100644 --

Linux 3.18.120

I'm announcing the release of the 3.18.120 kernel. All users of the 3.18 kernel series must upgrade. The updated 3.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.18.y and can be browsed at the normal kernel.org git web browser

Linux 4.4.153

I'm announcing the release of the 4.4.153 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 3.18.120

diff --git a/Makefile b/Makefile index 6f85cc732008..2ba32f17a470 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 3 PATCHLEVEL = 18 -SUBLEVEL = 119 +SUBLEVEL = 120 EXTRAVERSION = NAME = Diseased Newt diff --git a/arch/arm/boot/dts/am3517.dtsi b/arch/arm/boot/dts/am3517.dtsi ind

Re: Linux 4.4.153

diff --git a/Makefile b/Makefile index 523b0d4354fb..208a813be615 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 152 +SUBLEVEL = 153 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/x86/include/asm/mmu_context.h b/arch/x86/include/asm/mmu_

Re: [RFC PATCH 08/11] asm-generic/tlb: Track freeing of page-table directories in struct mmu_gather

On Mon, Aug 27, 2018 at 02:44:57PM +1000, Nicholas Piggin wrote: > powerpc may be able to use the unmap granule thing to improve > its page size dependent flushes, but it might prefer to go > a different way and track start-end for different page sizes. I don't really see how tracking multiple ra

Re: [PATCH v2] compiler.h: give up __compiletime_assert_fallback()

2018-08-28 19:55 GMT+09:00 Arnd Bergmann : > On Mon, Aug 27, 2018 at 10:44 PM Daniel Santos > wrote: >> >> On 08/27/2018 03:09 PM, Nick Desaulniers wrote: >> >> Now we're back to the question of "what do you mean by 'constant'"? If >> >> you mean a C constant expression (as defined in the C stan

Re: [RFC PATCH 08/11] asm-generic/tlb: Track freeing of page-table directories in struct mmu_gather

On Tue, Aug 28, 2018 at 03:46:38PM +0200, Peter Zijlstra wrote: > On Mon, Aug 27, 2018 at 02:44:57PM +1000, Nicholas Piggin wrote: > > > powerpc may be able to use the unmap granule thing to improve > > its page size dependent flushes, but it might prefer to go > > a different way and track start-

Re: [PATCH] x86/nmi: Fix some races in NMI uaccess

On Mon, 2018-08-27 at 19:10 -0700, Andy Lutomirski wrote: > On Mon, Aug 27, 2018 at 6:31 PM, Rik van Riel > wrote: > > > What is special about this path wrt nmi_uaccess_ok that is > > not also true for the need_flush branch right above it? > > > > What am I missing? > > Nothing. My patch is bu

[PATCH v4 01/16] sched/core: uclamp: extend sched_setattr to support utilization clamping

The SCHED_DEADLINE scheduling class provides an advanced and formal model to define tasks requirements which can be translated into proper decisions for both task placements and frequencies selections. Other classes have a more simplified model which is essentially based on the relatively simple co

[PATCH v4 00/16] Add utilization clamping support

This is a respin of: https://lore.kernel.org/lkml/20180806163946.28380-1-patrick.bell...@arm.com/ Which has been rebased on v4.19-rc1. Thanks for all the valuable comments collected so far! Further comments and feedbacks are more than welcome! Cheers Patrick Main changes in v4

[PATCH v4 02/16] sched/core: uclamp: map TASK's clamp values into CPU's clamp groups

Utilization clamping requires each CPU to know which clamp values are assigned to tasks that are currently RUNNABLE on that CPU. Multiple tasks can be assigned the same clamp value and tasks with different clamp values can be concurrently active on the same CPU. Thus, a proper data structure is req

[PATCH v4 15/16] sched/core: uclamp: add clamp group discretization support

The limited number of clamp groups is required to have both an effective and efficient run-time tracking of the clamp groups required by RUNNABLE tasks. However, being a limited number imposes some constraints on its usage at run-time. Specifically, a System Management Software should "reserve" all

[PATCH v4 13/16] sched/core: uclamp: use percentage clamp values

The utilization is a well defined property of tasks and CPUs with an in-kernel representation based on power-of-two values. The current representation, in the [0..SCHED_CAPACITY_SCALE] range, allows efficient computations in hot-paths and a sufficient fixed point arithmetic precision. However, the

[PATCH v4 16/16] sched/cpufreq: uclamp: add utilization clamping for RT tasks

Currently schedutil enforces a maximum frequency when RT tasks are RUNNABLE. Such a mandatory policy can be made more tunable from userspace thus allowing for example to define a max frequency which is still reasonable for the execution of a specific RT workload. This will contribute to make the R

[PATCH v4 05/16] sched/core: uclamp: enforce last task UCLAMP_MAX

When a util_max clamped task sleeps, its clamp constraints are removed from the CPU. However, the blocked utilization on that CPU can still be higher than the max clamp value enforced while that task was running. This max clamp removal when a CPU is going to be idle could thus allow unwanted CPU fr

[PATCH v4 12/16] sched/core: uclamp: update CPU's refcount on TG's clamp changes

When a task group refcounts a new clamp group, we need to ensure that the new clamp values are immediately enforced to all its tasks which are currently RUNNABLE. This is to ensure that all currently RUNNABLE tasks are boosted and/or clamped as requested as soon as possible. Let's ensure that, whe

[PATCH v4 14/16] sched/core: uclamp: request CAP_SYS_ADMIN by default

The number of clamp groups supported is limited and defined at compile time. However, a malicious user can currently ask for many different clamp values thus consuming all the available clamp groups. Since on properly configured systems we expect only a limited set of different clamp values, the p

[PATCH v4 07/16] sched/core: uclamp: extend cpu's cgroup controller

The cgroup's CPU controller allows to assign a specified (maximum) bandwidth to the tasks of a group. However this bandwidth is defined and enforced only on a temporal base, without considering the actual frequency a CPU is running on. Thus, the amount of computation completed by a task within an a

[PATCH v4 10/16] sched/core: uclamp: use TG's clamps to restrict Task's clamps

When a task's util_clamp value is configured via sched_setattr(2), this value has to be properly accounted in the corresponding clamp group every time the task is enqueued and dequeued. When cgroups are also in use, per-task clamp values have to be aggregated to those of the CPU's controller's Task

[PATCH v4 11/16] sched/core: uclamp: add system default clamps

Clamp values cannot be tuned at the root cgroup level. Moreover, because of the delegation model requirements and how the parent clamps propagation works, if we want to enable subgroups to set a non null util.min, we need to be able to configure the root group util.min to the allow the maximum util

[PATCH v4 08/16] sched/core: uclamp: propagate parent clamps

In order to properly support hierarchical resources control, the cgroup delegation model requires that attribute writes from a child group never fail but still are (potentially) constrained based on parent's assigned resources. This requires to properly propagate and aggregate parent attributes dow

[PATCH v4 06/16] sched/cpufreq: uclamp: add utilization clamping for FAIR tasks

Each time a frequency update is required via schedutil, a frequency is selected to (possibly) satisfy the utilization reported by the CFS class. However, when utilization clamping is in use, the frequency selection should consider the requirements suggested by userspace, for example, to: - boost

[PATCH v4 09/16] sched/core: uclamp: map TG's clamp values into CPU's clamp groups

Utilization clamping requires to map each different clamp value into one of the available clamp groups used by the scheduler's fast-path to account for RUNNABLE tasks. Thus, each time a TG's clamp value sysfs attribute is updated via: cpu_util_{min,max}_write_u64() we need to get (if possible) a

Re: [PATCH] MAINTAINERS: Move entry for Cirrus Logic Madera codecs

On 28/08/18 14:33, Geert Uytterhoeven wrote: To preserve alphabetical sort order. Fixes: 97c2b5cba2044f1c ("mfd: madera: Add register definitions for Cirrus Logic Madera codecs") Signed-off-by: Geert Uytterhoeven --- MAINTAINERS | 32 1 file changed, 16 inse

[PATCH v4 04/16] sched/core: uclamp: update CPU's refcount on clamp changes

Utilization clamp values enforced on a CPU by a task can be updated at run-time, for example via a sched_setattr syscall, while a task is currently RUNNABLE on that CPU. In these cases, the task can be already refcounting a clamp group for its CPU and thus we need to update this reference to ensure

[PATCH v4 03/16] sched/core: uclamp: add CPU's clamp groups accounting

Utilization clamping allows to clamp the utilization of a CPU within a [util_min, util_max] range. This range depends on the set of currently RUNNABLE tasks on a CPU, where each task references two "clamp groups" defining the util_min and the util_max clamp values to be considered for that task. Th

RE: [PATCH 3/3] dmaengine: xilinx_dma: Fix 64-bit simple CDMA transfer

> -Original Message- > From: Vinod > Sent: Tuesday, August 21, 2018 9:26 PM > To: Radhey Shyam Pandey > Cc: dan.j.willi...@intel.com; Michal Simek ; Appana > Durga Kedareswara Rao ; l...@metafoo.de; > dmaeng...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; linux- > ker...@vger.ke

Re: [PATCH v4 3/4] mm/memory_hotplug: Define nodemask_t as a stack variable

On 8/17/18 5:00 AM, Oscar Salvador wrote: > From: Oscar Salvador > > Currently, unregister_mem_sect_under_nodes() tries to allocate a nodemask_t > in order to check whithin the loop which nodes have already been unlinked, > so we do not repeat the operation on them. > > NODEMASK_ALLOC calls km

Re: [PATCH v13 09/13] x86/sgx: Enclave Page Cache (EPC) memory manager

On 08/28/2018 01:35 AM, Jarkko Sakkinen wrote: > On Mon, Aug 27, 2018 at 02:15:34PM -0700, Dave Hansen wrote: >> On 08/27/2018 11:53 AM, Jarkko Sakkinen wrote: >>> +struct sgx_epc_page_ops { >>> + bool (*get)(struct sgx_epc_page *epc_page); >>> + void (*put)(struct sgx_epc_page *epc_page); >>>

Re: [PATCH v3 0/2]: perf: reduce data loss when profiling highly parallel CPU bound workloads

Hi, On 28.08.2018 11:59, Jiri Olsa wrote: > On Mon, Aug 27, 2018 at 08:03:21PM +0300, Alexey Budankov wrote: >> >> Currently in record mode the tool implements trace writing serially. >> The algorithm loops over mapped per-cpu data buffers and stores ready >> data chunks into a trace file using

Re: [PATCH] Properly interpret indirect call in perf annotate.

Em Mon, Aug 27, 2018 at 11:06:21AM +0200, Martin Liška escreveu: > On 08/23/2018 04:12 PM, Arnaldo Carvalho de Melo wrote: > > Em Thu, Aug 23, 2018 at 02:29:34PM +0200, Martin Liška escreveu: > >> The patch changes interpretation of: > >> callq *0x8(%rbx) > >> > >> from: > >> 0.26 │ → callq

Re: [PATCH] Properly interpret indirect call in perf annotate.

Em Thu, Aug 23, 2018 at 02:29:34PM +0200, Martin Liška escreveu: > The patch changes interpretation of: > callq *0x8(%rbx) > > from: > 0.26 │ → callq *8 > to: > 0.26 │ → callq *0x8(%rbx) > > in this can an address is followed by a register, thus > one can't parse only address. > >

Re: [RFC PATCH 08/11] asm-generic/tlb: Track freeing of page-table directories in struct mmu_gather

On Tue, 28 Aug 2018 15:46:38 +0200 Peter Zijlstra wrote: > On Mon, Aug 27, 2018 at 02:44:57PM +1000, Nicholas Piggin wrote: > > > powerpc may be able to use the unmap granule thing to improve > > its page size dependent flushes, but it might prefer to go > > a different way and track start-end f

Re: [PATCH] sparc: Convert to using %pOFn instead of device_node.name

On Mon, Aug 27, 2018 at 8:52 PM Rob Herring wrote: > > In preparation to remove the node name pointer from struct device_node, > convert printf users to use the %pOFn format specifier. > > Cc: "David S. Miller" > Cc: sparcli...@vger.kernel.org > Signed-off-by: Rob Herring > --- > @@ -201,7 +201

Re: [PATCH v3 0/2]: perf: reduce data loss when profiling highly parallel CPU bound workloads

Hi, On 28.08.2018 14:58, Alexey Budankov wrote: > Hi Andi, > > On 28.08.2018 11:59, Jiri Olsa wrote: >> On Mon, Aug 27, 2018 at 08:03:21PM +0300, Alexey Budankov wrote: >>> >>> Currently in record mode the tool implements trace writing serially. >>> The algorithm loops over mapped per-cpu data b

Re: [PATCH v2] mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB

On Tue, 28 Aug 2018 22:16:08 +0800 (CST) "Liu Xiang" wrote: > Thanks for your suggestion. Should I send another patch? Yes please.

Re: [PATCH] Properly interpret indirect call in perf annotate.

Em Tue, Aug 28, 2018 at 11:10:47AM -0300, Arnaldo Carvalho de Melo escreveu: > Em Mon, Aug 27, 2018 at 11:06:21AM +0200, Martin Liška escreveu: > > On 08/23/2018 04:12 PM, Arnaldo Carvalho de Melo wrote: > > > Em Thu, Aug 23, 2018 at 02:29:34PM +0200, Martin Liška escreveu: > > >> The patch changes

Re:Re: [PATCH v2] mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB

Thanks for your suggestion. Should I send another patch? At 2018-08-28 21:23:05, "Boris Brezillon" wrote: >On Tue, 28 Aug 2018 21:21:16 +0800 >Liu Xiang wrote: > >> If the size of spi-nor flash is larger than 16MB, the read_opcode >> is set to SPINOR_OP_READ_1_1_4_4B, and fsl_qspi_get_se

[PATCH] ARM: mm: Stop printing the virtual memory layout

Since commit ad67b74d2469d9b8 ("printk: hash addresses printed with %p"), the virtual memory layout printed during boot up contains "ptrval" instead of actual addresses: Memory: 501296K/524288K available (6144K kernel code, 528K rwdata, 1944K rodata, 1024K init, 7584K bss, 22992K reserved, 0K

[PATCH] unicore32: Stop printing the virtual memory layout

Since commit ad67b74d2469d9b8 ("printk: hash addresses printed with %p"), the virtual memory layout printed during boot up contains "ptrval" instead of actual addresses. Instead of changing the printing to "%px", and leaking virtual memory layout information again, just remove the printing complet

Re: [PATCHv2 0/5] perf/hw_breakpoint: Fix breakpoint modify

Em Thu, Aug 09, 2018 at 02:03:00PM +0200, Jiri Olsa escreveu: > hi, > Milind reported that modify_user_hw_breakpoint wouldn't > allow the breakpoint changing if the new attr had 'disabled' > set to true. > > I found a case where it actualy prevents ptrace user interface > to change the breakpoint.

Re: [PATCH 2/8] mtd: maps: gpio-addr-flash: Fix ioremapped size

On Tue, 21 Aug 2018 16:31:46 +0200 Ricardo Ribalda Delgado wrote: > We should only iomap the area of the chip that is memory mapped. > Otherwise we could be mapping devices beyond the memory space or that > belong to other devices. > Can you add Fixes: ebd71e3a4861 ("mtd: maps: gpio-addr-flash

Re: [PATCH v2 0/3] Add SPI dts node for UniPhier SoCs

2018-07-26 16:09 GMT+09:00 Keiji Hayashibara : > This series adds SPI pin-mux node and SPI node for UniPhier SoCs. > > Changes since v1: > - remove the node for MCSSI which support multiple channels. > Since the current driver doesn't support MCSSI, it deletes this node. Applied. Thanks. > Ku

Re: [PATCH 1/2] ARM: uniphier: dts: add more clocks to Denali NAND controller node

2018-07-20 17:50 GMT+09:00 Masahiro Yamada : > Catch up with the new binding of the Denali IP where three clocks, > "nand", "nand_x", "ecc" are required. > > For UniPhier SoCs, the "nand_x" and "ecc" are tied up because they > are both 200MHz. > > Signed-off-by: Masahiro Yamada > --- Both applie

Re: [PATCH 4/5] perf/hw_breakpoint: Set breakpoint as disabled in modify_user_hw_breakpoint error path

Em Thu, Aug 09, 2018 at 06:30:15PM +0200, Jiri Olsa escreveu: > On Thu, Aug 09, 2018 at 04:17:13PM +0200, Oleg Nesterov wrote: > > On 08/09, Jiri Olsa wrote: > > > - if (err) > > > + if (err) { > > > + bp->attr.disabled = 1; > > > return err; > > > > Yes, but on the second though

Re: [PATCH] unicore32: Stop printing the virtual memory layout

On Tue, Aug 28, 2018 at 7:23 AM, Geert Uytterhoeven wrote: > Since commit ad67b74d2469d9b8 ("printk: hash addresses printed with > %p"), the virtual memory layout printed during boot up contains "ptrval" > instead of actual addresses. > > Instead of changing the printing to "%px", and leaking virt

Re: [GIT PULL] Staging/IIO driver patches for 4.19-rc1

Hi! On Tue, Aug 28, 2018 at 02:36:07PM +0200, Greg KH wrote: > On Tue, Aug 28, 2018 at 10:38:17AM +, Ahmed S. Darwish wrote: > > [ re-send; forgotten lkml CC added; sorry ] > > > > Hi, > > > > On Sat, 18 Aug 2018 17:57:24 +0200, Greg KH wrote: > > [...] > > > addition of some new IIO drivers.

Re: [PATCH] ARM: mm: Stop printing the virtual memory layout

On Tue, Aug 28, 2018 at 7:22 AM, Geert Uytterhoeven wrote: > Since commit ad67b74d2469d9b8 ("printk: hash addresses printed with > %p"), the virtual memory layout printed during boot up contains "ptrval" > instead of actual addresses: > > Memory: 501296K/524288K available (6144K kernel code, 5

Re: [PATCH] memory_hotplug: fix kernel_panic on offline page processing

On 8/28/18 7:25 AM, Michal Hocko wrote: > On Tue 28-08-18 11:05:39, Mikhail Zaslonko wrote: >> Within show_valid_zones() the function test_pages_in_a_zone() should be >> called for online memory blocks only. Otherwise it might lead to the >> VM_BUG_ON due to uninitialized struct pages (when CONFI

Re: VirtIO console hangs

On Tue, 28 Aug 2018 12:54:08 + Matteo Croce wrote: > With kernel 4.19.0-rc1 virtio_console hangs very often. > I can always trigger the bug by pasting some characters in the > terminal window, the console will stop receiving keypresses, but I can > still see output from the console. > Stangel

[PATCH v12 00/12]

livepatch: Atomic replace feature The atomic replace allows to create cumulative patches. They are useful when you maintain many livepatches and want to remove one that is lower on the stack. In addition it is very useful when more patches touch the same function and there are dependencies between

[PATCH v12 02/12] livepatch: Helper macros to define livepatch structures

The definition of struct klp_func might be a bit confusing. The original function is defined by name as a string. The new function is defined by name as a function pointer casted to unsigned long. This patch adds helper macros that hide the different types. The functions are defined just by the na

[PATCH v12 01/12] livepatch: Change void *new_func -> unsigned long new_addr in struct klp_func

The address of the to be patched function and new function is stored in struct klp_func as: void *new_func; unsigned long old_addr; The different naming scheme and type is derived from the way how the addresses are set. @old_addr is assigned at runtime using kallsyms-based search.

[PATCH v12 03/12] livepatch: Shuffle klp_enable_patch()/klp_disable_patch() code

We are going to simplify the API and code by removing the registration step. This would require calling init/free functions from enable/disable ones. This patch just moves the code the code to prevent more forward declarations. This patch does not change the code except of two forward declaration

[PATCH v12 05/12] livepatch: Refuse to unload only livepatches available during a forced transition

module_put() is currently never called in klp_complete_transition() when klp_force is set. As a result, we might keep the reference count even when klp_enable_patch() fails and klp_cancel_transition() is called. This might make an assumption that a module might get blocked in some strange init sta

[PATCH v12 08/12] livepatch: Add atomic replace

From: Jason Baron Sometimes we would like to revert a particular fix. Currently, this is not easy because we want to keep all other fixes active and we could revert only the last applied patch. One solution would be to apply new patch that implemented all the reverted functions like in the origi

[PATCH v12 10/12] livepatch: Atomic replace and cumulative patches documentation

User documentation for the atomic replace feature. It makes it easier to maintain livepatches using so-called cumulative patches. Signed-off-by: Petr Mladek --- Documentation/livepatch/cumulative-patches.txt | 105 + 1 file changed, 105 insertions(+) create mode 100644 D

[PATCH v12 11/12] livepatch: Remove ordering and refuse loading conflicting patches

The atomic replace and cumulative patches were introduced as a more secure way to handle dependent patches. They simplify the logic: + Any new cumulative patch is supposed to take over shadow variables and changes made by callbacks from previous livepatches. + All replaced patches are dis

[PATCH v5 0/5] seccomp trap to userspace

Hi all, Here's v5 of the seccomp user set. Major changes from v4 include: * switching to ioctl vs read/write * adding a way to query whether a notification id is valid * added a sample program that shows a complete usage of the API w/ notes about various TOCTOUs as well as a bunch of smaller f

[PATCH v5 5/5] samples: add an example of seccomp user trap

The idea here is just to give a demonstration of how one could safely use the SECCOMP_RET_USER_NOTIF feature to do mount policies. This particular policy is (as noted in the comment) not very interesting, but it serves to illustrate how one might apply a policy dodging the various TOCTOU issues. v

[PATCH v5 4/5] seccomp: add support for passing fds via USER_NOTIF

The idea here is that the userspace handler should be able to pass an fd back to the trapped task, for example so it can be returned from socket(). I've proposed one API here, but I'm open to other options. In particular, this only lets you return an fd from a syscall, which may not be enough in a

[PATCH v5 3/5] seccomp: add a way to get a listener fd from ptrace

As an alternative to SECCOMP_FILTER_FLAG_GET_LISTENER, perhaps a ptrace() version which can acquire filters is useful. There are at least two reasons this is preferable, even though it uses ptrace: 1. You can control tasks that aren't cooperating with you 2. You can control tasks whose filters blo

[PATCH v5 2/5] seccomp: make get_nth_filter available outside of CHECKPOINT_RESTORE

In the next commit we'll use this same mnemonic to get a listener for the nth filter, so we need it available outside of CHECKPOINT_RESTORE in the USER_NOTIFICATION case as well. v2: new in v2 v3: no changes v4: no changes v5: switch to CHECKPOINT_RESTORE || USER_NOTIFICATION to avoid warning when

[PATCH v12 12/12] selftests/livepatch: introduce tests

From: Joe Lawrence Add a few livepatch modules and simple target modules that the included regression suite can run tests against: - basic livepatching (multiple patches, atomic replace) - pre/post (un)patch callbacks - shadow variable API Signed-off-by: Joe Lawrence --- Documentation/l

[PATCH v12 07/12] livepatch: Use lists to manage patches, objects and functions

From: Jason Baron Currently klp_patch contains a pointer to a statically allocated array of struct klp_object and struct klp_objects contains a pointer to a statically allocated array of klp_func. In order to allow for the dynamic allocation of objects and functions, link klp_patch, klp_object, a

Re: [PATCH v3] mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB

On Tue, 28 Aug 2018 22:32:57 +0800 Liu Xiang wrote: > If the size of spi-nor flash is larger than 16MB, the read_opcode > is set to SPINOR_OP_READ_1_1_4_4B, and fsl_qspi_get_seqid() will > return -EINVAL when cmd is SPINOR_OP_READ_1_1_4_4B. This can > cause read operation fail. > > Fixes: e46ecd

[PATCH v5 1/5] seccomp: add a return code to trap to userspace

This patch introduces a means for syscalls matched in seccomp to notify some other task that a particular filter has been triggered. The motivation for this is primarily for use with containers. For example, if a container does an init_module(), we obviously don't want to load this untrusted code,

[PATCH v12 09/12] livepatch: Remove Nop structures when unused

Replaced patches are removed from the stack when the transition is finished. It means that Nop structures will never be needed again and can be removed. Why should we care? + Nop structures make false feeling that the function is patched even though the ftrace handler has no effect. + Ftr

[PATCH v12 06/12] livepatch: Simplify API by removing registration step

The possibility to re-enable a registered patch was useful for immediate patches where the livepatch module had to stay until the system reboot. The improved consistency model allows to achieve the same result by unloading and loading the livepatch module again. Also we are going to add a feature

Re: [PATCH 4/5] perf/hw_breakpoint: Set breakpoint as disabled in modify_user_hw_breakpoint error path

On Tue, Aug 28, 2018 at 11:29:14AM -0300, Arnaldo Carvalho de Melo wrote: > Em Thu, Aug 09, 2018 at 06:30:15PM +0200, Jiri Olsa escreveu: > > On Thu, Aug 09, 2018 at 04:17:13PM +0200, Oleg Nesterov wrote: > > > On 08/09, Jiri Olsa wrote: > > > > - if (err) > > > > + if (err) { > > > > +

[PATCH v12 04/12] livepatch: Consolidate klp_free functions

The code for freeing livepatch structures is a bit scattered and tricky: + direct calls to klp_free_*_limited() and kobject_put() are used to release partially initialized objects + klp_free_patch() removes the patch from the public list and releases all objects except for patch->kobj

Re: [PATCH 4/5] perf/hw_breakpoint: Set breakpoint as disabled in modify_user_hw_breakpoint error path

Em Tue, Aug 28, 2018 at 04:38:23PM +0200, Jiri Olsa escreveu: > On Tue, Aug 28, 2018 at 11:29:14AM -0300, Arnaldo Carvalho de Melo wrote: > > Em Thu, Aug 09, 2018 at 06:30:15PM +0200, Jiri Olsa escreveu: > > > On Thu, Aug 09, 2018 at 04:17:13PM +0200, Oleg Nesterov wrote: > > > > On 08/09, Jiri Ols

Re: [PATCH] dt-binding: arm/cpus.txt: fix dynamic-power-coefficient unit

Vincent Guittot writes: > Hi Amit, > > On Wed, 22 Aug 2018 at 12:11, Punit Agrawal wrote: >> >> Hi Vincent, >> >> Thanks for the patch. One comment about the choice of units below. >> >> Vincent Guittot writes: >> >> > The unit of dynamic-power-coefficient is described as mW/MHz/uV^2 whereas >>

Re: [PATCH] ata: ahci: Convert to using %pOFn instead of device_node.name

On 8/27/18 7:52 PM, Rob Herring wrote: > In preparation to remove the node name pointer from struct device_node, > convert printf users to use the %pOFn format specifier. Applied for 4.20, thanks. -- Jens Axboe

Re: [PATCH 2/8] mtd: maps: gpio-addr-flash: Fix ioremapped size

Hi Boris On Tue, Aug 28, 2018 at 4:26 PM Boris Brezillon wrote: > > On Tue, 21 Aug 2018 16:31:46 +0200 > Ricardo Ribalda Delgado wrote: > > > We should only iomap the area of the chip that is memory mapped. > > Otherwise we could be mapping devices beyond the memory space or that > > belong to ot

Re: [PATCH v2 11/40] mmc: sdhci: Add a quirk to skip clearing the transfer mode register on tuning

On Mon, 27 Aug 2018 14:01:52 +0300 Adrian Hunter wrote: > On 10/08/18 21:08, Aapo Vienamo wrote: > > Add SDHCI_QUIRK2_TUNE_SKIP_XFERRMODE_REG_PROG to skip programming the > > SDHCI_TRANSFER_MODE in sdhci_set_transfer_mode() if tuning command is > > being sent. > > > > On Tegra210 and Tegra186 th

Re: [PATCH] sched/fair: vruntime should normalize when switching from fair

On 08/27/2018 12:14 PM, Peter Zijlstra wrote: > On Fri, Aug 24, 2018 at 02:24:48PM -0700, Steve Muckle wrote: >> On 08/24/2018 02:47 AM, Peter Zijlstra wrote: > On 08/17/2018 11:27 AM, Steve Muckle wrote: >>> >> When rt_mutex_setprio changes a task's scheduling class to RT, >> we're see

Re: [RESEND] PCI: imx: Initial imx7d pm support

On Tue, Aug 28, 2018 at 01:00:02PM +, Leonard Crestez wrote: > On Tue, 2018-08-28 at 11:07 +0100, Lorenzo Pieralisi wrote: > > On Mon, Aug 27, 2018 at 02:28:37PM +0300, Leonard Crestez wrote: > > > On imx7d the pcie-phy power domain is turned off in suspend and this can > > > make the system ha

Re: [PATCH v8 6/8] ARM: dts: sun7i-a20: Add Video Engine and reserved memory nodes

On Tue, Aug 28, 2018 at 09:34:22AM +0200, Paul Kocialkowski wrote: > This adds nodes for the Video Engine and the associated reserved memory > for the A20. Up to 96 MiB of memory are dedicated to the CMA pool. > > The VPU can only map the first 256 MiB of DRAM, so the reserved memory > pool has to

[PATCH] input: olpc_apsp: remove unused pointer 'np'

From: Colin Ian King Pointer 'nb' is being assigned but is never used hence it is redundant and can be removed. Cleans up clang warning: warning: variable 'np' set but not used [-Wunused-but-set-variable] Signed-off-by: Colin Ian King --- drivers/input/serio/olpc_apsp.c | 2 -- 1 file changed

[PATCH 03/10] mm: Introduce vmf_insert_pfn_prot

Like vm_insert_pfn_prot(), but returns a vm_fault_t instead of an errno. Also unexport vm_insert_pfn_prot as it has no modular users. Signed-off-by: Matthew Wilcox --- include/linux/mm.h | 2 ++ mm/memory.c| 47 ++ 2 files changed, 33 insertio

[PATCH 10/10] mm: Convert insert_pfn to vm_fault_t

All callers convert its errno into a vm_fault_t, so convert it to return a vm_fault_t directly. Signed-off-by: Matthew Wilcox --- mm/memory.c | 24 +--- 1 file changed, 5 insertions(+), 19 deletions(-) diff --git a/mm/memory.c b/mm/memory.c index 9fef202b4ea7..368b65390762 1

[PATCH 08/10] mm: Inline vm_insert_pfn_prot into caller

vm_insert_pfn_prot() is only called from vmf_insert_pfn_prot(), so inline it and convert some of the errnos into vm_fault codes earlier. Signed-off-by: Matthew Wilcox --- mm/memory.c | 55 +++-- 1 file changed, 24 insertions(+), 31 deletions(-) di

<    1   2   3   4   5   6   7   >