Re: [PATCH] gpio: uniphier: add UniPhier GPIO controller driver

On Tuesday 08 August 2017 06:36 AM, Masahiro Yamada wrote: > Hi Linus, > > 2017-08-08 0:37 GMT+09:00 Linus Walleij : >> On Mon, Aug 7, 2017 at 3:50 PM, Masahiro Yamada >> wrote: >> >>> Adding "interrupts" property in DT causes >>>

[PATCH 2/3] autofs - make disc device user accessible

The autofs miscellanous device ioctls that shouldn't require CAP_SYS_ADMIN need to be accessible to user space applications in order to be able to get information about autofs mounts. The module checks capabilities so the miscelaneous device should be fine with broad permissions. Signed-off-by:

Re: [lkp-robot] [mm] 7674270022: will-it-scale.per_process_ops -19.3% regression

Nadav Amit wrote: > Minchan Kim wrote: > >> Hi, >> >> On Tue, Aug 08, 2017 at 09:19:23AM +0800, kernel test robot wrote: >>> Greeting, >>> >>> FYI, we noticed a -19.3% regression of will-it-scale.per_process_ops due to >>> commit: >>> >>> >>>

Re: [PATCH 0/4] Removing full paths from DT full_name

Rob Herring writes: > On Tue, Jul 25, 2017 at 4:44 PM, Rob Herring wrote: >> This series is the last steps to remove storing the full path for every >> DT node. Instead, we can create full path strings dynamically as needed >> with printf %pOF specifiers

[PATCH] Fixed typo in KGDB Kconfig file

Signed-off-by: James Pack --- lib/Kconfig.kgdb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/Kconfig.kgdb b/lib/Kconfig.kgdb index ab4ff0e..a5f7412 100644 --- a/lib/Kconfig.kgdb +++ b/lib/Kconfig.kgdb @@ -78,7 +78,7 @@ config KDB_DEFAULT_ENABLE

Re: [PATCH v2 03/18] firmware: arm_scmi: add basic driver infrastructure for SCMI

On Fri, Aug 4, 2017 at 8:01 PM, Sudeep Holla wrote: > +int scmi_do_xfer(const struct scmi_handle *handle, struct scmi_xfer *xfer) > +{ > + int ret; > + int timeout; > + struct scmi_info *info = handle_to_scmi_info(handle); > + struct device *dev

Re: [PATCH 1/2] f2fs: use IPU for cold files

On 2017/8/8 9:42, Jaegeuk Kim wrote: > We expect cold files write data sequentially, but sometimes some of small data > can be updated, which incurs fragmentation. > Let's avoid that. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks, > --- >

Re: [PATCH v2 4/5] input: Add MediaTek PMIC keys support

Hi Chen, On Mon, Aug 07, 2017 at 09:57:44AM +0800, Chen Zhong wrote: > This patch add support to handle MediaTek PMIC MT6397/MT6323 key > interrupts including pwrkey and homekey, also add setting for > long press key shutdown behavior. > > Signed-off-by: Chen Zhong >

Re: [PATCH 0/8] constify input usb_device_id.

On Sun, Aug 06, 2017 at 01:11:19PM +0530, Arvind Yadav wrote: > usb_device_id are not supposed to change at runtime. All functions > working with usb_device_id provided by work with > const usb_device_id. So mark the non-const structs as const. > > Fix checkpatch.pl error in patch 1,3 and 7: >

f7dd250789 ("gcc-plugins: structleak: add option to init all .."): kmodloader/112 is trying to release lock (module_mutex) at:

Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/gcc-plugin/structleak commit f7dd2507893cc3425d3ffc2369559619960befb0 Author: Ard Biesheuvel AuthorDate:

[PATCH v2 3/4] KVM: s390: implements the kvm_arch_vcpu_in_kernel()

This implements the kvm_arch_vcpu_in_kernel() for s390. Signed-off-by: Longpeng(Mike) --- arch/s390/kvm/kvm-s390.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c index 0b0c689..e46177b 100644 ---

[PATCH v2 2/4] KVM: X86: implement the logic for spinlock optimization

1. Implements the kvm_arch_vcpu_in_kernel(), because get_cpl requires vcpu_load, so we must cache the result(whether the vcpu was preempted when its cpl=0) in kvm_vcpu_arch. 2. Add ->spin_in_kernel hook, because we can get benefit from VMX. Signed-off-by: Longpeng(Mike)

Re: [PATCH -mm] mm: Clear to access sub-page last when clearing huge page

On 08/07/2017 12:21 AM, Huang, Ying wrote: > From: Huang Ying > > Huge page helps to reduce TLB miss rate, but it has higher cache > footprint, sometimes this may cause some issue. For example, when > clearing huge page on x86_64 platform, the cache footprint is 2M. But >

[PATCH v2 1/4] KVM: add spinlock optimization framework

If the vcpu(me) exit due to request a usermode spinlock, then the spinlock-holder may be preempted in usermode or kernmode. But if the vcpu(me) is in kernmode, then the holder must be preempted in kernmode, so we should choose a vcpu in kernmode as the most eligible candidate. This introduces

Re: [v5] wlcore: add missing nvs file name info for wilink8

* Reizer, Eyal [170807 00:47]: > Hi Tony, > > > > * Reizer, Eyal [170807 00:32]: > > > The following commits: > > > c815fde wlcore: spi: Populate config firmware data > > > d776fc8 wlcore: sdio: Populate config firmware data > > > > > > Populated the nvs entry for

Re: [PATCH 3/3] IPI: Avoid to use 2 cache lines for one call_single_data

Peter Zijlstra writes: > On Sat, Aug 05, 2017 at 08:47:02AM +0800, Huang, Ying wrote: >> Yes. That looks good. So you will prepare the final patch? Or you >> hope me to do that? > > I was hoping you'd do it ;-) Thanks! Here is the updated patch Best Regards, Huang,

[PATCH] usb: dwc3: omap: fix error return code in dwc3_omap_probe()

platform_get_irq() returns an error code, but the dwc3-omap driver ignores it and always returns -EINVAL. This is not correct and, prevents -EPROBE_DEFER from being propagated properly. Notice that platform_get_irq() no longer returns 0 on error:

[PATCH 2/2] ARM: dts: am572x-idk: Fix GPIO polarity for MMC1 card detect

The GPIO polarity for MMC1 card detect is set to '0' which means active-high. However the polarity should be active-low. Fix it here. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/am572x-idk.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/2] ARM: dts: am571x-idk: Fix GPIO polarity for MMC1 card detect

