Re: [PATCH 3/3] xen blkback: add fault injection facility

On 04/20/18 13:28, Juergen Gross wrote: On 20/04/18 12:47, Stanislav Kinsburskii wrote: This patch adds wrapper helpers around generic Xen fault inject facility. The major reason is to keep all the module fault injection directories in a dedicated subdirectory instead of Xen fault inject root.

[PATCH v3 2/6] drm/panel: Add support for the EDT ETM0700G0EDH6

From: Jan Tuerk The Emerging Display Technology ETM0700G0EDH6 is the uses the same panel as the ETM0700G0BDH6. It differs in the hardware design for the backlight and the touchscreen i2c interface. As the new display type has different requirements for drive-strengths on

RE: [PATCH V7 6/8] perf/x86/intel/uncore: Support IIO free running counters on SKX

> > From: Kan Liang > > As of Skylake Server, there are a number of free-running counters in > each IIO Box that collect counts for per box IO clocks and per Port > Input/Output x BW/Utilization. > Add a new PMU for these free-running counters. Don't let them share with >

Re: [PATCH 4/8] clk: mediatek: mt2701-mm: switch to mfd device

On 04/20/2018 03:00 PM, Matthias Brugger wrote: > Hi Stephen, > > On 11/15/2017 01:17 AM, Stephen Boyd wrote: >> On 11/14, Matthias Brugger wrote: >>> As the new mfd device is in place, switch probing >>> for the MMSYS to support invocation from the mfd device. >>> >>> Signed-off-by: Matthias

Re: [RFC PATCH 2/2] HISI LPC: Add PNP device support

On Fri, Apr 20, 2018 at 06:07:26PM +0800, John Garry wrote: > Currently the driver creates an per-ACPI device mfd_cell > for child devices. This does not suit devices which are > PNP-compatible, as we expect PNP-compatible devices to > derive PNP devices. > > To add PNP device support, we

Re: [PATCH bpf-next 1/5] samples/bpf: Fix typo in comment

On Fri, Apr 20, 2018 at 02:10:04PM +0200, Jesper Dangaard Brouer wrote: > > On Thu, 19 Apr 2018 09:34:02 +0800 Leo Yan wrote: > > > Fix typo by replacing 'iif' with 'if'. > > > > Signed-off-by: Leo Yan > > --- > > samples/bpf/bpf_load.c | 2 +- > > 1

[PATCH 4/7] perf,x86/msr: Fix possible Spectre-v1 for msr

> arch/x86/events/msr.c:178 msr_event_init() warn: potential spectre issue > 'msr' (local cap) Userspace controls @attr, sanitize cfg (attr->config) before using it to index an array. Reported-by: Dan Carpenter Signed-off-by: Peter Zijlstra ---

[PATCH 6/7] sched: Fix possible Spectre-v1 for sched_prio_to_weight[]

> kernel/sched/core.c:6921 cpu_weight_nice_write_s64() warn: potential spectre > issue 'sched_prio_to_weight' Userspace controls @nice, so sanitize the value before using it to index an array. Reported-by: Dan Carpenter Signed-off-by: Peter Zijlstra

[PATCH 5/7] perf,x86/cstate: Fix possible Spectre-v1 for pkg_msr

> arch/x86/events/intel/cstate.c:307 cstate_pmu_event_init() warn: potential > spectre issue 'pkg_msr' (local cap) Userspace controls @attr, sanitize cfg (attr->config) before using it to index an array. Reported-by: Dan Carpenter Signed-off-by: Peter Zijlstra

[PATCH 4/8] sh_eth: Change platform check to CONFIG_ARCH_RENESAS

Since commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS") is CONFIG_ARCH_RENESAS a more appropriate platform check than the legacy CONFIG_ARCH_SHMOBILE, hence use the former. Renesas SuperH SH-Mobile SoCs are still covered by the CONFIG_CPU_SH4 check. This will allow to drop

[PATCH 2/8] dmaengine: shdmac: Change platform check to CONFIG_ARCH_RENESAS

Since commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS") is CONFIG_ARCH_RENESAS a more appropriate platform check than the legacy CONFIG_ARCH_SHMOBILE, hence use the former. Renesas SuperH SH-Mobile SoCs are still covered by the CONFIG_CPU_SH4 check, just like before support for

[PATCH 5/8] staging: emxx_udc: Change platform dependency to ARCH_RENESAS

Emma Mobile is a Renesas ARM SoC. Since commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS") is ARCH_RENESAS a more appropriate platform dependency than the legacy ARCH_SHMOBILE, hence use the former. This will allow to drop ARCH_SHMOBILE on ARM in the near future. Signed-off-by:

[PATCH v2 7/9] nds32: Fix the unknown type u8 issue.

