Re: rcu kernel-doc issues (4.14-rc1)

On 10/16/17 13:26, Paul E. McKenney wrote: > On Mon, Oct 16, 2017 at 01:18:14PM -0700, Randy Dunlap wrote: >> On 10/16/17 13:07, Paul E. McKenney wrote: >>> On Mon, Oct 16, 2017 at 12:58:28PM -0700, Randy Dunlap wrote: Hi Jonathan and Paul, Please include these fixes before 4.14

Re: rcu kernel-doc issues (4.14-rc1)

On 10/16/17 13:26, Paul E. McKenney wrote: > On Mon, Oct 16, 2017 at 01:18:14PM -0700, Randy Dunlap wrote: >> On 10/16/17 13:07, Paul E. McKenney wrote: >>> On Mon, Oct 16, 2017 at 12:58:28PM -0700, Randy Dunlap wrote: Hi Jonathan and Paul, Please include these fixes before 4.14

Re: [PATCH v4] pidns: introduce syscall translate_pid

On Sat, 14 Oct 2017 11:17:47 +0300 Konstantin Khlebnikov wrote: > >>> pid_t translate_pid(pid_t pid, int source, int target); > >>> > >>> This syscall converts pid from source pid-ns into pid in target pid-ns. > >>> If pid is unreachable from target pid-ns it returns

Re: [PATCH v4] pidns: introduce syscall translate_pid

On Sat, 14 Oct 2017 11:17:47 +0300 Konstantin Khlebnikov wrote: > >>> pid_t translate_pid(pid_t pid, int source, int target); > >>> > >>> This syscall converts pid from source pid-ns into pid in target pid-ns. > >>> If pid is unreachable from target pid-ns it returns zero. > >>> > >>>

Re: [RESEND x2][PATCH 0/3] dwc2 fixes for edge cases on hikey

On Mon, Oct 16, 2017 at 1:36 AM, Minas Harutyunyan wrote: > On b-plug disconnect should asserted GOTGINT.SesEndDet interrupt. > According previously sent by you register dump (GHWCFG2 = 0x23affc70) > your core OTG_MODE=0. > Bellow fragment from programming guide on

Re: [RESEND x2][PATCH 0/3] dwc2 fixes for edge cases on hikey

On Mon, Oct 16, 2017 at 1:36 AM, Minas Harutyunyan wrote: > On b-plug disconnect should asserted GOTGINT.SesEndDet interrupt. > According previously sent by you register dump (GHWCFG2 = 0x23affc70) > your core OTG_MODE=0. > Bellow fragment from programming guide on Device disconnect: > >

Re: [PATCH 5/5] drm: Add four ioctls for managing drm mode object leases [v6]

Sean Paul writes: > nit: space before , Thanks. >> +/* Clone the lessor file to create a new file for us */ >> +DRM_DEBUG_LEASE("Allocating lease file\n"); >> +path_get(_file->f_path); > > Please forgive the stupid question, but where is this reference given

Re: [PATCH 5/5] drm: Add four ioctls for managing drm mode object leases [v6]

Sean Paul writes: > nit: space before , Thanks. >> +/* Clone the lessor file to create a new file for us */ >> +DRM_DEBUG_LEASE("Allocating lease file\n"); >> +path_get(_file->f_path); > > Please forgive the stupid question, but where is this reference given > up? That's not a

Re: interrupts-extended only allowed with different parents? [Was: Re: [PATCH 3/4] ARM: dts: imx28-tx28: fix interrupt flags and use interrupts-extended property]

On Mon, Oct 16, 2017 at 4:03 AM, Uwe Kleine-König wrote: > On Mon, Oct 16, 2017 at 10:56:32AM +0200, Lothar Waßmann wrote: >> Hi, >> >> On Mon, 16 Oct 2017 09:17:26 +0200 Uwe Kleine-König wrote: >> > Hello, >> > >> > On Wed, Oct 11, 2017 at 01:05:38PM +0200, Lothar

Re: interrupts-extended only allowed with different parents? [Was: Re: [PATCH 3/4] ARM: dts: imx28-tx28: fix interrupt flags and use interrupts-extended property]

On Mon, Oct 16, 2017 at 4:03 AM, Uwe Kleine-König wrote: > On Mon, Oct 16, 2017 at 10:56:32AM +0200, Lothar Waßmann wrote: >> Hi, >> >> On Mon, 16 Oct 2017 09:17:26 +0200 Uwe Kleine-König wrote: >> > Hello, >> > >> > On Wed, Oct 11, 2017 at 01:05:38PM +0200, Lothar Waßmann wrote: >> > > diff

Re: [PATCH 4.4 36/50] MIPS: IRQ Stack: Unwind IRQ stack onto task stack

