[HMM 13/16] mm/migrate: allow migrate_vma() to alloc new page on empty entry

This allow caller of migrate_vma() to allocate new page for empty CPU page table entry. It only support anoymous memory and it won't allow new page to be instance if userfaultfd is armed. This is useful to device driver that want to migrate a range of virtual address and would rather allocate new

Re: [BUG] stack tracing causes: kernel/module.c:271 module_assert_mutex_or_preempt

On Wed, Apr 05, 2017 at 03:52:23PM -0400, Steven Rostedt wrote: > On Wed, 5 Apr 2017 12:39:28 -0700 > "Paul E. McKenney" wrote: > > > Here's the crucial part of that stack dump again: > > > > > > save_stack_trace+0x1b/0x1d > > > check_stack+0xec/0x24a > > >

[HMM 06/16] mm/migrate: new memory migration helper for use with device memory v4

This patch add a new memory migration helpers, which migrate memory backing a range of virtual address of a process to different memory (which can be allocated through special allocator). It differs from numa migration by working on a range of virtual address and thus by doing migration in chunk

Re: [PATCH 0/6] mm: make movable onlining suck less

On Wed, Apr 05, 2017 at 06:34:39PM +0200, Michal Hocko wrote: This is really interesting. Because add_memory_resource does the following /* call arch's memory hotadd */ ret = arch_add_memory(nid, start, size); if (ret < 0) goto error; /* we

Is it safe for kthreadd to drain_all_pages?

Hi Mel, I suspect that it's not safe for kthreadd to drain_all_pages(); but I haven't studied flush_work() etc, so don't really know what I'm talking about: hoping that you will jump to a realization. 4.11-rc has been giving me hangs after hours of swapping load. At first they looked like

Re: [BUG] stack tracing causes: kernel/module.c:271 module_assert_mutex_or_preempt

On Wed, 5 Apr 2017 12:08:10 -0700 "Paul E. McKenney" wrote: > On Wed, Apr 05, 2017 at 02:54:25PM -0400, Steven Rostedt wrote: > > On Wed, 5 Apr 2017 10:59:25 -0700 > > "Paul E. McKenney" wrote: > > > > > > Note, this has nothing to do

[PATCH] misc: sram-exec: Use aligned fncpy instead of memcpy

Currently the sram-exec functionality, which allows allocation of executable memory and provides an API to move code to it, is only selected in configs for the ARM architecture. Based on commit 5756e9dd0de6 ("ARM: 6640/1: Thumb-2: Symbol manipulation macros for function body copying") simply

Re: [PATCH v2] crypto: arm64/sha: Add constant operand modifier to ASM_EXPORT

On 5 April 2017 at 19:34, Matthias Kaehlcke wrote: > The operand is an integer constant, make the constness explicit by > adding the modifier. This is needed for clang to generate valid code > and also works with gcc. > > Also change the constraint of the operand from 'I'

Re: [PATCH v6] vfio error recovery: kernel support

On Wed, 5 Apr 2017 16:54:33 +0800 Cao jin wrote: > Sorry for late. Distracted by other problem for a while. > > On 03/31/2017 02:16 AM, Alex Williamson wrote: > > On Thu, 30 Mar 2017 21:00:35 +0300 > > >> > >>> > >>> I also asked in my previous

Re: [BUG] stack tracing causes: kernel/module.c:271 module_assert_mutex_or_preempt

On Wed, Apr 05, 2017 at 03:21:41PM -0400, Steven Rostedt wrote: > On Wed, 5 Apr 2017 12:08:10 -0700 > "Paul E. McKenney" wrote: > > > On Wed, Apr 05, 2017 at 02:54:25PM -0400, Steven Rostedt wrote: > > > On Wed, 5 Apr 2017 10:59:25 -0700 > > > "Paul E. McKenney"

Re: sudo x86info -a => kernel BUG at mm/usercopy.c:78!

On Tue, Apr 4, 2017 at 5:22 PM, Linus Torvalds wrote: > On Tue, Apr 4, 2017 at 3:55 PM, Linus Torvalds > wrote: >> >> I already explained what the likely fix is: make devmem_is_allowed() >> return a ternary value, so that those things

Re: [PATCH v2 00/11] fujitsu-laptop: backlight cleanup

> On Wed, Apr 05, 2017 at 08:48:59AM +0200, Michał Kępień wrote: > > This series introduces further changes to the way LCD backlight is > > handled by fujitsu-laptop. These changes include fixing a bug in code > > responsible for generating brightness-related input events, cleaning up > >

Re: [PATCH v2 1/2] x86/mce/AMD: Redo use of SMCA MCA_DE{STAT,ADDR} registers

On Wed, Apr 05, 2017 at 07:29:48PM +, Ghannam, Yazen wrote: > If it's set, then I expect a Deferred error in MCA_STATUS since any > Correctable > Errors will be overwritten. Multiple bank types can generate Deferred errors > so there may also be cases where for some types a valid

[PATCH 15/24] asus-wmi: Restrict debugfs interface when the kernel is locked down

From: Matthew Garrett We have no way of validating what all of the Asus WMI methods do on a given machine - and there's a risk that some will allow hardware state to be manipulated in such a way that arbitrary code can be executed in the kernel, circumventing module

[PATCH 20/24] bpf: Restrict kernel image access functions when the kernel is locked down

From: Chun-Yi Lee There are some bpf functions can be used to read kernel memory: bpf_probe_read, bpf_probe_write_user and bpf_trace_printk. These allow private keys in kernel memory (e.g. the hibernation image signing key) to be read by an eBPF program. Prohibit those functions

[PATCH 19/24] acpi: Disable APEI error injection if the kernel is locked down

From: Linn Crosetto ACPI provides an error injection mechanism, EINJ, for debugging and testing the ACPI Platform Error Interface (APEI) and other RAS features. If supported by the firmware, ACPI specification 5.0 and later provide for a way to specify a physical memory address to

[PATCH 12/24] PCI: Lock down BAR access when the kernel is locked down

From: Matthew Garrett Any hardware that can potentially generate DMA has to be locked down in order to avoid it being possible for an attacker to modify kernel code, allowing them to circumvent disabled module loading or module signing. Default to paranoid - in future

[PATCH 21/24] scsi: Lock down the eata driver

When the kernel is running in secure boot mode, we lock down the kernel to prevent userspace from modifying the running kernel image. Whilst this includes prohibiting access to things like /dev/mem, it must also prevent access by means of configuring driver modules in such a way as to cause a

[PATCH 16/24] ACPI: Limit access to custom_method when the kernel is locked down

From: Matthew Garrett custom_method effectively allows arbitrary access to system memory, making it possible for an attacker to circumvent restrictions on module loading. Disable it if the kernel is locked down. Signed-off-by: Matthew Garrett

[PATCH 18/24] acpi: Disable ACPI table override if the kernel is locked down

From: Linn Crosetto >From the kernel documentation (initrd_table_override.txt): If the ACPI_INITRD_TABLE_OVERRIDE compile option is true, it is possible to override nearly any ACPI table provided by the BIOS with an instrumented, modified one. When securelevel is set, the

[PATCH 17/24] acpi: Ignore acpi_rsdp kernel param when the kernel has been locked down

From: Josh Boyer This option allows userspace to pass the RSDP address to the kernel, which makes it possible for a user to circumvent any restrictions imposed on loading modules. Ignore the option when the kernel is locked down. Signed-off-by: Josh Boyer

[PATCH v9 3/3] printk: fix double printing with earlycon

If a console was specified by ACPI SPCR table _and_ command line parameters like "console=ttyAMA0" _and_ "earlycon" were specified, then log messages appear twice. The root cause is that the code traverses the list of specified consoles (the `console_cmdline` array) and stops at the first match.

[PATCH 14/24] x86: Restrict MSR access when the kernel is locked down

From: Matthew Garrett Writing to MSRs should not be allowed if the kernel is locked down, since it could lead to execution of arbitrary code in kernel mode. Based on a patch by Kees Cook. Signed-off-by: Matthew Garrett Signed-off-by:

[PATCH 09/24] kexec_file: Disable at runtime if securelevel has been set

From: Chun-Yi Lee When KEXEC_VERIFY_SIG is not enabled, kernel should not loads image through kexec_file systemcall if securelevel has been set. This code was showed in Matthew's patch but not in git: https://lkml.org/lkml/2015/3/13/778 Cc: Matthew Garrett

[HMM 07/16] mm/migrate: migrate_vma() unmap page from vma while collecting pages

Common case for migration of virtual address range is page are map only once inside the vma in which migration is taking place. Because we already walk the CPU page table for that range we can directly do the unmap there and setup special migration swap entry. Signed-off-by: Jérôme Glisse

[HMM 08/16] mm/hmm: heterogeneous memory management (HMM for short)

HMM provides 3 separate types of functionality: - Mirroring: synchronize CPU page table and device page table - Device memory: allocating struct page for device memory - Migration: migrating regular memory to device memory This patch introduces some common helpers and definitions to

[HMM 05/16] mm/migrate: new migrate mode MIGRATE_SYNC_NO_COPY

Introduce a new migration mode that allow to offload the copy to a device DMA engine. This changes the workflow of migration and not all address_space migratepage callback can support this. So it needs to be tested in those cases. This is intended to be use by migrate_vma() which itself is use

Re: [PATCH 0/6] mm: make movable onlining suck less

On Wed 05-04-17 20:15:02, Michal Hocko wrote: > On Wed 05-04-17 12:32:49, Reza Arbab wrote: > > On Wed, Apr 05, 2017 at 05:42:59PM +0200, Michal Hocko wrote: > > >But one thing that is really bugging me is how could you see low pfns in > > >the previous oops. Please drop the last patch and

RE: [PATCH 1/2 v2] dt-bindings: qoriq-clock: Add coreclk

Hello Stephen and Michael, Do you have any comments on this patch set which was acked by Rob? Regards, Andy > -Original Message- > From: Yuantian Tang [mailto:andy.t...@nxp.com] > Sent: Monday, March 20, 2017 10:37 AM > To: mturque...@baylibre.com > Cc: sb...@codeaurora.org;

[PATCH v3 1/1] perf tools: fix perf build with ARCH=x86_64

From: Jiada Wang with commit: 0a943cb10ce78 (tools build: Add HOSTARCH Makefile variable) the following build failure is seen when build with ARCH=x86_64 In file included from util/event.c:2:0: tools/include/uapi/linux/mman.h:4:27: fatal error: uapi/asm/mman.h: No

[PATCH v3 0/1] fix perf build issue when ARCH=x86_64

From: Jiada Wang Changes from v3: replace ARCH with SRCARCH in perf Changes from v2: added function purify-arch, transforms both HOSTARCH and ARCH to supported values Jiada Wang (1): perf tools: fix perf build with ARCH=x86_64 tools/perf/Makefile.config | 38

Re: [PATCH 4/9] bio-integrity: fix interface for bio_integrity_trim v2

On 04/04/2017 08:56 PM, Dmitry Monakhov wrote: > bio_integrity_trim inherent it's interface from bio_trim and accept > offset and size, but this API is error prone because data offset > must always be insync with bio's data offset. That is why we have > integrity update hook in bio_advance() > >

Re: [PATCH 0/6] mm: make movable onlining suck less

On Tue 04-04-17 21:41:22, Michal Hocko wrote: > On Tue 04-04-17 13:30:13, Reza Arbab wrote: > > On Tue, Apr 04, 2017 at 06:44:53PM +0200, Michal Hocko wrote: > > >Thanks for your testing! This is highly appreciated. > > >Can I assume your Tested-by? > > > > Of course! Not quite done, though. >

Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")

On Mon, Apr 03, 2017 at 07:14:22PM +0300, Michael S. Tsirkin wrote: > On Mon, Apr 03, 2017 at 04:18:23PM +0200, Christoph Hellwig wrote: > > Mike, > > > > can you try the patch below? > > > > --- > > >From fe41a30b54878cc631623b7511267125e0da4b15 Mon Sep 17 00:00:00 2001 > > From: Christoph

Re: [PATCH 0/6] mm: make movable onlining suck less

On Tue 04-04-17 16:43:39, Reza Arbab wrote: > On Tue, Apr 04, 2017 at 09:41:22PM +0200, Michal Hocko wrote: > >On Tue 04-04-17 13:30:13, Reza Arbab wrote: > >>I think I found another edge case. You > >>get an oops when removing all of a node's memory: > >> > >>__nr_to_section > >>__pfn_to_section

[PATCH v2 07/11] platform/x86: fujitsu-laptop: make disable_brightness_adjust a boolean

Due to the way the disable_brightness_adjust module parameter is currently handled in acpi_fujitsu_bl_add(), it can only be set to either 0 or 1, which effectively makes it a boolean. Emphasize that by changing module parameter type to bool. Do not announce parameter value in a debug message as

[PATCH v2 00/11] fujitsu-laptop: backlight cleanup

This series introduces further changes to the way LCD backlight is handled by fujitsu-laptop. These changes include fixing a bug in code responsible for generating brightness-related input events, cleaning up handling of module parameters, reducing code duplication, removing superfluous debug

[PATCH v2 11/11] platform/x86: fujitsu-laptop: remove redundant fields from struct fujitsu_bl

The dev field of struct fujitsu_bl is assigned in acpi_fujitsu_bl_add(), but never used afterwards. brightness_changed is set in get_lcd_level() and then its value is only printed in a debug message, so it does not influence execution flow. Remove both fields as they are redundant. Update the

[PATCH v2 10/11] platform/x86: fujitsu-laptop: account for backlight power when determining brightness

The comment for the get_brightness backlight device callback in include/linux/backlight.h states that it should "return the current backlight brightness (accounting for power, fb_blank etc.)". fujitsu-laptop violates that premise by simply returning the value to which ACPI function GBLL evaluates

Re: [RFC PATCH 3/6] x86/apic: Extract APIC timer related code from apic_bsp_setup()

On Wed, 29 Mar 2017, Dou Liyang wrote: > +/* Setup local APIC timer and get the Id*/ > +static int __init apic_bsp_timer_setup(void) This does not make sense. The id and the timers have nothing to do with each other. > +{ > + int id; > + > + if (x2apic_mode) > + id =

Re: [PATCH 21/26] x86/mm: add support of additional page table level during early boot

On Mon, Mar 13, 2017 at 08:18:10AM +0100, Ingo Molnar wrote: > > * Kirill A. Shutemov wrote: > > > This patch adds support for 5-level paging during early boot. > > It generalizes boot for 4- and 5-level paging on 64-bit systems with > > compile-time switch

Re: [linux-sunxi] [PATCH 02/11] arm64: allwinner: a64: add NMI controller on A64

On Wed, Apr 5, 2017 at 3:28 PM, Maxime Ripard wrote: > On Wed, Apr 05, 2017 at 02:20:31PM +0800, Chen-Yu Tsai wrote: >> On Wed, Apr 5, 2017 at 2:11 PM, Maxime Ripard >> wrote: >> > On Wed, Apr 05, 2017 at 11:51:45AM +0800,

Re: [PATCH v6 17/39] platform: add video-multiplexer subdevice driver

Am Mittwoch, den 05.04.2017, 13:18 +0200 schrieb Pavel Machek: > Hi! > > > + * video stream multiplexer controlled via gpio or syscon > > + * > > + * Copyright (C) 2013 Pengutronix, Sascha Hauer > > + * Copyright (C) 2016 Pengutronix, Philipp Zabel

Re: [tip:x86/mm] x86/asm: Remove __VIRTUAL_MASK_SHIFT==47 assert

On Wed, Apr 05, 2017 at 01:50:27PM +0200, Denys Vlasenko wrote: > Er "Change top bits ... ((47 or 56 [bits] depending on paging mode)"? > I know that's wrong and that's not what you meant to say, > but it can be read this way too. "47th" instead of "47" > would eliminate this reading, but you

Re: [PATCH 04/16] fpga: intel: pcie: parse feature list and create platform device for features.

On Mon, Apr 03, 2017 at 04:44:15PM -0500, Alan Tull wrote: > On Thu, Mar 30, 2017 at 7:08 AM, Wu Hao wrote: > > From: Xiao Guangrong > > > > Device Featuer List structure creates a link list of feature headers > > within the MMIO space to provide

Re: [PATCH 4/4] mtd: nand: nandsim: convert to memalloc_noreclaim_*()

On Wed 05-04-17 13:39:16, Vlastimil Babka wrote: > On 04/05/2017 01:36 PM, Richard Weinberger wrote: > > Michal, > > > > Am 05.04.2017 um 13:31 schrieb Michal Hocko: > >> On Wed 05-04-17 09:47:00, Vlastimil Babka wrote: > >>> Nandsim has own functions set_memalloc() and clear_memalloc() for

Re: [PATCH 1/4] mm/vmalloc: allow to call vfree() in atomic context

On Wed 05-04-17 13:42:19, Vlastimil Babka wrote: > On 03/30/2017 04:48 PM, Andrey Ryabinin wrote: [...] > > --- a/mm/vmalloc.c > > +++ b/mm/vmalloc.c > > @@ -737,7 +737,8 @@ static void free_vmap_area_noflush(struct vmap_area *va) > > /* After this point, we may free va at any time */ > >

[PATCH v2] soc: qcom: smsm: Improve error handling, quiesce probe deferral

Don't use size if info indicates an error condition. Previously a non-ENOENT error (such as -EPROBE_DEFER) would lead to size being used even though it hadn't necessarily been initialized in qcom_smem_get. Don't print an error message in the -EPROBE_DEFER case. Signed-off-by: Jonathan Neuschäfer

Re: [PATCH v4 5/8] ARM: sun8i: a33: add thermal sensor

Hi, On Wed, Apr 05, 2017 at 11:06:31AM +0200, Quentin Schulz wrote: > This adds the DT node for the thermal sensor present in the Allwinner > A33 GPADC. > > Signed-off-by: Quentin Schulz > --- > > v3: > - switched compatible to allwinner,sun8i-a33-ths, >

Re: [PATCH v2] tpm_tis: convert to using locality callbacks

On Mon, Mar 27, 2017 at 08:46:04AM -0700, Jerry Snitselaar wrote: > This patch converts tpm_tis to use of the new tpm class ops > request_locality, and relinquish_locality. > > With the move to using the callbacks, release_locality is changed so > that we now release the locality even if there is

Re: [PATCH V8 1/6] LIBIO: Introduce a generic PIO mapping method

Hi, Thanks for your report! I am sorry for that! This issue was caused by missing the '#include ' in logic_pio.c for some architectures where the 'asm-generic/io.h' wasn't been included. Will be fixed in the next V9. Apologized for this! -Zhichang On 04/01/2017 01:58 PM, kbuild test robot

Re: [PATCH v4 8/8] ARM: sun8i: sina33: add highest OPP of CPUs

On Wed, Apr 05, 2017 at 11:06:34AM +0200, Quentin Schulz wrote: > The A33 supports 1.1GHz and 1.2GHz frequencies at 1.32V and the Sinlinx > SinA33 has its cpu-supply property set in the cpu DT node. > > Therefore, CPUfreq knows how to handle the regulator in charge of the > CPU and can adjust its

Re: [PATCH v2] i2c/muxes/i2c-mux-ltc4306: LTC4306 and LTC4305 I2C multiplexer/switch

On 04.04.2017 11:28, Peter Rosin wrote: *snip* *snip* +static int ltc4306_gpio_get(struct gpio_chip *chip, unsigned int offset) +{ + struct ltc4306 *data = gpiochip_get_data(chip); + int ret = 0; + + if (gpiochip_line_is_open_drain(chip, offset) || +

Re: [PATCH] HID: asus: support backlight on USB keyboards

On Apr 05 2017 or thereabouts, Carlo Caione wrote: > On Wed, Apr 5, 2017 at 11:41 AM, Benjamin Tissoires > wrote: > > Hi Carlo, > > [cut] > >> With this patch we create the usual 'asus::kbd_backlight' sysfs entry > > > > Please change 'sysfs' with 'led class' or

Re: [PATCH v6 03/11] powerpc/powernv: Detect supported IMC units and its events

On Tuesday 04 April 2017 07:11 AM, Daniel Axtens wrote: Madhavan Srinivasan writes: From: Hemant Kumar Parse device tree to detect IMC units. Traverse through each IMC unit node to find supported events and corresponding unit/scale

Re: [PATCHv2] ptrace: fix PTRACE_LISTEN race corrupting task->state

On 04/04, bseg...@google.com wrote: > > v2: slight clarification in comments, put the conditional around the > whole wakeup area Acked-by: Oleg Nesterov and I think this should go to -stable. > Oleg mentioned a preference for making LISTEN unfreeze instead; I have > no

[PATCH v5 2/2] tcmu: Add global data block pool support

From: Xiubo Li For each target there will be one ring, when the target number grows larger and larger, it could eventually runs out of the system memories. In this patch for each target ring, currently for the cmd area the size will be fixed to 8MB and for the data

[PATCH v5 1/2] tcmu: Add dynamic growing data area feature support

From: Xiubo Li Currently for the TCMU, the ring buffer size is fixed to 64K cmd area + 1M data area, and this will be bottlenecks for high iops. The struct tcmu_cmd_entry {} size is fixed about 112 bytes with iovec[N] & N <= 4, and the size of struct iovec is about

Re: [linux-sunxi] [PATCH 02/11] arm64: allwinner: a64: add NMI controller on A64

On Wed, Apr 05, 2017 at 11:51:45AM +0800, Chen-Yu Tsai wrote: > On Wed, Apr 5, 2017 at 2:01 AM, Icenowy Zheng wrote: > > Allwinner A64 SoC features a NMI controller, which is usually connected > > to the AXP PMIC. > > > > Add support for it. > > > > Signed-off-by: Icenowy Zheng

[PATCH v5 0/2] tcmu: Dynamic growing data area support

From: Xiubo Li Changed for V5: - Rebase to the newest target-pending repository. - Add as many comments as possbile to make the patch more readable. - Move tcmu_handle_completions() in timeout handler to unmap thread and then replace the spin lock with mutex

Re: [PATCH] mmc: core: add mmc-card hardware reset enable support

On 04/05/2017 06:40 AM, Jaehoon Chung wrote: > Hi, > > On 04/04/2017 11:16 PM, Richard Leitner wrote: >> Some eMMCs disable their hardware reset line (RST_N) by default. To enable >> it the host must set the corresponding bit in ECSD. An example for such >> a device is the Micron MTFCxGACAANA-4M.

linux-next: Tree for Apr 5

Hi all, Changes since 20170404: The crypto tree gained a conflict against the amlogic tree. The drm tree gained a conflict against Linus' tree. The mfd tree still had its build failure for which I reverted a commit. The keys tree lost its build failure. The tip tree gained a build failure

Re: [PATCH 1/9] bio-integrity: Do not allocate integrity context for bio w/o data

On 04/04/2017 08:56 PM, Dmitry Monakhov wrote: > If bio has no data, such as ones from blkdev_issue_flush(), > then we have nothing to protect. > > This patch prevent bugon like follows: > > kfree_debugcheck: out of range ptr ac1fa1d106742a5ah > kernel BUG at mm/slab.c:2773! > invalid opcode:

Re: [PATCH 2/9] bio-integrity: bio_trim should truncate integrity vector accordingly

On 04/04/2017 08:56 PM, Dmitry Monakhov wrote: > Reviewed-by: Christoph Hellwig > Signed-off-by: Dmitry Monakhov > --- > block/bio.c | 4 > 1 file changed, 4 insertions(+) > > diff --git a/block/bio.c b/block/bio.c > index e75878f..fa84323 100644 > ---

Re: [PATCH 1/3] phy: sun4i-usb: enable PHY0 dual route switching for A64 USB PHY

On Wed, Apr 05, 2017 at 02:45:16AM +0800, Icenowy Zheng wrote: > Allwinner A64 SoC features a switchable PHY0 like the one in H3, which > can switch between a MUSB controller and a pair of OHCI/EHCI controller. > > Enable PHY0 route auto switching for A64. > > Signed-off-by: Icenowy Zheng

[PATCH v4 4/8] iio: adc: sun4i-gpadc-iio: add support for A33 thermal sensor

This adds support for the Allwinner A33 thermal sensor. Unlike the A10, A13 and A31, the Allwinner A33 only has one channel which is dedicated to the thermal sensor. Moreover, its thermal sensor does not generate interruptions, thus we only need to directly read the register storing the

[PATCH] tpm_crb: remove a cruft constant

Remove a useless constant that slipped through me when I did the code review. This commit fixes the issue. Cc: Jiandi An Fixes: 69c558de63c7 ("tpm/tpm_crb: Enable TPM CRB interface for ARM64") Signed-off-by: Jarkko Sakkinen ---

Re: [PATCH] media: mtk-vcodec: remove informative log

On Wed, 2017-04-05 at 18:54 +0800, Minghsiu Tsai wrote: > Driver is stable. Remove DEBUG definition from driver. > > There are debug message in /var/log/messages if DEBUG is defined, > such as: > [MTK_V4L2] level=0 fops_vcodec_open(),170: decoder capability 0 > [MTK_V4L2] level=0

Re: [RFC PATCH 0/4] fs: introduce new writeback error tracking infrastructure and convert ext4 to use it

On Wed, 2017-04-05 at 09:13 +1000, NeilBrown wrote: > On Tue, Apr 04 2017, Jeff Layton wrote: > > > On Tue, 2017-04-04 at 09:12 -0700, Matthew Wilcox wrote: > > > On Tue, Apr 04, 2017 at 08:17:48AM -0400, Jeff Layton wrote: > > > > Agreed that we should focus on POSIX compliance. I'll also note

Re: [tip:x86/mm] x86/asm: Remove __VIRTUAL_MASK_SHIFT==47 assert

On Tue, Apr 04, 2017 at 05:36:33PM +0200, Denys Vlasenko wrote: > > diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S > > index 044d18e..f07b4ef 100644 > > --- a/arch/x86/entry/entry_64.S > > +++ b/arch/x86/entry/entry_64.S > > @@ -265,12 +265,9 @@ return_from_SYSCALL_64: > >

Re: [Xen-devel] [PATCH v2] xen, kdump: handle pv domain in paddr_vmcoreinfo_note()

On Tue, 4 Apr 2017 12:42:53 -0700 (PDT) Daniel Kiper wrote: > > On 03/04/17 14:42, Daniel Kiper wrote: > > > On Fri, Mar 31, 2017 at 12:14:38PM +0200, Juergen Gross wrote: > > >> For kdump to work correctly it needs the physical address of > > >> vmcoreinfo_note. When

Re: [PATCH v6 17/39] platform: add video-multiplexer subdevice driver

Hi! > + * video stream multiplexer controlled via gpio or syscon > + * > + * Copyright (C) 2013 Pengutronix, Sascha Hauer > + * Copyright (C) 2016 Pengutronix, Philipp Zabel This is actually quite interesting. Same email address for two people...

Re: [PATCH 1/4] mm: prevent potential recursive reclaim due to clearing PF_MEMALLOC

On Wed 05-04-17 09:46:57, Vlastimil Babka wrote: > The function __alloc_pages_direct_compact() sets PF_MEMALLOC to prevent > deadlock during page migration by lock_page() (see the comment in > __unmap_and_move()). Then it unconditionally clears the flag, which can clear > a > pre-existing

[PATCH] MAINTAINERS: Add Laurent and Andrzej as maintainers for bridge drivers

Add Laurent and Andrzej as maintainers for DRM bridge chip drivers. They actively review and contribute to bridge drivers and the bridge API. Cc: Laurent Pinchart Cc: Andrzej Hajda Signed-off-by: Archit Taneja ---

Re: [PATCH v3 0/3] add support of usb2-phy for rk3328

On Monday 06 March 2017 06:59 AM, Meng Dongyang wrote: > The config information of RK3328 about address and port property > is different from other platform. So adds config information in the > data of match table and the device tree bindings description for > usb2-phy. > > Changes in v2: > -

Re: [tpmdd-devel] Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot

Hi Paul, > tpm tpm0: Unable to read burstcount > tpm tpm0: tpm_transmit: tpm_send: error -16 > tpm_tis tpm_tis: Could not get TPM timeouts and durations This looks like a regression I had on ThinkPad X61S. You can try with a patch from the following commit which fixed it for me:

Re: [PATCH v3 00/11] add thermal throttling to Allwinner A33 SoC

Hi Lee, On 05/04/2017 11:57, Lee Jones wrote: > On Wed, 05 Apr 2017, Quentin Schulz wrote: >> On 04/04/2017 10:31, Lee Jones wrote: >>> On Tue, 21 Mar 2017, Quentin Schulz wrote: v3: - fixed compatible name in DT and in documentation, - fixed DT node name and label, -

Re: [PATCH 3/4] treewide: convert PF_MEMALLOC manipulations to new helpers

On Wed 05-04-17 09:46:59, Vlastimil Babka wrote: > We now have memalloc_noreclaim_{save,restore} helpers for robust setting and > clearing of PF_MEMALLOC. Let's convert the code which was using the generic > tsk_restore_flags(). No functional change. It would be really great to revisit why those

Re: [PATCH v5 1/3] phy: core: Add support for clock and reset to the phy core

On Tuesday 14 March 2017 01:57 AM, Alban wrote: > On Mon, 13 Feb 2017 23:25:44 +0100 > Alban wrote: > >> From: Alban Bedel >> >> Signed-off-by: Alban Bedel >> --- >> drivers/phy/phy-core.c | 48 >>

[PATCH] get_maintainer: apply all .get_maintainer.ignore files

Currently we are searching "./:$ENV{HOME}/:.scripts/" for ignore file, but would always get "./.get_maintainer.ignore" only. This patch applies all .get_maintainer.ignore, so it would be easier to add ignore list locally. Signed-off-by: Jeffy Chen ---

Re: [PATCH 2/4] mm: introduce memalloc_noreclaim_{save,restore}

On Wed 05-04-17 09:46:58, Vlastimil Babka wrote: > The previous patch has shown that simply setting and clearing PF_MEMALLOC in > current->flags can result in wrongly clearing a pre-existing PF_MEMALLOC flag > and potentially lead to recursive reclaim. Let's introduce helpers that > support >

Re: [PATCH v6 19/39] media: Add i.MX media core driver

Hi! > +References > +-- > + > +[1] "i.MX 6Dual/6Quad Applications Processor Reference Manual" > +[2] "i.MX 6Solo/6DualLite Applications Processor Reference Manual" [2] is not present in the text above. [1] is there many times. What is purpose of this section?

Re: [PATCH 4/4] mtd: nand: nandsim: convert to memalloc_noreclaim_*()

On Wed 05-04-17 09:47:00, Vlastimil Babka wrote: > Nandsim has own functions set_memalloc() and clear_memalloc() for robust > setting and clearing of PF_MEMALLOC. Replace them by the new generic helpers. > No functional change. This one smells like an abuser. Why the hell should read/write path

Re: [PATCH v6 19/39] media: Add i.MX media core driver

Hi! > +https://boundarydevices.com/products/nit6x_5mp I'd use /product/ in url, as it redirects there. > +https://boundarydevices.com/product/nit6x_5mp_mipi ..and for consistency. > +The following example configures a direct conversion pipeline to capture > +from the OV5640, transmitting on

Re: [PATCH 4/4] mtd: nand: nandsim: convert to memalloc_noreclaim_*()

Michal, Am 05.04.2017 um 13:31 schrieb Michal Hocko: > On Wed 05-04-17 09:47:00, Vlastimil Babka wrote: >> Nandsim has own functions set_memalloc() and clear_memalloc() for robust >> setting and clearing of PF_MEMALLOC. Replace them by the new generic helpers. >> No functional change. > > This

Re: [PATCH 1/4] mm: prevent potential recursive reclaim due to clearing PF_MEMALLOC

On 04/05/2017 10:46 AM, Vlastimil Babka wrote: > The function __alloc_pages_direct_compact() sets PF_MEMALLOC to prevent > deadlock during page migration by lock_page() (see the comment in > __unmap_and_move()). Then it unconditionally clears the flag, which can clear > a > pre-existing

Re: [PATCH 4/4] mtd: nand: nandsim: convert to memalloc_noreclaim_*()

On 04/05/2017 01:36 PM, Richard Weinberger wrote: > Michal, > > Am 05.04.2017 um 13:31 schrieb Michal Hocko: >> On Wed 05-04-17 09:47:00, Vlastimil Babka wrote: >>> Nandsim has own functions set_memalloc() and clear_memalloc() for robust >>> setting and clearing of PF_MEMALLOC. Replace them by

RE: [PATCH 11/16] fpga: intel: fme: add partial reconfiguration sub feature support

> >> The fpga_image_info struct started life as just image specific info, > >> but I want it to go in the direction of including parameters needed to > >> program it this specific time. Otherwise we are stuck having to keep > >> adding parameters as our use of FPGA develops. It probably could be

Re: [PATCH 1/4] mm/vmalloc: allow to call vfree() in atomic context

On 03/30/2017 04:48 PM, Andrey Ryabinin wrote: > On 03/30/2017 03:00 PM, Thomas Hellstrom wrote: > >>> >>> if (unlikely(nr_lazy > lazy_max_pages())) >>> - try_purge_vmap_area_lazy(); >> >> Perhaps a slight optimization would be to schedule work iff >> !mutex_locked(_purge_lock)

Re: [PATCH v4 0/3] phy: Group phy drivers based on vendor listing

Hi Vivek, On Wednesday 05 April 2017 05:07 PM, Vivek Gautam wrote: > Hi Kishon, > > > On 04/05/2017 04:34 PM, Kishon Vijay Abraham I wrote: >> Hi Vivek, >> >> On Monday 20 March 2017 06:49 PM, Vivek Gautam wrote: >>> This is the next version to an earlier posted series [1]. >>> Missed Cc'ing

[PATCH v2] iTCO_wdt: all versions count down twice

The ICH9 is listed as having TCO v2, and indeed the behavior in the datasheet corresponds to v2 (for example the NO_REBOOT flag is accessible via the 16KiB-aligned Root Complex Base Address). However, the TCO counts twice just like in v1; the documentation of the SECOND_TO_STS bit says: "ICH9

Re: [RFC PATCH 2/6] x86/apic: Construct a framework for setuping APIC mode as soon as possible

On Wed, 29 Mar 2017, Dou Liyang wrote: > Now, there are two ways to setup local apic and io-apic in X86 arch: > 1. In an SMP-capable system, it will be done when preparing the > cpus in native_smp_prepare_boot_cpu(). > 2. If UP_LATE_INIT is y, it will be done in smp_init() > > And, there are

Re: [tip:x86/mm] x86/asm: Remove __VIRTUAL_MASK_SHIFT==47 assert

On 04/05/2017 01:12 PM, Kirill A. Shutemov wrote: On Tue, Apr 04, 2017 at 05:36:33PM +0200, Denys Vlasenko wrote: diff --git a/arch/x86/entry/entry_64.S b/arch/x86/entry/entry_64.S index 044d18e..f07b4ef 100644 --- a/arch/x86/entry/entry_64.S +++ b/arch/x86/entry/entry_64.S @@ -265,12 +265,9

[PATCH v4 5/8] ARM: sun8i: a33: add thermal sensor

This adds the DT node for the thermal sensor present in the Allwinner A33 GPADC. Signed-off-by: Quentin Schulz --- v3: - switched compatible to allwinner,sun8i-a33-ths, - renamed DT node name and label to ths to better match datasheet's name,

Re: net/ipv4: use-after-free in ipv4_mtu

On Tue, Apr 4, 2017 at 7:45 PM, Eric Dumazet wrote: > On Tue, 2017-04-04 at 18:11 -0700, Cong Wang wrote: >> On Tue, Apr 4, 2017 at 11:51 AM, Eric Dumazet wrote: >> > Looking at fib->fib_metrics, I fail to understand how the following can >> > work :

Re: [PATCH V7 3/4] dt-bindings: phy: Add support for QMP phy

On 04/05, Vivek Gautam wrote: > Qualcomm chipsets have QMP phy controller that provides > support to a number of controller, viz. PCIe, UFS, and USB. > Adding dt binding information for the same. > > Signed-off-by: Vivek Gautam > Acked-by: Rob Herring

Re: [PATCH v6] vfio error recovery: kernel support

On Thu, 6 Apr 2017 01:36:31 +0300 "Michael S. Tsirkin" wrote: > On Wed, Apr 05, 2017 at 04:19:10PM -0600, Alex Williamson wrote: > > On Thu, 6 Apr 2017 00:50:22 +0300 > > "Michael S. Tsirkin" wrote: > > > > > On Wed, Apr 05, 2017 at 01:38:22PM -0600, Alex

[PATCH v6 1/6] platform/x86: intel_pmc_ipc: fix gcr offset

According to Broxton APL PMC spec, gcr mem region starts at offset 0x1000 from ipc mem base address. In this driver, PLAT_RESOURCE_GCR_OFFSET macro defines the offset of GCR memory region from IPC mem region. So we should use 0x1000(4K) as GCR offset. But currently this driver uses 0x1008 as GCT

[PATCH v2 1/3] hw_random: Migrate timeriomem_rng to new API

Preserves the existing behavior of only returning 32-bits per call. Signed-off-by: Rick Altherr --- Changes in v2: - Split API migration into separate patch drivers/char/hw_random/timeriomem-rng.c | 60 - 1 file changed, 30 insertions(+),

[PATCH v2 2/3] hw_random: timeriomem_rng: Shorten verbose type and variable names

No functional changes. Signed-off-by: Rick Altherr --- Changes in v2: - Split type and variable renames into separate patch drivers/char/hw_random/timeriomem-rng.c | 27 +-- 1 file changed, 13 insertions(+), 14 deletions(-) diff --git

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