RE: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence

2019-03-25 Thread Parav Pandit
> -Original Message- > From: linux-kernel-ow...@vger.kernel.org ow...@vger.kernel.org> On Behalf Of Parav Pandit > Sent: Monday, March 25, 2019 10:19 PM > To: Alex Williamson > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org; > kwankh...@nvidia.com > Subject: RE: [PATCH 8/8]

[PATCH v1 2/2] mmc: sdhci_f_sdh30: Add support for Milbeaut M10V host controller

2019-03-25 Thread Takao Orito
SD Host controller on Milbeaut is consist of two controller parts. One is core controller F_SDH30, this is similar to sdhci-fujitsu controller. Another is bridge controller. This bridge controller is not compatible with sdhci-fujitsu controller. This is special for Milbeaut series. This has some

[PATCH v1 0/2] mmc: sdhci_f_sdh30: Add support for Milbeaut

2019-03-25 Thread Takao Orito
The following patches add driver support for SD Host controller on Socionext's Milbeaut M10V platforms. SD Host controller on Milbeaut is consist of two controller parts. One is core controller F_SDH30, this is similar to sdhci-fujitsu controller. Another is bridge controller. This bridge

[PATCH v1 1/2] dt-bindings: mmc: sdhci-fujitsu.txt: add miilbeaut driver

2019-03-25 Thread Takao Orito
Add new compatible description for Milbeaut SoC. Socionext inherits F_SDH30 IP from Fujitsu. Then new Soc series "Milbeaut" has F_SDH30 controller specified by "socionext,milbeaut-m10v-sdhci-3.0". Signed-off-by: Takao Orito --- .../devicetree/bindings/mmc/sdhci-fujitsu.txt | 22

Re: [PATCH] MAINTAINERS: fix the file path of uniphier-mdmac.c

2019-03-25 Thread Masahiro Yamada
On Tue, Mar 26, 2019 at 11:15 AM Masahiro Yamada wrote: > > The pattern drivers/dmaengine/uniphier-mdmac.c has no match in the > source tree. > > The correct path is drivers/dma/uniphier-mdmac.c > > Reported-by: Joe Perches > Signed-off-by: Masahiro Yamada > --- I take this back. I sent this

Re: [Milbeaut PATCH v0.4 0/2] mmc: sdhci_f_sdh30: Add support for Milbeaut

2019-03-25 Thread orito.takao
Hi All I'm sorry, I had mistaken the Subject format of my patch series. I will send new patches with right format. Please ignore this series. Orito > The following patches add driver support for SD Host controller on > Socionext's Milbeaut M10V platforms. > > SD Host controller on Milbeaut is

Re: [PATCH v1 1/1] MAINTAINERS: fix typo in file name

2019-03-25 Thread Vinod Koul
On 26-03-19, 10:48, Amit Kucheria wrote: > Replace underscore with dash. > > Fixes: e31f941cf977 ("MAINTAINERS: update list of qcom drivers") > Reported-by: Joe Perches > Signed-off-by: Amit Kucheria Reviewed-by: Vinod Koul > --- > MAINTAINERS | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [PATCH 01/27] Add the ability to lock down access to the running kernel image

2019-03-25 Thread Matthew Garrett
Based on Andy's feedback, I'm going to rework this slightly and re-send tomorrow.

Re: Bad file pattern in MAINTAINERS section 'ARM/UNIPHIER ARCHITECTURE'

2019-03-25 Thread Vinod Koul
On 25-03-19, 14:24, Joe Perches wrote: > A file pattern line in this section of the MAINTAINERS file in linux-next > does not have a match in the linux source files. > > This could occur because a matching filename was never added, was deleted > or renamed in some other commit. > > The commits

Re: Bad file pattern in MAINTAINERS section 'ARM/QUALCOMM SUPPORT'

2019-03-25 Thread Amit Kucheria
On Tue, Mar 26, 2019 at 2:54 AM Joe Perches wrote: > > A file pattern line in this section of the MAINTAINERS file in linux-next > does not have a match in the linux source files. > > This could occur because a matching filename was never added, was deleted > or renamed in some other commit. > >

[PATCH v1 1/1] MAINTAINERS: fix typo in file name

2019-03-25 Thread Amit Kucheria
Replace underscore with dash. Fixes: e31f941cf977 ("MAINTAINERS: update list of qcom drivers") Reported-by: Joe Perches Signed-off-by: Amit Kucheria --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 3e5a5d263f29..d2c5852a3c8d

[Milbeaut PATCH v0.4 1/2] dt-bindings: mmc: sdhci-fujitsu.txt: add miilbeaut driver

2019-03-25 Thread Takao Orito
Add new compatible description for Milbeaut SoC. Socionext inherits F_SDH30 IP from Fujitsu. Then new Soc series "Milbeaut" has F_SDH30 controller specified by "socionext,milbeaut-m10v-sdhci-3.0". Signed-off-by: Takao Orito --- .../devicetree/bindings/mmc/sdhci-fujitsu.txt | 22

[Milbeaut PATCH v0.4 2/2] mmc: sdhci_f_sdh30: Add support for Milbeaut M10V host controller

2019-03-25 Thread Takao Orito
SD Host controller on Milbeaut is consist of two controller parts. One is core controller F_SDH30, this is similar to sdhci-fujitsu controller. Another is bridge controller. This bridge controller is not compatible with sdhci-fujitsu controller. This is special for Milbeaut series. This has some

[Milbeaut PATCH v0.4 0/2] mmc: sdhci_f_sdh30: Add support for Milbeaut

