Re: [PATCH v5 09/23] iommu/vt-d: add svm/sva invalidate function

Hi, On 05/12/2018 04:54 AM, Jacob Pan wrote: > When Shared Virtual Address (SVA) is enabled for a guest OS via > vIOMMU, we need to provide invalidation support at IOMMU API and driver > level. This patch adds Intel VT-d specific function to implement > iommu passdown invalidate API for shared

Re: CONFIG_KCOV causing crash in svm_vcpu_run()

On Mon, May 14, 2018 at 5:02 AM, Eric Biggers wrote: > Sorry, messed up address for KVM mailing list. See message below. > > On Sun, May 13, 2018 at 08:00:07PM -0700, Eric Biggers wrote: >> With CONFIG_KCOV=y and an AMD processor, running the following program >> crashes >>

Re: [PATCH 2/2] arm64: Clear the stack

On Sun, May 13, 2018 at 11:40:07AM +0300, Alexander Popov wrote: > It seems that previously I was very "lucky" to accidentally have those > MIN_STACK_LEFT, > call trace depth and oops=panic together to experience a hang on stack > overflow > during BUG(). > > > When I run my test in a loop

Re: [PATCH 01/10] autofs4 - merge auto_fs.h and auto_fs4.h

On 14/05/18 11:15, Al Viro wrote: > On Mon, May 14, 2018 at 11:03:50AM +0800, Ian Kent wrote: >> The autofs module has long since been removed so there's no need to have >> two separate include files for autofs. > > Umm... Why does fs/compat_ioctl.c need either include, actually? > >> ---

Re: [PATCH RFC 1/8] rcu: Add comment documenting how rcu_seq_snap works

On 05/13/2018 08:15 PM, Joel Fernandes (Google) wrote: > rcu_seq_snap may be tricky for someone looking at it for the first time. > Lets document how it works with an example to make it easier. > > Signed-off-by: Joel Fernandes (Google) > --- > kernel/rcu/rcu.h | 24

Re: [PATCH v3] ext4: handle errors on ext4_commit_super

On Mon, Apr 23, 2018 at 08:46:26AM -0600, Jaegeuk Kim wrote: > When remounting ext4 from ro to rw, currently it allows its transition, > even if ext4_commit_super() returns EIO. Even worse thing is, after that, > fs/buffer complains buffer dirty bits like: > > Call trace: > []

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

Hi all, Today's linux-next merge of the rcu tree got a conflict in: drivers/nvme/host/core.c between commit: 12d9f07022dc ("nvme: fix use-after-free in nvme_free_ns_head") from Linus' tree and commit: d9cf21bae6cf ("nvme: Avoid flush dependency in delete controller flow") from the rcu

Re: [PATCH 6/6] vfs: change inode times to use struct timespec64

Al, Are you ok with this approach to changing vfs timestamps? Kees mentioned that he wants to merge a patch to pstore that changes it to use timespec64 internally for 4.17: https://lkml.org/lkml/2018/5/13/3 I'm not sure how we usually merge such flag day patches. Should this be targeted for

[RFC 2/6] perf probe: Parse linerange for C++ functions

From: Holger Hans Peter Freyther perf probe --funcs will demangle C++ symbols by default but these functions can not be used for listing sourcecode. Modify the scanner to start searching for a line number only after a single ':'. ./perf probe -x ./cxx-example -L \

linux-next: manual merge of the kselftest tree with the kvm-fixes tree

Hi Shuah, Today's linux-next merge of the kselftest tree got a conflict in: tools/testing/selftests/kvm/vmx_tsc_adjust_test.c between commit: bcb2b94ae010 ("KVM: selftests: exit with 0 status code when tests cannot be run") from the kvm-fixes tree and commit: 13911360966d ("selftests:

Re: [PATCH v5 11/23] driver core: add per device iommu param

Hi, On 05/12/2018 04:54 AM, Jacob Pan wrote: > DMA faults can be detected by IOMMU at device level. Adding a pointer > to struct device allows IOMMU subsystem to report relevant faults > back to the device driver for further handling. > For direct assigned device (or user space drivers), guest OS

Re: [tip/core/rcu,16/21] rcu: Add funnel locking to rcu_start_this_gp()

On Sun, May 13, 2018 at 07:22:06PM -0700, Paul E. McKenney wrote: [..] > > > > > > If you don't mind going through the if conditions in the funnel > > > > > > locking loop > > > > > > with me, it would be quite helpful so that I don't mess the code up > > > > > > and would > > > > > > also help

Re: general protection fault in kernfs_kill_sb (2)