The GPIO polarity for MMC1 card detect is set to '0' which means active-high. However the polarity should be active-low. Fix it here. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/am571x-idk.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: block/ps3vram: Delete an error message for a failed memory allocation in ps3vram_cache_init()

On 08/07/2017 12:04 PM, SF Markus Elfring wrote: >> I think your original patch is OK, > > How does this feedback fit to the initial response “Not Applicable”? > https://patchwork.ozlabs.org/patch/798575/ I submitted your patch and a fix to ps3vram_probe() with the other patches in my queue.

Re: [PATCH v2 01/14] perf report: remove code to handle inline frames from browsers

Em Mon, Aug 07, 2017 at 09:22:08PM +0200, Milian Wolff escreveu: > On Montag, 7. August 2017 17:07:10 CEST Arnaldo Carvalho de Melo wrote: > > Em Sun, Aug 06, 2017 at 11:24:33PM +0200, Milian Wolff escreveu: > > > The follow-up commits will make inline frames first-class citizens > > > in the

Re: [PATCH v4] printk: Add monotonic, boottime, and realtime timestamps

On Mon, Aug 07, 2017 at 04:06:09PM -0400, Prarit Bhargava wrote: > > > On 08/07/2017 02:47 PM, John Stultz wrote: > > On Mon, Aug 7, 2017 at 11:04 AM, Prarit Bhargava wrote: > >> On 08/07/2017 12:52 PM, John Stultz wrote: > >>> Still not quite following why you're updating

Re: [kernel-hardening] [PATCH] lkdtm: Test VMAP_STACK allocates leading/trailing guard pages

On 7 August 2017 at 21:39, Kees Cook wrote: > Two new tests STACK_GUARD_PAGE_LEADING and STACK_GUARD_PAGE_TRAILING > attempt to read the byte before and after, respectively, of the current > stack frame, which should fault under VMAP_STACK. > > Signed-off-by: Kees Cook

Re: [PATCH v2 3/3] ARM: dts: at91: sama5d2: use sama5d2 compatible string for SMC

Hi Lee, On 07/08/2017 at 16:41:00 +0100, Lee Jones wrote: > On Tue, 18 Jul 2017, Ludovic Desroches wrote: > > > A new compatible string has been introduced for sama5d2 SMC to allow to > > manage the registers mapping change. > > > > Signed-off-by: Ludovic Desroches

[GIT PULL] MTD fixes for 4.13-rc5

