Re: [PATCH 3/5] ASoC: mediatek: Add MT8516 PCM driver

On Thu, May 02, 2019 at 02:10:39PM +0200, Fabien Parent wrote: > +static irqreturn_t mt8516_afe_irq_handler(int irq, void *dev_id) > +{ > + struct mtk_base_afe *afe = dev_id; > + unsigned int reg_value; > + unsigned int memif_status; > + int i, ret; > + > + ret =

[tip:perf/urgent] tools arch uapi: Copy missing unistd.h headers for arc, hexagon and riscv

Commit-ID: 18f90d372cf35b387663f1567de701e5393f6eb5 Gitweb: https://git.kernel.org/tip/18f90d372cf35b387663f1567de701e5393f6eb5 Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 22 Apr 2019 15:21:35 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:20 -0400

[tip:perf/urgent] perf tools: Remove needless asm/unistd.h include fixing build in some places

Commit-ID: 7e221b811f1472d0c58c7d4e0fe84fcacd22580a Gitweb: https://git.kernel.org/tip/7e221b811f1472d0c58c7d4e0fe84fcacd22580a Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 2 May 2019 09:26:23 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:20 -0400

[tip:perf/urgent] tools build: Add -ldl to the disassembler-four-args feature test

Commit-ID: c638417e1a64b1f43ebab589e697d1cd1a127a74 Gitweb: https://git.kernel.org/tip/c638417e1a64b1f43ebab589e697d1cd1a127a74 Author: Arnaldo Carvalho de Melo AuthorDate: Wed, 1 May 2019 16:27:00 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:20 -0400

[tip:perf/urgent] perf cs-etm: Always allocate memory for cs_etm_queue::prev_packet

Commit-ID: 35bb59c10a6d0578806dd500477dae9cb4be344e Gitweb: https://git.kernel.org/tip/35bb59c10a6d0578806dd500477dae9cb4be344e Author: Leo Yan AuthorDate: Sun, 28 Apr 2019 16:32:27 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:20 -0400 perf cs-etm:

[tip:perf/urgent] perf cs-etm: Don't check cs_etm_queue::prev_packet validity

Commit-ID: cf0c37b6dbf74fb71bea07b516612d29e00dcbc4 Gitweb: https://git.kernel.org/tip/cf0c37b6dbf74fb71bea07b516612d29e00dcbc4 Author: Leo Yan AuthorDate: Sun, 28 Apr 2019 16:32:28 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:20 -0400 perf cs-etm: Don't

[tip:perf/urgent] perf report: Report OOM in status line in the GTK UI

Commit-ID: 167e418fa0871c083e2c74508d73012abb01e6f7 Gitweb: https://git.kernel.org/tip/167e418fa0871c083e2c74508d73012abb01e6f7 Author: Thomas Richter AuthorDate: Tue, 23 Apr 2019 12:53:03 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:20 -0400 perf

[tip:perf/urgent] tools uapi x86: Sync vmx.h with the kernel

Commit-ID: 24e45b49eef07814e0507507161cd06f15b8ee1b Gitweb: https://git.kernel.org/tip/24e45b49eef07814e0507507161cd06f15b8ee1b Author: Arnaldo Carvalho de Melo AuthorDate: Mon, 22 Apr 2019 11:54:50 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:19 -0400

[tip:perf/urgent] perf bpf: Return value with unlocking in perf_env__find_btf()

Commit-ID: 2e712675ffd1331bb527dfc851b0e98cd684c2f1 Gitweb: https://git.kernel.org/tip/2e712675ffd1331bb527dfc851b0e98cd684c2f1 Author: Bo YU AuthorDate: Mon, 22 Apr 2019 04:01:38 -0400 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:19 -0400 perf bpf: Return

[tip:perf/urgent] tools lib traceevent: Change tag string for error

Commit-ID: 5f05182fab9a29fea6c4ab8113be45adf0c11bf0 Gitweb: https://git.kernel.org/tip/5f05182fab9a29fea6c4ab8113be45adf0c11bf0 Author: Leo Yan AuthorDate: Wed, 24 Apr 2019 09:38:02 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:19 -0400 tools lib

[tip:perf/urgent] perf bench numa: Add define for RUSAGE_THREAD if not present

Commit-ID: bf561d3c13423fc54daa19b5d49dc15fafdb7acc Gitweb: https://git.kernel.org/tip/bf561d3c13423fc54daa19b5d49dc15fafdb7acc Author: Arnaldo Carvalho de Melo AuthorDate: Thu, 25 Apr 2019 18:36:51 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:20 -0400

[tip:perf/urgent] perf annotate: Fix build on 32 bit for BPF annotation

Commit-ID: 01e985e900d3e602e9b1a55372a8e5274012a417 Gitweb: https://git.kernel.org/tip/01e985e900d3e602e9b1a55372a8e5274012a417 Author: Thadeu Lima de Souza Cascardo AuthorDate: Wed, 3 Apr 2019 16:44:52 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Thu, 2 May 2019 16:00:19

Re: [GIT PULL 00/11] perf/urgent fixes

gt; > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-urgent-for-mingo-5.1-20190502 > > for you to fetch changes up to 7e221b811f1472d0c58c7d4e0fe84fcacd22580a: > > perf tools: Remove needle

Re: [PATCH v2 12/17] kunit: tool: add Python wrappers for running KUnit tests

On Thu, May 2, 2019 at 6:45 PM Frank Rowand wrote: > > On 5/2/19 4:45 PM, Brendan Higgins wrote: > > On Thu, May 2, 2019 at 2:16 PM Frank Rowand wrote: > >> > >> On 5/2/19 11:07 AM, Brendan Higgins wrote: > >>> On Thu, May 2, 2019 at 4:02 AM Greg KH wrote: > > On Wed, May 01, 2019 at

[PATCH 2/2] regulator: da9xxx: Switch to SPDX identifier

Convert Dialog Semiconductor DA9xxx regulator drivers to SPDX identifier. Signed-off-by: Axel Lin --- drivers/regulator/da903x.c | 16 ++-- drivers/regulator/da9052-regulator.c | 20 +++- drivers/regulator/da9055-regulator.c | 20 +++-

[PATCH 1/2] regulator: pv880x0: Switch to SPDX identifier

Convert Powerventure Semiconductor PV88060/PV88080/PV88090 regulator drivers to SPDX identifier. Signed-off-by: Axel Lin --- drivers/regulator/pv88060-regulator.c | 18 -- drivers/regulator/pv88060-regulator.h | 11 +-- drivers/regulator/pv88080-regulator.c | 18

linux-next: Fixes tag needs some work in the usb-gadget tree

Hi Felipe, In commit 9f8dc24f7f5d ("usb: gadget: f_fs: don't free buffer prematurely") Fixes tag Fixes: 772a7a724f6 ("usb: gadget: f_fs: Allow scatter-gather buffers") has these problem(s): - SHA1 should be at least 12 digits long Can be fixed by setting core.abbrev to 12 (or more)

[PATCH 3/3] ARM: dts: Add Avenger96 devicetree support based on STM32MP157A

Add devicetree support for Avenger96 board based on STM32MP157A MPU from ST Micro. This board is one of the 96Boards Consumer Edition board from Arrow Electronics and has the following features: SoC: STM32MP157AAC PMIC: STPMIC1A RAM: 1024 Mbyte @ 533MHz Storage: eMMC v4.51: 8 Gbyte

[PATCH 0/3] Add Avenger96 board support

Hello, This patchset adds Avenger96 board support. This board is one of the Consumer Edition boards of the 96Boards family from Arrow Electronics featuring STM32MP157A MPU and has the following features: SoC: STM32MP157AAC PMIC: STPMIC1A RAM: 1024 Mbyte @ 533MHz Storage: eMMC v4.51: 8 Gbyte

[PATCH 1/3] dt-bindings: arm: stm32: Document Avenger96 devicetree binding

Document devicetree binding for Avenger96 board. Signed-off-by: Manivannan Sadhasivam --- Documentation/devicetree/bindings/arm/stm32/stm32.txt | 6 ++ 1 file changed, 6 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/stm32/stm32.txt

[PATCH 2/3] ARM: dts: stm32mp157: Add missing pinctrl definitions

Add missing pinctrl definitions for STM32MP157 MPU. Signed-off-by: Manivannan Sadhasivam --- arch/arm/boot/dts/stm32mp157-pinctrl.dtsi | 62 +++ 1 file changed, 62 insertions(+) diff --git a/arch/arm/boot/dts/stm32mp157-pinctrl.dtsi

Re: [PATCH v14 7/8] power: supply: Initial support for ROHM BD70528 PMIC charger block

Hello Sebastian, On Thu, 2019-05-02 at 21:50 +0200, Sebastian Reichel wrote: > Hi, > > On Thu, May 02, 2019 at 12:17:12PM +0300, Matti Vaittinen wrote: > > ROHM BD70528 PMIC includes battery charger block. Support charger > > staus queries and doing few basic settings like input current limit >

Re: [PATCH v2 2/2] regmap: soundwire: fix Kconfig select/depend issue

On Fri, Apr 19, 2019 at 02:46:49PM -0500, Pierre-Louis Bossart wrote: > config REGMAP_SOUNDWIRE > tristate > - depends on SOUNDWIRE_BUS > + select SOUNDWIRE_BUS This now makes _SOUNDWIRE different to all the other bus types; if this is a good change then surely the same thing

Re: [PATCH v2] ASoC: Intel: avoid Oops if DMA setup fails

On Mon, Apr 29, 2019 at 12:25:17PM -0600, Ross Zwisler wrote: > Currently in sst_dsp_new() if we get an error return from sst_dma_new() > we just print an error message and then still complete the function > successfully. This means that we are trying to run without sst->dma Please don't bury

[PATCH v2 4/9] PCI/LINK: Prefix dmesg logs with PCIe service name

bw_notification.c currently does not have any dmesg logs. As the service continues to expand in functionality, prefix logs anyways. Signed-off-by: Frederick Lawler --- drivers/pci/pcie/bw_notification.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/pci/pcie/bw_notification.c

[PATCH v2 8/9] PCI: hotplug: Remove unnecessary dbg/err/info/warn() printk() wrappers

Remove unnecessary deb/err/info/warn() printk() wrappers. Signed-off-by: Frederick Lawler --- drivers/pci/hotplug/pciehp.h | 9 - drivers/pci/hotplug/pciehp_core.c | 4 ++-- 2 files changed, 2 insertions(+), 11 deletions(-) diff --git a/drivers/pci/hotplug/pciehp.h

[PATCH v2 3/9] PCI/PME: Prefix dmesg logs with PCIe service name

Prefix dmesg logs with PCIe service name. Signed-off-by: Frederick Lawler --- drivers/pci/pcie/pme.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/pci/pcie/pme.c b/drivers/pci/pcie/pme.c index 54d593d10396..d6698423a6d6 100644 --- a/drivers/pci/pcie/pme.c +++

[PATCH v2 7/9] PCI: hotplug: Prefer CONFIG_DYNAMIC_DEBUG/DEBUG for dmesg logs

dbg() and ctrl_dbg() requires pciehp_debug module parameter to be set for debug log purposes. There are niche situations in pciehp_hpc.c where pciehp_debug is used: dbg_ctrl(), and pci_bus_check_dev(). Enabling CONFIG_DYNAMIC_DEBUG/DEBUG is well known for logging debug information. Therefore,

[PATCH v2 5/9] PCI/AER: Prefix dmesg logs with PCIe service name

Prefix dmesg logs with PCIe service name. Signed-off-by: Frederick Lawler --- drivers/pci/pcie/aer.c| 10 +++--- drivers/pci/pcie/aer_inject.c | 6 -- 2 files changed, 11 insertions(+), 5 deletions(-) diff --git a/drivers/pci/pcie/aer.c b/drivers/pci/pcie/aer.c index

[PATCH v2 6/9] PCI: hotplug: Prefix dmesg logs with PCIe service name

Prefix dmesg logs with PCIe service name. Signed-off-by: Frederick Lawler --- drivers/pci/hotplug/pciehp.h | 18 +- drivers/pci/hotplug/pciehp_core.c | 7 +-- drivers/pci/hotplug/pciehp_ctrl.c | 2 ++ drivers/pci/hotplug/pciehp_hpc.c | 4 +++-

[PATCH v2 9/9] PCI: hotplug: Prefix ctrl_*() dmesg logs with pciehp slot name

Remove current uses of "Slot(%s)" and then prefix ctrl_*() dmesg with pciehp slot name to include the slot name for all uses of ctrl_*() wrappers. Signed-off-by: Frederick Lawler --- drivers/pci/hotplug/pciehp.h | 12 --- drivers/pci/hotplug/pciehp_core.c | 9 +++--

[PATCH v2 2/9] PCI/DPC: Prefix dmesg logs with PCIe service name

Prefix dmesg logs with PCIe service name. Signed-off-by: Frederick Lawler --- drivers/pci/pcie/dpc.c | 37 ++--- 1 file changed, 18 insertions(+), 19 deletions(-) diff --git a/drivers/pci/pcie/dpc.c b/drivers/pci/pcie/dpc.c index 7b77754a82de..934391c91c23

[PATCH v2 1/9] PCI/AER: Cleanup dmesg logs

Cleanup dmesg logs. Signed-off-by: Frederick Lawler --- drivers/pci/pcie/aer.c | 11 +-- 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/drivers/pci/pcie/aer.c b/drivers/pci/pcie/aer.c index f8fc2114ad39..82eb45335b6f 100644 --- a/drivers/pci/pcie/aer.c +++

[PATCH v2 0/9] PCI: Use PCIe service name in dmesg logs

In referrence to [1], PCIe services did not have uniform logging via pci_*() printk wrappers. Add dev_fmt() to each service, clean up dmesg logs, use pci_dbg() for hotplug debug messages, and lastly, uniformally add Slot(%s) prefixes to hotplug ctrl_*() wrappers. 1.

[PATCH] signal: Adjust error codes according to restore_user_sigmask()

For all the syscalls that receive a sigmask from the userland, the user sigmask is to be in effect through the syscall execution. At the end of syscall, sigmask of the current process is restored to what it was before the switch over to user sigmask. But, for this to be true in practice, the

Re: [PATCH 2/4] devcoredump: allow to create several coredump files in one device

2019年5月2日(木) 21:47 Johannes Berg : > > On Thu, 2019-05-02 at 17:59 +0900, Akinobu Mita wrote: > > > > static void devcd_del(struct work_struct *wk) > > { > > struct devcd_entry *devcd; > > + int i; > > > > devcd = container_of(wk, struct devcd_entry, del_wk.work); > > > > +

linux-next: manual merge of the modules tree with the vfs tree

Hi all, Today's linux-next merge of the modules tree got a conflict in: include/linux/module.h between commit: 007ec26cdc9f ("vfs: Implement logging through fs_context") from the vfs tree and commit: dadec066d8fa ("module: add stubs for within_module functions") from the modules tree.

Re: [PATCH 0/4] nvme-pci: support device coredump

2019年5月2日(木) 22:03 Keith Busch : > > On Thu, May 02, 2019 at 05:59:17PM +0900, Akinobu Mita wrote: > > This enables to capture snapshot of controller information via device > > coredump machanism, and it helps diagnose and debug issues. > > > > The nvme device coredump is triggered before

Re: Strange issues with epoll since 5.0

On Thu, 02 May 2019, Deepa Dinamani wrote: Reported-by: Omar Kilani Do we actually know if this was the issue Omar was hitting? Thanks, Davidlohr

-Wuninitialized warning in drivers/misc/sgi-xp/xpc_partition.c

Hi all, When building with -Wuninitialized, Clang warns: drivers/misc/sgi-xp/xpc_partition.c:73:14: warning: variable 'buf' is uninitialized when used within its own initialization [-Wuninitialized] void *buf = buf; ~~~ ^~~ 1 warning generated. I am not really sure how

Re: [PATCH v3 1/3] PCI: qcom: Use clk_bulk API for 2.4.0 controllers

On 02-05-19, 08:00, Bjorn Andersson wrote: > On Thu 02 May 04:53 PDT 2019, Vinod Koul wrote: > > On 01-05-19, 17:19, Bjorn Andersson wrote: > [..] > > > diff --git a/drivers/pci/controller/dwc/pcie-qcom.c > > > b/drivers/pci/controller/dwc/pcie-qcom.c > > > index 0ed235d560e3..d740cbe0e56d 100644

RE: [PATCH V2] clk: imx: pllv4: add fractional-N pll support

> From: Stephen Boyd [mailto:sb...@kernel.org] > Sent: Thursday, May 2, 2019 5:01 AM > > The Content-transfer-encoding header is still base64. I guess it can't be > fixed. > How can we know it's base64? As I saw from the 'Headers' in patchwork, it's: "Content-Type: text/plain;

Re: Strange issues with epoll since 5.0

Deepa Dinamani wrote: > Eric, > Can you please help test this? Nope, that was _really_ badly whitespace-damaged. (C'mon, it's not like you're new to this)

Re: [PATCH] iio: dps310: Add pressure sensing capability

Hi Eddie, On Wed, 1 May 2019 at 14:43, Eddie James wrote: > > The DPS310 supports measurement of pressure, so support that in the > driver. Use background measurement like the temperature sensing and > default to lowest precision and lowest measurement rate. Upstream didn't accept my patch as

[PATCH] fix use-after-free in perf_sched__lat

After thread is added to machine->threads[i].dead in __machine__remove_thread, the machine->threads[i].dead is freed when calling free(session) in perf_session__delete(). So it get a Segmentation fault when accessing it in thread__put(). In this patch, we delay the perf_session__delete until all

[PATCH] staging: kpc2000: kpc_spi: Fix build error for {read,write}q

drivers/staging/kpc2000/kpc_spi/spi_driver.c:158:11: error: implicit declaration of function 'readq' [-Werror,-Wimplicit-function-declaration] drivers/staging/kpc2000/kpc_spi/spi_driver.c:167:5: error: implicit declaration of function 'writeq' [-Werror,-Wimplicit-function-declaration] Same as

[RFC][PATCH 1/2 v2] x86: Allow breakpoints to emulate call functions

[ This version of the patch passed all my tests! ] From: Peter Zijlstra In order to allow breakpoints to emulate call functions, they need to push the return address onto the stack. But because the breakpoint exception frame is added to the stack when the breakpoint is hit, there's no room to

Re: [PATCH v2 2/2] prctl.2: Document the new PR_GET_TASK_SIZE option

On Thu, May 02, 2019 at 03:23:12PM -0700, Yury Norov wrote: > чт, 2 мая 2019 г. в 13:52, Joel Savitz : > > > > Add a short explanation of the new PR_GET_TASK_SIZE option for the benefit > > of future generations. > > > > Signed-off-by: Joel Savitz > > --- > > man2/prctl.2 | 9 + > > 1

Re: [PATCH v2 04/17] kunit: test: add kunit_stream a std::stream like logger

On 5/1/19 5:01 PM, Brendan Higgins wrote: A lot of the expectation and assertion infrastructure prints out fairly complicated test failure messages, so add a C++ style log library for for logging test results. Signed-off-by: Brendan Higgins --- include/kunit/kunit-stream.h | 85

Re: [RFC PATCH 3/5] kobject: Fix kernel-doc comment first line

On 5/2/19 6:40 PM, Tobin C. Harding wrote: > On Thu, May 02, 2019 at 10:39:22AM +0200, Johan Hovold wrote: >> On Thu, May 02, 2019 at 06:25:39PM +1000, Tobin C. Harding wrote: > Adding >> Jon to CC >>> >>> On Thu, May 02, 2019 at 09:38:23AM +0200, Johan Hovold wrote: On Thu, May 02, 2019 at

[PATCH v2 RESEND] i2c-piix4: Add Hygon Dhyana SMBus support

The Hygon Dhyana CPU has the SMBus device with PCI device ID 0x790b, which is the same as AMD CZ SMBus device. So add Hygon Dhyana support to the i2c-piix4 driver by using the code path of AMD. Signed-off-by: Pu Wen Reviewed-by: Jean Delvare --- v2 RESEND: - Add 'Reviewed-by' tag from Jean

Re: [RFC PATCH 3/5] kobject: Fix kernel-doc comment first line

On Thu, May 02, 2019 at 10:39:22AM +0200, Johan Hovold wrote: > On Thu, May 02, 2019 at 06:25:39PM +1000, Tobin C. Harding wrote: > Adding > Jon to CC > > > > On Thu, May 02, 2019 at 09:38:23AM +0200, Johan Hovold wrote: > > > On Thu, May 02, 2019 at 12:31:40PM +1000, Tobin C. Harding wrote: > >

Re: [PATCH] kobject: clean up the kobject add documentation a bit more

On Thu, May 02, 2019 at 12:22:24PM +0200, Greg Kroah-Hartman wrote: > Commit 1fd7c3b438a2 ("kobject: Improve doc clarity kobject_init_and_add()") > tried to provide more clarity, but the reference to kobject_del() was > incorrect. Fix that up by removing that line, and hopefully be more explicit

Re: [PATCH] MAINTAINERS: update git tree for sound entries

Hi, On Thu, May 02, 2019 at 11:27:00AM -0600, Ross Zwisler wrote: > Several sound related entries in MAINTAINERS refer to the old git tree > at "git://git.alsa-project.org/alsa-kernel.git". This is no longer used > for development, and Takashi Iwai's kernel.org tree is used instead. > >

next/master boot bisection: next-20190502 on beagle-xm

of the problem may be somewhere else. * * Hope this helps! * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * next/master boot bisection: next-20190502 on beagle-xm Summary: Start: e8b243ea3b19 Add linux-next specific files for 20190502

linux-next: manual merge of the vfs tree with the kbuild tree

Hi all, Today's linux-next merge of the vfs tree got a conflict in: samples/Makefile between commit: a757ed09d672 ("samples: guard sub-directories with CONFIG options") from the kbuild tree and commit: f1b5618e013a ("vfs: Add a sample program for the new mount API") from the vfs tree.

Re: kobject_init_and_add() confusion

On Thu, May 02, 2019 at 10:34:12AM +0200, Petr Mladek wrote: > On Wed 2019-05-01 09:38:03, Tobin C. Harding wrote: > > Hi, > > > > Looks like I've created a bit of confusion trying to fix memleaks in > > calls to kobject_init_and_add(). Its spread over various patches and > > mailing lists so

linux-next: manual merge of the vfs tree with the orangefs tree

Hi all, Today's linux-next merge of the vfs tree got a conflict in: fs/orangefs/super.c between commit: 77becb76042a ("orangefs: implement xattr cache") from the orangefs tree and commit: f276ae0dd6d0 ("orangefs: make use of ->free_inode()") from the vfs tree. I fixed it up (see

linux-next: manual merge of the vfs tree with the fscrypt tree

Hi all, Today's linux-next merge of the vfs tree got a conflict in: fs/ext4/super.c fs/f2fs/super.c between commit: 2c58d548f570 ("fscrypt: cache decrypted symlink target in ->i_link") from the fscrypt tree and commits: 94053139d482 ("ext4: make use of ->free_inode()") d01718a050d0

INFO: task hung in mount_bdev (2)

Hello, syzbot found the following crash on: HEAD commit:9520b532 Merge tag 'for-linus' of git://git.armlinux.org.u.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1104bb90a0 kernel config: https://syzkaller.appspot.com/x/.config?x=a42d110b47dd6b36

Re: [PATCH] kexec_buffer measure

On 2019/05/03 1:28, Casey Schaufler wrote: > On 5/2/2019 8:48 AM, Mimi Zohar wrote: >> [Cc'ing Paul, John, Casey] >> >> On Mon, 2019-04-22 at 20:18 -0400, Mimi Zohar wrote: >>> [Cc'ing LSM mailing list] >>> >>> On Fri, 2019-04-19 at 17:30 -0700, prakhar srivastava wrote: >>> 2) Adding a LSM

Re: [PATCH 1/2] pinctrl: mediatek: Add mtk_eint_pm_ops to common-v2

On Thu, May 2, 2019 at 9:48 PM Yingjoe Chen wrote: > > On Mon, 2019-04-29 at 11:25 +0800, Nicolas Boichat wrote: > > pinctrl variants that include pinctrl-mtk-common-v2.h (and not > > pinctrl-mtk-common.h) also need to use mtk_eint_pm_ops to setup > > wake mask properly, so copy over the pm_ops

Re: [PATCH v4 00/16] NVIDIA Tegra devfreq improvements and Tegra20/30 support

03.05.2019 3:31, Chanwoo Choi пишет: > Hi Dmitry, > > On 19. 5. 2. 오전 8:37, Dmitry Osipenko wrote: >> Changelog: >> >> v4: Addressed all review comments that were made by Chanwoo Choi to v3: >> >> - changed the driver removal order to match the probe exactly >> - added clarifying comment

Re: linux-next: Tree for May 2

On 03/05/2019 00:03, Stephen Rothwell wrote: > Hi Daniel, > > On Thu, 2 May 2019 22:09:49 +0200 Daniel Lezcano > wrote: >> >> Yes, I picked the patch and it was merged it via the tip tree [1] as >> requested by Marc Zyngier [2] and notified [3]. >> >> In any case, this patch should have go

Re: [PATCH v5 3/6] devfreq: rk3399_dmc: Pass ODT and auto power down parameters to TF-A.

Hi Also, this patch was applied to linux-pm.git for for v5.2-rc1. [1] https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge=adfe3b76608ffe547af5a74415f15499b798f32a On 19. 5. 3. 오전 2:58, Gaël PORTAY wrote: > From: Enric Balletbo i Serra > > Trusted

Re: [PATCH v5 1/6] devfreq: rockchip-dfi: Move GRF definitions to a common place.

Hi Gaël, The patch1 was already applied to devfreq.git and then it was applied to linux-pm.git through pull request of devfreq. [1] https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=bleeding-edge=adfe3b76608ffe547af5a74415f15499b798f32a On 19. 5. 3. 오전 2:58, Gaël

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

> On May 2, 2019, at 4:19 PM, James Morris wrote: > >> On Thu, 2 May 2019, Matthew Garrett wrote: >> >>> On Thu, May 2, 2019 at 2:07 PM James Morris wrote: >>> One possible direction is to (as previously mentioned) assign IDs to each >>> callsite and be able to check this ID against a simple

Re: [PATCH v4 00/16] NVIDIA Tegra devfreq improvements and Tegra20/30 support

Hi Dmitry, On 19. 5. 2. 오전 8:37, Dmitry Osipenko wrote: > Changelog: > > v4: Addressed all review comments that were made by Chanwoo Choi to v3: > > - changed the driver removal order to match the probe exactly > - added clarifying comment for 1/8 ratio to the Tegra20 driver > >

[PATCH 03/11] perf annotate: Fix build on 32 bit for BPF annotation

From: Thadeu Lima de Souza Cascardo Commit 6987561c9e86 ("perf annotate: Enable annotation of BPF programs") adds support for BPF programs annotations but the new code does not build on 32-bit. Signed-off-by: Thadeu Lima de Souza Cascardo Acked-by: Song Liu Fixes: 6987561c9e86 ("perf

[PATCH 08/11] perf cs-etm: Always allocate memory for cs_etm_queue::prev_packet

From: Leo Yan Robert Walker reported a segmentation fault is observed when process CoreSight trace data; this issue can be easily reproduced by the command 'perf report --itrace=i1000i' for decoding tracing data. If neither the 'b' flag (synthesize branches events) nor 'l' flag (synthesize last

[PATCH 11/11] perf tools: Remove needless asm/unistd.h include fixing build in some places

From: Arnaldo Carvalho de Melo We were including sys/syscall.h and asm/unistd.h, since sys/syscall.h includes asm/unistd.h, sometimes this leads to the redefinition of defines, breaking the build. Noticed on ARC with uCLibc. Cc: Adrian Hunter Cc: Arnaldo Carvalho de Melo Cc: Arnd Bergmann

[PATCH 09/11] tools build: Add -ldl to the disassembler-four-args feature test

From: Arnaldo Carvalho de Melo Thomas Backlund reported that the perf build was failing on the Mageia 7 distro, that is because it uses: cat /tmp/build/perf/feature/test-disassembler-four-args.make.output /usr/bin/ld: /usr/lib64/libbfd.a(plugin.o): in function `try_load_plugin':

[PATCH 07/11] perf cs-etm: Don't check cs_etm_queue::prev_packet validity

From: Leo Yan Since cs_etm_queue::prev_packet is allocated for all cases, it will never be NULL pointer; now validity checking prev_packet is pointless, remove all of them. Signed-off-by: Leo Yan Tested-by: Robert Walker Cc: Alexander Shishkin Cc: Jiri Olsa Cc: Mathieu Poirier Cc: Mike

[PATCH 06/11] perf report: Report OOM in status line in the GTK UI

From: Thomas Richter An -ENOMEM error is not reported in the GTK GUI. Instead this error message pops up on the screen: [root@m35lp76 perf]# ./perf report -i perf.data.error68-1 Processing events... [974K/3M] Error:failed to process sample 0xf4198 [0x8]: failed to

[PATCH 02/11] tools uapi x86: Sync vmx.h with the kernel

From: Arnaldo Carvalho de Melo To pick up the changes from: 2b27924bb1d4 ("KVM: nVMX: always use early vmcs check when EPT is disabled") That causes this object in the tools/perf build process to be rebuilt: CC /tmp/build/perf/arch/x86/util/kvm-stat.o But it isn't using VMX_ABORT_

[PATCH 04/11] tools lib traceevent: Change tag string for error

From: Leo Yan The traceevent lib is used by the perf tool, and when executing perf test -v 6 it outputs error log on the ARM64 platform: running test 33 '*:*'trace-cmd: No such file or directory [...] trace-cmd: Invalid argument The trace event parsing code originally came from

[GIT PULL 00/11] perf/urgent fixes

-20190502 for you to fetch changes up to 7e221b811f1472d0c58c7d4e0fe84fcacd22580a: perf tools: Remove needless asm/unistd.h include fixing build in some places (2019-05-02 16:00:20 -0400) perf/urgent fixes: tools UAPI: Arnaldo

linux-next: build warning after merge of the btrfs-kdave tree

Hi David, After merging the btrfs-kdave tree, today's linux-next build (x86_64 allmodconfig) produced this warning: fs/btrfs/props.c: In function 'inherit_props': fs/btrfs/props.c:389:4: warning: 'num_bytes' may be used uninitialized in this function [-Wmaybe-uninitialized]

Re: [RFC PATCH v2 11/17] sched: Basic tracking of matching tasks

On 5/1/19 4:27 PM, Tim Chen wrote: > On 4/28/19 11:15 PM, Aaron Lu wrote: >> On Tue, Apr 23, 2019 at 04:18:16PM +, Vineeth Remanan Pillai wrote: >>> +/* >>> + * Find left-most (aka, highest priority) task matching @cookie. >>> + */ >>> +struct task_struct *sched_core_find(struct rq *rq,

Re: [PATCH 4.14 00/49] 4.14.116-stable review

stable-rc/linux-4.14.y boot: 122 boots: 1 failed, 121 passed (v4.14.115-50-ga4aa5bff0752) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.115-50-ga4aa5bff0752/ Full Build Summary:

Re: Strange issues with epoll since 5.0

Eric, Can you please help test this? If this solves your problem, I can post the fix. Thanks, - Deepa -8<--- Subject: [PATCH] signal: Adjust error codes according to restore_user_sigmask() For all the syscalls that receive a sigmask from the userland, the user sigmask is to be in

Re: [PATCH] perf vendor events arm64: Map Brahma-B53 CPUID to cortex-a53 events

Em Thu, May 02, 2019 at 02:28:02PM -0700, Florian Fainelli escreveu: > On 4/8/19 9:26 AM, Will Deacon wrote: > > On Fri, Apr 05, 2019 at 09:50:47AM -0700, Florian Fainelli wrote: > >> Broadcom's Brahma-B53 CPUs support the same type of events that the > >> Cortex-A53 supports, recognize its CPUID

Re: [RFC][PATCH 1/2] x86: Allow breakpoints to emulate call functions

On Thu, 2 May 2019 19:31:29 -0400 Steven Rostedt wrote: > Digging a little further, I pinpointed it out to being kretprobes. The > problem I believe is the use of kernel_stack_pointer() which does some > magic on x86_32. kretprobes uses this to hijack the return address of > the function (much

[PATCH v2] perf vendor events arm64: Add Cortex-A57 and Cortex-A72 events

The Cortex-A57 and Cortex-A72 both support all ARMv8 recommended events up to the RC_ST_SPEC (0x91) event with the exception of: - L1D_CACHE_REFILL_INNER (0x44) - L1D_CACHE_REFILL_OUTER (0x45) - L1D_TLB_RD (0x4E) - L1D_TLB_WR (0x4F) - L2D_TLB_REFILL_RD (0x5C) - L2D_TLB_REFILL_WR (0x5D) -

Re: [RFC][PATCH 1/2] x86: Allow breakpoints to emulate call functions

On Thu, 2 May 2019 18:52:25 -0400 Steven Rostedt wrote: > On Thu, 2 May 2019 22:21:46 +0200 > Peter Zijlstra wrote: > > > On Thu, May 02, 2019 at 11:43:37AM -0700, Linus Torvalds wrote: > > > What would it look like with the "int3-from-kernel is special" > > > modification? > > > >

Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir

On Thu, May 02 2019, Andreas Gruenbacher wrote: > On Thu, 2 May 2019 at 05:57, NeilBrown wrote: >> On Wed, May 01 2019, Amir Goldstein wrote: >> > On Wed, May 1, 2019 at 10:03 PM NeilBrown wrote: >> >> On Tue, Dec 06 2016, J. Bruce Fields wrote: >> >> > On Tue, Dec 06, 2016 at 02:18:31PM +0100,

linux-next: build failure after merge of the clk tree

commit 7c36ec8a90a8 ("clk: Remove CLK_IS_BASIC clk flag") I have used the clk tree from next-20190502 for today. (The above commit does not revert cleanly.) -- Cheers, Stephen Rothwell pgpxaBeDvQuVg.pgp Description: OpenPGP digital signature

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

On Thu, 2 May 2019, Matthew Garrett wrote: > On Thu, May 2, 2019 at 2:07 PM James Morris wrote: > > One possible direction is to (as previously mentioned) assign IDs to each > > callsite and be able to check this ID against a simple policy array > > (allow/deny). The default policy choices

Re: [RFC] Disable lockref on arm64

On Thu, May 02, 2019 at 09:12:18AM -0700, Linus Torvalds wrote: > On Thu, May 2, 2019 at 1:27 AM Jan Glauber wrote: > > > > I'll see how x86 runs the same testcase, I thought that playing > > cacheline ping-pong is not the optimal use case for any CPU. > > Oh, ping-pong is always bad. > > But

Re: [PATCH v6 00/12] mm: Sub-section memory hotplug support

On Thu, May 2, 2019 at 3:46 PM Pavel Tatashin wrote: > > Hi Dan, > > How do you test these patches? Do you have any instructions? Yes, I briefly mentioned this in the cover letter, but here is the test I am using: > > I see for example that check_hotplug_memory_range() still enforces >

Re: [PATCH] OVL: add honoracl=off mount option.

On Thu, May 02 2019, Amir Goldstein wrote: > On Thu, May 2, 2019 at 12:35 AM NeilBrown wrote: >> >> >> If the upper and lower layers use incompatible ACL formats, it is not >> possible to copy the ACL xttr from one to the other, so overlayfs >> cannot work with them. >> This happens particularly

Re: [PATCH 4.9 00/32] 4.9.173-stable review

stable-rc/linux-4.9.y boot: 104 boots: 2 failed, 99 passed with 3 offline (v4.9.172-33-gd35bcd092304) Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.172-33-gd35bcd092304/ Full Build Summary:

Re: [PATCH] overlayfs: ignore empty NFSv4 ACLs in ext4 upperdir

On Thu, May 02 2019, Miklos Szeredi wrote: > On Thu, May 2, 2019 at 10:05 AM Andreas Gruenbacher > wrote: >> >> On Thu, 2 May 2019 at 05:57, NeilBrown wrote: >> > On Wed, May 01 2019, Amir Goldstein wrote: >> > > On Wed, May 1, 2019 at 10:03 PM NeilBrown wrote: >> > >> On Tue, Dec 06 2016, J.

Re: [PATCH v4 0/1] Add support for IPMB driver

On Thu, May 02, 2019 at 09:14:46PM +, Vadim Pasternak wrote: > [...] > > > > > > >>Better, if you can avoid cast. > > > >>Would compiler warn if you use for example rol16(client->addr, 1) & > > GENMASK(7, 0); or something like it? > > > I thought it wouldn't be too much of an issue to use

[PATCH v2 1/2] platform/chrome: wilco_ec: Remove 256 byte transfers

The 0xF6 command, intended to send and receive 256 byte payloads to and from the EC, is not needed. The 0xF5 command for 32 byte payloads is sufficient. This patch removes support for the 0xF6 command and 256 byte payloads. Signed-off-by: Nick Crews ---

[PATCH 4/5] ARM: dts: rockchip: Add unwedge pinctrl entries for dw_hdmi on rk3288

This adds the "unwedge" pinctrl entries introduced by a recent dw_hdmi change that can unwedge the dw_hdmi i2c bus in some cases. It's expected that any boards using this would add: pinctrl-names = "default", "unwedge"; pinctrl-0 = <_ddc>; pinctrl-1 = <_ddc_unwedge>; Note that this isn't

[PATCH v2 2/2] platform/chrome: wilco_ec: Add telemetry char device interface

The Wilco Embedded Controller is able to send telemetry data which is useful for enterprise applications. A daemon running on the OS sends a command to the EC via a write() to a char device, and can read the response with a read(). The write() request is verified by the driver to ensure that it is

[PATCH 5/5] ARM: dts: rockchip: Add HDMI i2c unwedging for rk3288-veyron

Veyron uses the builtin i2c controller that's part of dw-hdmi. Hook up the unwedging feature. Signed-off-by: Douglas Anderson --- arch/arm/boot/dts/rk3288-veyron.dtsi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/rk3288-veyron.dtsi

[PATCH 3/5] ARM: dts: rockchip: Switch to builtin HDMI DDC bus on rk3288-veyron

Downstream Chrome OS kernels use the builtin DDC bus from dw_hdmi on veyron. This is the only way to get them to negotiate HDCP. Although HDCP isn't currently all supported upstream, it still seems like it makes sense to use dw_hdmi's builtin I2C. Maybe eventually we can get HDCP negotiation

Re: [RFC][PATCH 1/2] x86: Allow breakpoints to emulate call functions

On Thu, 2 May 2019 22:21:46 +0200 Peter Zijlstra wrote: > On Thu, May 02, 2019 at 11:43:37AM -0700, Linus Torvalds wrote: > > What would it look like with the "int3-from-kernel is special" > > modification? > > Something like so; it boots; but I could've made some horrible mistake > (again).

  1   2   3   4   5   6   7   8   9   >