[PATCH v4 02/11] counter: Documentation: Add Generic Counter sysfs documentation

This patch adds standard documentation for the userspace sysfs attributes of the Generic Counter interface. Signed-off-by: William Breathitt Gray --- .../ABI/testing/sysfs-bus-counter-generic-sysfs| 73 ++ MAINTAINERS

[PATCH v4 01/11] iio: Introduce the Generic Counter interface

This patch introduces the Generic Counter interface for supporting counter devices. The Generic Counter interface serves as a catch-all to enable rudimentary support for devices that qualify as counters. More specific and apt counter interfaces may be developed on top of the Generic Counter

DSAC static analysis

Hi, You have written several times: > This possible bug is found by my static analysis tool (DSAC) and my code > review. Is the DSAC static analysis tool available for download? If so, where? Thanks, -- ~Randy

[PATCH urgent 1/3] x86/power/64: Use struct desc_ptr for the IDT in struct saved_context

x86_64's saved_context nonsensically used separate idt_limit and idt_base fields and then cast _limit to struct desc_ptr *. This was correct (with -fno-strict-aliasing), but it's confusing, served no purpose, and required ifdeffery. Just use struct desc_ptr directly. Tested-by: Jarkko Nikula

[PATCH urgent 2/3] x86/power/32: Move SYSENTER MSR restoration to fix_processor_context()

x86_64 restores system call MSRs in fix_processor_context(), and x86_32 restored them along with segment registers. The 64-bit variant makes more sense, so move the 32-bit code to match the 64-bit code. Tested-by: Jarkko Nikula Signed-off-by: Andy Lutomirski

Re: [PATCH v2 01/17] mm/gup: Fixup p*_access_permitted()

On Thu, Dec 14, 2017 at 09:54:50PM +0100, Peter Zijlstra wrote: > On Thu, Dec 14, 2017 at 12:44:58PM -0800, Dave Hansen wrote: > > On 12/14/2017 06:37 AM, Peter Zijlstra wrote: > > > I'm also looking at pte_access_permitted() in handle_pte_fault(); that > > > looks very dodgy to me. How does that

Re: [PATCH 1/2] f2fs: pass down write hints to block layer for bufferd write

Hello, On 12/01, Hyunchul Lee wrote: > Hi Jaegeuk, > > On 12/01/2017 04:28 PM, Jaegeuk Kim wrote: > > On 11/30, Chao Yu wrote: > >> On 2017/11/28 8:23, Hyunchul Lee wrote: > >>> From: Hyunchul Lee > >>> > >>> This implements which hint is passed down to block layer > >>> for

Re: [Y2038] [PATCH v4 1/4] uinput: Use monotonic times for uinput timestamps.

On Thu, 2017-12-14 at 21:17 +, Ben Hutchings wrote: > On Thu, 2017-12-07 at 10:13 -0800, Deepa Dinamani wrote: > > struct timeval which is part of struct input_event to > > maintain the event times is not y2038 safe. > > > > Real time timestamps are also not ideal for input_event > > as this

[PATCH urgent 0/3] __restore_processor_state() fixes

__restore_processor_state() was spaghetti code, made no sense, and had bugs. And I broke resume on 32-bit systems. This series cleans it up and fixes it (hopefully!). Andy Lutomirski (3): x86/power/64: Use struct desc_ptr for the IDT in struct saved_context x86/power/32: Move SYSENTER MSR

Re: [PATCH] Fix resume on x86-32 machines

On Thu, Dec 14, 2017 at 12:47 PM, Linus Torvalds wrote: > On Thu, Dec 14, 2017 at 12:38 PM, Pavel Machek wrote: >> >> But given this is already "regression fix for x86-64 caused regression >> on x86-32", I really believe we should merge trivial fix

[PATCH urgent 3/3] x86/power: Make restore_processor_context() sane

My previous attempt to fix a couple of bugs in __restore_processor_context() introduced yet another bug. Rather than trying to come up with a minimal fix, let's try to clean it up for real. This patch fixes quite a few things: - The old code saved a nonsensical subset of segment registers.

Re: [RFC PATCH for 4.16 02/21] rseq: Introduce restartable sequences system call (v12)

On Thu, Dec 14, 2017 at 03:14:00PM -0600, Christopher Lameter wrote: > On Thu, 14 Dec 2017, Mathieu Desnoyers wrote: > > > If we port this concept to kernel-space (as I start to understand > > would be your wish), then a simple pointer store to the current > > task_struct would suffice. > >

Re: [PATCH v2 11/17] selftests/x86/ldt_gdt: Prepare for access bit forced

On Thu, Dec 14, 2017 at 11:43 AM, Linus Torvalds wrote: > On Thu, Dec 14, 2017 at 8:20 AM, Andy Lutomirski wrote: >> >> If this turns out to need reverting because it breaks Wine or >> something, we're really going to regret it. > > I really don't

Re: [PATCH v2 06/17] x86/ldt: Do not install LDT for kernel threads