On Fri, 2017-10-06 at 10:53 +0200, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Matt Redfearn > > > [ Upstream commit db8466c581cca1a08b505f1319c3ecd246f16fa8 ] [...] There

Re: [PATCH 4.4 36/50] MIPS: IRQ Stack: Unwind IRQ stack onto task stack

On Fri, 2017-10-06 at 10:53 +0200, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Matt Redfearn > > > [ Upstream commit db8466c581cca1a08b505f1319c3ecd246f16fa8 ] [...] There was a follow-up to this

Re: [PATCH v2] linux/types.h: Restore the ability to disable sparse endianness checks

On Mon, 2017-10-16 at 22:57 +0300, Michael S. Tsirkin wrote: > On Mon, Oct 16, 2017 at 10:26:33AM -0700, Bart Van Assche wrote: > > I think that this shows that the followed approach does not work, > > probably because several driver authors do not use sparse. For > > developers who are not the

Re: [PATCH v2] linux/types.h: Restore the ability to disable sparse endianness checks

On Mon, 2017-10-16 at 22:57 +0300, Michael S. Tsirkin wrote: > On Mon, Oct 16, 2017 at 10:26:33AM -0700, Bart Van Assche wrote: > > I think that this shows that the followed approach does not work, > > probably because several driver authors do not use sparse. For > > developers who are not the

Re: [PATCH] platform/x86: mlx-platform: make a couple of structures static

On Sat, Oct 07, 2017 at 05:03:41PM +0300, Andy Shevchenko wrote: > On Thu, Oct 5, 2017 at 1:42 PM, Colin King wrote: > > From: Colin Ian King > > > > The structures mlxplat_dev and mlxplat_hotplug are local to the source > > and do not need to

Re: [PATCH] platform/x86: mlx-platform: make a couple of structures static

On Sat, Oct 07, 2017 at 05:03:41PM +0300, Andy Shevchenko wrote: > On Thu, Oct 5, 2017 at 1:42 PM, Colin King wrote: > > From: Colin Ian King > > > > The structures mlxplat_dev and mlxplat_hotplug are local to the source > > and do not need to be in global scope, so make them static. > > > >

Re: [Part1 PATCH v6.1 14/17] x86: Add support for changing memory encryption attribute in early boot

On Mon, Oct 16, 2017 at 02:56:08PM -0500, Brijesh Singh wrote: > Some KVM-specific custom MSRs share the guest physical address with the > hypervisor in early boot. When SEV is active, the shared physical address > must be mapped with memory encryption attribute cleared so that both > hypervisor

Re: [Part1 PATCH v6.1 14/17] x86: Add support for changing memory encryption attribute in early boot

On Mon, Oct 16, 2017 at 02:56:08PM -0500, Brijesh Singh wrote: > Some KVM-specific custom MSRs share the guest physical address with the > hypervisor in early boot. When SEV is active, the shared physical address > must be mapped with memory encryption attribute cleared so that both > hypervisor

Re: [PATCH v6] PCI: quirks: update Cavium ThunderX ACS quirk implementation

[+cc David, Manish] Please use a subject line that tells more about what's going on. "Update quirk" doesn't really convey any useful information. Something like "Apply Cavium ThunderX ACS quirk only to Root Ports". On Wed, Sep 27, 2017 at 11:20:39AM -0700, Vadim Lomovtsev wrote: > This commit

Re: [PATCH v6] PCI: quirks: update Cavium ThunderX ACS quirk implementation

[+cc David, Manish] Please use a subject line that tells more about what's going on. "Update quirk" doesn't really convey any useful information. Something like "Apply Cavium ThunderX ACS quirk only to Root Ports". On Wed, Sep 27, 2017 at 11:20:39AM -0700, Vadim Lomovtsev wrote: > This commit

[tip:x86/timers] x86/platform/UV: Add check of TSC state set by UV BIOS

Commit-ID: 97d21003df3e7504c899b1701546f18ff475966f Gitweb: https://git.kernel.org/tip/97d21003df3e7504c899b1701546f18ff475966f Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:06 -0500 Committer: Thomas Gleixner CommitDate: Mon,

[tip:x86/timers] x86/tsc: Drastically reduce the number of firmware bug warnings

Commit-ID: 41e7864ab5ce4ec36e89a9f55d8d9dfe19b0392c Gitweb: https://git.kernel.org/tip/41e7864ab5ce4ec36e89a9f55d8d9dfe19b0392c Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:04 -0500 Committer: Thomas Gleixner CommitDate: Mon,

[tip:x86/timers] x86/tsc: Drastically reduce the number of firmware bug warnings

Commit-ID: 41e7864ab5ce4ec36e89a9f55d8d9dfe19b0392c Gitweb: https://git.kernel.org/tip/41e7864ab5ce4ec36e89a9f55d8d9dfe19b0392c Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:04 -0500 Committer: Thomas Gleixner CommitDate: Mon, 16 Oct 2017 22:50:36 +0200 x86/tsc:

