[PATCH 0/3] arm64: queued spinlocks and rw-locks

The patch 3 adds implementation for queued-based locking on ARM64, and the option in kernel config to enable it. Patches 1 and 2 fix some mess in header files to apply patch 3 smoothly. Tested on QDF2400 with huge improvements with these patches on the torture tests, by Adam Wallis. Tested on

[PATCH 0/3] arm64: queued spinlocks and rw-locks

The patch 3 adds implementation for queued-based locking on ARM64, and the option in kernel config to enable it. Patches 1 and 2 fix some mess in header files to apply patch 3 smoothly. Tested on QDF2400 with huge improvements with these patches on the torture tests, by Adam Wallis. Tested on

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On 05/03/2017 04:41 PM, Shawn Guo wrote: > On Wed, May 03, 2017 at 04:32:06PM +0200, Marek Vasut wrote: >> On 05/03/2017 04:26 PM, Marek Vasut wrote: >>> On 05/03/2017 03:57 PM, Shawn Guo wrote: On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: > On 04/25/2017 07:23 PM, Leonard

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On 05/03/2017 04:41 PM, Shawn Guo wrote: > On Wed, May 03, 2017 at 04:32:06PM +0200, Marek Vasut wrote: >> On 05/03/2017 04:26 PM, Marek Vasut wrote: >>> On 05/03/2017 03:57 PM, Shawn Guo wrote: On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: > On 04/25/2017 07:23 PM, Leonard

Re: [PATCH 0/7] KVM: MMU: fast write protect

On 05/03/2017 08:28 PM, Paolo Bonzini wrote: So if I understand correctly this relies on userspace doing: 1) KVM_GET_DIRTY_LOG without write protect 2) KVM_WRITE_PROTECT_ALL_MEM Writes may happen between 1 and 2; they are not represented in the live dirty bitmap but

Re: [PATCH 0/7] KVM: MMU: fast write protect

On 05/03/2017 08:28 PM, Paolo Bonzini wrote: So if I understand correctly this relies on userspace doing: 1) KVM_GET_DIRTY_LOG without write protect 2) KVM_WRITE_PROTECT_ALL_MEM Writes may happen between 1 and 2; they are not represented in the live dirty bitmap but

Re: [PATCHv2 0/4] Motorola Droid 4: Add WL1285C support

On Wed, May 3, 2017 at 9:22 AM, Sebastian Reichel wrote: > Hi, > > Motorola Droid 4 uses a WL1285C, as visible on iFixit [0]. This > fixes the DT file to use correct compatible for the wifi node > and adds the bluetooth node. > > [0]

Re: [PATCHv2 0/4] Motorola Droid 4: Add WL1285C support

On Wed, May 3, 2017 at 9:22 AM, Sebastian Reichel wrote: > Hi, > > Motorola Droid 4 uses a WL1285C, as visible on iFixit [0]. This > fixes the DT file to use correct compatible for the wifi node > and adds the bluetooth node. > > [0]

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Wed, May 3, 2017 at 5:24 PM, Wim Van Sebroeck wrote: >> On Tue, May 02, 2017 at 02:58:22PM -0700, Guenter Roeck wrote: >> > On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: >> > On a side note, it appears that I tagged "watchdog: iTCO_wdt: cleanup >> > set/unset

Re: linux-next: manual merge of the drivers-x86 tree with the watchdog tree

On Wed, May 3, 2017 at 5:24 PM, Wim Van Sebroeck wrote: >> On Tue, May 02, 2017 at 02:58:22PM -0700, Guenter Roeck wrote: >> > On Tue, May 02, 2017 at 02:30:46PM -0700, Darren Hart wrote: >> > On a side note, it appears that I tagged "watchdog: iTCO_wdt: cleanup >> > set/unset no_reboot_bit

Re: [PATCH 1/2] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

Hi Daniel, On Wednesday 03 May 2017 16:28:56 Daniel Vetter wrote: > On Wed, May 03, 2017 at 12:36:06PM +0300, Laurent Pinchart wrote: > > On Wednesday 03 May 2017 11:32:17 Daniel Vetter wrote: > >> On Wed, May 03, 2017 at 02:53:00PM +0530, Archit Taneja wrote: > >>> +panel/bridge reviewers. > >>>

Re: [PATCH 1/2] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

Hi Daniel, On Wednesday 03 May 2017 16:28:56 Daniel Vetter wrote: > On Wed, May 03, 2017 at 12:36:06PM +0300, Laurent Pinchart wrote: > > On Wednesday 03 May 2017 11:32:17 Daniel Vetter wrote: > >> On Wed, May 03, 2017 at 02:53:00PM +0530, Archit Taneja wrote: > >>> +panel/bridge reviewers. > >>>