On Thu, Dec 14, 2017 at 11:43 AM, Peter Zijlstra wrote: > On Thu, Dec 14, 2017 at 12:27:32PM +0100, Peter Zijlstra wrote: >> From: Thomas Gleixner >> >> Kernel threads can use the mm of a user process temporarily via use_mm(), >> but there is no point in

Re: BUG: unable to handle kernel paging request in __switch_to

On Thu, Dec 14, 2017 at 11:28 AM, Linus Torvalds wrote: > On Thu, Dec 14, 2017 at 10:54 AM, Andy Lutomirski wrote: >> >> 2. It actually tries to handle the breakpoint. A breakpoint is a >> benign exception, so any exception encountered while

Re: [PATCH] kobject: fix suppressing modalias in uevents delivered over netlink

| From: Dmitry Torokhov | Sent: Thursday, December 14, 2017 12:32 PM | | As far as I can see Eric's patch is landed in 4.15-rc1 so I do not | think we need this patch in .14. Except that Komali's bisect showed that the bug occured with kernel.org:

Re: BUG: unable to handle kernel paging request in __switch_to

On Thu, Dec 14, 2017 at 1:27 PM, Andy Lutomirski wrote: > On Thu, Dec 14, 2017 at 11:28 AM, Linus Torvalds > wrote: >> I don't think that's the case. "int3" is entirely synchronous, and >> doesn't have the same odd issues as a breakpoint trap

Re: [Y2038] [PATCH v4 4/4] input: serio: Replace timeval by timespec64

On Thu, 2017-12-07 at 10:13 -0800, Deepa Dinamani wrote: > struct timeval is not y2038 safe. > All references to timeval will be deleted from the > kernel to make it y2038 safe. > Replace its uses by y2038 safe struct timespec64. > > The timestamps changed here only keep track of delta > times.

Re: [PATCH] media: v4l: xilinx: Use SPDX-License-Identifier

Em Thu, 14 Dec 2017 21:57:06 +0100 Greg KH escreveu: > On Thu, Dec 14, 2017 at 10:44:16PM +0200, Laurent Pinchart wrote: > > Hi Greg, > > > > On Thursday, 14 December 2017 22:08:51 EET Greg KH wrote: > > > On Thu, Dec 14, 2017 at 09:05:27PM +0200, Laurent Pinchart

Re: [PATCH 2/6] blk-mq: replace timeout synchronization with a RCU and generation based scheme

On Thu, Dec 14, 2017 at 09:42:48PM +, Bart Van Assche wrote: > On Thu, 2017-12-14 at 21:20 +0100, Peter Zijlstra wrote: > > On Thu, Dec 14, 2017 at 06:51:11PM +, Bart Van Assche wrote: > > > On Tue, 2017-12-12 at 11:01 -0800, Tejun Heo wrote: > > > > +

Re: [PATCH v2 00/17] x86/ldt: Use a VMA based read only mapping

On Thu, Dec 14, 2017 at 01:03:37PM +0100, Thomas Gleixner wrote: > On Thu, 14 Dec 2017, Peter Zijlstra wrote: > > So here's a second posting of the VMA based LDT implementation; now without > > most of the crazy. > > > > I took out the write fault handler and the magic LAR touching code. > > > >

[PATCH] drm/virtio: Add window server support

This is to allow clients running within VMs to be able to communicate with a compositor in the host. Clients will use the communication protocol that the compositor supports, and virtio-gpu will assist with making buffers available in both sides, and copying content as needed. It is expected that

[PATCH v3] KVM: X86: Fix stack-out-of-bounds read in write_mmio

From: Wanpeng Li Reported by syzkaller: BUG: KASAN: stack-out-of-bounds in write_mmio+0x11e/0x270 [kvm] Read of size 8 at addr 8803259df7f8 by task syz-executor/32298 CPU: 6 PID: 32298 Comm: syz-executor Tainted: G OE4.15.0-rc2+ #18 Hardware

Re: [PATCH v7 0/6] perf report/script: Support percent and multiple range in --time option

On Fri, Dec 08, 2017 at 09:13:40PM +0800, Jin Yao wrote: > v7: > --- > v7 doesn't have functional change. The update is only: > > 1. Rebase to latest perf/core branch > > 2. Update patch description according to Arnaldo's comments. still looks ok ;-) u can keep the ack jirka

Re: [PATCH v2 1/2] acpi, spcr: Make SPCR avialable to other architectures

On 12/14/17 4:30 AM, Lorenzo Pieralisi wrote: I didn't want to put any ACPI code in amba-pl011.c, so putting it in spcr.c made the most sense. I agree the global variable is ugly. If you have a better idea, I'm all ears. I told you my idea. It could have been made easier by reusing the

Re: [PATCH V2] KVM/x86: Check input paging mode when cs.l is set