[tip:x86/timers] x86/platform/UV: Add check of TSC state set by UV BIOS

Commit-ID: 97d21003df3e7504c899b1701546f18ff475966f Gitweb: https://git.kernel.org/tip/97d21003df3e7504c899b1701546f18ff475966f Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:06 -0500 Committer: Thomas Gleixner CommitDate: Mon, 16 Oct 2017 22:50:37 +0200

[tip:x86/timers] x86/tsc: Skip TSC test and error messages if already unstable

Commit-ID: 9514ececa52e9f1436e7682e98c852d1338b699f Gitweb: https://git.kernel.org/tip/9514ececa52e9f1436e7682e98c852d1338b699f Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:03 -0500 Committer: Thomas Gleixner CommitDate: Mon,

[tip:x86/timers] x86/tsc: Skip TSC test and error messages if already unstable

Commit-ID: 9514ececa52e9f1436e7682e98c852d1338b699f Gitweb: https://git.kernel.org/tip/9514ececa52e9f1436e7682e98c852d1338b699f Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:03 -0500 Committer: Thomas Gleixner CommitDate: Mon, 16 Oct 2017 22:50:36 +0200 x86/tsc: Skip

Re: [PATCH v4 pci 0/2] PCI/MSI: pci-xgene-msi: Enable MSI support in ACPI boot for X-Gene v1

Hi Lorenzo, Do you have any comments for this patch? Best regards, Khuong Dinh On Tue, Sep 26, 2017 at 10:49 AM, Khuong Dinh wrote: > This patch set enables ACPI MSI support for X-Gene PCIe v1 hardware > and provides the proper MSI driver initialization ordering. > >

[tip:x86/timers] x86/tsc: Provide a means to disable TSC ART

Commit-ID: 6c66350d0a482892793b888b07c1177fc6d4b344 Gitweb: https://git.kernel.org/tip/6c66350d0a482892793b888b07c1177fc6d4b344 Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:05 -0500 Committer: Thomas Gleixner CommitDate: Mon,

Re: [PATCH v4 pci 0/2] PCI/MSI: pci-xgene-msi: Enable MSI support in ACPI boot for X-Gene v1

Hi Lorenzo, Do you have any comments for this patch? Best regards, Khuong Dinh On Tue, Sep 26, 2017 at 10:49 AM, Khuong Dinh wrote: > This patch set enables ACPI MSI support for X-Gene PCIe v1 hardware > and provides the proper MSI driver initialization ordering. > > Signed-off-by: Khuong

[tip:x86/timers] x86/tsc: Provide a means to disable TSC ART

Commit-ID: 6c66350d0a482892793b888b07c1177fc6d4b344 Gitweb: https://git.kernel.org/tip/6c66350d0a482892793b888b07c1177fc6d4b344 Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:05 -0500 Committer: Thomas Gleixner CommitDate: Mon, 16 Oct 2017 22:50:37 +0200 x86/tsc:

Re: [RFC PATCH 3/3] mm/map_contig: Add mmap(MAP_CONTIG) support

On 10/16/2017 02:03 PM, Laura Abbott wrote: > On 10/16/2017 01:32 PM, Mike Kravetz wrote: >> On 10/16/2017 11:07 AM, Michal Hocko wrote: >>> On Mon 16-10-17 10:43:38, Mike Kravetz wrote: Just to be clear, the posix standard talks about a typed memory object. The suggested implementation

Re: [RFC PATCH 3/3] mm/map_contig: Add mmap(MAP_CONTIG) support

On 10/16/2017 02:03 PM, Laura Abbott wrote: > On 10/16/2017 01:32 PM, Mike Kravetz wrote: >> On 10/16/2017 11:07 AM, Michal Hocko wrote: >>> On Mon 16-10-17 10:43:38, Mike Kravetz wrote: Just to be clear, the posix standard talks about a typed memory object. The suggested implementation

[tip:x86/timers] x86/tsc: Add option that TSC on Socket 0 being non-zero is valid

Commit-ID: 341102c3ef29c33611586072363cf9982a8bdb77 Gitweb: https://git.kernel.org/tip/341102c3ef29c33611586072363cf9982a8bdb77 Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:02 -0500 Committer: Thomas Gleixner CommitDate: Mon,

Re: [PATCH] staging: ccree: fix boolreturn.cocci warning

On Mon, Oct 16, 2017 at 03:39:57PM +0530, suni...@techveda.org wrote: > From: Suniel Mahesh > > This fixes the following coccinelle warning: > WARNING: return of 0/1 in function 'ssi_is_hw_key' with return type bool. Perhaps Coccinelle emits WARNING: return of 0/1 in