Re: [PATCH v4] platform/x86: ideapad-laptop: Add sysfs interface for touchpad state

On Wed, May 3, 2017 at 5:36 PM, Ritesh Raj Sarraf wrote: > Resending again, as Google servers are behaving weird lately. > > On Sun, 2017-04-30 at 15:54 +0300, Andy Shevchenko wrote: >> > > the main issue that driver doesn't >> > > send SW_TABLET_MODE event through input device.

Re: [PATCH v4] platform/x86: ideapad-laptop: Add sysfs interface for touchpad state

On Wed, May 3, 2017 at 5:36 PM, Ritesh Raj Sarraf wrote: > Resending again, as Google servers are behaving weird lately. > > On Sun, 2017-04-30 at 15:54 +0300, Andy Shevchenko wrote: >> > > the main issue that driver doesn't >> > > send SW_TABLET_MODE event through input device. >> > >> > Well.

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On Wed, May 03, 2017 at 04:32:06PM +0200, Marek Vasut wrote: > On 05/03/2017 04:26 PM, Marek Vasut wrote: > > On 05/03/2017 03:57 PM, Shawn Guo wrote: > >> On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: > >>> On 04/25/2017 07:23 PM, Leonard Crestez wrote: > Anyway, that version

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On Wed, May 03, 2017 at 04:32:06PM +0200, Marek Vasut wrote: > On 05/03/2017 04:26 PM, Marek Vasut wrote: > > On 05/03/2017 03:57 PM, Shawn Guo wrote: > >> On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: > >>> On 04/25/2017 07:23 PM, Leonard Crestez wrote: > Anyway, that version

[PULL REQUEST] i2c for 4.12

Linus, I2C has the following updates for you: * an immutable cross-subsystem branch fixing PMIC access on Intel Baytrail * bigger driver updates to the designware, meson, exynos5 drivers * new i2c_acpi_new_device() function to create devices from ACPI * struct i2c_driver has now a flag

[PULL REQUEST] i2c for 4.12

Linus, I2C has the following updates for you: * an immutable cross-subsystem branch fixing PMIC access on Intel Baytrail * bigger driver updates to the designware, meson, exynos5 drivers * new i2c_acpi_new_device() function to create devices from ACPI * struct i2c_driver has now a flag

Re: [PATCHv3 2/3] drm/prime: Introduce drm_gem_prime_import_platform