On 12/14/2017 7:41 PM, Paolo Bonzini wrote: On 14/12/2017 04:55, Lan Tianyu wrote: +* When EFER.LME and CR0.PG are set, CR4.PAE and EFER.LMA +* must be set. +*/ + if ((sregs->efer & EFER_LME) && (sregs->cr0 & X86_CR0_PG_BIT)) { + if (!(sregs->cr4 &

Re: [PATCH 1/2] x86: consider effective protection attributes in W+X check

On 14/12/17 15:15, Jan Beulich wrote: On 14.12.17 at 15:04, wrote: >> On 12/12/17 11:31, Jan Beulich wrote: >>> @@ -335,42 +346,45 @@ static inline bool kasan_page_table(stru >>> >>> #if PTRS_PER_PMD > 1 >>> >>> -static void walk_pmd_level(struct seq_file *m, struct

Re: [PATCH] watchdog: document watchdog_init_timeout() wdd parameter

On 12/13/2017 11:41 AM, Corentin Labbe wrote: All parameters of watchdog_init_timeout() are documented with exception of wdd, thus generating a build warning. This patch document it and so remove the following build warning: drivers/watchdog/watchdog_core.c:113: warning: No description found

Re: [PATCH] mm: save/restore current->journal_info in handle_mm_fault

On Thu, Dec 14, 2017 at 9:43 PM, Jan Kara wrote: > On Thu 14-12-17 18:55:27, Yan, Zheng wrote: >> We recently got an Oops report: >> >> BUG: unable to handle kernel NULL pointer dereference at (null) >> IP: jbd2__journal_start+0x38/0x1a2 >> [...] >> Call Trace: >>

Re: [PATCH] PCI/DPC: Fix shared interrupt handling

On Wed, Dec 13, 2017 at 05:01:58PM -0700, Alex Williamson wrote: > @@ -109,6 +109,7 @@ static void interrupt_event_handler(struct work_struct > *work) > struct dpc_dev *dpc = container_of(work, struct dpc_dev, work); > struct pci_dev *dev, *temp, *pdev = dpc->dev->port; > struct

Re: [PATCH] PCI/DPC: Fix shared interrupt handling

On Thu, 14 Dec 2017 07:50:31 -0700 Keith Busch wrote: > On Wed, Dec 13, 2017 at 05:01:58PM -0700, Alex Williamson wrote: > > @@ -109,6 +109,7 @@ static void interrupt_event_handler(struct work_struct > > *work) > > struct dpc_dev *dpc = container_of(work, struct

Re: [PATCH v2 0/2] mm: introduce MAP_FIXED_SAFE

On 1214T1415, Michal Hocko wrote: > On Thu 14-12-17 12:44:17, Edward Napierala wrote: > > Regarding the name - how about adopting MAP_EXCL? It was introduced in > > FreeBSD, > > and seems to do exactly this; quoting mmap(2): > > > > MAP_FIXEDDo not permit the system to select a different

RE: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest`

> [Mario from Dell added to CC list.] > > Dear Alexander, > > > On 12/11/17 17:08, alexander.stef...@infineon.com wrote: > > >> On 12/08/17 17:18, Jason Gunthorpe wrote: > >>> On Fri, Dec 08, 2017 at 05:07:39PM +0100, Paul Menzel wrote: > >>> > I have no access to the system right now,

Re: d1fc031747 ("sched/wait: assert the wait_queue_head lock is .."): EIP: __wake_up_common

On Wed, Dec 13, 2017 at 05:03:00PM -0800, Andrew Morton wrote: > > sched/wait: assert the wait_queue_head lock is held in __wake_up_common > > > > Better ensure we actually hold the lock using lockdep than just > > commenting > > on it. Due to the various exported _locked

[PATCH v5 2/3] PCI: endpoint: Populate func_no before calling pci_epc_add_epf()

func_no is a member of struct pci_epf. struct pci_epf is used as an argument to pci_epc_add_epf(), therefore func_no should be populated before calling pci_epc_add_epf(). Fixes: d74679911610 ("PCI: endpoint: Introduce configfs entry for configuring EP functions") Signed-off-by: Niklas Cassel

[PATCH v5 0/3] Fix find_first_zero_bit() usage

find_first_zero_bit()'s parameter 'size' is defined in bits, not in bytes. Calling find_first_zero_bit() with the wrong size unit will lead to insidious bugs. Fix all uses of find_first_zero_bit() called with sizeof() as size argument in drivers/pci. Niklas Cassel (3): PCI: designware-ep: Fix

Re: [PATCH] KVM: x86: ioapic: Clear IRR for rtc bit when rtc EOI gotten

On 14/12/17 14:23, Gonglei wrote: We hit a bug in our test while run PCMark 10 in a windows 7 VM, The VM got stuck and the wallclock was hang after several minutes running PCMark 10 in it. It is quite easily to reproduce the bug with the upstream KVM and Qemu. We found that KVM can not inject

[PATCH v5 1/3] PCI: designware-ep: Fix find_first_zero_bit() usage

find_first_zero_bit()'s parameter 'size' is defined in bits, not in bytes. find_first_zero_bit() is called with size in bytes rather than bits, which thus defines a too low upper limit, causing dw_pcie_ep_inbound_atu() to assign iatu index #4 to both bar 4 and bar 5, which makes bar 5 overwrite

[PATCH v5 3/3] PCI: endpoint: Fix find_first_zero_bit() usage

find_first_zero_bit()'s parameter 'size' is defined in bits, not in bytes. Calling find_first_zero_bit() with the wrong size unit will lead to insidious bugs. Fix this by calling find_first_zero_bit() with size BITS_PER_LONG, rather than sizeof() and add missing find_first_zero_bit() return

Re: d1fc031747 ("sched/wait: assert the wait_queue_head lock is .."): EIP: __wake_up_common

On Thu, Dec 14, 2017 at 04:58:09AM -0800, Matthew Wilcox wrote: > On Wed, Dec 13, 2017 at 05:03:00PM -0800, Andrew Morton wrote: > > > sched/wait: assert the wait_queue_head lock is held in > > > __wake_up_common > > > > > > Better ensure we actually hold the lock using lockdep than

Re: [intel-sgx-kernel-dev] [PATCH v7 4/8] intel_sgx: driver for Intel Software Guard Extensions

On Tue, Dec 12, 2017 at 01:46:48PM -0800, Sean Christopherson wrote: > So it looks like you avoid the described case by moving B to the head of > the list in sgx_eldu.  The bug I am seeing is still straightforward to > theorize: > > 1. Three VA pages.  List = A->B->C > 2. Fill A and B,

Re: [PATCH] KVM: arm/arm64: don't set vtimer->cnt_ctl in kvm_arch_timer_handler

On Thu, Dec 14, 2017 at 12:57:54PM +0800, Jia He wrote: Hi Jia, > > I have tried your newer level-mapped-v7 branch, but bug is still there. > > There is no special load in both host and guest. The guest (kernel > 4.14) is often hanging when booting > > the guest kernel log > > [ OK ] Reached

Re: Linux 4.15-rc2: Regression in resume from ACPI S3

On Thu, 14 Dec 2017, Thomas Gleixner wrote: > Now, what's different vs. 4.14: > > The 4.14 code accidentaly had the irq descriptor for this vector still > populated in the old CPU due to the convoluted way the vector allocation > worked. I have still to investigate if one of those cases is

[PATCH 06/14] ARM: dts: dra76-evm: Add pinctrl data for higher speed MMC/SD modes

From: Sekhar Nori The SD card interface on DRA76x EVM can support high speed SD cards. The eMMC onboard can support upto HS200 mode. Enable support for these higher speed modes in the device-tree file. Signed-off-by: Sekhar Nori Signed-off-by: Kishon Vijay

Re: [PATCH v4 0/3] Fix find_first_zero_bit() usage

On Thu, Dec 14, 2017 at 02:32:30PM +0100, Niklas Cassel wrote: > On Wed, Dec 13, 2017 at 03:59:25PM -0600, Bjorn Helgaas wrote: > > On Tue, Dec 12, 2017 at 03:16:31PM +0100, Niklas Cassel wrote: > > > find_first_zero_bit()'s parameter 'size' is defined in bits, > > > not in bytes. > > > > > >

[PATCH 01/14] ARM: multi_v7_defconfig: Enable CONFIG_MMC_SDHCI_OMAP

Enable CONFIG_MMC_SDHCI_OMAP so that TI's dra7/k2g based SoC's can use sdhci-omap for eMMC/SD/SDIO controller.. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/configs/multi_v7_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/multi_v7_defconfig

Re: [PATCH v4 3/5] media: i2c: Add TDA1997x HDMI receiver driver

On 14/12/17 00:35, Tim Harvey wrote: >>> Close. What is missing is a check of the AVI InfoFrame: if it has an >>> explicit >>> colorimetry then use that. E.g. check for HDMI_COLORIMETRY_ITU_601 or >>> ITU_709 >>> and set the colorspace accordingly. Otherwise fall back to what you have >>> here.

Re: [RFC][PATCHv6 00/12] printk: introduce printing kernel thread

On Mon 2017-12-04 22:48:13, Sergey Senozhatsky wrote: > Hello, > > RFC > > A new version, yet another rework. Lots of changes, e.g. hand off > control based on Steven's patch. Another change is that this time around > we finally have a kernel module to test printk offloading (YAYY!).

Re: [v3,1/2] hwmon (pmbus): Export pmbus device debugfs directory entry

On Mon, Dec 11, 2017 at 03:32:49PM -0600, eaja...@linux.vnet.ibm.com wrote: > From: "Edward A. James" > > Pmbus client drivers, if they want to use debugfs, should use the same > root directory as the pmbus debugfs entries are using. Therefore, export > the device dentry for

Re: [PATCH v2] ARM64: dts: meson-axg: add ethernet mac controller

On Thu, 2017-12-14 at 11:02 +0800, Yixun Lan wrote: > Add DT info for the stmmac ethernet MAC which found in > the Amlogic's Meson-AXG SoC, also describe the ethernet > pinctrl & clock information here. > > This is tested in the S400 dev board which use a RTL8211F PHY, > and the pins connect to

Re: [PATCH v6 00/14] soundwire: Add a new SoundWire subsystem

On Thu, Dec 14, 2017 at 01:49:49PM +0100, Greg Kroah-Hartman wrote: > Ok, but that feels a bit rushed, as I'm guessing those sysfs files are > essencial for the use of the hardware. To not include them feels odd to > me :) As a reviewer if we can get the rest of the series moving so that

Re: [PATCH] powerpc/perf: Dereference bhrb entries safely

On Tue, Dec 12, 2017 at 11:29 PM, Ravi Bangoria wrote: > It may very well happen that branch instructions recorded by > bhrb entries already get unmapped before they get processed by > the kernel. Hence, trying to dereference such memory location > will endup in

[PATCH] KVM: x86: ioapic: Clear IRR for rtc bit when rtc EOI gotten

We hit a bug in our test while run PCMark 10 in a windows 7 VM, The VM got stuck and the wallclock was hang after several minutes running PCMark 10 in it. It is quite easily to reproduce the bug with the upstream KVM and Qemu. We found that KVM can not inject any RTC irq to VM after it was hang,

Re: [PATCH v5 01/18] PCI: dwc: Use the DMA-API to get the MSI address

Ok. I will compile and test it now. Thanks. On 14/12/2017 12:22, Lorenzo Pieralisi wrote: > On Thu, Dec 14, 2017 at 12:16:38PM +, Gustavo Pimentel wrote: >> Hi Niklas and Lorenzo, >> >> I'm going to work on PCI software development now as told by Joao and I will >> test your code now. >> >>

Re: [PATCH v10 00/13] Introduce framework for SLIMbus device driver

On 13/12/17 09:25, Greg Kroah-Hartman wrote: On Mon, Dec 11, 2017 at 11:42:54PM +, srinivas.kandaga...@linaro.org wrote: From: Srinivas Kandagatla SLIMbus (Serial Low Power Interchip Media Bus) is a specification developed by MIPI (Mobile Industry

Re: [BUG]kernel softlockup due to sidtab_search_context run for long time because of too many sidtab context node

On Thu, 2017-12-14 at 03:19 +, yangjihong wrote: > Hello, > > >  So, does docker just keep allocating a unique category set for > > every new container, never reusing them even if the container is > > destroyed?  > >  That would be a bug in docker IMHO.  Or are you creating an > > unbounded

[PATCH] wireless: Always rewrite generated files from scratch

ertificates have their timestamps modified between builds and thereby trigger the generation rules. Fixes: 715a12334764 ("wireless: don't write C files on failures") Signed-off-by: Thierry Reding <tred...@nvidia.com> --- Based on next-20171214 net/wireless/Makefile | 4 ++-- 1 file chang

[PATCH v9 0/2] Add support for Arasan NAND Flash controller

This patch series adds the basic driver support for Arasan NAND Flash controller. We are reinitiating the patch series by fixing the comments given by Boris and Rob. Previous Patch reference: https://lkml.org/lkml/2017/1/8/245 Naga Sureshkumar Relli (2): mtd: arasan: Add device tree binding

[PATCH 09/14] ARM: dts: dra76-evm: Add "vqmmc-supply" property for mmc2

Add "vqmmc-supply" property for mmc2 to indicate the supply connected to the IO lines. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/dra76-evm.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/dra76-evm.dts b/arch/arm/boot/dts/dra76-evm.dts

[PATCH 10/14] ARM: dts: dra71-evm: Correct evm_sd regulator max voltage

From: Ravikumar Kattekola Correct vpo_sd_1v8_3v3 regulator max voltage to 3.3V Fixes: 9868bc585ae2 ("ARM: dts: Add support for dra718-evm") Signed-off-by: Ravikumar Kattekola Signed-off-by: Sekhar Nori Signed-off-by: Kishon Vijay Abraham I

[PATCH 08/14] ARM: dts: am57xx-idk: Add "vqmmc-supply" property for mmc2

Add "vqmmc-supply" property for mmc2 to indicate the supply connected to the IO lines. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/boot/dts/am57xx-idk-common.dtsi | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/am57xx-idk-common.dtsi

[PATCH 09/10] staging: ccree: fix fips event irq handling build

When moving from internal for kernel FIPS infrastructure the FIPS event irq handling code was left with the old ifdef by mistake. Fix it. Fixes: b7e607bf33a2 ("staging: ccree: move FIPS support to kernel infrastructure") Cc: sta...@vger.kernel.org Signed-off-by: Gilad Ben-Yossef

Re: [PATCH v2 1/3] mmc: dt-bindings: add mmc support to MT7623 SoC

On Thu, 2017-12-14 at 12:16 +0100, Matthias Brugger wrote: > Hi Ulf, > > On 12/07/2017 07:43 AM, sean.w...@mediatek.com wrote: > > From: Sean Wang > > > > Add the devicetree binding for MT7623 SoC using MT2701 as the fallback. > > > > Cc: devicet...@vger.kernel.org > >

Re: general protection fault in show_timer

On Thu, Dec 14, 2017 at 3:26 PM, Thomas Gleixner wrote: > On Tue, 12 Dec 2017, Greg KH wrote: > >> On Tue, Dec 05, 2017 at 11:58:07AM -0800, Kees Cook wrote: >> > On Thu, Nov 30, 2017 at 4:57 AM, Thomas Gleixner >> > wrote: >> > > On Thu, 30 Nov 2017,

Re: arm64: unhandled level 0 translation fault

Hi Catalin, Will, Dave, On Tue, Dec 12, 2017 at 11:20 AM, Geert Uytterhoeven wrote: > During userspace (Debian jessie NFS root) boot on arm64: > > rpcbind[1083]: unhandled level 0 translation fault (11) at 0x0008, > esr 0x9204, in dash[adf77000+1a000] > CPU: 0

Re: [PATCH 06/12] mmc: sdhci_omap: Add support to set IODELAY values

Hi, * Kishon Vijay Abraham I [171214 13:13]: > The data manual of J6/J6 Eco recommends to set different IODELAY values > depending on the mode in which the MMC/SD is enumerated in order to > ensure IO timings are met. > > Add support to set the IODELAY values depending on the

Re: [PATCH RFC 0/7] kvm pvtimer

On 2017/12/14 19:56, Paolo Bonzini wrote: On 13/12/2017 17:28, Konrad Rzeszutek Wilk wrote: 1) VM idle path and network req/resp services: Does this go away if you don't hit the idle path? Meaning if you loop without hitting HLT/MWAIT? I am assuming the issue you are facing is the latency -

Re: [PATCH v5 01/18] PCI: dwc: Use the DMA-API to get the MSI address

On Thu, Dec 14, 2017 at 12:16:38PM +, Gustavo Pimentel wrote: > Hi Niklas and Lorenzo, > > I'm going to work on PCI software development now as told by Joao and I will > test your code now. > > I was retrieving the patches through the patchwork >

Re: [PATCH v4 net-next 0/4] bpftool: cgroup bpf operations

2017-12-13 15:18 UTC+ ~ Roman Gushchin > This patchset adds basic cgroup bpf operations to bpftool. > > Right now there is no convenient way to perform these operations. > The /samples/bpf/load_sock_ops.c implements attach/detacg operations, > but only for BPF_CGROUP_SOCK_OPS

Re: [PATCH v19 3/7] xbitmap: add more operations

On Wed, Dec 13, 2017 at 08:26:06PM +0800, Wei Wang wrote: > On 12/12/2017 09:20 PM, Tetsuo Handa wrote: > > Can you eliminate exception path and fold all xbitmap patches into one, and > > post only one xbitmap patch without virtio-baloon changes? If exception path > > is valuable, you can add

Re: [PATCH v4 net-next 0/4] bpftool: cgroup bpf operations

On 12/13/2017 04:18 PM, Roman Gushchin wrote: > This patchset adds basic cgroup bpf operations to bpftool. > > Right now there is no convenient way to perform these operations. > The /samples/bpf/load_sock_ops.c implements attach/detacg operations, > but only for BPF_CGROUP_SOCK_OPS programs. Bps

Re: wlcore: fix unused function warning

Arnd Bergmann wrote: > The newly added wlcore_fw_sleep function is called conditionally, > which causes a warning without CONFIG_PM: > > drivers/net/wireless/ti/wlcore/main.c:981:12: error: 'wlcore_fw_sleep' > defined but not used [-Werror=unused-function] > > Instead of trying

Re: [Xen-devel] [PATCH V3 1/2] Drivers/PCI: Export pcie_has_flr() interface

On Wed, Dec 13, 2017 at 03:24:21PM -0600, Bjorn Helgaas wrote: > Prior to a60a2b73ba69, we had > > int pcie_flr(struct pci_dev *dev, int probe); > > like all the other reset methods. AFAICT, the addition of > pcie_has_flr() was to optimize the path slightly because when drivers > call

Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

[CC linix-api] On Wed 13-12-17 19:10:16, Ross Zwisler wrote: > This is the third revision of my patches adding a sysfs representation > of the ACPI Heterogeneous Memory Attribute Table (HMAT). These patches > are based on v4.15-rc3 and a working tree can be found here: > >

[PATCH 08/12] mmc: sdhci-omap: Add support to override f_max and iodelay from pdata

DRA74x EVM Rev H EVM comes with revision 2.0 silicon. However, earlier versions of EVM can come with either revision 1.1 or revision 1.0 of silicon. The device-tree file is written to support rev 2.0 of silicon. pdata-quirks are used to then override the settings needed for PG 1.1 silicon. PG

[PATCH 03/12] mmc: sdhci-omap: Add custom set_uhs_signaling sdhci_host ops

UHS-1 DDR50 and MMC DDR52 mode require DDR bit to be set in the configuration register (MMCHS_CON). Add sdhci-omap specific set_uhs_signaling ops to set this bit. Also while setting the UHSMS bit, clock should be disabled. Signed-off-by: Kishon Vijay Abraham I ---

Re: [PATCH v2 0/2] mm: introduce MAP_FIXED_SAFE

On Thu 14-12-17 12:44:17, Edward Napierala wrote: > Regarding the name - how about adopting MAP_EXCL? It was introduced in > FreeBSD, > and seems to do exactly this; quoting mmap(2): > > MAP_FIXEDDo not permit the system to select a different address > than the one

RE: [PATCH] KVM: x86: ioapic: Clear IRR for rtc bit when rtc EOI gotten

> -Original Message- > From: Liran Alon [mailto:liran.a...@oracle.com] > Sent: Thursday, December 14, 2017 9:02 PM > To: Gonglei (Arei); pbonz...@redhat.com; rkrc...@redhat.com > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org; Huangweidong (C) > Subject: Re: [PATCH] KVM: x86:

Re: [alsa-devel] [PATCH v10 08/13] regmap: add SLIMbus support

On 14/12/17 08:19, Takashi Iwai wrote: On Thu, 14 Dec 2017 06:17:39 +0100, Vinod Koul wrote: On Wed, Dec 13, 2017 at 04:06:11PM +, Mark Brown wrote: On Mon, Dec 11, 2017 at 11:43:02PM +, srinivas.kandaga...@linaro.org wrote: Mark, can I get an Ack for this patch so I can take it

[PATCH 2/2] input - leds: fix input_led_disconnect path

Before unregistering the led classes, we have to be sure there is no more events in the input pipeline. Closing the input node before removing the led classes flushes the pipeline and this prevents segfaults. Found with https://github.com/whot/fuzzydevice Link:

[PATCH 0/2] input - leds: fix bugs found by fuzzing

Hi, Peter wrote a fuzzing uinput program[1] to check on libinput, and the result is that the kernel fails more often than libinput :) These 2 patches allow to fix the early failures. I marked them as stable as I believe eventhough not many people discovered those and reported them, they should

[PATCH 1/2] input - leds: do not iterate over non initialized leds

We only instantiate the led classes if there is a definition in input_led_info[]. However, the max for EV_LED is bigger than the values filled in this array, and there are some holes in it. In .connect(), we check for these holes, but in leds_init_work() we do not, leading to some nice kernel

RE: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest`

> -Original Message- > From: alexander.stef...@infineon.com [mailto:alexander.stef...@infineon.com] > Sent: Thursday, December 14, 2017 6:21 AM > To: pmen...@molgen.mpg.de; j...@ziepe.ca > Cc: linux-integr...@vger.kernel.org; linux-kernel@vger.kernel.org; > Limonciello, > Mario

[PATCH 2/3] sched/isolation: Enable CONFIG_CPU_ISOLATION=y by default

From: "Paul E. McKenney" The "isolcpus=" boot parameter support was always built-in before we moved the related code under CONFIG_CPU_ISOLATION. Having it disabled by default is very confusing for people accustomed to use this parameter. So enable it by dafault to

[PATCH 3/3] sched/isolation: Document boot parameters dependency on CONFIG_CPU_ISOLATION

From: "Paul E. McKenney" The "isolcpus=" and "nohz_full=" boot parameters depend on CPU Isolation support. Let's document that. Signed-off-by: Frederic Weisbecker Cc: Paul E. McKenney Cc: Thomas Gleixner

Re: [PATCH 00/19] fs: rework and optimize i_version handling in filesystems

On Wed, 2017-12-13 at 19:02 -0500, Jeff Layton wrote: > On Thu, 2017-12-14 at 10:03 +1100, Dave Chinner wrote: > > On Wed, Dec 13, 2017 at 03:14:28PM -0500, Jeff Layton wrote: > > > On Wed, 2017-12-13 at 10:05 -0500, J. Bruce Fields wrote: > > > > This is great, thanks. > > > > > > > > On Wed,

[PATCH 1/3] sched/isolation: Make NO_HZ_FULL select CPU_ISOLATION

From: "Paul E. McKenney" CONFIG_NO_HZ_FULL doesn't make sense without CONFIG_CPU_ISOLATION. In fact enabling the first without the second is a regression as nohz_full= boot parameter gets silently ignored. Besides this unnatural combination hangs RCU gp kthread when

Re: [PATCH 1/2] x86: consider effective protection attributes in W+X check

>>> On 14.12.17 at 15:04, wrote: > On 12/12/17 11:31, Jan Beulich wrote: >> @@ -335,42 +346,45 @@ static inline bool kasan_page_table(stru >> >> #if PTRS_PER_PMD > 1 >> >> -static void walk_pmd_level(struct seq_file *m, struct pg_state *st, pud_t >> addr, unsigned long P)

[GIT PULL] Nohz / isolation fixes

Ingo, Please pull the nohz/fixes branch that can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git nohz/fixes HEAD: 11c3146353bb83028ace8ad089a911c390395986 Thanks, Frederic --- Paul E. McKenney (3): sched/isolation: Make NO_HZ_FULL

Re: [PATCH 1/1] dt-bindings: arm: document supported STM32 SoC family

On Wed, Dec 13, 2017 at 2:40 AM, Ludovic BARRE wrote: > hi Rob > > Today there was no bindings documentation for STM32 SoC > already upstreamed. This patch adds initial list of STM32 > existing in kernel. > The next serie adds just new soc and one compatible on STM32 list.

Re: [PATCH] KVM: x86: ioapic: Clear IRR for rtc bit when rtc EOI gotten

On 14/12/2017 14:01, Liran Alon wrote: >> But in our test, we found that there is a possible situation that Vcpu >> fails to read >> RTC_REG_C to clear irq, This could happens while two VCpus are >> writing/reading >> registers at the same time, for example, vcpu 0 is trying to read >> RTC_REG_C,

[PATCH 03/14] ARM: configs: keystone: Enable CONFIG_MMC_SDHCI_OMAP

Enable CONFIG_MMC_SDHCI_OMAP so that TI's k2g SoC can use sdhci-omap driver for MMC/SD controller. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/configs/keystone_defconfig | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm/configs/keystone_defconfig

[PATCH 04/14] ARM: dts: dra76x: Create a common file with MMC/SD IOdelay data

From: Sekhar Nori Add a common device-tree include file with MMC/SD IOdelay data for DRA76x SoC. In the most common case, IOdelay data available in datamanual can directly be used. This file caters to that common case. Data is based on DRA76x datamanual, SPRS993A, revised July

[PATCH 12/14] ARM: dts: am57xx-idk: Select pull down for mmc1_clk line in default mode

During a short period when the bus voltage is switched from 3.3v to 1.8v, (to enumerate UHS mode), the mmc module is disabled and the mmc IO lines are kept in a state according to the programmed pad mux pull type. According to 4.2.4.2 Timing to Switch Signal Voltage in "SD Specifications Part 1

[PATCH 02/14] ARM: omap2plus_defconfig: Enable CONFIG_MMC_SDHCI_OMAP

Enable CONFIG_MMC_SDHCI_OMAP so that TI's dra7 based SoC's can use sdhci-omap driver for eMMC/SD/SDIO controller. Signed-off-by: Kishon Vijay Abraham I --- arch/arm/configs/omap2plus_defconfig | 3 +++ 1 file changed, 3 insertions(+) diff --git

Re: [PATCH PTI v3 03/10] x86/pti/64: Fix ESPFIX64 user mapping

On Wed, Dec 13, 2017 at 09:01:50AM -0800, Andy Lutomirski wrote: > On Wed, Dec 13, 2017 at 5:12 AM, Kirill A. Shutemov > wrote: > > On Tue, Dec 12, 2017 at 07:56:38AM -0800, Andy Lutomirski wrote: > >> The ESPFIX64 user mapping belongs in pti.c just like all the other > >>

[PATCH V3] KVM/x86: Check input paging mode when cs.l is set

Reported by syzkaller: WARNING: CPU: 0 PID: 27962 at arch/x86/kvm/emulate.c:5631 x86_emulate_insn+0x557/0x15f0 [kvm] Modules linked in: kvm_intel kvm [last unloaded: kvm] CPU: 0 PID: 27962 Comm: syz-executor Tainted: GB W 4.15.0-rc2-next-20171208+ #32 Hardware name:

Re: [PATCH 6/8 v3] staging: pi433: use defines for shifting register values

You'll need to resend everything. The thread is too messy. On Wed, Dec 13, 2017 at 06:44:44PM +0100, Valentin Vidic wrote: > diff --git a/drivers/staging/pi433/rf69.c b/drivers/staging/pi433/rf69.c > index f77ecd60f43a..0889c65d5a31 100644 > --- a/drivers/staging/pi433/rf69.c > +++

Re: brcmsmac: use ARRAY_SIZE on rfseq_updategainu_events

Colin Ian King wrote: > From: Colin Ian King > > Use the ARRAY_SIZE macro on rfseq_updategainu_events to determine > size of the array. Improvement suggested by coccinelle. > > Signed-off-by: Colin Ian King >

Re: [BISECTED] tpm CLKRUN breaks PS/2 keyboard and touchpad on Braswell system

Hello Jarkko, On 12/14/2017 12:21 PM, Jarkko Sakkinen wrote: > On Mon, Dec 11, 2017 at 07:37:29PM +, James Ettle wrote: >> Hello, >> >> [First: Apologies if cross-posting from Kernel.org BZ is bad form; my >> distro BZ advised I post this to your mailing list as well.] >> >> Situation:

  1   2   3   4   5   6   7   8   9   10   >