[tip:x86/timers] x86/tsc: Add option that TSC on Socket 0 being non-zero is valid

Commit-ID: 341102c3ef29c33611586072363cf9982a8bdb77 Gitweb: https://git.kernel.org/tip/341102c3ef29c33611586072363cf9982a8bdb77 Author: mike.tra...@hpe.com AuthorDate: Thu, 12 Oct 2017 11:32:02 -0500 Committer: Thomas Gleixner CommitDate: Mon, 16 Oct 2017 22:50:36 +0200 x86/tsc: Add

Re: [PATCH] staging: ccree: fix boolreturn.cocci warning

On Mon, Oct 16, 2017 at 03:39:57PM +0530, suni...@techveda.org wrote: > From: Suniel Mahesh > > This fixes the following coccinelle warning: > WARNING: return of 0/1 in function 'ssi_is_hw_key' with return type bool. Perhaps Coccinelle emits WARNING: return of 0/1 in function 'ssi_is_hw_key'

Re: [PATCH v3] drm/amd/powerplay: Remove unnecessary cast on void pointer

Hi Harsha, [auto build test WARNING on v4.14-rc3] [cannot apply to drm/drm-next next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v3] drm/amd/powerplay: Remove unnecessary cast on void pointer

Hi Harsha, [auto build test WARNING on v4.14-rc3] [cannot apply to drm/drm-next next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] staging: ccree: Fix bool comparison

On Mon, Oct 16, 2017 at 03:38:11PM +0530, suni...@techveda.org wrote: > From: Suniel Mahesh > > Bool tests don't need comparisons. This commit log could be a bit longer. You may like to read Documentation/process/submitting-patches.rst (section 2). > This fixes the

Re: [PATCH] staging: ccree: Fix bool comparison

On Mon, Oct 16, 2017 at 03:38:11PM +0530, suni...@techveda.org wrote: > From: Suniel Mahesh > > Bool tests don't need comparisons. This commit log could be a bit longer. You may like to read Documentation/process/submitting-patches.rst (section 2). > This fixes the following coccinelle

Re: tracing, dma-buf: Remove unused trace event dma_fence_annotate_wait_on

On Mon, 16 Oct 2017 20:49:11 +0530 Sumit Semwal wrote: > I suspect it should be ok; please do feel free to add my > Acked-by: Sumit Semwal > if you wish :) Done. Thanks! -- Steve

Re: tracing, dma-buf: Remove unused trace event dma_fence_annotate_wait_on

On Mon, 16 Oct 2017 20:49:11 +0530 Sumit Semwal wrote: > I suspect it should be ok; please do feel free to add my > Acked-by: Sumit Semwal > if you wish :) Done. Thanks! -- Steve

Re: [PATCH 3/3] bpf: Make sure that ->comm does not change under us.

Am Montag, 16. Oktober 2017, 23:02:06 CEST schrieb Daniel Borkmann: > On 10/16/2017 10:55 PM, Richard Weinberger wrote: > > Am Montag, 16. Oktober 2017, 22:50:43 CEST schrieb Daniel Borkmann: > >>> struct task_struct *task = current; > >>> > >>> + task_lock(task); > >>> > >>>

Re: [PATCH 3/3] bpf: Make sure that ->comm does not change under us.

Am Montag, 16. Oktober 2017, 23:02:06 CEST schrieb Daniel Borkmann: > On 10/16/2017 10:55 PM, Richard Weinberger wrote: > > Am Montag, 16. Oktober 2017, 22:50:43 CEST schrieb Daniel Borkmann: > >>> struct task_struct *task = current; > >>> > >>> + task_lock(task); > >>> > >>>

Re: [PATCH] drm/omap: Replace list_for_each with list_for_each_entry

Hi Harsha, [auto build test ERROR on drm/drm-next] [also build test ERROR on v4.14-rc5 next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] drm/omap: Replace list_for_each with list_for_each_entry

Hi Harsha, [auto build test ERROR on drm/drm-next] [also build test ERROR on v4.14-rc5 next-20171013] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v4] pidns: introduce syscall translate_pid

On 10/16/2017 09:24 AM, Oleg Nesterov wrote: On 10/13, Konstantin Khlebnikov wrote: On 13.10.2017 19:05, Oleg Nesterov wrote: I won't insist, but this suggests we should add a new helper, get_ns_by_fd_type(fd, type), and convert get_net_ns_by_fd() to use it as well. That was in v3. I'll

Re: [PATCH v4] pidns: introduce syscall translate_pid

On 10/16/2017 09:24 AM, Oleg Nesterov wrote: On 10/13, Konstantin Khlebnikov wrote: On 13.10.2017 19:05, Oleg Nesterov wrote: I won't insist, but this suggests we should add a new helper, get_ns_by_fd_type(fd, type), and convert get_net_ns_by_fd() to use it as well. That was in v3. I'll