-20170807 for you to fetch changes up to 33983675fbd5b2447430c3dd4c205e879576b475: Merge tag 'nand/fixes-for-4.13-rc4' of git://git.infradead.org/l2-mtd into MTD (2017-08-04 18:42:37 -0700) MTD fixes for 4.13-rc5: Just NAND fixes

[RFC PATCH 2/2] bpf: Initialise mod[] in bpf_trace_printk

In bpf_trace_printk(), the elements in mod[] are left uninitialised, but they are then incremented to track the width of the formats. Zero initialise the array just in case the memory contains non-zero values on entry. Fixes: 9c959c863f82 ("tracing: Allow BPF programs to call bpf_trace_printk()")

Re: [PATCH v2 05/23] clk: rockchip: fix up the pll clks error for rv1108 SoC

Am Mittwoch, 2. August 2017, 16:33:04 CEST schrieb Andy Yan: > From: Elaine Zhang > > fix up the lock_shift describe error. > remove the ROCKCHIP_PLL_SYNC_RATE flag for gpll. > > Signed-off-by: Elaine Zhang > Signed-off-by: Andy Yan

Re: [PATCH v2 04/23] clk: rockchip: support more rates for cpuclk

Am Mittwoch, 2. August 2017, 16:32:23 CEST schrieb Andy Yan: > From: Elaine Zhang > > fix up the cpuclk rates table for support more freqs. > fix up the mux_core_mask describe error. > > Signed-off-by: Elaine Zhang > Signed-off-by: Andy Yan

Re: [PATCH] lkdtm: Test VMAP_STACK allocates leading/trailing guard pages

On 08/07/2017 03:00 PM, Mark Rutland wrote: > Hi, > > On Mon, Aug 07, 2017 at 01:39:48PM -0700, Kees Cook wrote: >> Two new tests STACK_GUARD_PAGE_LEADING and STACK_GUARD_PAGE_TRAILING >> attempt to read the byte before and after, respectively, of the current >> stack frame, which should fault

[PATCH 1/2] lib: make bitmap_parselist thread-safe and much faster

Current implementation of bitmap_parselist() uses the static variable to save local state while setting bits in the bitmap. It is obviously wrong if we assume execution in multiprocessor environment. Fortunately, it's possible to rewrite this portion of code to avoid using the static variable. It

[PATCH 2/2] lib: add test for bitmap_parselist()

Do some basic checks for the bitmap_parselist(). Signed-off-by: Yury Norov --- lib/test_bitmap.c | 73 +++ 1 file changed, 73 insertions(+) diff --git a/lib/test_bitmap.c b/lib/test_bitmap.c index

[PATCH v2 1/4] arch/sparc: Separate the exception handlers from NG4memcpy

Separate the exception handlers from NG4memcpy so that it can be used with new memcpy routines. Make a separate file for all these handlers. Signed-off-by: Babu Moger --- arch/sparc/lib/Makefile |2 + arch/sparc/lib/Memcpy_utils.S | 163

Re: [PATCH] block: Fix warning when I/O elevator is changed as request_queue is being removed

On Tue, Aug 8, 2017 at 3:38 AM, David Jeffery wrote: > There is a race between changing I/O elevator and request_queue removal > which can trigger the warning in kobject_add_internal. A program can > use sysfs to request a change of elevator at the same time another task >

[PATCH v2 0/4] Update memcpy, memset etc. for M7/M8 architectures

This series of patches updates the memcpy, memset, copy_to_user, copy_from_user etc for SPARC M7/M8 architecture. New algorithm here takes advantage of the M7/M8 block init store ASIs, with much more optimized way to improve the performance. More detail are in code comments. Tested and compared

[PATCH v2 2/4] arch/sparc: Rename exception handlers

Rename exception handlers to memcpy_xxx as these are going to be used by new memcpy routines and these handlers are not exclusive to NG4memcpy anymore. Signed-off-by: Babu Moger --- arch/sparc/lib/Memcpy_utils.S | 120 +++---

Re: [PATCH v6 1/3] perf/core: use rb trees for pinned/flexible groups

On 07.08.2017 19:57, Peter Zijlstra wrote: > On Mon, Aug 07, 2017 at 07:27:30PM +0300, Alexey Budankov wrote: >> On 07.08.2017 18:55, Peter Zijlstra wrote: > >>> In the extreme, if you construct your program such that you'll never get >>> hit by the tick (this used to be a popular measure to hide

Re: [PATCH v6 1/3] perf/core: use rb trees for pinned/flexible groups