It broke the 'allmodconfig' build. We need to include to make sure the type is defined before using it. Signed-off-by: Greentime Hu Acked-by: Arnd Bergmann --- arch/nds32/include/asm/io.h | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH v2 4/9] nds32: Fix drivers/gpu/drm/udl/udl_fb.c building error by defining PAGE_SHARED

It broke the 'allmodconfig' build. drivers/gpu/drm/udl/udl_fb.c: In function 'udl_fb_mmap': drivers/gpu/drm/udl/udl_fb.c:183:52: error: 'PAGE_SHARED' undeclared (first use in this function) if (remap_pfn_range(vma, start, page, PAGE_SIZE, PAGE_SHARED))

[PATCH v2 5/9] nds32: Fix xfs_buf built failed by export invalidate_kernel_vmap_range and flush_kernel_vmap_range

It broke the 'allmodconfig' build. fs/xfs/xfs_buf.c: In function 'xfs_buf_bio_end_io': fs/xfs/xfs_buf.c:1242:3: error: implicit declaration of function 'invalidate_kernel_vmap_range' [-Werror=implicit-function-declaration] invalidate_kernel_vmap_range(bp->b_addr, xfs_buf_vmap_len(bp));

Re: [PATCH 0/8] arm: renesas: Change platform dependency to ARCH_RENESAS

On Fri, Apr 20, 2018 at 3:28 PM, Geert Uytterhoeven wrote: > Hi all, > > Commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS") > started the conversion from ARCH_SHMOBILE to ARCH_RENESAS for Renesas > ARM SoCs. This patch series completes the

Re: [PATCH] lib: micro-optimization for __bitmap_complement()

Ping? On Wed, Apr 11, 2018 at 05:59:14PM +0300, Yury Norov wrote: > Use BITS_TO_LONGS() macro to avoid calculation of reminder > (bits % BITS_PER_LONG) On ARM64 it saves 5 instruction for function - > 16 before and 11 after. > > Signed-off-by: Yury Norov > --- >

Re: [PATCH v2 03/10] videobuf2-core: Add helper to get buffer private data from media request

On 04/19/18 17:41, Paul Kocialkowski wrote: > When calling media operation driver callbacks related to media requests, > only a pointer to the request itself is provided, which is insufficient > to retrieve the driver's context. Since the driver context is usually > set as vb2 queue private data

Re: [PATCH v2 02/10] media-request: Add a request complete operation to allow m2m scheduling