Re: [PATCH 3/5] drm: Add drm_object lease infrastructure [v4]

On Mon, Oct 16, 2017 at 01:42:46PM -0700, Keith Packard wrote: > Sean Paul writes: > > > > With these nits fixed, > > Reviewed-by: Sean Paul > > Like this? > Perfect, thanks! Sean > From 0aa52dd5a0873831c79c14942075354c041e5bed Mon Sep 17

Re: [PATCH 3/5] drm: Add drm_object lease infrastructure [v4]

On Mon, Oct 16, 2017 at 01:42:46PM -0700, Keith Packard wrote: > Sean Paul writes: > > > > With these nits fixed, > > Reviewed-by: Sean Paul > > Like this? > Perfect, thanks! Sean > From 0aa52dd5a0873831c79c14942075354c041e5bed Mon Sep 17 00:00:00 2001 > From: Keith Packard > Date: Mon,

Re: [RFC PATCH 3/3] mm/map_contig: Add mmap(MAP_CONTIG) support

On 10/16/2017 01:32 PM, Mike Kravetz wrote: > On 10/16/2017 11:07 AM, Michal Hocko wrote: >> On Mon 16-10-17 10:43:38, Mike Kravetz wrote: >>> Just to be clear, the posix standard talks about a typed memory object. >>> The suggested implementation has one create a connection to the memory >>>

Re: [RFC PATCH 3/3] mm/map_contig: Add mmap(MAP_CONTIG) support

On 10/16/2017 01:32 PM, Mike Kravetz wrote: > On 10/16/2017 11:07 AM, Michal Hocko wrote: >> On Mon 16-10-17 10:43:38, Mike Kravetz wrote: >>> Just to be clear, the posix standard talks about a typed memory object. >>> The suggested implementation has one create a connection to the memory >>>

Re: [PATCH 5/5] drm: Add four ioctls for managing drm mode object leases [v6]

On Thu, Oct 12, 2017 at 06:56:31PM -0700, Keith Packard wrote: > drm_mode_create_lease > > Creates a lease for a list of drm mode objects, returning an > fd for the new drm_master and a 64-bit identifier for the lessee > > drm_mode_list_lesees > > List the identifiers of the

Re: [PATCH 5/5] drm: Add four ioctls for managing drm mode object leases [v6]

On Thu, Oct 12, 2017 at 06:56:31PM -0700, Keith Packard wrote: > drm_mode_create_lease > > Creates a lease for a list of drm mode objects, returning an > fd for the new drm_master and a 64-bit identifier for the lessee > > drm_mode_list_lesees > > List the identifiers of the

Re: [PATCH 3/3] bpf: Make sure that ->comm does not change under us.

On 10/16/2017 10:55 PM, Richard Weinberger wrote: Am Montag, 16. Oktober 2017, 22:50:43 CEST schrieb Daniel Borkmann: struct task_struct *task = current; + task_lock(task); strncpy(buf, task->comm, size); + task_unlock(task); Wouldn't this potentially lead to a

Re: [PATCH 3/3] bpf: Make sure that ->comm does not change under us.

On 10/16/2017 10:55 PM, Richard Weinberger wrote: Am Montag, 16. Oktober 2017, 22:50:43 CEST schrieb Daniel Borkmann: struct task_struct *task = current; + task_lock(task); strncpy(buf, task->comm, size); + task_unlock(task); Wouldn't this potentially lead to a

[GIT PULL] vfs i_version fix for Linus