On Mon, Aug 07, 2017 at 10:39:55AM -0700, Andi Kleen wrote: > I'm not sure Alexey's patch kit will be able to solve every possible > problem with the event scheduler. Trying to fix everything at > the same time is usually difficult. I didn't say he should solve this. Just said that putting

Re: [PATCH v3] printk: Add boottime and real timestamps

On 08/07/2017 01:14 PM, Luis R. Rodriguez wrote: > > Note printk_late_init() is a late_initcall(). This means if the > printk_time_setting was disabled it will take a while to enable it. Enabling > it > is done at the device_initcall(), so if printk setting is disabled but a user > enables it

Re: [PATCH 1/2] kbuild: Add macros cc-option-3 and __cc-option-3

Hi Masahiro, El Mon, Aug 07, 2017 at 10:01:41AM +0900 Masahiro Yamada ha dit: > Hi Matthias, > > Sorry for my late reply. > > 2017-08-03 1:46 GMT+09:00 Matthias Kaehlcke : > > El Fri, Jul 21, 2017 at 02:56:56PM -0700 Matthias Kaehlcke ha dit: > > > >> The macro cc-option

[PATCH 06/14] arm64: clean up irq stack definitions

Before we add yet another stack to the kernel, it would be nice to ensure that we consistently organise stack definitions and related helper functions. This patch moves the basic IRQ stack defintions to to live with their task stack counterparts. Helpers used for unwinding are moved into , where

[PATCH 04/14] arm64: factor out PAGE_* and CONT_* definitions

Some headers rely on PAGE_* definitions from , but cannot include this due to potential circular includes. For example, a number of definitions in rely on PAGE_SHIFT, and includes . This requires users of these definitions to include both headers, which is fragile and error-prone. This patch

[PATCH 09/14] arm64: factor out entry stack manipulation

In subsequent patches, we will detect stack overflow in our exception entry code, by verifying the SP after it has been decremented to make space for the exception regs. This verification code is small, and we can minimize its impact by placing it directly in the vectors. To avoid redundant

[PATCH 08/14] efi/arm64: add EFI_KIMG_ALIGN

The EFI stub is intimately coupled with the kernel, and takes advantage of this by relocating the kernel at a weaker alignment than the documented boot protocol mandates. However, it does so by assuming it can align the kernel to the segment alignment, and assumes that this is 64K. In subsequent

[PATCH 07/14] arm64: move SEGMENT_ALIGN to

Currently we define SEGMENT_ALIGN directly in our vmlinux.lds.S. This is unfortunate, as the EFI stub currently open-codes the same number, and in future we'll want to fiddle with this. This patch moves the definition to our , where it can be used by both vmlinux.lds.S and the EFI stub code.

[PATCH 11/14] arm64: use an irq stack pointer

We allocate our IRQ stacks using a percpu array. This allows us to generate our IRQ stack pointers with adr_this_cpu, but bloats the kernel Image with the boot CPU's IRQ stack. Additionally, these are packed with other percpu variables, and aren't guaranteed to have guard pages. When we enable

[PATCH 12/14] arm64: add basic VMAP_STACK support

This path enables arm64 to be built with vmap'd task and IRQ stacks. As vmap'd stacks are mapped at page granularity, stacks must be a multiple of PAGE_SIZE. This means that a 64K page kernel must use stacks of at least 64K in size. To minimize the increase in Image size, IRQ stacks are

[PATCH 10/14] arm64: assembler: allow adr_this_cpu to use the stack pointer

From: Ard Biesheuvel Given that adr_this_cpu already requires a temp register in addition to the destination register, tweak the instruction sequence so that sp may be used as well. This will simplify switching to per-cpu stacks in subsequent patches. While this

variable length array in structure

Hi Arnd Bergmann, Following commit have introduced compilation issue. commit 2df2c3402fc81918a888e1ec711369f6014471f2 Author: Arnd Bergmann Date: Sat Aug 5 21:57:46 2017 -0400 ext4: fix warning about stack corruption Observed following error - /fs/ext4/mballoc.c:2303:17:

Re: [PATCH -mm] mm: Clear to access sub-page last when clearing huge page