On 05/03/2017 12:39 AM, Daniel Vetter wrote: > On Tue, May 02, 2017 at 09:22:13PM +0100, Chris Wilson wrote: >> On Tue, May 02, 2017 at 10:02:07AM -0700, Laura Abbott wrote: >>> /** >>> + * drm_gem_prime_import_platform - alternate implementation of the import >>> callback >>> + * @dev:

Re: [PATCHv3 2/3] drm/prime: Introduce drm_gem_prime_import_platform

On 05/03/2017 12:39 AM, Daniel Vetter wrote: > On Tue, May 02, 2017 at 09:22:13PM +0100, Chris Wilson wrote: >> On Tue, May 02, 2017 at 10:02:07AM -0700, Laura Abbott wrote: >>> /** >>> + * drm_gem_prime_import_platform - alternate implementation of the import >>> callback >>> + * @dev:

Re: [PATCH v4] platform/x86: ideapad-laptop: Add sysfs interface for touchpad state

Resending again, as Google servers are behaving weird lately. On Sun, 2017-04-30 at 15:54 +0300, Andy Shevchenko wrote: > > > the main issue that driver doesn't > > > send SW_TABLET_MODE event through input device. > > > > Well. Yes. That is one part. If SW_TABLET_MODE is done in the driver,

Re: [PATCH v4] platform/x86: ideapad-laptop: Add sysfs interface for touchpad state

Resending again, as Google servers are behaving weird lately. On Sun, 2017-04-30 at 15:54 +0300, Andy Shevchenko wrote: > > > the main issue that driver doesn't > > > send SW_TABLET_MODE event through input device. > > > > Well. Yes. That is one part. If SW_TABLET_MODE is done in the driver,

Re: I'd like to donate a MacBook Pro

2017-05-03 5:58 GMT-06:00 Greg KH : > On Tue, May 02, 2017 at 10:55:09PM -0600, Alex Henrie wrote: >> Today I ran a regression test to determine which commit made the >> keyboard stop working entirely. The last commit that worked for me was >>

Re: I'd like to donate a MacBook Pro

2017-05-03 5:58 GMT-06:00 Greg KH : > On Tue, May 02, 2017 at 10:55:09PM -0600, Alex Henrie wrote: >> Today I ran a regression test to determine which commit made the >> keyboard stop working entirely. The last commit that worked for me was >> c09e22d5370739e16463c113525df51b5980b1d5. After that,

Re: [v2 3/5] mm: add "zero" argument to vmemmap allocators

From: Pavel Tatashin Date: Fri, 24 Mar 2017 15:19:50 -0400 > Allow clients to request non-zeroed memory from vmemmap allocator. > The following two public function have a new boolean argument called zero: > > __vmemmap_alloc_block_buf() > vmemmap_alloc_block() > >

Re: [v2 3/5] mm: add "zero" argument to vmemmap allocators

From: Pavel Tatashin Date: Fri, 24 Mar 2017 15:19:50 -0400 > Allow clients to request non-zeroed memory from vmemmap allocator. > The following two public function have a new boolean argument called zero: > > __vmemmap_alloc_block_buf() > vmemmap_alloc_block() > > When zero is true, memory

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On 05/03/2017 04:26 PM, Marek Vasut wrote: > On 05/03/2017 03:57 PM, Shawn Guo wrote: >> On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: >>> On 04/25/2017 07:23 PM, Leonard Crestez wrote: Anyway, that version also sets the supply for reg_arm and reg_soc. It is not necessary

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On 05/03/2017 04:26 PM, Marek Vasut wrote: > On 05/03/2017 03:57 PM, Shawn Guo wrote: >> On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: >>> On 04/25/2017 07:23 PM, Leonard Crestez wrote: Anyway, that version also sets the supply for reg_arm and reg_soc. It is not necessary

Re: [PATCH 1/2] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

On Wed, May 03, 2017 at 12:36:06PM +0300, Laurent Pinchart wrote: > Hi Daniel, > > On Wednesday 03 May 2017 11:32:17 Daniel Vetter wrote: > > On Wed, May 03, 2017 at 02:53:00PM +0530, Archit Taneja wrote: > > > +panel/bridge reviewers. > > > > > > This does make things much cleaner, but it seems

Re: [PATCH 1/2] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

On Wed, May 03, 2017 at 12:36:06PM +0300, Laurent Pinchart wrote: > Hi Daniel, > > On Wednesday 03 May 2017 11:32:17 Daniel Vetter wrote: > > On Wed, May 03, 2017 at 02:53:00PM +0530, Archit Taneja wrote: > > > +panel/bridge reviewers. > > > > > > This does make things much cleaner, but it seems

Re: [tpmdd-devel] [PATCH 2/3] tpm: move ordinals definition to include/linux/tpm_command.h

On 5/3/2017 2:48 PM, Jarkko Sakkinen wrote: ORD ought not be used outside of drivers/char/tpm. TPM 1.2 trusted keys does use this header but it should be eventually moved to drivers/char/tpm (not done because of other stuff at this point). Ok. Then, I just move the ordinal conversion to the

Re: [tpmdd-devel] [PATCH 2/3] tpm: move ordinals definition to include/linux/tpm_command.h

On 5/3/2017 2:48 PM, Jarkko Sakkinen wrote: ORD ought not be used outside of drivers/char/tpm. TPM 1.2 trusted keys does use this header but it should be eventually moved to drivers/char/tpm (not done because of other stuff at this point). Ok. Then, I just move the ordinal conversion to the

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On 05/03/2017 03:57 PM, Shawn Guo wrote: > On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: >> On 04/25/2017 07:23 PM, Leonard Crestez wrote: >>> Anyway, that version also sets the supply for reg_arm and reg_soc. It >>> is not necessary for fixing the crash I'm seeing but is good

Re: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override

On 05/03/2017 03:57 PM, Shawn Guo wrote: > On Tue, Apr 25, 2017 at 07:28:06PM +0200, Marek Vasut wrote: >> On 04/25/2017 07:23 PM, Leonard Crestez wrote: >>> Anyway, that version also sets the supply for reg_arm and reg_soc. It >>> is not necessary for fixing the crash I'm seeing but is good

[PATCHv2 1/4] wlcore: add wl1285 compatible

Motorola Droid 4 uses a WL 1285C. With differences between chips not being public let's add explicit binding for wl1285 instead of relying on wl1283 being very similar. Signed-off-by: Sebastian Reichel ---

[PATCHv2 1/4] wlcore: add wl1285 compatible

Motorola Droid 4 uses a WL 1285C. With differences between chips not being public let's add explicit binding for wl1285 instead of relying on wl1283 being very similar. Signed-off-by: Sebastian Reichel --- Documentation/devicetree/bindings/net/wireless/ti,wlcore.txt | 1 +

Re: [linux-sunxi] Designware UART bug

On Wed, May 3, 2017 at 4:26 AM, Olliver Schinagl wrote: > Hey Chen-Yu > > On 03-05-17 12:40, Chen-Yu Tsai wrote: >> >> On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl >> wrote: >>> >>> Hey Jamie, >>> >>> Several years ago you wrote the glue-code [0] for

Re: [linux-sunxi] Designware UART bug

On Wed, May 3, 2017 at 4:26 AM, Olliver Schinagl wrote: > Hey Chen-Yu > > On 03-05-17 12:40, Chen-Yu Tsai wrote: >> >> On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl >> wrote: >>> >>> Hey Jamie, >>> >>> Several years ago you wrote the glue-code [0] for the DW 8250 IP. Over >>> the >>> years

[PATCHv2 4/4] ARM: dts: omap4-droid4: Add bluetooth

Droid 4 has WL 1285C connected to the OMAP's UART4 port, which is used for Bluetooth and most likely can also be used for controlling the FM radio and GPS receivers. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap4-droid4-xt894.dts | 20

[PATCHv2 4/4] ARM: dts: omap4-droid4: Add bluetooth

Droid 4 has WL 1285C connected to the OMAP's UART4 port, which is used for Bluetooth and most likely can also be used for controlling the FM radio and GPS receivers. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap4-droid4-xt894.dts | 20 1 file changed, 20

[PATCHv2 2/4] ARM: dts: omap4-droid4: Use wl1285 for wifi compatible

The Motorola Droid 4 uses a WL 1285C, so let's use correct compatible value instead of relying on WL 1283 being very similar. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap4-droid4-xt894.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCHv2 3/4] Bluetooth: hci_ll: Add compatible values for more WL chips

Add compatible values for WiLink chips from 128x and 180x series. Also the DT binding already contained compatible values for the 127x series, but the driver did not. This brings the list on par with the list from wlcore (the wifi driver). Signed-off-by: Sebastian Reichel

[PATCHv2 2/4] ARM: dts: omap4-droid4: Use wl1285 for wifi compatible

The Motorola Droid 4 uses a WL 1285C, so let's use correct compatible value instead of relying on WL 1283 being very similar. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/omap4-droid4-xt894.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCHv2 3/4] Bluetooth: hci_ll: Add compatible values for more WL chips

Add compatible values for WiLink chips from 128x and 180x series. Also the DT binding already contained compatible values for the 127x series, but the driver did not. This brings the list on par with the list from wlcore (the wifi driver). Signed-off-by: Sebastian Reichel ---

[PATCHv2 0/4] Motorola Droid 4: Add WL1285C support

Hi, Motorola Droid 4 uses a WL1285C, as visible on iFixit [0]. This fixes the DT file to use correct compatible for the wifi node and adds the bluetooth node. [0] https://www.ifixit.com/Teardown/Motorola+Droid+4+Teardown/7759#s31961 Changes to PATCHv1: - use proper compatible value for

[PATCHv2 0/4] Motorola Droid 4: Add WL1285C support

Hi, Motorola Droid 4 uses a WL1285C, as visible on iFixit [0]. This fixes the DT file to use correct compatible for the wifi node and adds the bluetooth node. [0] https://www.ifixit.com/Teardown/Motorola+Droid+4+Teardown/7759#s31961 Changes to PATCHv1: - use proper compatible value for

[RFC PATCH v2 1/9] debugfs: add support for more elaborate ->d_fsdata

Currently, the user provided fops, "real_fops", are stored directly into ->d_fsdata. In order to be able to store more per-file state and thus prepare for more granular file removal protection, wrap the real_fops into a dynamically allocated container struct, debugfs_fsdata. A struct

[RFC PATCH v2 1/9] debugfs: add support for more elaborate ->d_fsdata

Currently, the user provided fops, "real_fops", are stored directly into ->d_fsdata. In order to be able to store more per-file state and thus prepare for more granular file removal protection, wrap the real_fops into a dynamically allocated container struct, debugfs_fsdata. A struct

Re: [PATCH v4] fpga manager: Add Altera CvP driver

On Tue, May 2, 2017 at 7:14 PM, Anatolij Gustschin wrote: > On Wed, 3 May 2017 00:28:17 +0300 > Andy Shevchenko andy.shevche...@gmail.com wrote: > ... Is 0xff a mask here? (Btw, you missed spaces around <<) >>> >>> yes, it is. Will add spaces (checkpatch didn't warn here). >>

Re: [PATCH v4] fpga manager: Add Altera CvP driver

On Tue, May 2, 2017 at 7:14 PM, Anatolij Gustschin wrote: > On Wed, 3 May 2017 00:28:17 +0300 > Andy Shevchenko andy.shevche...@gmail.com wrote: > ... Is 0xff a mask here? (Btw, you missed spaces around <<) >>> >>> yes, it is. Will add spaces (checkpatch didn't warn here). >> >>Then it makes

RE: [PATCH] ASoC: da7218: Fix incorrect usage of bitwise '&' operator for SRM check

On 03 May 2017 15:10, Takashi Sakamoto wrote: > On May 3 2017 22:54, Adam Thomson wrote: > > In the SRM lock check section of code the '&' bitwise operator is > > used as part of checking lock status. Functionally the code works > > as intended, but the conditional statement is a boolean

RE: [PATCH] ASoC: da7218: Fix incorrect usage of bitwise '&' operator for SRM check

On 03 May 2017 15:10, Takashi Sakamoto wrote: > On May 3 2017 22:54, Adam Thomson wrote: > > In the SRM lock check section of code the '&' bitwise operator is > > used as part of checking lock status. Functionally the code works > > as intended, but the conditional statement is a boolean

[RFC PATCH v2 7/9] debugfs: call debugfs_real_fops() only after debugfs_file_get()

The current implementation of debugfs_real_fops() relies on a debugfs_fsdata instance to be installed at ->d_fsdata. With future patches introducing lazy allocation of these, this requirement will be guaranteed to be fullfilled only inbetween a debugfs_file_get()/debugfs_file_put() pair. The

[PATCH 2/2] kvm: arm/arm64: Fix use after free of stage2 page table

We yield the kvm->mmu_lock occassionaly while performing an operation (e.g, unmap or permission changes) on a large area of stage2 mappings. However this could possibly cause another thread to clear and free up the stage2 page tables while we were waiting for regaining the lock and thus the

[RFC PATCH v2 7/9] debugfs: call debugfs_real_fops() only after debugfs_file_get()

The current implementation of debugfs_real_fops() relies on a debugfs_fsdata instance to be installed at ->d_fsdata. With future patches introducing lazy allocation of these, this requirement will be guaranteed to be fullfilled only inbetween a debugfs_file_get()/debugfs_file_put() pair. The

[PATCH 2/2] kvm: arm/arm64: Fix use after free of stage2 page table

We yield the kvm->mmu_lock occassionaly while performing an operation (e.g, unmap or permission changes) on a large area of stage2 mappings. However this could possibly cause another thread to clear and free up the stage2 page tables while we were waiting for regaining the lock and thus the

[PATCH 1/2] kvm: arm/arm64: Fix race in resetting stage2 PGD

In kvm_free_stage2_pgd() we check the stage2 PGD before holding the lock and proceed to take the lock if it is valid. And we unmap the page tables, followed by releasing the lock. We reset the PGD only after dropping this lock, which could cause a race condition where another thread waiting on or

[PATCH 1/2] kvm: arm/arm64: Fix race in resetting stage2 PGD

In kvm_free_stage2_pgd() we check the stage2 PGD before holding the lock and proceed to take the lock if it is valid. And we unmap the page tables, followed by releasing the lock. We reset the PGD only after dropping this lock, which could cause a race condition where another thread waiting on or

[RFC PATCH v2 9/9] debugfs: free debugfs_fsdata instances

Currently, a dentry's debugfs_fsdata instance is allocated from debugfs_file_get() at first usage, i.e. at first file opening. It won't ever get freed though. Ideally, these instances would get freed after the last open file handle gets closed again, that is from the fops' ->release().

[RFC PATCH v2 8/9] debugfs: defer debugfs_fsdata allocation to first usage

Currently, __debugfs_create_file allocates one struct debugfs_fsdata instance for every file created. However, there are potentially many debugfs file around, most of which are never touched by userspace. Thus, defer the allocations to the first usage, i.e. to the first debugfs_file_get(). A

[GIT PULL] Audit patches for v4.12

Hi Linus, Fourteen audit patches for v4.12 that span the full range of fixes, new features, and internal cleanups. We have a patches to move to 64-bit timestamps, convert refcounts from atomic_t to refcount_t, track PIDs using the pid struct instead of pid_t, convert our own private audit buffer

[RFC PATCH v2 9/9] debugfs: free debugfs_fsdata instances

Currently, a dentry's debugfs_fsdata instance is allocated from debugfs_file_get() at first usage, i.e. at first file opening. It won't ever get freed though. Ideally, these instances would get freed after the last open file handle gets closed again, that is from the fops' ->release().

[RFC PATCH v2 8/9] debugfs: defer debugfs_fsdata allocation to first usage

Currently, __debugfs_create_file allocates one struct debugfs_fsdata instance for every file created. However, there are potentially many debugfs file around, most of which are never touched by userspace. Thus, defer the allocations to the first usage, i.e. to the first debugfs_file_get(). A

[GIT PULL] Audit patches for v4.12

Hi Linus, Fourteen audit patches for v4.12 that span the full range of fixes, new features, and internal cleanups. We have a patches to move to 64-bit timestamps, convert refcounts from atomic_t to refcount_t, track PIDs using the pid struct instead of pid_t, convert our own private audit buffer

[PATCHv2 0/2] kvm: arm/arm64: Fixes for race conditions

These two patches fixes race conditions in the stage2 page table handling of the KVM on arm/arm64. Applies on next-20170503. Changes since v1: http://lists.infradead.org/pipermail/linux-arm-kernel/2017-April/502867.html - Dropped patch for fixing mmu_notifier race condition, which couldn't

[PATCHv2 0/2] kvm: arm/arm64: Fixes for race conditions

These two patches fixes race conditions in the stage2 page table handling of the KVM on arm/arm64. Applies on next-20170503. Changes since v1: http://lists.infradead.org/pipermail/linux-arm-kernel/2017-April/502867.html - Dropped patch for fixing mmu_notifier race condition, which couldn't

[RFC PATCH v2 2/9] debugfs: implement per-file removal protection

Since commit 49d200deaa68 ("debugfs: prevent access to removed files' private data"), accesses to a file's private data are protected from concurrent removal by covering all file_operations with a SRCU read section and sychronizing with those before returning from debugfs_remove() by means of

[RFC PATCH v2 2/9] debugfs: implement per-file removal protection

Since commit 49d200deaa68 ("debugfs: prevent access to removed files' private data"), accesses to a file's private data are protected from concurrent removal by covering all file_operations with a SRCU read section and sychronizing with those before returning from debugfs_remove() by means of

[RFC PATCH v2 4/9] debugfs: convert to debugfs_file_get() and -put()

Convert all calls to the now obsolete debugfs_use_file_start() and debugfs_use_file_finish() from the debugfs core itself to the new debugfs_file_get() and debugfs_file_put() API. Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private data") Signed-off-by:

[RFC PATCH v2 4/9] debugfs: convert to debugfs_file_get() and -put()

Convert all calls to the now obsolete debugfs_use_file_start() and debugfs_use_file_finish() from the debugfs core itself to the new debugfs_file_get() and debugfs_file_put() API. Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private data") Signed-off-by:

[RFC PATCH v2 5/9] IB/hfi1: convert to debugfs_file_get() and -put()

Convert all calls to the now obsolete debugfs_use_file_start() and debugfs_use_file_finish() to the new debugfs_file_get() and debugfs_file_put() API. Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private data") Signed-off-by: Nicolai Stange

[RFC PATCH v2 5/9] IB/hfi1: convert to debugfs_file_get() and -put()

Convert all calls to the now obsolete debugfs_use_file_start() and debugfs_use_file_finish() to the new debugfs_file_get() and debugfs_file_put() API. Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private data") Signed-off-by: Nicolai Stange ---

[RFC PATCH v2 3/9] debugfs: debugfs_real_fops(): drop __must_hold sparse annotation

Currently, debugfs_real_fops() is annotated with a __must_hold(_srcu) sparse annotation. With the conversion of the SRCU based protection of users against concurrent file removals to a per-file refcount based scheme, this becomes wrong. Drop this annotation. Signed-off-by: Nicolai Stange

[RFC PATCH v2 6/9] debugfs: purge obsolete SRCU based removal protection

Purge the SRCU based file removal race protection in favour of the new, refcount based debugfs_file_get()/debugfs_file_put() API. Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private data") Signed-off-by: Nicolai Stange ---

[RFC PATCH v2 3/9] debugfs: debugfs_real_fops(): drop __must_hold sparse annotation

Currently, debugfs_real_fops() is annotated with a __must_hold(_srcu) sparse annotation. With the conversion of the SRCU based protection of users against concurrent file removals to a per-file refcount based scheme, this becomes wrong. Drop this annotation. Signed-off-by: Nicolai Stange ---

[RFC PATCH v2 6/9] debugfs: purge obsolete SRCU based removal protection

Purge the SRCU based file removal race protection in favour of the new, refcount based debugfs_file_get()/debugfs_file_put() API. Fixes: 49d200deaa68 ("debugfs: prevent access to removed files' private data") Signed-off-by: Nicolai Stange --- fs/debugfs/file.c | 48

[RFC PATCH v2 0/9] debugfs: per-file removal protection

Hello Greg, this is the second attempt to implement debugfs file removal protection at file granularity. The first one can be found at [1]. Note that I left out the IB/hfi1 people from the get_maintainer list and thus, sent this in RFC mode only because the following still needs to get sorted

[RFC PATCH v2 0/9] debugfs: per-file removal protection

Hello Greg, this is the second attempt to implement debugfs file removal protection at file granularity. The first one can be found at [1]. Note that I left out the IB/hfi1 people from the get_maintainer list and thus, sent this in RFC mode only because the following still needs to get sorted

Re: [PATCH 1/2] drm: Introduce crtc->mode_valid() callback

Hi Daniel, On 03-05-2017 07:19, Daniel Vetter wrote: > On Tue, May 2, 2017 at 11:29 AM, Jose Abreu wrote: >> On 02-05-2017 09:48, Daniel Vetter wrote: >>> On Wed, Apr 26, 2017 at 11:48:34AM +0100, Jose Abreu wrote: Some crtc's may have restrictions in the mode they

Re: [PATCH 1/2] drm: Introduce crtc->mode_valid() callback

Hi Daniel, On 03-05-2017 07:19, Daniel Vetter wrote: > On Tue, May 2, 2017 at 11:29 AM, Jose Abreu wrote: >> On 02-05-2017 09:48, Daniel Vetter wrote: >>> On Wed, Apr 26, 2017 at 11:48:34AM +0100, Jose Abreu wrote: Some crtc's may have restrictions in the mode they can display. In

Re: [PATCH] net/sched: remove redundant null check on head

Wed, May 03, 2017 at 03:50:40PM CEST, colin.k...@canonical.com wrote: >From: Colin Ian King > >head is previously null checked and so the 2nd null check on head >is redundant and therefore can be removed. > >Detected by CoverityScan, CID#1399505 ("Logically dead code") >

Re: [PATCH] net/sched: remove redundant null check on head

Wed, May 03, 2017 at 03:50:40PM CEST, colin.k...@canonical.com wrote: >From: Colin Ian King > >head is previously null checked and so the 2nd null check on head >is redundant and therefore can be removed. > >Detected by CoverityScan, CID#1399505 ("Logically dead code") > >Signed-off-by: Colin Ian

Re: [PATCH] ARM: imx_v6_v7_defconfig: Enable cpufreq governors

On Tue, May 02, 2017 at 05:46:00PM +0300, Leonard Crestez wrote: > Enable more common cpufreq governors in imx defconfig because this is > very useful for testing. In particular you can't use cpufreq-set -f > $FREQ without explicitly defining CONFIG_CPU_FREQ_GOV_USERSPACE=y. > > Signed-off-by:

Re: [PATCH] ARM: imx_v6_v7_defconfig: Enable cpufreq governors

On Tue, May 02, 2017 at 05:46:00PM +0300, Leonard Crestez wrote: > Enable more common cpufreq governors in imx defconfig because this is > very useful for testing. In particular you can't use cpufreq-set -f > $FREQ without explicitly defining CONFIG_CPU_FREQ_GOV_USERSPACE=y. > > Signed-off-by:

Re: [PATCH] arm64: Do not leave an invalid area->pages pointer in dma_common_contiguous_remap()

On Wed, May 03, 2017 at 01:10:26PM +0100, Robin Murphy wrote: > On 25/04/17 19:22, Catalin Marinas wrote: > > The dma_common_pages_remap() function allocates a vm_struct object and > > initialises the pages pointer to value passed as argument. However, when > > this function is called

Re: [PATCH] arm64: Do not leave an invalid area->pages pointer in dma_common_contiguous_remap()

On Wed, May 03, 2017 at 01:10:26PM +0100, Robin Murphy wrote: > On 25/04/17 19:22, Catalin Marinas wrote: > > The dma_common_pages_remap() function allocates a vm_struct object and > > initialises the pages pointer to value passed as argument. However, when > > this function is called

Re: [PATCH] netfilter: conntrack: Force inlining of build check to prevent build failure

On Wed, May 03, 2017 at 09:55:16AM -0400, David Miller wrote: > From: Geert Uytterhoeven > Date: Wed, 3 May 2017 14:18:43 +0200 > > > If gcc (e.g. 4.1.2) decides not to inline total_extension_size(), the > > build will fail with: > > > > net/built-in.o: In function

Re: [PATCH] netfilter: conntrack: Force inlining of build check to prevent build failure

On Wed, May 03, 2017 at 09:55:16AM -0400, David Miller wrote: > From: Geert Uytterhoeven > Date: Wed, 3 May 2017 14:18:43 +0200 > > > If gcc (e.g. 4.1.2) decides not to inline total_extension_size(), the > > build will fail with: > > > > net/built-in.o: In function

Re: [PATCH] ASoC: da7218: Fix incorrect usage of bitwise '&' operator for SRM check

On May 3 2017 22:54, Adam Thomson wrote: > In the SRM lock check section of code the '&' bitwise operator is > used as part of checking lock status. Functionally the code works > as intended, but the conditional statement is a boolean comparison > so should really use '&&' logical operator

Re: [PATCH] ASoC: da7218: Fix incorrect usage of bitwise '&' operator for SRM check

On May 3 2017 22:54, Adam Thomson wrote: > In the SRM lock check section of code the '&' bitwise operator is > used as part of checking lock status. Functionally the code works > as intended, but the conditional statement is a boolean comparison > so should really use '&&' logical operator

[PATCH] tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() (Was: Re: [PATCH] tracing: Resolve stack corruption due to string copy)

[ Here's the new patch ] From: Amey Telawane Strcpy is inherently not safe, and strlcpy() should be used instead. __trace_find_cmdline() uses strcpy() because the comms saved must have a terminating nul character, but it doesn't hurt to add the extra protection of using

[PATCH] tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline() (Was: Re: [PATCH] tracing: Resolve stack corruption due to string copy)

[ Here's the new patch ] From: Amey Telawane Strcpy is inherently not safe, and strlcpy() should be used instead. __trace_find_cmdline() uses strcpy() because the comms saved must have a terminating nul character, but it doesn't hurt to add the extra protection of using strlcpy() instead of

Re: [PATCH 0/2] ASoC: sunxi: Add ADC support for A33

Hello, On 03/05/2017 15:56, Mylène Josserand wrote: Hello everyone, This is a first version of a serie to add ADC support for Sun8i-A33. Based on asoc/for-next branch, last commit: 20d5c84bef067b7e804a163e2abca16c47125bad. The first patch adds the support of ADC and microphones in the digital

Re: [PATCH 0/2] ASoC: sunxi: Add ADC support for A33

Hello, On 03/05/2017 15:56, Mylène Josserand wrote: Hello everyone, This is a first version of a serie to add ADC support for Sun8i-A33. Based on asoc/for-next branch, last commit: 20d5c84bef067b7e804a163e2abca16c47125bad. The first patch adds the support of ADC and microphones in the digital

Hello My name is Casperina Litaay. I suffer from throat cancer, I am childless. I plan to make a donation of my property because I am sick and my doctor told me that I would not survive the next two m

Hello My name is Casperina Litaay. I suffer from throat cancer, I am childless. I plan to make a donation of my property because I am sick and my doctor told me that I would not survive the next two m

[PATCH 09/10] perf symbols: Allow user probes on versioned symbols

From: Paul Clarke Symbol versioning, as in glibc, results in symbols being defined as: @[@] (Note that "@@" identifies a default symbol, if the symbol name is repeated.) perf is currently unable to deal with this, and is unable to create user probes at such symbols: --

[PATCH 09/10] perf symbols: Allow user probes on versioned symbols

From: Paul Clarke Symbol versioning, as in glibc, results in symbols being defined as: @[@] (Note that "@@" identifies a default symbol, if the symbol name is repeated.) perf is currently unable to deal with this, and is unable to create user probes at such symbols: -- $ nm

[GIT PULL 00/10] perf/core improvements and fixes

into perf/core (2017-04-24 23:31:35 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-4.12-20170503 for you to fetch changes up to 4341ec6b3db4c3e903d6c44958722918baec1e59: perf config: Refactor a duplicated

[GIT PULL 00/10] perf/core improvements and fixes

into perf/core (2017-04-24 23:31:35 +0200) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo-4.12-20170503 for you to fetch changes up to 4341ec6b3db4c3e903d6c44958722918baec1e59: perf config: Refactor a duplicated

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