2019-03-25 Thread Takao Orito
The following patches add driver support for SD Host controller on Socionext's Milbeaut M10V platforms. SD Host controller on Milbeaut is consist of two controller parts. One is core controller F_SDH30, this is similar to sdhci-fujitsu controller. Another is bridge controller. This bridge

[RFC PATCH v2 1/3] arch/x86: add the support of ACRN guest

2019-03-25 Thread Zhao Yakui
ACRN is one open-source hypervisour, which is maintained by Linux foundation. This is to add the para-virtualization support so that it allows the Linux guest to run on acrn-hypervisor. This adds x86_hyper_acrn into supported hypervisors array, which enables Linux ACRN guest running on ACRN

[RFC PATCH v2 0/3] arch/x86: Add the support of ACRN guest under arch/x86

2019-03-25 Thread Zhao Yakui
ACRN is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open source platform. It is built for embedded IOT with small footprint and real-time features. More details can be found in

[RFC PATCH v2 2/3] arch/x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for Acrn upcall vector

2019-03-25 Thread Zhao Yakui
Linux kernel uses the HYPERVISOR_CALLBACK_VECTOR for hypervisor upcall vector. And it is already used for Xen and HyperV. After Acrn hypervisor is detected, it will also use this defined vector to notify kernel. V1->V2: Remove the unused API definition of acrn_setup_intr_handler and

[RFC PATCH v2 3/3] arch/x86/acrn: add hypercall for acrn_guest

2019-03-25 Thread Zhao Yakui
When acrn_hypervisor is detected, the hypercall is needed so that the acrn guest can query/config some settings. For example: it can be used to query the resources in hypervisor and manage the CPU/memory/device/ interrupt for Guest system. So the hypercall is added so that the kernel can

RE: [PATCH v19,RESEND 24/27] x86/vdso: Add __vdso_sgx_enter_enclave() to wrap SGX enclave transitions

2019-03-25 Thread Xing, Cedric
> On Mon, Mar 25, 2019 at 11:03 AM Sean Christopherson > wrote: > > > > On Sun, Mar 24, 2019 at 01:59:48AM -0700, Xing, Cedric wrote: > > > As said in my previous email, this vDSO API isn't even compliant to > > > x86_64 ABI and is absolutely NOT for average developers. Instead, > > >

[PATCH] Revert "gpio: use new gpio_set_config() helper in more places"

2019-03-25 Thread Andrew Jeffery
gpio-aspeed implements support for PIN_CONFIG_INPUT_DEBOUNCE. As of v5.1-rc1 we're seeing the following when booting a Romulus BMC kernel: > [ 21.373137] [ cut here ] > [ 21.374545] WARNING: CPU: 0 PID: 1 at drivers/gpio/gpio-aspeed.c:834 >

[PATCH] kbuild: do not overwrite .gitignore in output directory

2019-03-25 Thread Masahiro Yamada
Commit 3a51ff344204 ("kbuild: gitignore output directory") seemed to bother people who version-control output directories. Andre Przywara says: "Unfortunately this breaks my setup, because I keep a totally separate git repository in my build directories to track (various versions of) .config. So

RE: [PATCH v19,RESEND 24/27] x86/vdso: Add __vdso_sgx_enter_enclave() to wrap SGX enclave transitions

2019-03-25 Thread Xing, Cedric
> I think you're misunderstanding me. I'm not talking about security at > all here. SGX isn't a sandbox, full stop. I'm talking about the degree > to which an SGX enclave acts like a well-behaved black box. Any meaningful communication requires an agreement in place. The host and the enclave

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

2019-03-25 Thread Al Viro
On Mon, Mar 25, 2019 at 08:18:25PM -0700, Mark Fasheh wrote: > Hey Al, > > It's been a while since I've looked at that bit of code but it looks like > Ocfs2 is syncing the inode to disk and disposing of it's memory > representation (which would include the cluster locks held) so that other >

DO YOU SPEAK ENGLISH?

2019-03-25 Thread dinah nilesh
DO YOU SPEAK ENGLISH? Dear,i am Dinah Nilesh,it would be great to know you, i have a very important and confidential matter that i want to discuss with you,reply me back for more discussion. Regards Dinah.

linux-next: Tree for Mar 26