On Mon, 7 Aug 2017, Huang, Ying wrote: > --- a/mm/memory.c > +++ b/mm/memory.c > @@ -4374,9 +4374,31 @@ void clear_huge_page(struct page *page, > } > > might_sleep(); > - for (i = 0; i < pages_per_huge_page; i++) { > + VM_BUG_ON(clamp(addr_hint, addr, addr + > +

[PATCH net-next v2 2/2] bpf: Extend check_uarg_tail_zero() checks

The function check_uarg_tail_zero() was created from bpf(2) for BPF_OBJ_GET_INFO_BY_FD without taking the access_ok() nor the PAGE_SIZE checks. Make this checks more generally available while unlikely to be triggered, extend the memory range check and add an explanation including why the ToCToU

[PATCH net-next v2 1/2] bpf: Move check_uarg_tail_zero() upward

The function check_uarg_tail_zero() may be useful for other part of the code in the syscall.c file. Move this function at the beginning of the file. Signed-off-by: Mickaël Salaün Acked-by: Daniel Borkmann Cc: Alexei Starovoitov Cc: David

Re: block/ps3vram: Delete an error message for a failed memory allocation in ps3vram_cache_init()

On 08/07/2017 11:34 AM, SF Markus Elfring wrote: >> I didn't consider one would be triggered by the kzalloc failure. > > Do you reconsider any special system settings for further > software evolution then? Sorry, I don't quite understand your question. I think your original patch is OK, and I

Re: block/ps3vram: Delete an error message for a failed memory allocation in ps3vram_cache_init()

>>> I didn't consider one would be triggered by the kzalloc failure. >> >> Do you reconsider any special system settings for further >> software evolution then? > > Sorry, I don't quite understand your question. Do you try to configure the Linux error reporting to any special needs? > I think

Re: [PATCH] ipc: optimize semget/shmget/msgget for lots of keys

On Mon, 31 Jul 2017, Guillaume Knispel wrote: struct ipc_ids { int in_use; unsigned short seq; + bool tables_initialized; So this is really ugly to have, but I understand why you added it. I wonder what folks would think if we just panic() in the rhashtable_init() ENOMEM

Re: [PATCH v2 0/2] mm,fork,security: introduce MADV_WIPEONFORK

On 08/06/2017 07:04 AM, r...@redhat.com wrote: > v2: fix MAP_SHARED case and kbuild warnings > > Introduce MADV_WIPEONFORK semantics, which result in a VMA being > empty in the child process after fork. This differs from MADV_DONTFORK > in one important way. It seems that the target use case

Re: [PATCH net-next v1 1/2] bpf: Move check_uarg_tail_zero() upward

On 08/07/2017 06:36 PM, Mickaël Salaün wrote: The function check_uarg_tail_zero() may be useful for other part of the code in the syscall.c file. Move this function at the beginning of the file. Signed-off-by: Mickaël Salaün Cc: Alexei Starovoitov Cc: Daniel

Re: [PATCH] hns3: fix unused function warning

From: Arnd Bergmann Date: Mon, 7 Aug 2017 12:41:53 +0200 > Without CONFIG_PCI_IOV, we get a harmless warning about an > unused function: > > drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c:2273:13: error: > 'hclge_disable_sriov' defined but not used

Re: [PATCH v2] hysdn: fix to a race condition in put_log_buffer

From: Anton Volkov Date: Mon, 7 Aug 2017 15:54:14 +0300 > The synchronization type that was used earlier to guard the loop that > deletes unused log buffers may lead to a situation that prevents any > thread from going through the loop. > > The patch deletes previously used

Re: [PATCH RFC v2 3/5] samples/bpf: Fix inline asm issues building samples on arm64

Please, no. The amount of hellish hacks we are adding to deal with this is getting way out of control. BPF programs MUST have their own set of asm headers, this is the only way to get around this issue in the long term. I am also strongly against adding -static to the build.

Re: block/ps3vram: Delete an error message for a failed memory allocation in ps3vram_cache_init()

On 08/07/2017 09:27 AM, SF Markus Elfring wrote: >>> Omit an extra message for a memory allocation failure in this function. >>> >>> This issue was detected by using the Coccinelle software. >> >> NACK >> >> When a user asks me for help I would certainly like to get >> 'Could not allocate cache

Re: pull-request: wireless-drivers-next 2017-08-07

From: Kalle Valo Date: Mon, 07 Aug 2017 17:55:40 +0300 > here's the first pull request to net-next for 4.14, more info in the > signed tag below. This time there's a simple conflict in iwlwifi but > you can fix it just like Stephen did: > >

Re: block/ps3vram: Delete an error message for a failed memory allocation in ps3vram_cache_init()

>> Do you find the default allocation failure report insufficient? > > The default is OK. Thanks for this information. > I didn't consider one would be triggered by the kzalloc failure. Do you reconsider any special system settings for further software evolution then? Regards, Markus

Re: [PATCH net-next v1 2/2] bpf: Extend check_uarg_tail_zero() checks

On 08/07/2017 06:36 PM, Mickaël Salaün wrote: The function check_uarg_tail_zero() was created from bpf(2) for BPF_OBJ_GET_INFO_BY_FD without taking the access_ok() nor the PAGE_SIZE checks. Make this checks more generally available while unlikely to be triggered, extend the memory range check

[PATCH 00/14] arm64: VMAP_STACK support

Hi, Ard and I have worked together to implement vmap stack support for arm64. This supersedes our earlier vmap stack RFCs [0,1]. The git author stats are a little misleading, as I've teased parts out into smaller patches for review. The series is based on our stack dump rework [2,3], which can

[PATCH 05/14] arm64: clean up THREAD_* definitions

Currently we define THREAD_SIZE and THREAD_SIZE order separately, with the latter dependent on particular CONFIG_ARM64_*K_PAGES definitions. This is somewhat opaque, and will get in the way of future modifications to THREAD_SIZE. This patch cleans this up, defining both in terms of a common

[PATCH 01/14] arm64: remove __die()'s stack dump

Our __die() implementation tries to dump the stack memory, in addition to a backtrace, which is problematic. For contemporary 16K stacks, this can be a lot of data, which can take a long time to dump, and can push other useful context out of the kernel's printk ringbuffer (and/or a user's

[PATCH 14/14] arm64: add VMAP_STACK overflow detection

This patch adds stack overflow detection to arm64, usable when vmap'd stacks are in use. Overflow is detected in a small preamble executed for each exception entry, which checks whether there is enough space on the current stack for the general purpose registers to be saved. If there is not

[PATCH 13/14] arm64: add on_accessible_stack()

Both unwind_frame() and dump_backtrace() try to check whether a stack address is sane to access, with very similar logic. Both will need updating in order to handle overflow stacks. Factor out this logic into a helper, so that we can avoid further duplication when we add overflow stacks.

[PATCH 02/14] fork: allow arch-override of VMAP stack alignment

In some cases, an architecture might wish its stacks to be aligned to a boundary larger than THREAD_SIZE. For example, using an alignment of double THREAD_SIZE can allow for stack overflows smaller than THREAD_SIZE to be detected by checking a single bit of the stack pointer. This patch allows

[PATCH 03/14] arm64: kernel: remove {THREAD,IRQ_STACK}_START_SP

From: Ard Biesheuvel For historical reasons, we leave the top 16 bytes of our task and IRQ stacks unused, a practice used to ensure that the SP can always be masked to find the base of the current stack (historically, where thread_info could be found). However, this

Re: Switching to MQ by default may generate some bug reports

> Il giorno 07 ago 2017, alle ore 19:32, Paolo Valente > ha scritto: > >> >> Il giorno 05 ago 2017, alle ore 00:05, Paolo Valente >> ha scritto: >> >>> >>> Il giorno 04 ago 2017, alle ore 13:01, Mel Gorman >>>

Re: kvm_intel fails to load on Conroe CPUs running Linux 4.12

On 07.08.2017 19:50, Paolo Bonzini wrote: On 07/08/2017 19:17, Sebastian Rachuj wrote: Thank you for looking into the issue. My cpuinfo is as follows: Looks like Intel was already differentiating virtualization features across SKUs. Please run the attached script as root to see what other

Re: [PATCH v4] printk: Add monotonic, boottime, and realtime timestamps

On Mon, Aug 7, 2017 at 11:04 AM, Prarit Bhargava wrote: > On 08/07/2017 12:52 PM, John Stultz wrote: >> Still not quite following why you're updating all the defconfigs. I'd >> make sure the Kconfig default settings are right, and leave updating >> the defconfig to arch/device

[PATCH v2] KVM: arm64: pass vcpu esr_el2 and far_el2 sysre to user space

For the firmware-first RAS solution, SEA and SEI is injected by the user space, user space needs to know the vcpu's esr_el2 and far_el2 value, so add them to sysreg. user space uses the IOCTL KVM_GET_ONE_REG can get their value. Signed-off-by: Dongjiu Geng ---

Re: [PATCH] KVM: arm64: add esr_el2 and far_el2 to sysreg

Marc, On 2017/8/8 0:56, Marc Zyngier wrote: > On 07/08/17 17:23, gengdongjiu wrote: >> Hi Marc, >> As James's suggestion, I move injection SEA Error logic to the user >> space(Qemu), Qemu sets the related guest OS esr/elr/pstate/spsr >> through IOCTL KVM_SET_ONE_REG. For the SEA, when Qemu

[PATCH] arm64: KVM: Reject non-compliant HVC calls from guest kernel

The SMC/HVC instructions with an immediate value non-zero are not compliant according to 'SMC calling convention system software document'. Add a validation check in handle_hvc() to avoid malicious HVC calls from VM, and inject an undefined instruction for those calls.

Re: [PATCH v2] KVM: arm64: pass vcpu esr_el2 and far_el2 sysre to user space

On Tue, Aug 08 2017 at 3:17:34 am BST, Dongjiu Geng wrote: > For the firmware-first RAS solution, SEA and SEI is injected > by the user space, user space needs to know the vcpu's esr_el2 and > far_el2 value, so add them to sysreg. user space uses > the IOCTL

Re: FSGSBASE ABI considerations

On Mon, Aug 7, 2017 at 10:35 AM, Linus Torvalds wrote: > On Mon, Aug 7, 2017 at 9:20 AM, Andy Lutomirski wrote: >> >> Windows does something sort of like this (I think), but I don't like >> this solution. I fully expect that someone will write a

[PATCH] KVM: SVM: Limit PFERR_NESTED_GUEST_PAGE error_code check to L1 guest

Commit: 1472775 (kvm: svm: Add support for additional SVM NPF error codes) added new error code to aid nested page fault handling. The commit unprotect (kvm_mmu_unprotect_page) the page when we get a NFP due to guest page table walk where the page was marked RO. Paolo highlighted a use case,

Re: [RFC] Tagging of vmalloc pages for supporting the pmalloc allocator

On Mon, Aug 07, 2017 at 05:13:00PM +0300, Igor Stoppa wrote: > > > On 07/08/17 16:31, Jerome Glisse wrote: > > On Mon, Aug 07, 2017 at 02:26:21PM +0300, Igor Stoppa wrote: > > [...] > > >> I'll add a vm_area field as you advised. > >> > >> Is this something I could send as standalone patch? >

Re: [PATCH v5 2/6] seccomp: Sysctl to configure actions that are allowed to be logged

On 2017-08-04 17:24:00, Tyler Hicks wrote: > On 08/03/2017 11:33 AM, Kees Cook wrote: > > On Fri, Jul 28, 2017 at 1:55 PM, Tyler Hicks wrote: > >> Adminstrators can write to this sysctl to set the seccomp actions that > >> are allowed to be logged. Any actions not found in

Re: [PATCH 0/6] In-kernel QMI handling

Hi Bjorn, >>> This series starts by moving the common definitions of the QMUX >>> protocol to the >>> uapi header, as they are shared with clients - both in kernel and >>> userspace. >>> >>> This series then introduces in-kernel helper functions for aiding the >>> handling >>> of QMI encoded

Re: [PATCH 10/18] staging: typec: fusb302: Add support for fcs,vbus-regulator-name device-property

Hi, On 07-08-17 17:41, Mark Brown wrote: On Mon, Aug 07, 2017 at 04:41:18PM +0200, Hans de Goede wrote: On 07-08-17 13:10, Mark Brown wrote: Problem 1) The regulator in question is part of the bq24292i charger-IC attached to a private i2c bus between the PMIC and the charger. The driver

[GIT PULL] xfs: fixes for 4.13-rc5

Hi Linus, I have a couple more bug fixes for you today. --Darrick The following changes since commit 5b094d6dac0451ad89b1dc088395c7b399b7e9e8: xfs: fix multi-AG deadlock in xfs_bunmapi (2017-07-26 08:20:03 -0700) are available in the git repository at:

Re: [PATCH v2 01/14] perf report: remove code to handle inline frames from browsers

On Montag, 7. August 2017 17:07:10 CEST Arnaldo Carvalho de Melo wrote: > Em Sun, Aug 06, 2017 at 11:24:33PM +0200, Milian Wolff escreveu: > > The follow-up commits will make inline frames first-class citizens > > in the callchain, thereby obsoleting all of this special code. > > So you are

[PATCH] [media] vs6624: constify vs6624_default_fmt

The structure vs6624_default_fmt is only copied into another structure field, so it can be const. Done with the help of Coccinelle. Signed-off-by: Julia Lawall --- drivers/media/i2c/vs6624.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH V3] get_maintainer: Prepare for separate MAINTAINERS files

On 08/06/17 20:32, Joe Perches wrote: > On Sun, 2017-08-06 at 19:16 -0700, Frank Rowand wrote: >> On 08/04/17 21:45, Joe Perches wrote: >>> Allow for MAINTAINERS to become a directory and if it is, >>> read all the files in the directory for maintained sections. >>> >>> Optionally look for all

Re: [PATCH 3.18 00/50] 3.18.64-stable review

On Sat, Aug 05, 2017 at 12:11:19PM -0700, Guenter Roeck wrote: > On 08/05/2017 08:43 AM, Greg Kroah-Hartman wrote: > > On Sat, Aug 05, 2017 at 08:02:17AM +0200, Willy Tarreau wrote: > > > On Sat, Aug 05, 2017 at 07:55:11AM +0200, Willy Tarreau wrote: > > > > On Fri, Aug 04, 2017 at 07:51:07PM

[PATCH] block: Fix warning when I/O elevator is changed as request_queue is being removed

There is a race between changing I/O elevator and request_queue removal which can trigger the warning in kobject_add_internal. A program can use sysfs to request a change of elevator at the same time another task is unregistering the request_queue the elevator would be attached to. The elevator's

[PATCH] Make kernel taint on invalid module signatures configurable

The default kernel behaviour is for unsigned or invalidly signed modules to load without warning. Right now, If CONFIG_MODULE_SIG is enabled the kernel will be tainted in this case. Distributions may wish to enable CONFIG_MODULE_SIG in order to permit signature enforcement, but may not wish to

Re: [PATCH 4/7] signal/mips: Document a conflict with SI_USER with SIGFPE

On Mon, Aug 07, 2017 at 10:41:39AM -0700, Linus Torvalds wrote: > On Mon, Aug 7, 2017 at 9:18 AM, Maciej W. Rozycki wrote: > > > > So what would be the right value of `si_code' to use here for such an > > unexpected exception condition? I think `BUG()' would be too big a > >

[PATCH 1/3] MAINTAINERS: Add Jonathan Derrick as VMD maintainer

Add myself as VMD maintainer Signed-off-by: Jon Derrick --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index f66488d..3ec39df 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10090,6 +10090,7 @@ F:

[PATCH 2/3] pci: Generalize is_vmd behavior

Generalize is_vmd behavior to remove dependency on domain number checking in pci quirks. Signed-off-by: Jon Derrick --- arch/x86/include/asm/pci.h | 8 +++- arch/x86/pci/common.c | 2 +- drivers/pci/quirks.c | 2 +- include/linux/pci.h| 4

[PATCH 3/3] iommu: prevent VMD child devices from being remapping targets

VMD child devices must use the VMD endpoint's ID as the DMA source. Because of this, there needs to be a way to link the parent VMD endpoint's DMAR domain to the VMD child devices' DMAR domain such that attaching and detaching child devices modify the endpoint's DMAR mapping and prevents early

Re: iov_iter_pipe warning.

On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote: > > currently running v4.11-rc8-75-gf83246089ca0 > > > > sunrpc bit is for the other unrelated problem I'm chasing. > > > > note also, I saw the backtrace without the

[v6 06/15] sparc64: simplify vmemmap_populate

Remove duplicating code by using common functions vmemmap_pud_populate and vmemmap_pgd_populate. Signed-off-by: Pavel Tatashin Reviewed-by: Steven Sistare Reviewed-by: Daniel Jordan Reviewed-by: Bob Picco

[v6 10/15] x86/kasan: explicitly zero kasan shadow memory

To optimize the performance of struct page initialization, vmemmap_populate() will no longer zero memory. We must explicitly zero the memory that is allocated by vmemmap_populate() for kasan, as this memory does not go through struct page initialization path. Signed-off-by: Pavel Tatashin

[v6 11/15] arm64/kasan: explicitly zero kasan shadow memory

To optimize the performance of struct page initialization, vmemmap_populate() will no longer zero memory. We must explicitly zero the memory that is allocated by vmemmap_populate() for kasan, as this memory does not go through struct page initialization path. Signed-off-by: Pavel Tatashin

Re: [PATCH 1/2] acpi: arm64: add iort support for PMCG

Hi Robin, Thank you for the review. On 8/7/2017 7:17 AM, Robin Murphy wrote: > Hi Neil, > > On 04/08/17 20:59, Neil Leeder wrote: [...] >> +res[1].start = pmcg->base_address + SZ_64K; > > Ugh, I see there's a nasty spec hole here - IORT only defines one base > address, but SMMUv3 says

Re: [PATCH 03/14] mmc: meson-gx: clean up some constants

Jerome Brunet writes: > Remove useless clock rate defines. These should not be defined but To be more precise, they're also unused, so maybe s/useless/unused/ ? > equested from the clock framework. s/equested/requested/ > Also correct typo on the DELAY register > >

<    1   2   3   4   5   6   7   8   9   10   >