On 04/19/18 17:41, Paul Kocialkowski wrote: > When using the request API in the context of a m2m driver, the > operations that come with a m2m run scheduling call in their > (m2m-specific) ioctl handler are delayed until the request is queued > (for instance, this includes queuing buffers and

[no subject]

Hi Linux https://bit.ly/2K1tXfw

Re: [PATCH net-next 2/2] netns: isolate seqnums to use per-netns locks

On Wed, Apr 18, 2018 at 11:52:47PM +0200, Christian Brauner wrote: > On Wed, Apr 18, 2018 at 11:55:52AM -0500, Eric W. Biederman wrote: > > Christian Brauner writes: > > > > > Now that it's possible to have a different set of uevents in different > > > network

Re: [PATCH] drm: udl: Destroy framebuffer only if it was initialized

On Fri, Apr 20, 2018 at 01:50:01PM +0200, Emil Lundmark wrote: > This fixes a NULL pointer dereference that can happen if the UDL > driver is unloaded before the framebuffer is initialized. This can > happen e.g. if the USB device is unplugged right after it was plugged > in. > JFYI, in future,

Re: [PATCH v2 05/10] media: v4l: Add definitions for MPEG2 frame format and header metadata

On 04/19/18 17:45, Paul Kocialkowski wrote: > Stateless video decoding engines require both the MPEG slices and > associated metadata from the video stream in order to decode frames. > > This introduces definitions for a new pixel format, describing buffers > with MPEG2 slice data, as well as a

Re: [RFC PATCH 1/2] ACPI / PNP: Don't add "enumeration_by_parent" devices

On 20/04/2018 14:52, Mika Westerberg wrote: On Fri, Apr 20, 2018 at 02:24:18PM +0100, John Garry wrote: Hi Mika, On 20/04/2018 14:07, Mika Westerberg wrote: On Fri, Apr 20, 2018 at 06:07:25PM +0800, John Garry wrote: + } else { + device->driver_data = dev; I think this

Re: s390 perf events JSONs query

e JSONs contain many common (identical actually) events > >>between different chips for this arch. > >> > >>Support was added for factoring out common arch events in > >>https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/tools/perf/pmu-

Re: [PATCH V2] USB: Increment wakeup count on remote wakeup.

On Thu, 19 Apr 2018, Ravi Chandra Sadineni wrote: > On chromebooks we depend on wakeup count to identify the wakeup source. > But currently USB devices do not increment the wakeup count when they > trigger the remote wake. This patch addresses the same. > > Resume condition is reported

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On Fri, 20 Apr 2018 16:01:57 +0200 Petr Mladek wrote: > On Fri 2018-04-20 08:04:28, Steven Rostedt wrote: > > On Fri, 20 Apr 2018 11:12:24 +0200 > > Petr Mladek wrote: > > > > > Yes, my number was arbitrary. The important thing is that it was long > > >

Re: [RFC] perf/core: what is exclude_idle supposed to do

On Fri, 20 Apr 2018, Peter Zijlstra wrote: > On Wed, Apr 18, 2018 at 11:10:20AM -0400, Vince Weaver wrote: > > On Tue, 17 Apr 2018, Jiri Olsa wrote: > > > > > On Mon, Apr 16, 2018 at 10:04:53PM +, Stephane Eranian wrote: > > > > Hi, > > > > > > > > I am trying to understand what the

Re: [patch v2] mm, oom: fix concurrent munlock and oom reaper unmap

On Fri 20-04-18 10:23:49, Michal Hocko wrote: > On Thu 19-04-18 12:34:53, David Rientjes wrote: [...] > > I understand the concern, but it's the difference between the victim > > getting stuck in exit_mmap() and actually taking a long time to free its > > memory in exit_mmap(). I don't have

Re: [RESEND][PATCH 2/4] NFC: st21nfca: Fix memory OOB and leak issues in connectivity events handler

On Wed, 2018-04-18 at 15:35 +0530, Amit Pundir wrote: > if (skb->data[transaction->aid_len + 2] != > - NFC_EVT_TRANSACTION_PARAMS_TAG) > + NFC_EVT_TRANSACTION_PARAMS_TAG || > + skb->len < transaction->aid_len + transaction- >

Re: [RESEND][PATCH 4/4] NFC: fdp: Fix possible buffer overflow in WCS4000 NFC driver

On Wed, 2018-04-18 at 15:35 +0530, Amit Pundir wrote: > + if (phy->next_read_size > > FDP_NCI_I2C_MAX_PAYLOAD) { > + dev_dbg(>dev, "%s: corrupted > packet\n", > + __func__); If Android people would follow the

Re: [Xen-devel] [PATCH] xen-netfront: Fix hang on device removal

On Thu, Apr 19, 2018 at 4:09 PM, Simon Gaiser wrote: > Jason Andryuk: >> On Thu, Apr 19, 2018 at 2:10 PM, Simon Gaiser >> wrote: >>> Jason Andryuk: A toolstack may delete the vif frontend and backend xenstore entries while

Re: [PATCH 4/8] dma-buf: add peer2peer flag

On Fri, Apr 20, 2018 at 12:44:01PM +0200, Christian König wrote: > > > What we need is an sg_alloc_table_from_resources(dev, resources, > > > num_resources) which does the handling common to all drivers. > > A structure that contains > > > > {page,offset,len} + {dma_addr+dma_len} > > > > is not

Re: [RFC PATCH 2/2] HISI LPC: Add PNP device support

On Fri, 2018-04-20 at 18:07 +0800, John Garry wrote: > Currently the driver creates an per-ACPI device mfd_cell > for child devices. This does not suit devices which are > PNP-compatible, as we expect PNP-compatible devices to > derive PNP devices. > > To add PNP device support, we continue to

Re: [PATCH v3] selftests/livepatch: introduce tests

Hi Joe, I know I am late to the party, yet have some questions about the code. On Thu 12-04-18 10:54:31, Joe Lawrence wrote: > Add a few livepatch modules and simple target modules that the included > regression suite can run tests against. > > Signed-off-by: Joe Lawrence

Re: [PATCH 1/1] arm: dts: rockchip: default serial for Tinker Board

Am Dienstag, 17. April 2018, 22:56:23 CEST schrieb Heinrich Schuchardt: > The Asus Tinker Board uses serial 2 with 115,200 baud by default for > communication in U-Boot. The same value is also chosen for other RK3288 > boards. > > So let us set the same value in the Tinker Board device tree. > >

[PATCH v3 4/6] ARM: dts: imx: Add an cpu0 label for imx6dl devices.

From: Jan Tuerk Adding the label cpu0 allows the adjustment of cpu-parameters by reference in overlaying dtsi files in the same way as it is possible for imx6q devices. Signed-off-by: Jan Tuerk --- arch/arm/boot/dts/imx6dl.dtsi | 2 +- 1 file

[PATCH v3 3/6] dt-bindings: display: Document the EDT et* displays in one file.

From: Jan Tuerk Document the Emerging Display Technology Corp. (EDT) using the simple-panel binding in one single file. Signed-off-by: Jan Tuerk --- .../bindings/display/panel/edt,et-series.txt | 39 ++

[PATCH v3 6/6] ARM: imx_v6_v7_defconfig: Enable DA0963 PMIC support.

From: Jan Tuerk All recent emtrion modules based on i.mx6 make use of the DA0963. Therefore enable it with the following defaults: - CONFIG_MFD_DA9063=y - CONFIG_REGULATOR_DA9063=y - CONFIG_DA9063_WATCHDOG=m MFD and REGULATOR are built-in to have it

[PATCH v3 5/6] ARM: dts: Add support for emtrion emCON-MX6 series

From: Jan Tuerk This patch adds support for the emtrion GmbH emCON-MX6 modules. They are available with imx.6 Solo, Dual-Lite, Dual and Quad equipped with Memory from 512MB to 2GB (configured by U-Boot). Our default developer-Kit ships with the Avari baseboard and the EDT

[PATCH v3 0/6] Add basic support for emtrion emCON-MX6 modules

From: Jan Tuerk Changes for v3: [PATCH v3 1/6] drm/panel: Add support for the EDT ETM0700G0BDH6 - moved Documentation into seperate commit ([PATCH v3/6]) [PATCH v3 2/6] drm/panel: Add support for the EDT ETM0700G0EDH6 - new Patch, adding additionally

Re: [PATCH v3 0/7] Add tda998x (HDMI) support to atmel-hlcdc

On 2018-04-20 13:38, jacopo mondi wrote: > Hi Peter, > > On Fri, Apr 20, 2018 at 01:05:21PM +0200, Peter Rosin wrote: >> On 2018-04-20 12:18, Laurent Pinchart wrote: >>> Hello, >>> >>> On Friday, 20 April 2018 11:52:35 EEST jacopo mondi wrote: Hi Peter, I've been a bit a pain in the

[PATCH v3 1/6] drm/panel: Add support for the EDT ETM0700G0BDH6

From: Jan Tuerk The Emerging Display Technology ETM0700G0BDH6 is exactly the same display as the ETM0700G0DH6, exept the pixelclock polarity. Therefore re-use the ETM0700G0DH6 modes. It is used by default on emtrion Avari based development kits. Signed-off-by: Jan Tuerk

Re: [RFC PATCH 1/2] ACPI / PNP: Don't add "enumeration_by_parent" devices

On Fri, Apr 20, 2018 at 06:07:25PM +0800, John Garry wrote: > + } else { > + device->driver_data = dev; I think this deserves a comment explaining why we (ab)use driver_data like this.

Re: [PATCH net-next v4 0/3] kernel: add support to collect hardware logs in crash recovery kernel

On Thursday, April 04/19/18, 2018 at 20:23:37 +0530, Eric W. Biederman wrote: > Rahul Lakkireddy writes: > > > On Thursday, April 04/19/18, 2018 at 07:10:30 +0530, Dave Young wrote: > >> On 04/18/18 at 06:01pm, Rahul Lakkireddy wrote: > >> > On Wednesday, April

[PATCH][next] cifs: ensure full_path is free'd on error exit path

From: Colin Ian King Currently the check on the mode flags that returns -EPERM is leaking full_path on the error exit return. Fix this by kfree'ing it before the return. Detected by CoverityScan, CID#1468029 ("Resource Leak") Fixes: 49162bfde140 ("cifs: do not allow

[PATCH 1/7] perf: Fix possible Spectre-v1 for aux_pages

> kernel/events/ring_buffer.c:871 perf_mmap_to_page() warn: potential spectre > issue 'rb->aux_pages' Userspace controls @pgoff through the fault address. Sanitize the array index before doing the array dereference. Reported-by: Dan Carpenter Signed-off-by: Peter

[PATCH 7/7] sched,autogroup: Fix possible Spectre-v1 for sched_prio_to_weight

> kernel/sched/autogroup.c:230 proc_sched_autogroup_set_nice() warn: potential > spectre issue 'sched_prio_to_weight' Userspace controls @nice, sanitize the array index. Reported-by: Dan Carpenter Signed-off-by: Peter Zijlstra ---

[PATCH] cifs: dir: fix memory leak in cifs_mknod

Free allocated memory for full_path and xid before return. Addresses-Coverity-ID: 1468029 ("Resource leak") Fixes: 49162bfde140 ("cifs: do not allow creating sockets except with SMB1 posix exensions") Signed-off-by: Gustavo A. R. Silva --- fs/cifs/dir.c | 5 - 1 file

[PATCH 2/7] perf,x86: Fix possible Spectre-v1 for hw_perf_event

> arch/x86/events/core.c:319 set_ext_hw_attr() warn: potential spectre issue > 'hw_cache_event_ids[cache_type]' (local cap) > arch/x86/events/core.c:319 set_ext_hw_attr() warn: potential spectre issue > 'hw_cache_event_ids' (local cap) > arch/x86/events/core.c:328 set_ext_hw_attr() warn:

Re: s390 perf events JSONs query

gt; Support was added for factoring out common arch events in > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/tools/perf/pmu-events?h=next-20180420=e9d32c1bf0cd7a98358ec4aa1625bf2b3459b9ac > > ARM64 chips use this feature. I am not familiar with the s390 arch, but do

Re: [RFC PATCH 1/2] ACPI / PNP: Don't add "enumeration_by_parent" devices

Hi Mika, On 20/04/2018 14:07, Mika Westerberg wrote: On Fri, Apr 20, 2018 at 06:07:25PM +0800, John Garry wrote: + } else { + device->driver_data = dev; I think this deserves a comment explaining why we (ab)use driver_data like this. Sure, could add. I didn't see any

[GIT PULL] Please pull powerpc/linux.git powerpc-4.17-3 tag

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Linus, Please pull some more powerpc fixes for 4.17: The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) are available in the git repository at:

Re: [PATCH v3 7/7] drm/i2c: tda998x: register as a drm bridge

On 2018-04-20 12:24, Russell King - ARM Linux wrote: > On Fri, Apr 20, 2018 at 01:06:49PM +0300, Laurent Pinchart wrote: >> Hi Peter, >> >> Thank you for the patch. >> >> On Thursday, 19 April 2018 19:27:51 EEST Peter Rosin wrote: >>> This makes this driver work with all(?) drivers that are not

Re: [RFC PATCH 2/2] HISI LPC: Add PNP device support

On Fri, 2018-04-20 at 14:09 +0100, John Garry wrote: > On 20/04/2018 13:50, Andy Shevchenko wrote: > > On Fri, 2018-04-20 at 18:07 +0800, John Garry wrote: > > > + if (res->flags | IORESOURCE_IO) > > > > What does this mean? > > Here we check the resource flag for each resource

[PATCH 6/8] ASoC: sh: Update menu title and platform dependency

Change the menu title to refer to "Renesas SoCs" instead of "SuperH", as both SuperH and ARM SoCs are supported. Since commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS") is ARCH_RENESAS a more appropriate platform dependency for Renesas ARM SoCs than the legacy ARCH_SHMOBILE, hence

[PATCH v2 1/9] nds32: lib: To use generic lib instead of libgcc to prevent the symbol undefined issue.

We can use the generic lib to fix these error because the symbol of libgcc in toolchain is not exported. ERROR: "__ucmpdi2" [fs/xfs/xfs.ko] undefined! ERROR: "__ashrdi3" [fs/xfs/xfs.ko] undefined! ERROR: "__lshrdi3" [fs/xfs/xfs.ko] undefined! ERROR: "__ashldi3" [fs/ntfs/ntfs.ko] undefined! ...

[PATCH v2 2/9] nds32: Fix building error when CONFIG_FREEZE is enabled.

To include kernel/Kconfig.freezer to make sure the dependency between CONFIG_CGROUP_FREEZER and CONFIG_FREEZER It will cause building error when I make allmodconfig. kernel/cgroup/freezer.c: In function 'freezer_css_online': kernel/cgroup/freezer.c:116:15: error: 'system_freezing_cnt' undeclared

Re: [PATCH net-next v4 0/3] kernel: add support to collect hardware logs in crash recovery kernel

Rahul Lakkireddy writes: > On Thursday, April 04/19/18, 2018 at 20:23:37 +0530, Eric W. Biederman wrote: >> Rahul Lakkireddy writes: >> >> > On Thursday, April 04/19/18, 2018 at 07:10:30 +0530, Dave Young wrote: >> >> On 04/18/18 at

Re: [RFC PATCH 2/2] HISI LPC: Add PNP device support

Hi Mika, /* @@ -469,8 +472,11 @@ static int hisi_lpc_acpi_probe(struct device *hostdev) struct acpi_device *child; int size, ret, count = 0, cell_num = 0; - list_for_each_entry(child, >children, node) + list_for_each_entry(child, >children, node) { +

Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On Fri, Apr 20, 2018 at 03:08:52PM +0200, Michal Hocko wrote: > > In order to detect these bugs reliably I submit this patch that changes > > kvmalloc to always use vmalloc if CONFIG_DEBUG_VM is turned on. > > No way. This is just wrong! First of all, you will explode most likely > on many

Re: [PATCH v6 24/30] drm/rockchip: Disable PSR on input events

Hi Enric, On 05.04.2018 11:49, Enric Balletbo i Serra wrote: > From: "Kristian H. Kristensen" > > To improve PSR exit latency, we speculatively start exiting when we > receive input events. Occasionally, this may lead to false positives, > but most of the time we get a

Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM

On Fri 20-04-18 06:41:36, Matthew Wilcox wrote: > On Fri, Apr 20, 2018 at 03:08:52PM +0200, Michal Hocko wrote: > > > In order to detect these bugs reliably I submit this patch that changes > > > kvmalloc to always use vmalloc if CONFIG_DEBUG_VM is turned on. > > > > No way. This is just wrong!

Re: [RFC] vhost: introduce mdev based hardware vhost backend

On Fri, Apr 20, 2018 at 03:50:41AM +, Liang, Cunming wrote: > > > > -Original Message- > > From: Bie, Tiwei > > Sent: Friday, April 20, 2018 11:28 AM > > To: Michael S. Tsirkin > > Cc: Jason Wang ; alex.william...@redhat.com; > >

Re: [PATCH v6 24/30] drm/rockchip: Disable PSR on input events

Hi Andrzej, On 20/04/18 15:47, Andrzej Hajda wrote: > Hi Enric, > > > On 05.04.2018 11:49, Enric Balletbo i Serra wrote: >> From: "Kristian H. Kristensen" >> >> To improve PSR exit latency, we speculatively start exiting when we >> receive input events. Occasionally, this

Re: [PATCH bpf-next 1/5] samples/bpf: Fix typo in comment

On Fri, 20 Apr 2018 14:21:16 +0100 Daniel Thompson wrote: > On Fri, Apr 20, 2018 at 02:10:04PM +0200, Jesper Dangaard Brouer wrote: > > > > On Thu, 19 Apr 2018 09:34:02 +0800 Leo Yan wrote: > > > > > Fix typo by replacing 'iif' with 'if'. > >

Re: [RFC PATCH 1/2] ACPI / PNP: Don't add "enumeration_by_parent" devices

On Fri, Apr 20, 2018 at 02:24:18PM +0100, John Garry wrote: > Hi Mika, > > On 20/04/2018 14:07, Mika Westerberg wrote: > > On Fri, Apr 20, 2018 at 06:07:25PM +0800, John Garry wrote: > > > + } else { > > > + device->driver_data = dev; > > > > I think this deserves a comment explaining

[PATCH] [net] ipv6: sr: fix NULL pointer dereference in seg6_do_srh_encap()- v4 pkts

In case of seg6 in encap mode, seg6_do_srh_encap() calls set_tun_src() in order to set the src addr of outer IPv6 header. The net_device is required for set_tun_src(). However calling ip6_dst_idev() on dst_entry in case of IPv4 traffic results on the following bug. Using just dst->dev should fix

Re: [PATCH v2 05/10] media: v4l: Add definitions for MPEG2 frame format and header metadata

On 04/19/18 17:45, Paul Kocialkowski wrote: > Stateless video decoding engines require both the MPEG slices and > associated metadata from the video stream in order to decode frames. > > This introduces definitions for a new pixel format, describing buffers > with MPEG2 slice data, as well as a

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On Fri 2018-04-20 08:04:28, Steven Rostedt wrote: > On Fri, 20 Apr 2018 11:12:24 +0200 > Petr Mladek wrote: > > > Yes, my number was arbitrary. The important thing is that it was long > > enough. Or do you know about an console that will not be able to write > > 100 lines

Re: [PATCH 1/2] IB/hfi1: Try slot reset before secondary bus reset

[+cc Rajat, Alex because of their interest in the reset/hotplug issue] For context, Sinan's patch is this: > diff --git a/drivers/infiniband/hw/hfi1/pcie.c > b/drivers/infiniband/hw/hfi1/pcie.c > index 83d66e8..75f49e3 100644 > --- a/drivers/infiniband/hw/hfi1/pcie.c > +++

Re: possible deadlock in blkdev_reread_part

Tetsuo Handa wrote: > Eric Biggers wrote: > > It seems that ->bd_mutex is held while opening and closing block devices, > > which > > should rank it above both ->lo_ctl_mutex and loop_index_mutex (see > > lo_open() and > > lo_release()). > > > > But blkdev_reread_part(), which takes ->bd_mutex,

Re: [PATCH v2] sched/rt: Rework for_each_process_thread() iterations in tg_has_rt_tasks()

On 20/04/18 13:06, Kirill Tkhai wrote: > From: Kirill Tkhai > > tg_rt_schedulable() iterates over all child task groups, > while tg_has_rt_tasks() iterates over all linked tasks. > In case of systems with big number of tasks, this may > take a lot of time. > > I observed

Re: [PATCH] printk: Ratelimit messages printed by console drivers

On Fri, 20 Apr 2018 10:17:51 -0400 Steven Rostedt wrote: > int git_context(void) That should have been get_context(void) ;-) -- Steve

Re: [PATCH 1/2] IB/hfi1: Try slot reset before secondary bus reset

On 4/20/2018 10:00 AM, Bjorn Helgaas wrote: > [+cc Rajat, Alex because of their interest in the reset/hotplug issue] > > For context, Sinan's patch is this: > >> diff --git a/drivers/infiniband/hw/hfi1/pcie.c >> b/drivers/infiniband/hw/hfi1/pcie.c >> index 83d66e8..75f49e3 100644 >> ---

Re: [PATCH net] tcp: don't read out-of-bounds opsize

On 04/20/2018 06:57 AM, Jann Horn wrote: > The old code reads the "opsize" variable from out-of-bounds memory (first > byte behind the segment) if a broken TCP segment ends directly after an > opcode that is neither EOL nor NOP. > > The result of the read isn't used for anything, so the worst

Re: [PATCH v2] KVM: Extend MAX_IRQ_ROUTES to 4096 for all archs

On Fri, 20 Apr 2018 21:51:13 +0800 Wanpeng Li wrote: > 2018-04-20 15:15 GMT+08:00 Cornelia Huck : > > On Thu, 19 Apr 2018 17:47:28 -0700 > > Wanpeng Li wrote: > > > >> From: Wanpeng Li > >> > >> Our virtual

Re: [PATCH v2] sched/rt: Rework for_each_process_thread() iterations in tg_has_rt_tasks()

On 20.04.2018 17:11, Juri Lelli wrote: > On 20/04/18 13:06, Kirill Tkhai wrote: >> From: Kirill Tkhai >> >> tg_rt_schedulable() iterates over all child task groups, >> while tg_has_rt_tasks() iterates over all linked tasks. >> In case of systems with big number of tasks,

RE: [PATCH v2] platform/x86: dell-wmi: Ignore new rfkill and fn-lock events

> -Original Message- > From: Pali Rohár [mailto:pali.ro...@gmail.com] > Sent: Friday, April 20, 2018 2:29 AM > To: Kai-Heng Feng > Cc: mj...@srcf.ucam.org; dvh...@infradead.org; a...@infradead.org; > Limonciello, Mario; platform-driver-...@vger.kernel.org; linux- > ker...@vger.kernel.org

[PATCH 02/17] perf/core: Store context switch out type in PERF_RECORD_SWITCH[_CPU_WIDE]

From: Alexey Budankov Store preempting context switch out event into Perf trace as a part of PERF_RECORD_SWITCH[_CPU_WIDE] record. Percentage of preempting and non-preempting context switches help understanding the nature of workloads (CPU or IO bound) that are

Re: [PATCH v2] tracing: fix bad use of igrab in trace_uprobe.c

On Thu, Apr 19, 2018 at 6:37 PM, Song Liu wrote: > > >> On Apr 19, 2018, at 7:44 AM, Miklos Szeredi wrote: >> >> On Thu, Apr 19, 2018 at 10:58 AM, Miklos Szeredi wrote: >>> On Wed, Apr 18, 2018 at 7:40 PM, Song Liu

[PATCH 13/17] perf record: Remove suggestion to enable APIC

From: Andi Kleen 'perf record' suggests to enable the APIC on errors. APIC is practically always used today and the problem is usually somewhere else. Just remove the outdated suggestion. Signed-off-by: Andi Kleen Acked-by: Jiri Olsa

[PATCH 14/17] perf tools: Add '\n' at the end of parse-options error messages

From: Ravi Bangoria Few error messages does not have '\n' at the end and thus next prompt gets printed in the same line. Ex, linux~$ perf buildid-cache -verbose --add ./a.out Error: did you mean `--verbose` (with two dashes ?)linux~$ Fix it.

[PATCH 12/17] perf record: Remove misleading error suggestion

From: Andi Kleen When perf record encounters an error setting up an event it suggests to enable CONFIG_PERF_EVENTS. This is misleading because: - Usually it is enabled (it is really hard to disable on x86) - The problem is usually somewhere else, e.g. the CPU is not

[PATCH 04/17] perf script: Extend misc field decoding with switch out event type

From: Alexey Budankov Append 'p' sign to 'S' tag designating the type of context switch out event so 'Sp' means preemption context switch. Documentation is extended to cover new presentation changes. $ perf script --show-switch-events -F +misc -I -i perf.data:

[PATCH 05/17] perf list: Add s390 support for detailed/verbose PMU event description

From: Thomas Richter 'perf list' with flags -d and -v print a description (-d) or a very verbose explanation (-v) of CPU specific counter events. These descriptions are provided with the json files in directory pmu-events/arch/s390/*.json. Display of these

[PATCH 06/17] perf: Return proper values for user stack errors

From: Jiri Olsa Return immediately when we find issue in the user stack checks. The error value could get overwritten by following check for PERF_SAMPLE_REGS_INTR. Signed-off-by: Jiri Olsa Cc: Alexander Shishkin Cc: Andi

Re: [PATCH] [net] ipv6: sr: fix NULL pointer dereference in seg6_do_srh_encap()- v4 pkts

On 04/20/2018 02:58 PM, Ahmed Abdelsalam wrote: In case of seg6 in encap mode, seg6_do_srh_encap() calls set_tun_src() in order to set the src addr of outer IPv6 header. The net_device is required for set_tun_src(). However calling ip6_dst_idev() on dst_entry in case of IPv4 traffic results on

Re: [PATCH] x86: ipc: fix x32 version of shmid64_ds and msqid64_ds

On Fri, Apr 20, 2018 at 3:53 PM, Jeffrey Walton wrote: >> +#if !defined(__x86_64__) || !defined(__ilp32__) >> #include >> +#else > > I understand there's some progress having Clang compile the kernel. > Clang treats __ILP32__ and friends differently than GCC. I believe >

Re: [PATCHv3 3/8] drm/omap: add support for manually updated displays

Hi Tony! On 20 April 2018 at 15:25, Tony Lindgren wrote: > * Daniel Stone [180420 10:21]: >> On 20 April 2018 at 08:09, Tomi Valkeinen wrote: >> > It's actually not quite clear to me how manual update displays work with >> > DRM...

RE: [PATCH] platform/x86: dell-smbios: Match on www.dell.com in OEM strings too

> -Original Message- > From: Darren Hart [mailto:dvh...@infradead.org] > Sent: Thursday, April 19, 2018 6:43 PM > To: Limonciello, Mario > Cc: Andy Shevchenko; LKML; platform-driver-...@vger.kernel.org > Subject: Re: [PATCH] platform/x86: dell-smbios: Match on www.dell.com in OEM >

[REVIEW][PATCH 10/22] signal/nios2: Use force_sig_fault where appropriate

Filling in struct siginfo before calling force_sig_info a tedious and error prone process, where once in a great while the wrong fields are filled out, and siginfo has been inconsistently cleared. Simplify this process by using the helper force_sig_fault. Which takes as a parameters all of the

[REVIEW][PATCH 09/22] signal/nds32: Use force_sig_fault where appropriate

Filling in struct siginfo before calling force_sig_info a tedious and error prone process, where once in a great while the wrong fields are filled out, and siginfo has been inconsistently cleared. Simplify this process by using the helper force_sig_fault. Which takes as a parameters all of the

[REVIEW][PATCH 08/22] signal/mips: Use force_sig_fault where appropriate

Filling in struct siginfo before calling force_sig_info a tedious and error prone process, where once in a great while the wrong fields are filled out, and siginfo has been inconsistently cleared. Simplify this process by using the helper force_sig_fault. Which takes as a parameters all of the

[REVIEW][PATCH 07/22] signal/microblaze: Use force_sig_fault where appropriate

Filling in struct siginfo before calling force_sig_info a tedious and error prone process, where once in a great while the wrong fields are filled out, and siginfo has been inconsistently cleared. Simplify this process by using the helper force_sig_fault. Which takes as a parameters all of the

[REVIEW][PATCH 05/22] signal/m68k: Use force_sig_fault where appropriate

Filling in struct siginfo before calling force_sig_info a tedious and error prone process, where once in a great while the wrong fields are filled out, and siginfo has been inconsistently cleared. Simplify this process by using the helper force_sig_fault. Which takes as a parameters all of the

[REVIEW][PATCH 03/22] signal/c6x: Use force_sig_fault where appropriate

Filling in struct siginfo before calling force_sig_info a tedious and error prone process, where once in a great while the wrong fields are filled out, and siginfo has been inconsistently cleared. Simplify this process by using the helper force_sig_fault. Which takes as a parameters all of the

Re: [RFC PATCH v2 4/6] sched/fair: Introduce an energy estimation helper function

Hi Leo, On Wednesday 18 Apr 2018 at 20:15:47 (+0800), Leo Yan wrote: > Sorry I introduce mess at here to spread my questions in several > replying, later will try to ask questions in one replying. Below are > more questions which it's good to bring up: > > The code for energy computation is

Re: [PATCH] [net] ipv6: sr: fix NULL pointer dereference in seg6_do_srh_encap()- v4 pkts

On Fri, 20 Apr 2018 15:38:08 +0100 David Lebrun wrote: > On 04/20/2018 02:58 PM, Ahmed Abdelsalam wrote: > > In case of seg6 in encap mode, seg6_do_srh_encap() calls set_tun_src() > > in order to set the src addr of outer IPv6 header. > > > > The net_device is required for

[REVIEW][PATCH 19/22] signal/um: Use force_sig_fault in relay_signal.

Today user mode linux only works on x86 and x86_64 and this allows simplifications of relay_signal. - x86 always set si_errno to 0 in fault handlers. - x86 does not implement si_trapno. - Only si_codes between SI_USER and SI_KERNEL have a fault address. Therefore warn if si_errno is set (it

<    4   5   6   7   8   9   10   11   12   13   >