2019-03-25 Thread Stephen Rothwell
Hi all, Changes since 20190325: The sound-asoc tree gained a build failure for which I disabled a driver. Non-merge commits (relative to Linus' tree): 3009 2690 files changed, 83944 insertions(+), 43073 deletions

Re: [PATCH v7 7/10] KVM: arm/arm64: context-switch ptrauth registers

2019-03-25 Thread Amit Daniel Kachhap
Hi, On 3/26/19 1:34 AM, Kristina Martsenko wrote: On 19/03/2019 08:30, Amit Daniel Kachhap wrote: From: Mark Rutland When pointer authentication is supported, a guest may wish to use it. This patch adds the necessary KVM infrastructure for this to work, with a semi-lazy context switch of the

[PATCH] kbuild: skip parsing pre sub-make code for recursion

2019-03-25 Thread Masahiro Yamada
When Make recurses to the top Makefile with sub-make-done unset, the code block surrounded by 'ifneq ($(sub-make-done),1) ... endif' is parsed multiple times. This happens for in-tree building of include/config/auto.conf, *-pkg, etc. with GNU Make 4.x. This is a slight regression by commit

Re: [PATCH v2] RISC-V: Always compile mm/init.c with cmodel=medany

2019-03-25 Thread Anup Patel
On Tue, Mar 26, 2019 at 7:52 AM Palmer Dabbelt wrote: > > On Mon, 25 Mar 2019 00:01:45 PDT (-0700), a...@brainfault.org wrote: > > On Mon, Mar 25, 2019 at 12:18 PM Christoph Hellwig > > wrote: > >> > >> On Mon, Mar 25, 2019 at 01:25:50PM +0800, Alan Kao wrote: > >> > Hi Anup, > >> > > >> >

Re: [PATCH v3] RISC-V: Always compile mm/init.c with cmodel=medany and notrace

2019-03-25 Thread Anup Patel
On Mon, Mar 25, 2019 at 5:08 PM Christoph Hellwig wrote: > > > +ifdef CONFIG_FTRACE > > +CFLAGS_REMOVE_init.o = -pg > > +endif > > + > > obj-y += init.o > > obj-y += fault.o > > obj-y += extable.o > > obj-y += ioremap.o > > obj-y += cacheflush.o > > + > > +CFLAGS_init.o := -mcmodel=medany >

[PATCH v2] svm/avic: Fix invalidate logical APIC id entry

2019-03-25 Thread Suthikulpanit, Suravee
Only clear the valid bit when invalidate logical APIC id entry. The current logic clear the valid bit, but also set the rest of the bits (including reserved bits) to 1. Fixes: 98d90582be2e ('svm: Fix AVIC DFR and LDR handling') Signed-off-by: Suravee Suthikulpanit --- arch/x86/kvm/svm.c | 3 ++-

Re: [PATCH] svm/avic: Fix invalidate logical APIC id entry

2019-03-25 Thread Suthikulpanit, Suravee
On 3/22/19 8:04 PM, Vitaly Kuznetsov wrote: > "Suthikulpanit, Suravee" writes: > >> Only clear the valid bit when invalidate logical APIC id entry. >> The current logic clear the valid bit, but also set the rest of >> the bits (including reserved bits) to 1. >> >> Fixes: 98d90582be2e ('svm:

RE: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence

2019-03-25 Thread Parav Pandit
> -Original Message- > From: Alex Williamson > Sent: Monday, March 25, 2019 9:17 PM > To: Parav Pandit > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org; > kwankh...@nvidia.com > Subject: Re: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence > > On Tue, 26 Mar 2019

Re: [PATCH v12 01/11] bitops: Introduce the for_each_set_clump8 macro

2019-03-25 Thread William Breathitt Gray
On Mon, Mar 25, 2019 at 10:38:54AM +0100, Lukas Wunner wrote: > On Mon, Mar 25, 2019 at 03:22:23PM +0900, William Breathitt Gray wrote: > > +/** > > + * find_next_clump8 - find next 8-bit clump with set bits in a memory > > region > > + * @clump: location to store copy of found clump > > + *

Re: [PATCH 4/4] pinctrl: add drive for I2C related pins on MT8183

2019-03-25 Thread Zhiyong Tao
On Mon, 2019-03-25 at 11:25 -0700, Nicolas Boichat wrote: > On Mon, Mar 25, 2019 at 5:23 AM Zhiyong Tao wrote: > > > > This patch provides the advanced drive for I2C used pins on MT8183. > > The detail strength specification description of the I2C pin: > > When E1=0/E0=0, the strength is 0.125mA.

[PATCH] libata: fix using DMA buffers on stack

2019-03-25 Thread raymond pang
When CONFIG_VMAP_STACK=y, __pa() returns incorrect physical address for a stack virtual address. Stack DMA buffers must be avoided. Signed-off-by: raymond pang --- drivers/ata/libata-zpodd.c | 36 ++-- 1 file changed, 26 insertions(+), 10 deletions(-) diff --git

Re: [PATCH 0/4] pid: add pidctl()

2019-03-25 Thread Joel Fernandes
On Mon, Mar 25, 2019 at 09:54:58PM +, Jonathan Kowalski wrote: > On Mon, Mar 25, 2019 at 9:43 PM Joel Fernandes wrote: > > > > On Mon, Mar 25, 2019 at 10:19:26PM +0100, Jann Horn wrote: > > > On Mon, Mar 25, 2019 at 10:11 PM Joel Fernandes > > > wrote: > > > > > > But often you don't just

Re: [PATCH RESEND v3 3/4] arm64: dts: mt8183: add pintcrl device node

2019-03-25 Thread Zhiyong Tao
On Mon, 2019-03-25 at 11:17 -0700, Nicolas Boichat wrote: > On Mon, Mar 25, 2019 at 5:41 AM Zhiyong Tao wrote: > > > > The commit adds pintcrl device node for mt8183 > > Minor nit: This should say pinctrl (in the commit title as well). ==> Thanks for your suggestion, we will change it in next

Re: [PATCH v12 01/11] bitops: Introduce the for_each_set_clump8 macro

2019-03-25 Thread William Breathitt Gray
On Mon, Mar 25, 2019 at 03:12:36PM +0200, Andy Shevchenko wrote: > On Mon, Mar 25, 2019 at 03:22:23PM +0900, William Breathitt Gray wrote: > > This macro iterates for each 8-bit group of bits (clump) with set bits, > > within a bitmap memory region. For each iteration, "start" is set to the > >

Re: [PATCH 2/4] arm64: dts: mt8183: add pintcrl file

2019-03-25 Thread Zhiyong Tao
On Mon, 2019-03-25 at 14:30 -0500, Rob Herring wrote: > On Mon, Mar 25, 2019 at 08:23:00PM +0800, Zhiyong Tao wrote: > > This patch adds pinctrl file for mt8183. > > Still has a typo in the subject. ==>we will change it in next version > > > > > Signed-off-by: Zhiyong Tao > > --- > >

RE: [PATCH V10 1/4] dt-bindings: fsl: scu: add thermal binding

2019-03-25 Thread Anson Huang
Ping... Hi, Eduardo What is your opinion about where to put the HW resource ID in DT? Best Regards! Anson Huang > -Original Message- > From: Anson Huang > Sent: 2019年3月13日 16:12 > To: 'Rob Herring' ; 'edubez...@gmail.com' > > Cc: 'mark.rutl...@arm.com' ; > 'shawn...@kernel.org'

linux-next: build failure after merge of the sound-asoc tree

2019-03-25 Thread Stephen Rothwell
Hi all, After merging the sound-asoc tree, today's linux-next build (powerpc allyesconfig) failed like this: sound/soc/codecs/tlv320aic32x4-clk.c:19:16: error: field 'hw' has incomplete type struct clk_hw hw; ^~ In file included from include/linux/init.h:5,

Re: [PATCH 0/3] tracing: introduce TRACE_EVENT_NONE and use it

2019-03-25 Thread Yafang Shao
On Tue, Mar 26, 2019 at 10:17 AM Steven Rostedt wrote: > > On Tue, 26 Mar 2019 09:40:04 +0800 > Yafang Shao wrote: > > > In this patchset, I introduce a new macro TRACE_EVENT_NONE(), which will > > define a tracepoint as a do-nothing inline function. > > #define TRACE_EVENT_NONE(name,

Re: [PATCH] scsi: gdth: Only call dma_free_coherent when buf is not NULL in ioc_general

2019-03-25 Thread Martin K. Petersen
Nathan, > When building with -Wsometimes-uninitialized, Clang warns: > > drivers/scsi/gdth.c:3662:6: warning: variable 'paddr' is used > uninitialized whenever 'if' condition is false > [-Wsometimes-uninitialized] > > Don't attempt to call dma_free_coherent when buf is NULL (meaning that > we

Re: [PATCH 2/3] sched/fair: do not expose some tracepoints to user if CONFIG_SCHEDSTATS is not set

2019-03-25 Thread Yafang Shao
On Tue, Mar 26, 2019 at 10:21 AM Steven Rostedt wrote: > > On Tue, 26 Mar 2019 09:40:06 +0800 > Yafang Shao wrote: > > > The tracepoints trace_sched_stat_{iowait, blocked, wait, sleep} should > > be not exposed to user if CONFIG_SCHEDSTATS is not set. > > > > Signed-off-by: Yafang Shao > > ---

Re: [PATCH v2] RISC-V: Always compile mm/init.c with cmodel=medany

2019-03-25 Thread Palmer Dabbelt
On Mon, 25 Mar 2019 00:01:45 PDT (-0700), a...@brainfault.org wrote: On Mon, Mar 25, 2019 at 12:18 PM Christoph Hellwig wrote: On Mon, Mar 25, 2019 at 01:25:50PM +0800, Alan Kao wrote: > Hi Anup, > > Sorry for being late to the party. I think one more thing should > move together with

Re: [PATCH 2/3] sched/fair: do not expose some tracepoints to user if CONFIG_SCHEDSTATS is not set

2019-03-25 Thread Steven Rostedt
On Tue, 26 Mar 2019 09:40:06 +0800 Yafang Shao wrote: > The tracepoints trace_sched_stat_{iowait, blocked, wait, sleep} should > be not exposed to user if CONFIG_SCHEDSTATS is not set. > > Signed-off-by: Yafang Shao > --- > include/trace/events/sched.h | 14 ++ > 1 file changed,

RE: Why CMA allocater fails if there is a signal pending?

2019-03-25 Thread Peter Chen
> > On 3/25/19 3:26 AM, Russell King - ARM Linux admin wrote: > > On Mon, Mar 25, 2019 at 04:37:09PM +0800, Peter Chen wrote: > >> Hi Michal & Marek, > >> > >> I meet an issue that the DMA (CMA used) allocation failed if there is > >> a user signal, Eg Ctrl+C, it causes the USB xHCI stack fails

Re: [PATCH 0/3] tracing: introduce TRACE_EVENT_NONE and use it

2019-03-25 Thread Steven Rostedt
On Tue, 26 Mar 2019 09:40:04 +0800 Yafang Shao wrote: > In this patchset, I introduce a new macro TRACE_EVENT_NONE(), which will > define a tracepoint as a do-nothing inline function. > #define TRACE_EVENT_NONE(name, proto) \ > static inline void

Re: [PATCH] scsi: lpfc: avoid uninitialized variable warning

2019-03-25 Thread Martin K. Petersen
Arnd, > clang -Wuninitialized incorrectly sees a variable being used without > initialization: > > drivers/scsi/lpfc/lpfc_nvme.c:2102:37: error: variable 'localport' is > uninitialized when used here > [-Werror,-Wuninitialized] > lport = (struct lpfc_nvme_lport

Re: [PATCH v2 00/12] Add some functionalities for Tegra soctherm

2019-03-25 Thread Wei Ni
Hi all, Does there have any comments on this serial? Thanks. Wei. On 21/2/2019 6:18 PM, Wei Ni wrote: > Move the hw/sw shutdown patches into this serial. There already have > some discussion for it in https://lkml.org/lkml/2018/12/7/225. > Support GPU HW throttle, thermal IRQ, set_trips(), EDP

Re: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence

2019-03-25 Thread Alex Williamson
On Tue, 26 Mar 2019 01:43:44 + Parav Pandit wrote: > > -Original Message- > > From: Alex Williamson > > Sent: Monday, March 25, 2019 7:06 PM > > To: Parav Pandit > > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org; > > kwankh...@nvidia.com > > Subject: Re: [PATCH 8/8]

Re: [PATCH] scsi: qla4xxx: avoid freeing unallocated dma memory

2019-03-25 Thread Martin K. Petersen
Arnd, > Clang -Wuninitialized notices that on is_qla40XX we never allocate any > DMA memory in get_fw_boot_info() but attempt to free it anyway: Applied to 5.2/scsi-queue, thanks! -- Martin K. Petersen Oracle Linux Engineering

[PATCH] MAINTAINERS: fix the file path of uniphier-mdmac.c

2019-03-25 Thread Masahiro Yamada
The pattern drivers/dmaengine/uniphier-mdmac.c has no match in the source tree. The correct path is drivers/dma/uniphier-mdmac.c Reported-by: Joe Perches Signed-off-by: Masahiro Yamada --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS

Re: [PATCH 2/2] x86/mmap: handle worst-case heap randomization in mmap_base

2019-03-25 Thread Saidi, Ali
On 3/21/19, 9:11 AM, "linux-arm-kernel on behalf of Thomas Gleixner" wrote: On Tue, 12 Mar 2019, Ali Saidi wrote: > Increase mmap_base by the worst-case brk randomization so that > the stack and heap remain apart. > > In Linux 4.13 a change was committed that

Hallo

2019-03-25 Thread Guanglu Ma
Schönen Tag, Ich bin ein Unternehmensgründungs- und Anlageberater für Privatinvestoren und Investmentgesellschaften sowie andere Finanzierungsquellen, die privat nach Gelegenheiten Ausschau halten, die eine höhere Rendite für ihr privates Anlageportfolio erzielen können Nehmen Sie Kontakt mit

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

2019-03-25 Thread Al Viro
On Mon, Mar 25, 2019 at 11:37:32PM +, Al Viro wrote: > For debugfs it's clearly "use default ->evict_inode(), have explicit > ->destroy_inode() using free_inode_nonrcu()" - there we have nothing > else done in ->evict_inode() and kfree is obviously safe in softirq. > I'll post that (or push

debugfs: fix use-after-free on symlink traversal

2019-03-25 Thread Al Viro
symlink body shouldn't be freed without an RCU delay. Switch debugfs to ->destroy_inode() and use of call_rcu(); free both the inode and symlink body in the callback. Similar to solution for bpf, only here it's even more obvious that ->evict_inode() can be dropped. Signed-off-by: Al Viro ---

RE: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence

2019-03-25 Thread Parav Pandit
> -Original Message- > From: Alex Williamson > Sent: Monday, March 25, 2019 7:06 PM > To: Parav Pandit > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org; > kwankh...@nvidia.com > Subject: Re: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence > > On Mon, 25 Mar 2019

Re: [PATCH 1/2] platform/x86: intel_pmc_core: Convert to a platform_driver

2019-03-25 Thread Rajat Jain
Hi Rajneesh, On Mon, Mar 25, 2019 at 3:23 AM Bhardwaj, Rajneesh wrote: > > Hi Rajat > > On 23-Mar-19 6:00 AM, Rajat Jain wrote: > > Hi Rajneesh, > > > > > > > > On Fri, Mar 22, 2019 at 12:56 PM Bhardwaj, Rajneesh > > wrote: > >> Some suggestions below > >> > >> On 18-Mar-19 8:36 PM, Rajat Jain

[PATCH 3/3] rcu: validate arguments for rcu tracepoints

2019-03-25 Thread Yafang Shao
When CONFIG_RCU_TRACE is not set, all these tracepoints are define as do-nothing macro. We'd better make those inline functions that take proper arguments. As RCU_TRACE() is defined as do-nothing marco as well when CONFIG_RCU_TRACE is not set, so we can clean it up. Signed-off-by: Yafang Shao

[PATCH 2/3] sched/fair: do not expose some tracepoints to user if CONFIG_SCHEDSTATS is not set

2019-03-25 Thread Yafang Shao
The tracepoints trace_sched_stat_{iowait, blocked, wait, sleep} should be not exposed to user if CONFIG_SCHEDSTATS is not set. Signed-off-by: Yafang Shao --- include/trace/events/sched.h | 14 ++ 1 file changed, 14 insertions(+) diff --git a/include/trace/events/sched.h

[PATCH 1/3] tracing: introduce TRACE_EVENT_NONE()

2019-03-25 Thread Yafang Shao
Sometimes we want define a tracepoint as a do-nothing function. So I introduce this TRACE_EVENT_NONE() for this kind of usage. Signed-off-by: Yafang Shao --- include/linux/tracepoint.h | 8 include/trace/define_trace.h | 4 2 files changed, 12 insertions(+) diff --git

ubifs: fix use-after-free on symlink traversal

2019-03-25 Thread Al Viro
free the symlink body after the same RCU delay we have for freeing the struct inode itself, so that traversal during RCU pathwalk wouldn't step into freed memory. Signed-off-by: Al Viro --- diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c index 8dc2818fdd84..12628184772c 100644 ---

jffs2: fix use-after-free on symlink traversal

2019-03-25 Thread Al Viro
free the symlink body after the same RCU delay we have for freeing the struct inode itself, so that traversal during RCU pathwalk wouldn't step into freed memory. Signed-off-by: Al Viro --- diff --git a/fs/jffs2/readinode.c b/fs/jffs2/readinode.c index 389ea53ea487..bccfc40b3a74 100644 ---

[PATCH 0/3] tracing: introduce TRACE_EVENT_NONE and use it

2019-03-25 Thread Yafang Shao
In this patchset, I introduce a new macro TRACE_EVENT_NONE(), which will define a tracepoint as a do-nothing inline function. #define TRACE_EVENT_NONE(name, proto) \ static inline void trace_##name(proto) \ { }

ceph: fix use-after-free on symlink traversal

2019-03-25 Thread Al Viro
free the symlink body after the same RCU delay we have for freeing the struct inode itself, so that traversal during RCU pathwalk wouldn't step into freed memory. Signed-off-by: Al Viro --- diff --git a/fs/ceph/inode.c b/fs/ceph/inode.c index e3346628efe2..2d61ddda9bf5 100644 ---

Re: [PATCH -next] ring-buffer: Fix ring buffer size in rb_write_something

2019-03-25 Thread Steven Rostedt
On Sun, 23 Sep 2018 12:11:33 + YueHaibing wrote: > 'cnt' should be used to calculate ring buffer size rather than data->cnt I just found this patch in my inbox (was traveling at the time. But now I have patchwork attached to my INBOX so patches like these shouldn't be missed anymore!) Yes,

Re: [BACKPORT 4.4.y 24/25] lib/int_sqrt: optimize small argument

2019-03-25 Thread Greg KH
On Fri, Mar 22, 2019 at 04:44:15PM +0100, Arnd Bergmann wrote: > From: Peter Zijlstra > > The current int_sqrt() computation is sub-optimal for the case of small > @x. Which is the interesting case when we're going to do cumulative > distribution functions on idle times, which we assume to be a

Re: [BACKPORT 4.4.y 23/25] serial: sprd: clear timeout interrupt only rather than all interrupts

2019-03-25 Thread Greg KH
On Fri, Mar 22, 2019 at 04:44:14PM +0100, Arnd Bergmann wrote: > From: Lanqing Liu > > On Spreadtrum's serial device, nearly all of interrupts would be cleared > by hardware except timeout interrupt. This patch removed the operation > of clearing all interrupt in irq handler, instead added an

Re: [BACKPORT 4.4.y 21/25] arm64: traps: disable irq in die()

2019-03-25 Thread Greg KH
On Fri, Mar 22, 2019 at 04:44:12PM +0100, Arnd Bergmann wrote: > From: Qiao Zhou > > In current die(), the irq is disabled for __die() handle, not > including the possible panic() handling. Since the log in __die() > can take several hundreds ms, new irq might come and interrupt > current die().

Re: [BACKPORT 4.4.y 20/25] Hang/soft lockup in d_invalidate with simultaneous calls

2019-03-25 Thread Greg KH
On Fri, Mar 22, 2019 at 04:44:11PM +0100, Arnd Bergmann wrote: > From: Al Viro > > It's not hard to trigger a bunch of d_invalidate() on the same > dentry in parallel. They end up fighting each other - any > dentry picked for removal by one will be skipped by the rest > and we'll go for the

Re: [RFC PATCH] mm: readahead: add readahead_shift into backing device

2019-03-25 Thread Fengguang Wu
On Mon, Mar 25, 2019 at 09:59:31AM -0700, Mark Salyzyn wrote: On 03/25/2019 05:16 AM, Fengguang Wu wrote: Martin, On Fri, Mar 22, 2019 at 11:46:11PM +0800, Martin Liu wrote: As the discussion https://lore.kernel.org/patchwork/patch/334982/ We know an open file's ra_pages might run out of sync

Re: [BACKPORT 4.4.y 17/25] mmc: core: don't try to switch block size for dual rate mode

2019-03-25 Thread Greg KH
On Fri, Mar 22, 2019 at 04:44:08PM +0100, Arnd Bergmann wrote: > From: Ziyuan Xu > > Per spec, block size should always be 512 bytes for dual rate mode, > so any attempts to switch the block size under dual rate mode should > be neglected. > > Signed-off-by: Ziyuan Xu > Signed-off-by: Shawn

Re: [BACKPORT 4.4.y 19/25] serial: sprd: adjust TIMEOUT to a big value

2019-03-25 Thread Greg KH
On Fri, Mar 22, 2019 at 04:44:10PM +0100, Arnd Bergmann wrote: > From: Wei Qiao > > SPRD_TIMEOUT was 256, which is too small to wait until the status > switched to workable in a while loop, so that the earlycon could > not work correctly. > > Signed-off-by: Wei Qiao > Signed-off-by: Chunyan

Re: [BACKPORT 4.4.y 04/25] USB: iowarrior: fix oops with malicious USB descriptors

2019-03-25 Thread Greg Kroah-Hartman
On Fri, Mar 22, 2019 at 04:43:55PM +0100, Arnd Bergmann wrote: > From: Josh Boyer > > The iowarrior driver expects at least one valid endpoint. If given > malicious descriptors that specify 0 for the number of endpoints, > it will crash in the probe function. Ensure there is at least > one

Re: [BACKPORT 4.4.y 02/25] ALSA: compress: add support for 32bit calls in a 64bit kernel

2019-03-25 Thread Greg KH
On Fri, Mar 22, 2019 at 04:43:53PM +0100, Arnd Bergmann wrote: > From: Ravindra Lokhande > > Compress offload does not support ioctl calls from a 32bit userspace > in a 64 bit kernel. This patch adds support for ioctls from a 32bit > userspace in a 64bit kernel > > Signed-off-by: Ravindra

Re: [BACKPORT 4.4.y 01/25] mmc: pwrseq: constify mmc_pwrseq_ops structures

2019-03-25 Thread Greg KH
On Fri, Mar 22, 2019 at 04:43:52PM +0100, Arnd Bergmann wrote: > From: Julia Lawall > > The mmc_pwrseq_ops structures are never modified, so declare them as const. > > Done with the help of Coccinelle. > > Signed-off-by: Julia Lawall > Signed-off-by: Ulf Hansson > (cherry picked from commit

Re: [RFC PATCH 2/3] arch/x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for Acrn upcall vector

2019-03-25 Thread Zhao, Yakui
On 2019年03月25日 16:27, Thomas Gleixner wrote: On Mon, 25 Mar 2019, Zhao, Yakui wrote: +/* SPDX-License-Identifier: GPL-2.0 */ #ifndef _ASM_X86_ACRNHYPER_H +#define _ASM_X86_ACRNHYPER_H + +#include +#include + +#ifdef CONFIG_ACRN +/* ACRN Hypervisor callback */ +void

Re: [RFC PATCH 3/3] arch/x86/acrn: add hypercall for acrn_hypervisor

2019-03-25 Thread Zhao, Yakui
On 2019年03月25日 16:30, Thomas Gleixner wrote: On Mon, 25 Mar 2019, Zhao, Yakui wrote: -Original Message- From: Thomas Gleixner [mailto:t...@linutronix.de] Sent: Saturday, March 23, 2019 12:02 AM To: Zhao, Yakui Cc: linux-kernel@vger.kernel.org; x...@kernel.org; Chen, Jason CJ

RE: [PATCH V9 1/5] dt-bindings: pwm: Add i.MX TPM PWM binding

2019-03-25 Thread Anson Huang
Hi, Rob Best Regards! Anson Huang > -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: 2019年3月26日 4:42 > To: Anson Huang > Cc: thierry.red...@gmail.com; mark.rutl...@arm.com; > shawn...@kernel.org; s.ha...@pengutronix.de; ker...@pengutronix.de; > feste...@gmail.com;

Re: "cat /proc/lockdep" after "rmmod " when !debug_locks will crash the system

2019-03-25 Thread Bart Van Assche
On 3/25/19 5:27 PM, shenghui wrote: On 3/26/19 1:06 AM, Bart Van Assche wrote: On Mon, 2019-03-25 at 17:45 +0800, shenghui wrote: [ 47.103637] vboxdrv: loading out-of-tree module taints kernel. [ 47.111919] vboxdrv: Found 2 processor cores [ 47.119013] vboxdrv: fAsync=0 offMin=0x2ee

[PATCH v2 bpf-next 01/21] bpf: Add base proto function for cgroup-bpf programs

2019-03-25 Thread Andrey Ignatov
Currently kernel/bpf/cgroup.c contains only one program type and one proto function cgroup_dev_func_proto(). It'd be useful to have base proto function that can be reused for new cgroup-bpf program types coming soon. Introduce cgroup_base_func_proto(). Signed-off-by: Andrey Ignatov ---

Re: [PATCH 02/17] fpga: dfl: fme: align PR buffer size per PR datawidth

2019-03-25 Thread Wu Hao
On Mon, Mar 25, 2019 at 12:50:40PM -0500, Alan Tull wrote: > On Sun, Mar 24, 2019 at 10:23 PM Wu Hao wrote: > > Hi Hao, > > Looks good, one question below. > > > > > Current driver checks if input bitstream file size is aligned or > > not per PR data width (default 32bits). It requires one

Re: [PATCH 25/27] debugfs: Restrict debugfs when the kernel is locked down

2019-03-25 Thread Greg Kroah-Hartman
On Mon, Mar 25, 2019 at 05:38:09PM -0700, Matthew Garrett wrote: > On Mon, Mar 25, 2019 at 5:35 PM Greg Kroah-Hartman > wrote: > > On Mon, Mar 25, 2019 at 03:09:52PM -0700, Matthew Garrett wrote: > > > Normal device interaction should be done through configfs, sysfs or a > > > miscdev, not

Re: [RESEND PATCH v6 00/12] x86: Enable FSGSBASE instructions

2019-03-25 Thread Andy Lutomirski
On Fri, Mar 15, 2019 at 1:07 PM Chang S. Bae wrote: > > Updates from v5 [5]: > * Drop the new tain flag (TAINT_INSECURE) > * Cleanup copy_thread_tls(), some changelog, and unnecessary comments on > assembly macros > * Rearrange some helper updates appropriately (from patch 4 to 6) I think this

Re: [PATCH 25/27] debugfs: Restrict debugfs when the kernel is locked down

2019-03-25 Thread Matthew Garrett
On Mon, Mar 25, 2019 at 5:35 PM Greg Kroah-Hartman wrote: > On Mon, Mar 25, 2019 at 03:09:52PM -0700, Matthew Garrett wrote: > > Normal device interaction should be done through configfs, sysfs or a > > miscdev, not debugfs. > > Then why not just not allow debugfs at all if it is such a "big >

Re: [RESEND PATCH v6 04/12] x86/fsgsbase/64: Enable FSGSBASE instructions in the helper functions

2019-03-25 Thread Andi Kleen
>So on user space to kernel space transitions swapping in kernel GS should >simply do: > userGS = RDGSBASE() > WRGSBASE(kernelGS) This would also need to find kernelGS first, by doing RDPID and then reading it from memory in the right index (which might be a full cache miss if

Re: [PATCH 25/27] debugfs: Restrict debugfs when the kernel is locked down

2019-03-25 Thread Greg Kroah-Hartman
On Mon, Mar 25, 2019 at 03:09:52PM -0700, Matthew Garrett wrote: > From: David Howells > > Disallow opening of debugfs files that might be used to muck around when > the kernel is locked down as various drivers give raw access to hardware > through debugfs. Given the effort of auditing all 2000

Re: pidfd design

2019-03-25 Thread Andy Lutomirski
On Mon, Mar 25, 2019 at 5:12 PM Christian Brauner wrote: > > On Mon, Mar 25, 2019 at 05:00:17PM -0700, Andy Lutomirski wrote: > > On Mon, Mar 25, 2019 at 4:45 PM Christian Brauner > > wrote: > > > > > > On Mon, Mar 25, 2019 at 04:42:14PM -0700, Andy Lutomirski wrote: > > > > On Mon, Mar 25,

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

2019-03-25 Thread Al Viro
On Mon, Mar 25, 2019 at 04:44:40PM -0700, Alexei Starovoitov wrote: > On Mon, Mar 25, 2019 at 11:37:32PM +, Al Viro wrote: > > > > For debugfs it's clearly "use default ->evict_inode(), have explicit > > ->destroy_inode() using free_inode_nonrcu()" - there we have nothing > > else done in

[PATCH v2 1/1] x86/mm: Fix limit mmap() of /dev/mem to valid physical addresses

2019-03-25 Thread rcampbell
From: Ralph Campbell valid_phys_addr_range() is used to sanity check the physical address range of an operation, e.g., access to /dev/mem. It uses __pa(high_memory) internally. If memory is populated at the end of the physical address space, then __pa(high_memory) is outside of the physical

[PATCH v2 0/1] x86/mm: Fix limit mmap() of /dev/mem to valid physical

2019-03-25 Thread rcampbell
From: Ralph Campbell I was debugging with v5.1.0-rc1 and while booting I hit a kernel BUG at arch/x86/mm/physaddr.c:27 which I fixed with the following patch but now I can't seem to reproduce the exact setup that triggered it. Still, it seems like a valid problem and maybe my difficulty in

Re: pidfd design

2019-03-25 Thread Christian Brauner
On Mon, Mar 25, 2019 at 05:00:17PM -0700, Andy Lutomirski wrote: > On Mon, Mar 25, 2019 at 4:45 PM Christian Brauner > wrote: > > > > On Mon, Mar 25, 2019 at 04:42:14PM -0700, Andy Lutomirski wrote: > > > On Mon, Mar 25, 2019 at 1:23 PM Daniel Colascione > > > wrote: > > > > > > > > On Mon,

Re: [PATCH V3 01/23] perf/x86: Support outputting XMM registers

2019-03-25 Thread Thomas Gleixner
On Fri, 22 Mar 2019, kan.li...@linux.intel.com wrote: > > + PERF_REG_X86_XMM15 = 62, > + > + /* All registers include the XMMX registers */ > + PERF_REG_X86_MAX = PERF_REG_X86_XMM15 + 2, Ergo: PERF_REG_X86_MAX == 64 > -#define REG_RESERVED (~((1ULL << PERF_REG_X86_MAX) - 1ULL)) >

[PATCH 1/1] RFC: security: add SECURE_KEEP_FSUID to preserve fsuid/fsgid across execve

2019-03-25 Thread Igor Lubashev
Many kernel interfaces require real and/or effective root uid instead of relying solely of capabilities. An executable that uses such interfaces has to be set-uid-root or be executed by a thread with effective root uid. Presently, fsuid and saved uid will reset to the effective uid during execve.

Re: [PATCH 8/8] vfio/mdev: Improve the create/remove sequence

2019-03-25 Thread Alex Williamson
On Mon, 25 Mar 2019 23:34:28 + Parav Pandit wrote: > > -Original Message- > > From: Alex Williamson > > Sent: Monday, March 25, 2019 6:19 PM > > To: Parav Pandit > > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org; > > kwankh...@nvidia.com > > Subject: Re: [PATCH 8/8]

Re: [PATCH V3 01/23] perf/x86: Support outputting XMM registers

2019-03-25 Thread Thomas Gleixner
On Mon, 25 Mar 2019, Liang, Kan wrote: > On 3/23/2019 5:56 AM, Peter Zijlstra wrote: > > On Fri, Mar 22, 2019 at 10:22:50AM -0700, Andi Kleen wrote: > > > > > diff --git a/arch/x86/include/uapi/asm/perf_regs.h > > > > > b/arch/x86/include/uapi/asm/perf_regs.h > > > > > index

Re: pidfd design

2019-03-25 Thread Andy Lutomirski
On Mon, Mar 25, 2019 at 4:45 PM Christian Brauner wrote: > > On Mon, Mar 25, 2019 at 04:42:14PM -0700, Andy Lutomirski wrote: > > On Mon, Mar 25, 2019 at 1:23 PM Daniel Colascione wrote: > > > > > > On Mon, Mar 25, 2019 at 1:14 PM Jann Horn wrote: > > > > > > > > On Mon, Mar 25, 2019 at 8:44 PM

Re: [PATCH v19,RESEND 24/27] x86/vdso: Add __vdso_sgx_enter_enclave() to wrap SGX enclave transitions

2019-03-25 Thread Andy Lutomirski
On Mon, Mar 25, 2019 at 11:03 AM Sean Christopherson wrote: > > On Sun, Mar 24, 2019 at 01:59:48AM -0700, Xing, Cedric wrote: > > As said in my previous email, this vDSO API isn't even compliant to > > x86_64 ABI and is absolutely NOT for average developers. Instead, > > host/enclave

[PATCH] regulator: sc2731: Constify regulators

2019-03-25 Thread Axel Lin
The regulators array should never need to be modified, make it const so compiler can put it to .rodata. Signed-off-by: Axel Lin --- drivers/regulator/sc2731-regulator.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/regulator/sc2731-regulator.c

  1   2   3   4   5   6   7   8   9   10   >