Hi Al, This pull request contains a single patch that allows file systems to be mounted with i_version.  I would really appreciate your forwarding this patch to Linus. thanks, Mimi --- The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f: Linux 4.14-rc4 (2017-10-08

[GIT PULL] vfs i_version fix for Linus

Hi Al, This pull request contains a single patch that allows file systems to be mounted with i_version.  I would really appreciate your forwarding this patch to Linus. thanks, Mimi --- The following changes since commit 8a5776a5f49812d29fe4b2d0a2d71675c3facf3f: Linux 4.14-rc4 (2017-10-08

Re: [RFC PATCH 3/3] mm/map_contig: Add mmap(MAP_CONTIG) support

On Mon 16-10-17 13:32:45, Mike Kravetz wrote: > On 10/16/2017 11:07 AM, Michal Hocko wrote: [...] > > That depends on who is actually going to use the contiguous memory. If > > we are talking about drivers to communication to the userspace then > > using driver specific fd with its mmap

Re: [RFC PATCH 3/3] mm/map_contig: Add mmap(MAP_CONTIG) support

On Mon 16-10-17 13:32:45, Mike Kravetz wrote: > On 10/16/2017 11:07 AM, Michal Hocko wrote: [...] > > That depends on who is actually going to use the contiguous memory. If > > we are talking about drivers to communication to the userspace then > > using driver specific fd with its mmap

Re: [PATCH 00/12] of: overlay: clean up device tree overlay code

On Fri, Oct 13, 2017 at 5:03 PM, Frank Rowand wrote: > Hi Rob, > > On 10/02/17 20:53, frowand.l...@gmail.com wrote: >> From: Frank Rowand >> >> I have found the device tree overlay code to be difficult to read and >> maintain. This patch series

Re: [PATCH 00/12] of: overlay: clean up device tree overlay code

On Fri, Oct 13, 2017 at 5:03 PM, Frank Rowand wrote: > Hi Rob, > > On 10/02/17 20:53, frowand.l...@gmail.com wrote: >> From: Frank Rowand >> >> I have found the device tree overlay code to be difficult to read and >> maintain. This patch series attempts to improve that situation. >> >> The

Re: [PATCH] of: overlay: fix memory leak related to duplicated property

On Mon, Oct 16, 2017 at 1:07 AM, Frank Rowand wrote: > Hi Alan, > > It is Rob's choice of which order to take the patches in. If we have a choice, better to take fixes first so they can be more easily backported. Rob > Either order, it will be a trivial fixup to the

Re: [PATCH 3/3] bpf: Make sure that ->comm does not change under us.

Am Montag, 16. Oktober 2017, 22:50:43 CEST schrieb Daniel Borkmann: > > struct task_struct *task = current; > > > > + task_lock(task); > > > > strncpy(buf, task->comm, size); > > > > + task_unlock(task); > > Wouldn't this potentially lead to a deadlock? E.g. you attach yourself >

Re: [PATCH] of: overlay: fix memory leak related to duplicated property

On Mon, Oct 16, 2017 at 1:07 AM, Frank Rowand wrote: > Hi Alan, > > It is Rob's choice of which order to take the patches in. If we have a choice, better to take fixes first so they can be more easily backported. Rob > Either order, it will be a trivial fixup to the second patchset > to go in.

Re: [PATCH 3/3] bpf: Make sure that ->comm does not change under us.

Am Montag, 16. Oktober 2017, 22:50:43 CEST schrieb Daniel Borkmann: > > struct task_struct *task = current; > > > > + task_lock(task); > > > > strncpy(buf, task->comm, size); > > > > + task_unlock(task); > > Wouldn't this potentially lead to a deadlock? E.g. you attach yourself >

Re: [PATCH 3/3] bpf: Make sure that ->comm does not change under us.

On 10/16/2017 08:18 PM, Richard Weinberger wrote: Sadly we cannot use get_task_comm() since bpf_get_current_comm() allows truncation. Signed-off-by: Richard Weinberger --- kernel/bpf/helpers.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/bpf/helpers.c

Re: [PATCH 3/3] bpf: Make sure that ->comm does not change under us.

On 10/16/2017 08:18 PM, Richard Weinberger wrote: Sadly we cannot use get_task_comm() since bpf_get_current_comm() allows truncation. Signed-off-by: Richard Weinberger --- kernel/bpf/helpers.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/bpf/helpers.c b/kernel/bpf/helpers.c

[PATCH] ipv4: mark expected switch fall-throughs

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Notice that in some cases I placed the "fall through" comment on its own line, which is what GCC is expecting to find. Addresses-Coverity-ID: 115108 Signed-off-by: Gustavo A. R. Silva

[PATCH] ipv4: mark expected switch fall-throughs

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Notice that in some cases I placed the "fall through" comment on its own line, which is what GCC is expecting to find. Addresses-Coverity-ID: 115108 Signed-off-by: Gustavo A. R. Silva

Re: [PATCH 2/3] bpf: Remove dead variable

On 10/16/2017 09:22 PM, Richard Weinberger wrote: [...] So, I can happily squash 2/3 into 1/3 and resent. Yeah, please just squash them. Thanks, Daniel

Re: [PATCH 2/3] bpf: Remove dead variable

On 10/16/2017 09:22 PM, Richard Weinberger wrote: [...] So, I can happily squash 2/3 into 1/3 and resent. Yeah, please just squash them. Thanks, Daniel

Re: [RFC 00/11] KVM, EFI, arm64: EFI Runtime Services Sandboxing

On Tue, Sep 26, 2017 at 11:14:52PM +0200, Florent Revest wrote: > On Thu, 2017-08-31 at 11:26 +0200, Christoffer Dall wrote: > > I wonder if this should be split into two series; one that sets up > > anything you may need from KVM, and another one that uses that for > > UEFI. > > > > There's a

Re: [RFC 00/11] KVM, EFI, arm64: EFI Runtime Services Sandboxing

On Tue, Sep 26, 2017 at 11:14:52PM +0200, Florent Revest wrote: > On Thu, 2017-08-31 at 11:26 +0200, Christoffer Dall wrote: > > I wonder if this should be split into two series; one that sets up > > anything you may need from KVM, and another one that uses that for > > UEFI. > > > > There's a

Re: [PATCH] of: overlay: move resolve phandles into of_overlay_apply()

On Tue, Oct 10, 2017 at 8:02 PM, wrote: > From: Frank Rowand > > Move more code into of_overlay_apply() so that it does not have > to be duplicated by each caller of of_overlay_apply(). > > The test in of_resolve_phandles() that the overlay tree is

Re: [PATCH] of: overlay: move resolve phandles into of_overlay_apply()

On Tue, Oct 10, 2017 at 8:02 PM, wrote: > From: Frank Rowand > > Move more code into of_overlay_apply() so that it does not have > to be duplicated by each caller of of_overlay_apply(). > > The test in of_resolve_phandles() that the overlay tree is detached is > temporarily disabled so that old

Re: of: unittest fails on UML

On Fri, Oct 13, 2017 at 5:38 PM, Thomas Meyer wrote: > Hi, > > drivers/of/unittest.c fails on UML with a kernel crash. > The crash is due to of_find_device_by_node() returning NULL: > > 841│ /* Test that a missing irq domain returns -EPROBE_DEFER */ > 842│ np =

Re: of: unittest fails on UML

On Fri, Oct 13, 2017 at 5:38 PM, Thomas Meyer wrote: > Hi, > > drivers/of/unittest.c fails on UML with a kernel crash. > The crash is due to of_find_device_by_node() returning NULL: > > 841│ /* Test that a missing irq domain returns -EPROBE_DEFER */ > 842│ np =

Re: [PATCH 0/4] char-TPM: Adjustments for ten function implementations

> A minor complaint: all commits are missing "Fixes:" tag. * Do you require it to be added to the commit messages? * Would you like to get a finer patch granularity then? * Do you find any more information missing? Regards, Markus

Re: [RFC 04/11] KVM, arm, arm64: Offer PAs to IPAs idmapping to internal VMs

On Tue, Sep 26, 2017 at 11:14:45PM +0200, Florent Revest wrote: > On Thu, 2017-08-31 at 11:23 +0200, Christoffer Dall wrote: > > > diff --git a/virt/kvm/arm/mmu.c b/virt/kvm/arm/mmu.c > > > index 2ea21da..1d2d3df 100644 > > > --- a/virt/kvm/arm/mmu.c > > > +++ b/virt/kvm/arm/mmu.c > > > @@ -772,6

Re: [PATCH 0/4] char-TPM: Adjustments for ten function implementations

> A minor complaint: all commits are missing "Fixes:" tag. * Do you require it to be added to the commit messages? * Would you like to get a finer patch granularity then? * Do you find any more information missing? Regards, Markus

Re: [RFC 04/11] KVM, arm, arm64: Offer PAs to IPAs idmapping to internal VMs

On Tue, Sep 26, 2017 at 11:14:45PM +0200, Florent Revest wrote: > On Thu, 2017-08-31 at 11:23 +0200, Christoffer Dall wrote: > > > diff --git a/virt/kvm/arm/mmu.c b/virt/kvm/arm/mmu.c > > > index 2ea21da..1d2d3df 100644 > > > --- a/virt/kvm/arm/mmu.c > > > +++ b/virt/kvm/arm/mmu.c > > > @@ -772,6

Re: [PATCH 3/5] drm: Add drm_object lease infrastructure [v4]

Sean Paul writes: > With these nits fixed, > Reviewed-by: Sean Paul Like this? From 0aa52dd5a0873831c79c14942075354c041e5bed Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 16 Oct 2017 13:41:20 -0700 Subject: [PATCH]

Re: [PATCH 3/5] drm: Add drm_object lease infrastructure [v4]

Sean Paul writes: > With these nits fixed, > Reviewed-by: Sean Paul Like this? From 0aa52dd5a0873831c79c14942075354c041e5bed Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Mon, 16 Oct 2017 13:41:20 -0700 Subject: [PATCH] drm: Mark functions requiring idr_mutex. Add lockdep to

Re: [patch v3 0/3] drivers/platform: replace module x86/mlxcpld-hotplug with mellanox/mlxreg-hotplug

On Mon, Sep 11, 2017 at 03:12:36PM +, Vadim Pasternak wrote: > The patchset modifies x86/mlxcpld-hotplug.c for making it architecture > independent, renames to mlxreg-hotplug and moves it from > drivers/platform/x86 folder to new drivers/platform/mellanox folder. > This modification also

Re: [patch v3 0/3] drivers/platform: replace module x86/mlxcpld-hotplug with mellanox/mlxreg-hotplug

On Mon, Sep 11, 2017 at 03:12:36PM +, Vadim Pasternak wrote: > The patchset modifies x86/mlxcpld-hotplug.c for making it architecture > independent, renames to mlxreg-hotplug and moves it from > drivers/platform/x86 folder to new drivers/platform/mellanox folder. > This modification also

RE: staging: rtsx: Add support for RTS5260

> -Original Message- > From: Lee Jones [mailto:lee.jo...@linaro.org] > Sent: Friday, October 13, 2017 4:15 PM > To: Limonciello, Mario > Cc: rui_f...@realsil.com.cn; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; de...@driverdev.osuosl.org;

RE: staging: rtsx: Add support for RTS5260

> -Original Message- > From: Lee Jones [mailto:lee.jo...@linaro.org] > Sent: Friday, October 13, 2017 4:15 PM > To: Limonciello, Mario > Cc: rui_f...@realsil.com.cn; gre...@linuxfoundation.org; linux- > ker...@vger.kernel.org; de...@driverdev.osuosl.org; ricky...@realtek.com; >

Re: [PATCH 4/5] drm: Check mode object lease status in all master ioctl paths [v3]

On Thu, Oct 12, 2017 at 06:56:30PM -0700, Keith Packard wrote: > Attempts to modify un-leased objects are rejected with an error. > Information returned about unleased objects is modified to make them > appear unusable and/or disconnected. > > Changes for v2 as suggested by Daniel Vetter

Re: [PATCH 4/5] drm: Check mode object lease status in all master ioctl paths [v3]

On Thu, Oct 12, 2017 at 06:56:30PM -0700, Keith Packard wrote: > Attempts to modify un-leased objects are rejected with an error. > Information returned about unleased objects is modified to make them > appear unusable and/or disconnected. > > Changes for v2 as suggested by Daniel Vetter : > >

Re: [RFC PATCH 3/3] mm/map_contig: Add mmap(MAP_CONTIG) support

On 10/16/2017 11:07 AM, Michal Hocko wrote: > On Mon 16-10-17 10:43:38, Mike Kravetz wrote: >> Just to be clear, the posix standard talks about a typed memory object. >> The suggested implementation has one create a connection to the memory >> object to receive a fd, then use mmap as usual to get

Re: [RFC PATCH 3/3] mm/map_contig: Add mmap(MAP_CONTIG) support

On 10/16/2017 11:07 AM, Michal Hocko wrote: > On Mon 16-10-17 10:43:38, Mike Kravetz wrote: >> Just to be clear, the posix standard talks about a typed memory object. >> The suggested implementation has one create a connection to the memory >> object to receive a fd, then use mmap as usual to get

Re: [PATCH 6/7] ARM: dts: imx6ul: add support for TXUL modules on TXUL-Mainboard

Hi Lothar, On Fri, Oct 13, 2017 at 7:43 AM, Lothar Waßmann wrote: > +/ { > + aliases { > + lcdif_24bit_pins_a = _disp0_3; > + mmc0 = Is this mmc0 alias really needed here? I see it inside imx6ul.dtsi, but even inside imx6ul.dtsi:

Re: [PATCH 6/7] ARM: dts: imx6ul: add support for TXUL modules on TXUL-Mainboard

Hi Lothar, On Fri, Oct 13, 2017 at 7:43 AM, Lothar Waßmann wrote: > +/ { > + aliases { > + lcdif_24bit_pins_a = _disp0_3; > + mmc0 = Is this mmc0 alias really needed here? I see it inside imx6ul.dtsi, but even inside imx6ul.dtsi: does it make sense to have

[GIT PULL for v4.14-rc6] media fixes

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media media/v4.14-2 For the following media core fixes: - cec: Respond to unregistered initiators, when applicable - dvb_frontend: only use kref after initialized and the following driver-specific

[GIT PULL for v4.14-rc6] media fixes

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media media/v4.14-2 For the following media core fixes: - cec: Respond to unregistered initiators, when applicable - dvb_frontend: only use kref after initialized and the following driver-specific

[PATCH] decnet: af_decnet: mark expected switch fall-throughs

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Signed-off-by: Gustavo A. R. Silva --- This code was tested by compilation only (GCC 7.2.0 was used). Please, verify if the actual intention of the code is to

[PATCH] decnet: af_decnet: mark expected switch fall-throughs

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Signed-off-by: Gustavo A. R. Silva --- This code was tested by compilation only (GCC 7.2.0 was used). Please, verify if the actual intention of the code is to fall through.

Re: [PATCH] inet: frags: Convert timers to use timer_setup()

Hello. On 05.10.2017 02:52, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. > > Cc: Alexander Aring > Cc:

Re: [PATCH] inet: frags: Convert timers to use timer_setup()

Hello. On 05.10.2017 02:52, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. > > Cc: Alexander Aring > Cc: Stefan Schmidt > Cc:

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