On Mon, May 14, 2018 at 12:20:16PM +0900, Tetsuo Handa wrote: > But there remains a refcount bug because deactivate_locked_super() from > kernfs_mount_ns() triggers kobj_ns_drop() from sysfs_kill_sb() via > sb->kill_sb() when kobj_ns_drop() is always called by sysfs_mount() > if kernfs_mount_ns()

Re: [PATCH v6 3/6] kernel/reboot.c: export pm_power_off_prepare

On 12.05.2018 13:13, Rafael J. Wysocki wrote: > On Friday, May 4, 2018 8:50:52 PM CEST Oleksij Rempel wrote: >> Hallo Andrew, >> I need your ACK or NACK for this patch. >> >> This function is used to configure external PMIC to interpret >> signal which will be triggered by pm_power_off as power

linux-next: build warnings after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/staging/most/video/video.c: In function 'vidioc_enum_fmt_vid_cap': drivers/staging/most/video/video.c:265:25: warning: unused variable 'mdev' [-Wunused-variable] struct

Re: general protection fault in kernfs_kill_sb (2)

On Mon, May 14, 2018 at 05:04:15AM +0100, Al Viro wrote: > diff --git a/fs/sysfs/mount.c b/fs/sysfs/mount.c > index b428d317ae92..92682fcc41f6 100644 > --- a/fs/sysfs/mount.c > +++ b/fs/sysfs/mount.c > @@ -25,7 +25,7 @@ static struct dentry *sysfs_mount(struct file_system_type > *fs_type, > { >

Re: [PATCH] ARM: s3c64xx: Tidy up handling of regulator GPIO lookups

On Thu, Apr 19, 2018 at 5:01 PM, Charles Keepax wrote: > From: Charles Keepax > > Rather than unconditionally registering the GPIO lookup table only do so > for devices that require it. > > Signed-off-by: Charles Keepax

Re: [PATCH v6 3/6] kernel/reboot.c: export pm_power_off_prepare

On 14.05.2018 06:33, Oleksij Rempel wrote: > > > On 12.05.2018 13:13, Rafael J. Wysocki wrote: >> On Friday, May 4, 2018 8:50:52 PM CEST Oleksij Rempel wrote: >>> Hallo Andrew, >>> I need your ACK or NACK for this patch. >>> >>> This function is used to configure external PMIC to interpret >>>

[PATCH v2] Revert "alx: remove WoL support"

This reverts commit bc2bebe8de8ed4ba6482c9cc370b0dd72ffe8cd2. The WoL feature is a must to pass Energy Star 6.1 and above, the power consumption will be measured during S3 with WoL is enabled. Reverting "alx: remove WoL support", and will try to fix the unintentional wake up issue when WoL is

Re: [PATCH] f2fs: Fix deadlock in shutdown ioctl

On 2018/5/10 21:20, Sahitya Tummala wrote: > f2fs_ioc_shutdown() ioctl gets stuck in the below path > when going down with full sync (F2FS_GOING_DOWN_FULLSYNC) > option. > > __switch_to+0x90/0xc4 > percpu_down_write+0x8c/0xc0 > freeze_super+0xec/0x1e4 > freeze_bdev+0xc4/0xcc >

Re: WARNING: suspicious RCU usage in tipc_bearer_find

On Fri, Feb 09, 2018 at 12:00:01PM -0800, syzbot wrote: > syzbot has found reproducer for the following crash on net-next commit > 617aebe6a97efa539cc4b8a52adccd89596e6be0 (Sun Feb 4 00:25:42 2018 +) > Merge tag 'usercopy-v4.16-rc1' of > git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux

linux-next: build warning after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) produced this warning: WARNING: drivers/staging/vc04_services/bcm2835-camera/bcm2835-v4l2.o(.data+0x0): Section mismatch in reference from the variable bcm2835_camera_driver to the function

Re: [PATCH RFC 1/8] rcu: Add comment documenting how rcu_seq_snap works

On Sun, May 13, 2018 at 08:47:24PM -0700, Randy Dunlap wrote: > On 05/13/2018 08:15 PM, Joel Fernandes (Google) wrote: > > rcu_seq_snap may be tricky for someone looking at it for the first time. > > Lets document how it works with an example to make it easier. > > > > Signed-off-by: Joel

Re: [PATCH] scsi: clean up generated file scsi_devinfo_tbl.c

On Sun, 13 May 2018 17:10:52 -0700 Randy Dunlap wrote: > From: Randy Dunlap > > "make clean" should remove the generated file "scsi_devinfo_tbl.c", > so list it in the clean-files variable so that the file gets > cleaned up. > > Fixes:

[RFC 6/6] perf probe: Make it possible to add a C++ uprobe

From: Holger Hans Peter Freyther If the linkage name looks like a common C++ ABI name use it instead of the original function name. This makes adding a uprobe for a C++ symbol possible. ./perf probe -x ./cxx-example "std::vector::at" Added new

[RFC 5/6] perf probe: Make listing of variables work for C++ functions

From: Holger Hans Peter Freyther Update call sites with die_match_name to call matches_demangled as well. This requires to pass the struct debuginfo/struct dso to the callbacks and modifies the closure/void *data parameter. For most functions this will change the

[RFC 4/6] perf probe: Show variables for C++ functions

From: Holger Hans Peter Freyther The demangled C++ function name contains spaces and using the generic argc_split would split the function in the middle. Create a separate version that counts the number of opening and closing '<', '>' for templated functions. $ ./perf

[RFC 3/6] perf probe: Make listing of C++ functions work

From: Holger Hans Peter Freyther If die_match_name does not match, attempt to demangle the linkage name. To use the generic demangling API we require to have a struct dso. Store it inside the debuginfo and pass it to the relevant callbacks. ./perf probe -x ./foo -L \

[RFC 0/6] perf probe: Attempt to improve C++ probing

From: Holger Hans Peter Freyther Currently perf probe -x app --funcs will list and demangle C++ functions but the other probe actions can't work with them. When asking probe to not demangle it will not list any of the application symbols creating the impression that

[RFC 1/6] perf probe: Do not exclude mangled C++ funcs

From: Holger Hans Peter Freyther Using --funcs --no-demangle on a C++ binary does not list any of the C++ functions. Change the default filter to not exclude the Common C++ ABI symbols. $ ./perf probe -x ./cxx-example --funcs --no-demangle ...

Re: general protection fault in rds_ib_get_mr

On 5/13/18 2:10 PM, Eric Biggers wrote: On Wed, Mar 21, 2018 at 09:00:01AM -0700, syzbot wrote: [...] Still reproducible on Linus' tree (commit 66e1c94db3cd4) and linux-next (next-20180511). Here's a simplified reproducer: Thanks for the test case !! Regards, Santosh

general protection fault in shmem_unused_huge_count

Hello, syzbot found the following crash on: HEAD commit:3eb2ce825ea1 Linux 4.16-rc7 git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=16bd9d9380 kernel config: https://syzkaller.appspot.com/x/.config?x=8addcf4530d93e53 dashboard link:

Re: [PATCH] scsi: libosd: Remove VLA usage

On 03/05/18 01:55, Kees Cook wrote: > On the quest to remove all VLAs from the kernel[1] this rearranges the > code to avoid a VLA warning under -Wvla (gcc doesn't recognize "const" > variables as not triggering VLA creation). Additionally cleans up variable > naming to avoid 80 character column

Re: [PATCH 1/5] media: docs: selection: fix typos

Hi Luca, My apologies for the long delay in reviewing this. It all looks very good and if you can post a v2 with these small issues fixed, then I'll merge it for 4.18. Regards, Hans On 05/13/2018 11:13 AM, Hans Verkuil wrote: > On 04/03/2018 11:15 PM, Luca Ceresoli wrote: > > Please

Re: [alsa-devel] Timeout issues in wait_for_avail function

On Mon, 07 May 2018 12:49:34 +0200, Zengtao (B) wrote: > > Hi perex and tiwai: > > I have met a timeout case when capture audio from snd-usb-audio device, > when the host call the pcm_read and get into the wait_for_avail function. > The following happends > 1. No available data for

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

Hi, On 05/04/2018 06:56 AM, Ard Biesheuvel wrote: Hi Hans, One comment below, which I missed in review before. On 29 April 2018 at 11:35, Hans de Goede wrote: Just like with PCI options ROMs, which we save in the setup_efi_pci* functions from

nand_base.c:undefined reference to `__udivdi3'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: ccda3c4b7f66aeb3c531352bb40d59501c59 commit: 3057fcef385348fe85173f1b0c824d89f1176f72 mtd: rawnand: Make sure we wait tWB before polling the STATUS reg date: 3 days ago config: m68k-allyesconfig

[GIT pull] scheduler fix for 4.17

Linus, please pull the latest sched-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-urgent-for-linus Revert the new NUMA aware placement approach which turned out to create more problems than it solved. Thanks, tglx

Re: [PATCH 1/6] x86/early-quirks: Rename duplicate define of dev_err

On Wed, 9 May 2018, Joe Perches wrote: > dev_err is becoming a macro calling _dev_err to allow prefixing of > dev_fmt to any dev_ use that has a #define dev_fmt(fmt) similar > to the existing #define pr_fmt(fmt) uses. > > Remove this dev_err macro and convert the existing two uses to pr_err. >

Re: [PATCH v3 3/6] MAINTAINERS: add at91 usart spi driver

On Fri, May 11, 2018 at 1:38 PM, Radu Pirea wrote: > Added entry for at91 usart mfd driver. > You are adding a record for not existing file? > Signed-off-by: Radu Pirea > --- > MAINTAINERS | 7 +++ > 1 file changed, 7 insertions(+) > >

Re: common non-cache coherent direct dma mapping ops

On 11.05.2018 09:59, Christoph Hellwig wrote: > this series continues consolidating the dma-mapping code, with a focus > on architectures that do not (always) provide cache coherence for DMA. > Three architectures (arm, mips and powerpc) are still left to be > converted later due to complexity of

[PATCH] m68k: Implement ndelay() as an inline function to force type checking/casting

ndelay() is supposed to take an unsigned long, but if you define ndelay() as a macro and the caller pass an unsigned long long instead of an unsigned long, the unsigned long long to unsigned long cast is not done and we end up with an "undefined reference to `__udivdi3'" error at link time. Fix

Re: [PATCH v5 04/23] iommu/vt-d: add bind_pasid_table function

Hi, On 05/12/2018 04:53 AM, Jacob Pan wrote: > Add Intel VT-d ops to the generic iommu_bind_pasid_table API > functions. > > The primary use case is for direct assignment of SVM capable > device. Originated from emulated IOMMU in the guest, the request goes > through many layers (e.g. VFIO). Upon

Re: [PATCH][RFC v2] ACPI: acpi_pad: Do not launch acpi_pad threads on idle cpus

On Saturday, May 5, 2018 1:53:22 PM CEST Chen Yu wrote: > According to current implementation of acpi_pad driver, > it does not make sense to spawn any power saving threads > on the cpus which are already idle - it might bring > unnecessary overhead on these idle cpus and causes power > waste. So

[RFC PATCH] net: Remove a confusing comment of macro SIOCDEVPRIVATE

I have been reading the NET related header files recently. I found there is a macro "#define SIOCDEVPRIVATE 0x89F0" defined in include/uapi/linux/sockios.h which is useful for private controls of net devices. When I read this section: /* Device private ioctl calls */ /* * These 16 ioctls

Re: KASAN: use-after-free Read in corrupted

Dmitry Vyukov wrote: > This looks very similar to "KASAN: use-after-free Read in fuse_kill_sb_blk": > https://groups.google.com/d/msg/syzkaller-bugs/4C4oiBX8vZ0/0NTQRcUYBgAJ > > which you fixed with "fuse: don't keep dead fuse_conn at fuse_fill_super().": >

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

Hi, On 05/03/2018 11:31 PM, Luis R. Rodriguez wrote: On Wed, May 02, 2018 at 04:49:53PM +0200, Hans de Goede wrote: Hi, On 05/01/2018 09:29 PM, Andy Lutomirski wrote: On Sun, Apr 29, 2018 at 2:36 AM Hans de Goede wrote: +The EFI embedded-fw code works by scanning all

[PATCH] clk: stm32mp1: Fix a memory leak in 'clk_stm32_register_gate_ops()'

We allocate some memory which is neither used, nor referenced by anything. So axe it. Signed-off-by: Christophe JAILLET --- This patch as not been compile-tested, I don't have the corresponding arch and have not taken time to cross-compile it. ---

[tip:x86/cpu] x86/CPU: Move cpu_detect_cache_sizes() into init_intel_cacheinfo()

Commit-ID: 606e20959ef49f22cddb611f2cefef8e6501e3dd Gitweb: https://git.kernel.org/tip/606e20959ef49f22cddb611f2cefef8e6501e3dd Author: David Wang AuthorDate: Thu, 3 May 2018 10:32:45 +0800 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[tip:x86/cpu] x86/CPU: Make intel_num_cpu_cores() generic

Commit-ID: 2cc61be60e37b1856a97ccbdcca3e86e593bf06a Gitweb: https://git.kernel.org/tip/2cc61be60e37b1856a97ccbdcca3e86e593bf06a Author: David Wang AuthorDate: Thu, 3 May 2018 10:32:44 +0800 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[tip:x86/cpu] x86/Centaur: Report correct CPU/cache topology

Commit-ID: 5a19009043fcffd1591b04a588d53336a66855d5 Gitweb: https://git.kernel.org/tip/5a19009043fcffd1591b04a588d53336a66855d5 Author: David Wang AuthorDate: Thu, 3 May 2018 10:32:46 +0800 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[GIT pull] x86/pti updates for 4.17

Linus, please pull the latest x86-pti-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus A mixed bag of fixes and updates for the ghosts which are hunting us. The scheduler fixes have been pulled into that branch to avoid conflicts. - A

[REGRESSION] And a drity fix for 0cf3:3004 QCA Rome device

Hi, Marcel Since f44cb4b older AR3012 devices stopped working. We discussed that before that QCA released a ROME device with a duplicate code. If there is no easy way to check which one is used, then it may be a good decision to change the kernel code for the newer device in new kernels. But

[tip:x86/build] x86/build: Remove no-op macro VMLINUX_SYMBOL()

Commit-ID: 2a7ffe465769bc15cb4a77f6a71e6f071d644068 Gitweb: https://git.kernel.org/tip/2a7ffe465769bc15cb4a77f6a71e6f071d644068 Author: Masahiro Yamada AuthorDate: Wed, 9 May 2018 16:49:34 +0900 Committer: Thomas Gleixner CommitDate:

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

Hi, On 05/13/2018 12:43 PM, Ard Biesheuvel wrote: On 13 May 2018 at 13:03, Hans de Goede wrote: Hi, On 05/04/2018 06:56 AM, Ard Biesheuvel wrote: Hi Hans, One comment below, which I missed in review before. On 29 April 2018 at 11:35, Hans de Goede

Re: [PATCH v3 5/6] spi: at91-usart: add driver for at91-usart as spi

> I will refer to above as (1) later on. > The question is, why you didn't utilize what SPI core provides you? Here I should have referred to (1). -- With Best Regards, Andy Shevchenko

Re: for_each_cpu() is buggy for UP kernel?

On Wed, 9 May 2018, Andrew Morton wrote: > On Wed, 9 May 2018 06:24:16 + Dexuan Cui wrote: > > > In include/linux/cpumask.h, for_each_cpu is defined like this for UP kernel > > (CONFIG_NR_CPUS=1): > > > > #define for_each_cpu(cpu, mask) \ > >

DEBUG_RWSEMS warning from thaw_super()

Hi Waiman, Since kernel v4.17-rc1 and DEBUG_RWSEMS, I see the warning below after filesystem freeze/thaw. This is a case where one process acquires a bunch of rwsem and another process releases them. To convey this use case to lockdep, freeze_super() calls lockdep_sb_freeze_release() on exit

[tip:timers/core] timer_list: Remove unused function pointer typedef

Commit-ID: ed772ec873cb0d378c0329d266ae656ec1f2b511 Gitweb: https://git.kernel.org/tip/ed772ec873cb0d378c0329d266ae656ec1f2b511 Author: Chen Lin AuthorDate: Fri, 11 May 2018 23:47:29 +0800 Committer: Thomas Gleixner CommitDate: Sun, 13 May 2018

[tip:timers/core] timers: Adjust a kernel-doc comment

Commit-ID: bf9c96bec76fbc4424b4c70be563af4107d8044f Gitweb: https://git.kernel.org/tip/bf9c96bec76fbc4424b4c70be563af4107d8044f Author: Mauro Carvalho Chehab AuthorDate: Mon, 7 May 2018 06:35:48 -0300 Committer: Thomas Gleixner

[tip:irq/core] dt-bindings/gic-v3: Add documentation for MBI support

Commit-ID: 53667c670fe00d63246fb3cfb4480bb1ba247bcc Gitweb: https://git.kernel.org/tip/53667c670fe00d63246fb3cfb4480bb1ba247bcc Author: Marc Zyngier AuthorDate: Tue, 8 May 2018 13:14:38 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[tip:irq/core] irqchip/gic-v3: Add PCI/MSI support to the GICv3 MBI sub-driver

Commit-ID: 38985351492b4ef2f63ffe527ef7cdfa66680f94 Gitweb: https://git.kernel.org/tip/38985351492b4ef2f63ffe527ef7cdfa66680f94 Author: Marc Zyngier AuthorDate: Tue, 8 May 2018 13:14:37 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[tip:irq/core] irqchip/gic-v3: Add support for Message Based Interrupts as an MSI controller

Commit-ID: 505287525c24d5c78b662fd73721ad9900b91fcc Gitweb: https://git.kernel.org/tip/505287525c24d5c78b662fd73721ad9900b91fcc Author: Marc Zyngier AuthorDate: Tue, 8 May 2018 13:14:36 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[PATCH v2] KVM: X86: Fix CR3 reserve bits

From: Wanpeng Li MSB of CR3 is a reserved bit if the PCIDE bit is not set in CR4. It should be checked when PCIDE bit is not set, however commit 'd1cd3ce900441 ("KVM: MMU: check guest CR3 reserved bits based on its physical address width")' removes the bit 63 checking

Re: KASAN: use-after-free Read in corrupted

On Sun, May 13, 2018 at 12:20 PM, Tetsuo Handa wrote: > Dmitry Vyukov wrote: >> This looks very similar to "KASAN: use-after-free Read in fuse_kill_sb_blk": >> https://groups.google.com/d/msg/syzkaller-bugs/4C4oiBX8vZ0/0NTQRcUYBgAJ >> >> which you fixed with

Re: KASAN: use-after-free Read in corrupted

Dmitry Vyukov wrote: > On Sun, May 13, 2018 at 12:20 PM, Tetsuo Handa > wrote: > > Dmitry Vyukov wrote: > >> This looks very similar to "KASAN: use-after-free Read in > >> fuse_kill_sb_blk": > >>

Re: [PATCH] edac: fix skx_edac build error when ACPI_NFIT=m

On Sat, May 12, 2018 at 06:02:12PM -0700, Randy Dunlap wrote: > From: Randy Dunlap > > Prevent build error when CONFIG_ACPI_NFIT=m and CONFIG_EDAC_SKX=y > by limiting EDAC_SKX based on how ACPI_NFIT is set. > > Fixes this build error: > drivers/edac/skx_edac.o: In

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

On 13 May 2018 at 13:03, Hans de Goede wrote: > Hi, > > > On 05/04/2018 06:56 AM, Ard Biesheuvel wrote: >> >> Hi Hans, >> >> One comment below, which I missed in review before. >> >> On 29 April 2018 at 11:35, Hans de Goede wrote: >>> >>> Just like with

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

Hi, On 05/03/2018 11:35 PM, Andy Lutomirski wrote: On Thu, May 3, 2018 at 3:31 PM Luis R. Rodriguez wrote: On Wed, May 02, 2018 at 04:49:53PM +0200, Hans de Goede wrote: Hi, On 05/01/2018 09:29 PM, Andy Lutomirski wrote: On Sun, Apr 29, 2018 at 2:36 AM Hans de Goede

[GIT pull] perf fixes for 4.17

Linus, please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus Another small set of perf tooling fixes and updates: . Revert "perf pmu: Fix pmu events parsing rule", as it broke Intel PT event

Re: [PATCH 3/3] arm64: dts: renesas: draak: Describe HDMI input

Hi Jacopo, Thanks for your patch. On 2018-05-11 12:00:02 +0200, Jacopo Mondi wrote: > Describe HDMI input connected to VIN4 interface for R-Car D3 Draak > development board. > > Signed-off-by: Jacopo Mondi > --- > arch/arm64/boot/dts/renesas/r8a77995-draak.dts | 68

[tip:timers/core] tick: Prefer a lower rating device only if it's CPU local device

Commit-ID: 1332a90558013ae4242e3dd7934bdcdeafb06c0d Gitweb: https://git.kernel.org/tip/1332a90558013ae4242e3dd7934bdcdeafb06c0d Author: Sudeep Holla AuthorDate: Wed, 9 May 2018 17:02:08 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

Re: [REGRESSION] And a drity fix for 0cf3:3004 QCA Rome device

And the worst thing is that if has been CCed to sta...@vger.kernel.org. This means that the regression will affect all supported kernels soon. This should be fixed!! 2018-05-13 16:08 GMT+03:00 Dmitry Tunin : > Hi, Marcel > > Since f44cb4b older AR3012 devices stopped

Re: [PATCH v2] ARM: dts: exynos: Update x and y properties for mms114 touchscreen

On Fri, May 11, 2018 at 06:25:33AM +0900, Andi Shyti wrote: > The mms114 binding [1] specifies that the 'x' and 'y' should be > called respectively 'touchscreen-size-x' and 'touchscreen-size-y' > in coherence with the touchscreen [2] binding. > > Update the mms114 node for trats2 and trats dts

Re: INFO: rcu detected stall in kfree_skbmem

On Fri, May 11, 2018 at 10:42 PM, Marcelo Ricardo Leitner wrote: > On Fri, May 11, 2018 at 12:08:33PM -0700, Eric Dumazet wrote: >> >> >> On 05/11/2018 11:41 AM, Marcelo Ricardo Leitner wrote: >> >> > But calling ip6_xmit with rcu_read_lock is expected. tcp stack also

[tip:irq/core] dma-iommu: Fix compilation when !CONFIG_IOMMU_DMA

Commit-ID: 8a22a3e1e768c309b718f99bd86f9f25a453e0dc Gitweb: https://git.kernel.org/tip/8a22a3e1e768c309b718f99bd86f9f25a453e0dc Author: Marc Zyngier AuthorDate: Tue, 8 May 2018 13:14:33 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[tip:irq/core] irqchip/gic-v3: Mark the base irq domain as DOMAIN_BUS_WIRED

Commit-ID: b2425b51bed7437c08c11ce71bb0f308f4516451 Gitweb: https://git.kernel.org/tip/b2425b51bed7437c08c11ce71bb0f308f4516451 Author: Marc Zyngier AuthorDate: Tue, 8 May 2018 13:14:35 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[tip:irq/core] irqdomain: Let irq_find_host default to DOMAIN_BUS_WIRED

Commit-ID: 6461934371bfc1bfe6b424b197a546b4effd0a32 Gitweb: https://git.kernel.org/tip/6461934371bfc1bfe6b424b197a546b4effd0a32 Author: Marc Zyngier AuthorDate: Tue, 8 May 2018 13:14:34 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

Re: [PATCH 1/2] KVM: X86: Fix CR3 reserve bits

- kernel...@gmail.com wrote: > 2018-05-13 16:28 GMT+08:00 Liran Alon : > > > > - kernel...@gmail.com wrote: > > > >> 2018-05-13 15:53 GMT+08:00 Liran Alon : > >> > > >> > - kernel...@gmail.com wrote: > >> > > >> >> From: Wanpeng Li

Re: [PATCH 2/5] media: docs: clarify relationship between crop and selection APIs

On 04/03/2018 11:15 PM, Luca Ceresoli wrote: > Having two somewhat similar and largely overlapping APIs is confusing, > especially since the older one appears in the docs before the newer > and most featureful counterpart. > > Clarify all of this in several ways: > - swap the two sections > -

Re: [PATCH 1/5] media: docs: selection: fix typos

On 04/03/2018 11:15 PM, Luca Ceresoli wrote: Please add a commit message here. Yes, it can be as simple as 'Fixed typos in the selection documentation.' Regards, Hans > Cc: Hans Verkuil > Signed-off-by: Luca Ceresoli > --- >

Re: [PATCH 1/2] KVM: X86: Fix CR3 reserve bits

2018-05-13 17:09 GMT+08:00 Liran Alon : > > - kernel...@gmail.com wrote: > >> 2018-05-13 16:28 GMT+08:00 Liran Alon : >> > >> > - kernel...@gmail.com wrote: >> > >> >> 2018-05-13 15:53 GMT+08:00 Liran Alon : >> >> > >> >>

Re: [PATCH 3/5] media: docs: selection: rename files to something meaningful

On 04/03/2018 11:15 PM, Luca Ceresoli wrote: > These files have an automatically-generated numbering. Replaname them Replaname -> Replace > to something that suggests their meaning. to -> with Regards, Hans > > Reported-by: Hans Verkuil > Cc: Hans Verkuil

Re: [PATCH v7] mtd: rawnand: use bit-wise majority to recover the contents of ONFI parameter

Applied after fixing a few things (see below). Changed the subject to "mtd: rawnand: use bit-wise majority to recover the ONFI param page" On Sun, 13 May 2018 04:30:02 + "Wan, Jane (Nokia - US/Sunnyvale)" wrote: > Per ONFI specification (Rev. 4.0), if all parameter

Re: [PATCH] selftests/x86: Add mov_to_ss

Hi! > +#ifdef __x86_64__ > + , "r8", "r9", "r10", "r11" > +#endif > + ); > + } > + > + printf("[OK]\tI aten't dead\n"); > + return 0; aren't? am not? Pavel --

Re: [PATCH v2] KVM: X86: Fix CR3 reserve bits

- kernel...@gmail.com wrote: > From: Wanpeng Li > > MSB of CR3 is a reserved bit if the PCIDE bit is not set in CR4. > It should be checked when PCIDE bit is not set, however commit > 'd1cd3ce900441 ("KVM: MMU: check guest CR3 reserved bits based on > its physical

Re: [PATCH 3/3] arm64: dts: renesas: draak: Describe HDMI input

Hi Simon, On 2018-05-13 10:17:50 +0200, Simon Horman wrote: > On Fri, May 11, 2018 at 12:00:02PM +0200, Jacopo Mondi wrote: > > Describe HDMI input connected to VIN4 interface for R-Car D3 Draak > > development board. > > > > Signed-off-by: Jacopo Mondi > > Hi

Re: KASAN: use-after-free Read in corrupted

On Sun, May 13, 2018 at 12:47 PM, Tetsuo Handa wrote: > Dmitry Vyukov wrote: >> On Sun, May 13, 2018 at 12:20 PM, Tetsuo Handa >> wrote: >> > Dmitry Vyukov wrote: >> >> This looks very similar to "KASAN: use-after-free Read

Re: [PATCH] ARM: dts: exynos: Use dedicated DT bindings for Odroid X/X2, U3

On Fri, May 11, 2018 at 10:09:47AM +0200, Sylwester Nawrocki wrote: > Use dedicated Odroid audio subsystem DT bindings instead of the simple-card. > This adds support for audio on the HDMI interface. How about changing the subject to "Add suppor for audio over HDMI for Odroid X/X2/U3"? > >

Re: [PATCH v3 5/6] spi: at91-usart: add driver for at91-usart as spi

On Fri, May 11, 2018 at 1:38 PM, Radu Pirea wrote: > This is the driver for at91-usart in spi mode. The USART IP can be configured > to work in many modes and one of them is SPI. > +#include > +#include Here is something wrong. You need to use latter one in new code.

Re: [Ksummit-discuss] bug-introducing patches

On Sat, May 12, 2018 at 7:38 AM, Stephen Rothwell wrote: > Hi all, > > On Wed, 9 May 2018 20:47:27 +1000 Stephen Rothwell > wrote: >> >> On Wed, 9 May 2018 18:03:46 +0900 Mark Brown wrote: >> > >> > On Wed, May 09, 2018 at

[tip:irq/core] genirq/msi: Allow level-triggered MSIs to be exposed by MSI providers

Commit-ID: 0be8153cbc2af9a96e9ab8631fc3ba23bb52dbe3 Gitweb: https://git.kernel.org/tip/0be8153cbc2af9a96e9ab8631fc3ba23bb52dbe3 Author: Marc Zyngier AuthorDate: Tue, 8 May 2018 13:14:30 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[tip:irq/core] irqchip/mvebu-gicp: Use level-triggered MSIs between ICU and GICP

Commit-ID: 25eaaabb51c9925dc65f5b54fd9a362bf118e70a Gitweb: https://git.kernel.org/tip/25eaaabb51c9925dc65f5b54fd9a362bf118e70a Author: Marc Zyngier AuthorDate: Tue, 8 May 2018 13:14:32 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

[tip:irq/core] genirq/msi: Limit level-triggered MSI to platform devices

Commit-ID: 6988e0e0d28328467e218f59589b2770675a9ebd Gitweb: https://git.kernel.org/tip/6988e0e0d28328467e218f59589b2770675a9ebd Author: Marc Zyngier AuthorDate: Tue, 8 May 2018 13:14:31 +0100 Committer: Thomas Gleixner CommitDate: Sun, 13 May

Re: [PATCH v5 2/5] efi: Add embedded peripheral firmware support

Hi, On 05/08/2018 06:12 PM, Luis R. Rodriguez wrote: On Fri, May 04, 2018 at 07:54:28AM +0200, Ard Biesheuvel wrote: On 4 May 2018 at 01:29, Luis R. Rodriguez wrote: On Sun, Apr 29, 2018 at 11:35:55AM +0200, Hans de Goede wrote: [...] diff --git

Re: [PATCH 00/13] drm/kms/mode: using helper func drm_display_mode_to/from_videomode for calculating timing parameters

On Wed, May 9, 2018 at 1:52 PM, Satendra Singh Thakur wrote: > On Thu, May 08, 2018 at 16:28:30 +0530, Satendra Singh Thakur wrote: >> On Thu, May 07, 2018 at 15:46:02 +0200, Daniel Vetter wrote: >> > On Thu, May 03, 2018 at 01:53:55PM +0530, Satendra Singh Thakur wrote:

Re: [PATCH 3/3] sched/fair: schedutil: explicit update only when required

On Sat, May 12, 2018 at 11:04:43PM -0700, Joel Fernandes wrote: > On Thu, May 10, 2018 at 04:05:53PM +0100, Patrick Bellasi wrote: > > Schedutil updates for FAIR tasks are triggered implicitly each time a > > cfs_rq's utilization is updated via cfs_rq_util_change(), currently > > called by

Re: [PATCH 2/2] KVM: X86: Fix loss of CR3_PCID_INVD bit when guest writes CR3

- kernel...@gmail.com wrote: > From: Wanpeng Li > > SDM volume 3, section 4.10.4: > > * MOV to CR3. The behavior of the instruction depends on the value of > CR4.PCIDE: > — If CR4.PCIDE = 1 and bit 63 of the instruction’s source operand is > 1, the > instruction

Re: [PATCH v5 03/23] iommu/vt-d: add a flag for pasid table bound status

Hi again, On 05/12/2018 04:53 AM, Jacob Pan wrote: > Adding a flag in device domain into to track whether a guest or > user PASID table is bound to a device. > > Signed-off-by: Jacob Pan > --- > include/linux/intel-iommu.h | 1 + > 1 file changed, 1 insertion(+) >

Re: [PATCH 1/2] KVM: X86: Fix CR3 reserve bits

- kernel...@gmail.com wrote: > 2018-05-13 15:53 GMT+08:00 Liran Alon : > > > > - kernel...@gmail.com wrote: > > > >> From: Wanpeng Li > >> > >> MSB of CR3 is a reserved bit if the PCIDE bit is not set in CR4. > >> It should be checked when

  1   2   3   4   5   6   7   >