A few more filesystem encryption questions

Hello, A few more questions about the new filesystem encryption code: I found that a process without access to the master encryption key can read a file's full decrypted contents, provided that the file was opened recently by a process with access to the key. This is true even if the privileged

A few more filesystem encryption questions

Hello, A few more questions about the new filesystem encryption code: I found that a process without access to the master encryption key can read a file's full decrypted contents, provided that the file was opened recently by a process with access to the key. This is true even if the privileged

Re: [PATCH 0/3] mm/mmap.c: don't unmap the overlapping VMA(s)

On Sat, Apr 2, 2016 at 10:17 PM, Piotr Kwapulinski wrote: > Currently the mmap(MAP_FIXED) discards the overlapping part of the > existing VMA(s). > Introduce the new MAP_DONTUNMAP flag which forces the mmap to fail > with ENOMEM whenever the overlapping occurs and

Re: [PATCH 0/3] mm/mmap.c: don't unmap the overlapping VMA(s)

On Sat, Apr 2, 2016 at 10:17 PM, Piotr Kwapulinski wrote: > Currently the mmap(MAP_FIXED) discards the overlapping part of the > existing VMA(s). > Introduce the new MAP_DONTUNMAP flag which forces the mmap to fail > with ENOMEM whenever the overlapping occurs and MAP_FIXED is set. > No existing

[PATCH] mm/mmap: kill hook arch_rebalance_pgtables

Nobody use it. Signed-off-by: Konstantin Khlebnikov --- mm/mmap.c |5 - 1 file changed, 5 deletions(-) diff --git a/mm/mmap.c b/mm/mmap.c index bd2e1a533bc1..fba246b8f1a5 100644 --- a/mm/mmap.c +++ b/mm/mmap.c @@ -55,10 +55,6 @@ #define arch_mmap_check(addr, len,

[PATCH] mm/mmap: kill hook arch_rebalance_pgtables

Nobody use it. Signed-off-by: Konstantin Khlebnikov --- mm/mmap.c |5 - 1 file changed, 5 deletions(-) diff --git a/mm/mmap.c b/mm/mmap.c index bd2e1a533bc1..fba246b8f1a5 100644 --- a/mm/mmap.c +++ b/mm/mmap.c @@ -55,10 +55,6 @@ #define arch_mmap_check(addr, len, flags) (0)

[PATCH 06/13] fscrypto: crypto_alloc_skcipher() always returns an ERR_PTR(), never NULL

Signed-off-by: Eric Biggers --- fs/crypto/keyinfo.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/crypto/keyinfo.c b/fs/crypto/keyinfo.c index 33296c0..cb06351 100644 --- a/fs/crypto/keyinfo.c +++ b/fs/crypto/keyinfo.c @@ -208,8 +208,8 @@ retry:

[PATCH 01/13] fscrypto: remove unnecessary includes

Signed-off-by: Eric Biggers --- fs/crypto/crypto.c | 1 - fs/crypto/fname.c | 2 -- fs/crypto/keyinfo.c | 3 --- 3 files changed, 6 deletions(-) diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c index 06cd1a2..2c7923d 100644 --- a/fs/crypto/crypto.c +++

[PATCH 05/13] fscrypto: comment improvements and fixes

Signed-off-by: Eric Biggers --- fs/crypto/crypto.c | 13 ++-- fs/crypto/fname.c| 33 ++ fs/crypto/keyinfo.c | 8 include/linux/fscrypto.h | 53 ++-- 4 files changed,

[PATCH 06/13] fscrypto: crypto_alloc_skcipher() always returns an ERR_PTR(), never NULL

Signed-off-by: Eric Biggers --- fs/crypto/keyinfo.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/crypto/keyinfo.c b/fs/crypto/keyinfo.c index 33296c0..cb06351 100644 --- a/fs/crypto/keyinfo.c +++ b/fs/crypto/keyinfo.c @@ -208,8 +208,8 @@ retry: goto

[PATCH 01/13] fscrypto: remove unnecessary includes

Signed-off-by: Eric Biggers --- fs/crypto/crypto.c | 1 - fs/crypto/fname.c | 2 -- fs/crypto/keyinfo.c | 3 --- 3 files changed, 6 deletions(-) diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c index 06cd1a2..2c7923d 100644 --- a/fs/crypto/crypto.c +++ b/fs/crypto/crypto.c @@ -27,7 +27,6

[PATCH 05/13] fscrypto: comment improvements and fixes

Signed-off-by: Eric Biggers --- fs/crypto/crypto.c | 13 ++-- fs/crypto/fname.c| 33 ++ fs/crypto/keyinfo.c | 8 include/linux/fscrypto.h | 53 ++-- 4 files changed, 90 insertions(+), 17

fs/xfs/xfs_ondisk.h:86:2: error: call to '__compiletime_assert_86' declared with attribute error: XFS: sizeof(xfs_dir2_data_unused_t) is wrong, expected 6

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: ab9d1e4f7b0217948a3b35a64178602ab30ff45d Merge branch 'xfs-misc-fixes-4.6-3' into for-next date: 4 weeks

fs/xfs/xfs_ondisk.h:86:2: error: call to '__compiletime_assert_86' declared with attribute error: XFS: sizeof(xfs_dir2_data_unused_t) is wrong, expected 6

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: ab9d1e4f7b0217948a3b35a64178602ab30ff45d Merge branch 'xfs-misc-fixes-4.6-3' into for-next date: 4 weeks

[PATCH 02/13] fscrypto: rename some functions for clarity

Rename fscrypt_complete() to page_crypt_complete(). This callback is specifically for data pages; fscrypto also performs filename encryption. Rename dir_crypt_complete() to fname_crypt_complete(). This callback is also used for symlink targets, not just directory entries. Rename

[PATCH 00/13] fscrypto: cleanups and fixes

This patchset includes various cleanups for the new filesystem encryption code as well as some bug fixes for the FS_IOC_SET_ENCRYPTION_POLICY ioctl. Eric Biggers (13): fscrypto: remove unnecessary includes fscrypto: rename some functions for clarity fscrypto: rename functions to load and

[PATCH 04/13] fscrypto: return bool instead of int where appropriate

Signed-off-by: Eric Biggers --- fs/crypto/policy.c | 24 include/linux/fscrypto.h | 12 ++-- 2 files changed, 18 insertions(+), 18 deletions(-) diff --git a/fs/crypto/policy.c b/fs/crypto/policy.c index 03a2f50..93244b5 100644 ---

[PATCH 02/13] fscrypto: rename some functions for clarity

Rename fscrypt_complete() to page_crypt_complete(). This callback is specifically for data pages; fscrypto also performs filename encryption. Rename dir_crypt_complete() to fname_crypt_complete(). This callback is also used for symlink targets, not just directory entries. Rename

[PATCH 00/13] fscrypto: cleanups and fixes

This patchset includes various cleanups for the new filesystem encryption code as well as some bug fixes for the FS_IOC_SET_ENCRYPTION_POLICY ioctl. Eric Biggers (13): fscrypto: remove unnecessary includes fscrypto: rename some functions for clarity fscrypto: rename functions to load and

[PATCH 04/13] fscrypto: return bool instead of int where appropriate

Signed-off-by: Eric Biggers --- fs/crypto/policy.c | 24 include/linux/fscrypto.h | 12 ++-- 2 files changed, 18 insertions(+), 18 deletions(-) diff --git a/fs/crypto/policy.c b/fs/crypto/policy.c index 03a2f50..93244b5 100644 --- a/fs/crypto/policy.c +++

[PATCH 03/13] fscrypto: rename functions to load and unload inode encryption info

Perform the following renamings: fscrypt_get_encryption_info() => fscrypt_load_encryption_info() fscrypt_put_encryption_info() => fscrypt_unload_encryption_info() get_crypt_info => load_crypt_info() put_crypt_info() => free_crypt_info() The new names better

[PATCH 07/13] fscrypto: simplify building key descriptor string

Signed-off-by: Eric Biggers --- fs/crypto/keyinfo.c | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/fs/crypto/keyinfo.c b/fs/crypto/keyinfo.c index cb06351..5fcee4d 100644 --- a/fs/crypto/keyinfo.c +++ b/fs/crypto/keyinfo.c @@ -164,13 +164,8 @@

[PATCH 11/13] fscrypto: restrict setting encryption policy to inode owner

On a filesystem with encryption enabled, a user could set an encryption policy on any empty directory to which they have readonly access. This is a potential security issue since such a directory might be owned by another user, and the new encryption policy may prevent that user from creating

[PATCH 12/13] fscrypto: require write access to mount to set encryption policy

Since setting an encryption policy requires writing data to the filesystem, it should be guarded by mnt_want_write/mnt_drop_write. Otherwise, a user could cause a write to a readonly or frozen filesystem. Signed-off-by: Eric Biggers --- fs/crypto/policy.c | 11

[PATCH 07/13] fscrypto: simplify building key descriptor string

Signed-off-by: Eric Biggers --- fs/crypto/keyinfo.c | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/fs/crypto/keyinfo.c b/fs/crypto/keyinfo.c index cb06351..5fcee4d 100644 --- a/fs/crypto/keyinfo.c +++ b/fs/crypto/keyinfo.c @@ -164,13 +164,8 @@ retry:

[PATCH 11/13] fscrypto: restrict setting encryption policy to inode owner

On a filesystem with encryption enabled, a user could set an encryption policy on any empty directory to which they have readonly access. This is a potential security issue since such a directory might be owned by another user, and the new encryption policy may prevent that user from creating

[PATCH 12/13] fscrypto: require write access to mount to set encryption policy

Since setting an encryption policy requires writing data to the filesystem, it should be guarded by mnt_want_write/mnt_drop_write. Otherwise, a user could cause a write to a readonly or frozen filesystem. Signed-off-by: Eric Biggers --- fs/crypto/policy.c | 11 +-- fs/f2fs/file.c

[PATCH 03/13] fscrypto: rename functions to load and unload inode encryption info

Perform the following renamings: fscrypt_get_encryption_info() => fscrypt_load_encryption_info() fscrypt_put_encryption_info() => fscrypt_unload_encryption_info() get_crypt_info => load_crypt_info() put_crypt_info() => free_crypt_info() The new names better

[PATCH 13/13] fscrypto: improve error handling in fscrypt_set_policy()

In some cases, the previous code did not correctly propagate errors to the caller. Also, only one call to ->get_context() is required. Signed-off-by: Eric Biggers --- fs/crypto/policy.c | 64 +- 1 file changed, 29

[PATCH 09/13] fscrypto: make fname_encrypt() actually return length of ciphertext

This makes the return value match the comment. Previously it would actually return 0 if encryption was successful. (No callers currently care.) Signed-off-by: Eric Biggers --- fs/crypto/fname.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git

[PATCH 13/13] fscrypto: improve error handling in fscrypt_set_policy()

In some cases, the previous code did not correctly propagate errors to the caller. Also, only one call to ->get_context() is required. Signed-off-by: Eric Biggers --- fs/crypto/policy.c | 64 +- 1 file changed, 29 insertions(+), 35

[PATCH 09/13] fscrypto: make fname_encrypt() actually return length of ciphertext

This makes the return value match the comment. Previously it would actually return 0 if encryption was successful. (No callers currently care.) Signed-off-by: Eric Biggers --- fs/crypto/fname.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/fs/crypto/fname.c

[PATCH 08/13] fscrypto: use standard macros from kernel.h

Signed-off-by: Eric Biggers --- fs/crypto/fname.c | 17 + 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/fs/crypto/fname.c b/fs/crypto/fname.c index cd0eae8..e5c6959 100644 --- a/fs/crypto/fname.c +++ b/fs/crypto/fname.c @@ -14,11 +14,6 @@

[PATCH 08/13] fscrypto: use standard macros from kernel.h

Signed-off-by: Eric Biggers --- fs/crypto/fname.c | 17 + 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/fs/crypto/fname.c b/fs/crypto/fname.c index cd0eae8..e5c6959 100644 --- a/fs/crypto/fname.c +++ b/fs/crypto/fname.c @@ -14,11 +14,6 @@ #include #include

[PATCH 10/13] fscrypto: restrict setting new policy to empty files and directories only

On f2fs, a user could create a regular file of small positive size and issue FS_IOC_SET_ENCRYPTION_POLICY to set its encryption policy. However, this did not behave as expected because the existing data was not actually encrypted by the ioctl. Fix this by only permitting an encryption policy to

[PATCH 10/13] fscrypto: restrict setting new policy to empty files and directories only

On f2fs, a user could create a regular file of small positive size and issue FS_IOC_SET_ENCRYPTION_POLICY to set its encryption policy. However, this did not behave as expected because the existing data was not actually encrypted by the ioctl. Fix this by only permitting an encryption policy to

RE: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Saturday, April 2, 2016 6:48 PM > To: KY Srinivasan > Cc: o...@aepfle.de; jasow...@redhat.com; linux-kernel@vger.kernel.org; > a...@canonical.com; de...@linuxdriverproject.org > Subject:

RE: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Saturday, April 2, 2016 6:48 PM > To: KY Srinivasan > Cc: o...@aepfle.de; jasow...@redhat.com; linux-kernel@vger.kernel.org; > a...@canonical.com; de...@linuxdriverproject.org > Subject: Re: [PATCH 0/6]

include/linux/unaligned/access_ok.h:7:19: error: redefinition of 'get_unaligned_le16'

Hi Clément, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: dece45855a8b0d1dcf48eb01d0822070ded6a4c8 NFC: nxp-nci: Add support for NXP NCI chips date: 1 year ago

include/linux/unaligned/access_ok.h:7:19: error: redefinition of 'get_unaligned_le16'

Hi Clément, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: dece45855a8b0d1dcf48eb01d0822070ded6a4c8 NFC: nxp-nci: Add support for NXP NCI chips date: 1 year ago

Re: [PATCH 1/3 v2] drm/i2c/adv7511: Add audio support

Hi Jose, [auto build test ERROR on drm/drm-next] [also build test ERROR on v4.6-rc1 next-20160401] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [PATCH 1/3 v2] drm/i2c/adv7511: Add audio support

Hi Jose, [auto build test ERROR on drm/drm-next] [also build test ERROR on v4.6-rc1 next-20160401] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

drivers/infiniband/hw/mlx5/main.c:2357:31: error: 'mlx5_ib_get_vf_config' undeclared

Hi Eli, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: eff901d30e6cebd940072637f112ce4d0090ac12 IB/mlx5: Implement callbacks for manipulating VFs date: 12 days

drivers/infiniband/hw/mlx5/main.c:2357:31: error: 'mlx5_ib_get_vf_config' undeclared

Hi Eli, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: eff901d30e6cebd940072637f112ce4d0090ac12 IB/mlx5: Implement callbacks for manipulating VFs date: 12 days

[PATCH v14 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

This patch adds drm_bridge driver for parade DSI to eDP bridge chip. Signed-off-by: Jitao Shi Reviewed-by: Daniel Kurtz --- Changes since v13: - add const on data, ps8640_write_bytes(struct i2c_client *client, const u8 *data, u16 data_len) - fix

[PATCH v14 1/2] Documentation: bridge: Add documentation for ps8640 DT properties

Add documentation for DT properties supported by ps8640 DSI-eDP converter. Signed-off-by: Jitao Shi Acked-by: Rob Herring Reviewed-by: Philipp Zabel --- Changes since v13: - No change ---

[PATCH v14 1/2] Documentation: bridge: Add documentation for ps8640 DT properties

Add documentation for DT properties supported by ps8640 DSI-eDP converter. Signed-off-by: Jitao Shi Acked-by: Rob Herring Reviewed-by: Philipp Zabel --- Changes since v13: - No change --- .../devicetree/bindings/display/bridge/ps8640.txt | 43 1 file changed, 43

[PATCH v14 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

This patch adds drm_bridge driver for parade DSI to eDP bridge chip. Signed-off-by: Jitao Shi Reviewed-by: Daniel Kurtz --- Changes since v13: - add const on data, ps8640_write_bytes(struct i2c_client *client, const u8 *data, u16 data_len) - fix PAGE2_SW_REST tyro. - move the buf[3] init to

drivers/mfd/syscon.c:67:9: error: implicit declaration of function 'ioremap'

Hi Philipp, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: ca668f0edfae65438c3f0a3ad5d3e59e3515915f mfd: syscon: Set regmap max_register in of_syscon_register date:

drivers/mfd/syscon.c:67:9: error: implicit declaration of function 'ioremap'

Hi Philipp, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: ca668f0edfae65438c3f0a3ad5d3e59e3515915f mfd: syscon: Set regmap max_register in of_syscon_register date:

drivers/mfd/syscon.c:89:2: error: implicit declaration of function 'iounmap'

Hi Rob, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: 0166dc11be911213e0b1b764488c671be4c48cf3 of: make CONFIG_OF user selectable date: 10 months ago config:

drivers/mfd/syscon.c:89:2: error: implicit declaration of function 'iounmap'

Hi Rob, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f7eeb8a87c033d126ff6b8c35405ba5dc4e55754 commit: 0166dc11be911213e0b1b764488c671be4c48cf3 of: make CONFIG_OF user selectable date: 10 months ago config:

Re: [PATCH] ARM: dts: s3c: Fix DTC unit name warnings in S3C2416 and S3C6410

On Fri, Apr 01, 2016 at 04:22:59PM +0200, Joachim Eastwood wrote: > On 1 April 2016 at 09:11, Krzysztof Kozlowski wrote: > > Fix following DTC warnings in S3C2416 and S3C6410 boards: > > > > Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, > >

Re: [PATCH] ARM: dts: s3c: Fix DTC unit name warnings in S3C2416 and S3C6410

On Fri, Apr 01, 2016 at 04:22:59PM +0200, Joachim Eastwood wrote: > On 1 April 2016 at 09:11, Krzysztof Kozlowski wrote: > > Fix following DTC warnings in S3C2416 and S3C6410 boards: > > > > Warning (unit_address_vs_reg): Node /memory has a reg or ranges property, > > but no unit name > > > >

Re: [PATCH 01/11] ARM: dts: exynos: Fix DTC unit name warnings in cros-adc-thermistors

On Fri, Apr 01, 2016 at 10:31:34AM -0500, Rob Herring wrote: > On Fri, Apr 1, 2016 at 1:57 AM, Krzysztof Kozlowski > wrote: > > Fix following DTC warnings in cros-adc-thermistors: > > Warning (unit_address_vs_reg): Node /adc@12D1/ncp15wb473@3 has a unit > > name, but

Re: [PATCH 01/11] ARM: dts: exynos: Fix DTC unit name warnings in cros-adc-thermistors

On Fri, Apr 01, 2016 at 10:31:34AM -0500, Rob Herring wrote: > On Fri, Apr 1, 2016 at 1:57 AM, Krzysztof Kozlowski > wrote: > > Fix following DTC warnings in cros-adc-thermistors: > > Warning (unit_address_vs_reg): Node /adc@12D1/ncp15wb473@3 has a unit > > name, but no reg property > >

Re: [RT] Warning from swake_up_all_locked in rt-4.4.4-rt11

On Fri, 1 Apr 2016 12:33:18 +0200 Sebastian Andrzej Siewior wrote: > * Thomas Gleixner | 2016-03-14 09:49:52 [+0100]: > > >On Sun, 13 Mar 2016, Clark Williams wrote: > > > >> I'm hitting the WARN_ON(wakes > 2) in $SUBJECT when resuming from suspend > >> on my laptop

Re: [RT] Warning from swake_up_all_locked in rt-4.4.4-rt11

On Fri, 1 Apr 2016 12:33:18 +0200 Sebastian Andrzej Siewior wrote: > * Thomas Gleixner | 2016-03-14 09:49:52 [+0100]: > > >On Sun, 13 Mar 2016, Clark Williams wrote: > > > >> I'm hitting the WARN_ON(wakes > 2) in $SUBJECT when resuming from suspend > >> on my laptop (quad-core i7 with HT

[PATCH v2] PM / runtime: Document steps for device removal

Put a reminder that during device removal drivers should revert all PM runtime changes from the probe. Signed-off-by: Krzysztof Kozlowski --- Changes since v1: 1. Address Alan's comments. --- Documentation/power/runtime_pm.txt | 4 1 file changed, 4 insertions(+) diff

[PATCH v2] PM / runtime: Document steps for device removal

Put a reminder that during device removal drivers should revert all PM runtime changes from the probe. Signed-off-by: Krzysztof Kozlowski --- Changes since v1: 1. Address Alan's comments. --- Documentation/power/runtime_pm.txt | 4 1 file changed, 4 insertions(+) diff --git

Re: [PATCH 06/11] ARM: dts: exynos: Fix DTC unit name warnings in Exynos5250

On Fri, Apr 01, 2016 at 01:21:45PM -0400, Javier Martinez Canillas wrote: > > > > - usb@1200 { > > + usb_dwc3 { > > compatible = "samsung,exynos5250-dwusb3"; > > clocks = < CLK_USB3>; > > clock-names = "usbdrd30"; > > The ePAPR document says that "The

Re: [PATCH 06/11] ARM: dts: exynos: Fix DTC unit name warnings in Exynos5250

On Fri, Apr 01, 2016 at 01:21:45PM -0400, Javier Martinez Canillas wrote: > > > > - usb@1200 { > > + usb_dwc3 { > > compatible = "samsung,exynos5250-dwusb3"; > > clocks = < CLK_USB3>; > > clock-names = "usbdrd30"; > > The ePAPR document says that "The

[bisect] Merge tag 'mmc-v4.6' of git://git.linaro.org/people/ulf.hansson/mmc (was [GIT PULL] MMC for v.4.6)

On 03/21/2016 05:59 AM, Ulf Hansson wrote: > Hi Linus, > > Here's the PR for MMC v4.6. > > Details about the highlights are as usual found in the signed tag. > > Please pull this in! > > Kind regards > Ulf Hansson > > > The following changes since commit

[bisect] Merge tag 'mmc-v4.6' of git://git.linaro.org/people/ulf.hansson/mmc (was [GIT PULL] MMC for v.4.6)

On 03/21/2016 05:59 AM, Ulf Hansson wrote: > Hi Linus, > > Here's the PR for MMC v4.6. > > Details about the highlights are as usual found in the signed tag. > > Please pull this in! > > Kind regards > Ulf Hansson > > > The following changes since commit

Re: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

On Sat, Apr 02, 2016 at 11:46:21PM +, KY Srinivasan wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Saturday, April 2, 2016 3:23 PM > > To: KY Srinivasan > > Cc: linux-kernel@vger.kernel.org;

Re: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

On Sat, Apr 02, 2016 at 11:46:21PM +, KY Srinivasan wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Saturday, April 2, 2016 3:23 PM > > To: KY Srinivasan > > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; > >

Re: [GIT PULL] Thermal SoC management updates for v4.6-rc2

On Sat, Apr 02, 2016 at 08:09:08PM -0500, Linus Torvalds wrote: > On Sat, Apr 2, 2016 at 8:04 PM, Eduardo Valentin wrote: > > > > Please pull from > > > > git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal > > fixes > > > > to receive Thermal-SoC

Re: [GIT PULL] Thermal SoC management updates for v4.6-rc2

On Sat, Apr 02, 2016 at 08:09:08PM -0500, Linus Torvalds wrote: > On Sat, Apr 2, 2016 at 8:04 PM, Eduardo Valentin wrote: > > > > Please pull from > > > > git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal > > fixes > > > > to receive Thermal-SoC Management updates for

Hilsener.

God dag, Jeg trenger en utenlandsk partner for en gjensidig virksomhet forslag, som er relatert til overføring av en stor sum penger til en utenlandsk konto, som mottaker av midlene. Alt om denne transaksjonen vil bli gjort lovlig uten bro av økonomisk autoritet både i mitt land og yours.I

Hilsener.

God dag, Jeg trenger en utenlandsk partner for en gjensidig virksomhet forslag, som er relatert til overføring av en stor sum penger til en utenlandsk konto, som mottaker av midlene. Alt om denne transaksjonen vil bli gjort lovlig uten bro av økonomisk autoritet både i mitt land og yours.I

Re: [GIT PULL] Thermal SoC management updates for v4.6-rc2

On Sat, Apr 2, 2016 at 8:04 PM, Eduardo Valentin wrote: > > Please pull from > > git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal > fixes > > to receive Thermal-SoC Management updates for v4.6-rc2 with top-most This is not a "fixes" pull. This is

Re: [GIT PULL] Thermal SoC management updates for v4.6-rc2

On Sat, Apr 2, 2016 at 8:04 PM, Eduardo Valentin wrote: > > Please pull from > > git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal > fixes > > to receive Thermal-SoC Management updates for v4.6-rc2 with top-most This is not a "fixes" pull. This is a merge window pull,

[GIT PULL] Thermal SoC management updates for v4.6-rc2

Hello Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes to receive Thermal-SoC Management updates for v4.6-rc2 with top-most c960fe12d00275c52dffc0013d64c5a50538a74c: thermal: hisilicon: fix IRQ imbalance enabling (2016-03-29 08:43:02

[GIT PULL] Thermal SoC management updates for v4.6-rc2

Hello Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal fixes to receive Thermal-SoC Management updates for v4.6-rc2 with top-most c960fe12d00275c52dffc0013d64c5a50538a74c: thermal: hisilicon: fix IRQ imbalance enabling (2016-03-29 08:43:02

collect2: error: ld returned 1 exit status

Hi Anton, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d6c24df08255e24dbd19b52dd322f61fbc30b11d commit: 238abecde8ad43f914e095fcf23e0bd35dc7a7f2 powerpc: Don't use gcc specific options on clang date: 10 months

collect2: error: ld returned 1 exit status

Hi Anton, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d6c24df08255e24dbd19b52dd322f61fbc30b11d commit: 238abecde8ad43f914e095fcf23e0bd35dc7a7f2 powerpc: Don't use gcc specific options on clang date: 10 months

arch/xtensa/kernel/coprocessor.S:93: Error: invalid register number (240) for 'rur240'

Hi Piet, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d6c24df08255e24dbd19b52dd322f61fbc30b11d commit: 2c684d892bb2ee31cc48f4a8b91e86a0f15e82f9 xtensa: add Three Core HiFi-2 MX Variant. date: 2 weeks ago

arch/xtensa/kernel/coprocessor.S:93: Error: invalid register number (240) for 'rur240'

Hi Piet, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d6c24df08255e24dbd19b52dd322f61fbc30b11d commit: 2c684d892bb2ee31cc48f4a8b91e86a0f15e82f9 xtensa: add Three Core HiFi-2 MX Variant. date: 2 weeks ago

Re: [PATCH v2 net-next] net: hns: add support of pause frame ctrl for HNS V2

From: Yisen Zhuang Date: Thu, 31 Mar 2016 21:00:09 +0800 > From: Lisheng > > The patch adds support of pause ctrl for HNS V2, and this feature is lost > by HNS V1: >1) service ports can disable rx pause frame, >2) debug ports can

Re: [PATCH v2 net-next] net: hns: add support of pause frame ctrl for HNS V2

From: Yisen Zhuang Date: Thu, 31 Mar 2016 21:00:09 +0800 > From: Lisheng > > The patch adds support of pause ctrl for HNS V2, and this feature is lost > by HNS V1: >1) service ports can disable rx pause frame, >2) debug ports can open tx/rx pause frame. > > And this patch

Re: [PATCH] netlink: use nla_get_in_addr and nla_put_in_addr for ipv4 address

From: Haishuang Yan Date: Thu, 31 Mar 2016 18:21:38 +0800 > Since nla_get_in_addr and nla_put_in_addr were implemented, > so use them appropriately. > > Signed-off-by: Haishuang Yan Applied, thank you.

Re: [PATCH] netlink: use nla_get_in_addr and nla_put_in_addr for ipv4 address

From: Haishuang Yan Date: Thu, 31 Mar 2016 18:21:38 +0800 > Since nla_get_in_addr and nla_put_in_addr were implemented, > so use them appropriately. > > Signed-off-by: Haishuang Yan Applied, thank you.

Re: [PATCH 2/2] UBIFS: Implement ->migratepage()

Hi Kirill, [auto build test ERROR on v4.6-rc1] [also build test ERROR on next-20160401] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [PATCH 2/2] UBIFS: Implement ->migratepage()

Hi Kirill, [auto build test ERROR on v4.6-rc1] [also build test ERROR on next-20160401] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

{standard input}:116: Error: number (0x9000000080000000) larger than 32 bits

Hi Sasha, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 264800b5ecc7be49b2c6027738091ff3385e0cae commit: 71458cfc782eafe4b27656e078d379a34e472adf kernel: add support for gcc 5 date: 1 year, 6 months ago config:

{standard input}:116: Error: number (0x9000000080000000) larger than 32 bits

Hi Sasha, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 264800b5ecc7be49b2c6027738091ff3385e0cae commit: 71458cfc782eafe4b27656e078d379a34e472adf kernel: add support for gcc 5 date: 1 year, 6 months ago config:

arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_ovf_sar'

Hi Max, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 264800b5ecc7be49b2c6027738091ff3385e0cae commit: 9da8320bb97768e35f2e64fa7642015271d672eb xtensa: add test_kc705_hifi variant date: 2 weeks ago config:

arch/xtensa/kernel/coprocessor.S:93: Error: unknown opcode or format name 'rur.ae_ovf_sar'

Hi Max, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 264800b5ecc7be49b2c6027738091ff3385e0cae commit: 9da8320bb97768e35f2e64fa7642015271d672eb xtensa: add test_kc705_hifi variant date: 2 weeks ago config:

Re: [RFC patch 4/7] futex: Add support for attached futexes

On Sat, Apr 02 2016, Thomas Gleixner wrote: > The standard futex mechanism in the Linux kernel uses a global hash to store > transient state. Collisions on that hash can lead to performance degradation > and on real-time enabled kernels even to priority inversions. > > To

Re: [RFC patch 4/7] futex: Add support for attached futexes

On Sat, Apr 02 2016, Thomas Gleixner wrote: > The standard futex mechanism in the Linux kernel uses a global hash to store > transient state. Collisions on that hash can lead to performance degradation > and on real-time enabled kernels even to priority inversions. > > To guarantee futexes

RE: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Saturday, April 2, 2016 3:23 PM > To: KY Srinivasan > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; > o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com; >

RE: [PATCH 0/6] Drivers: hv: vmbus: Cleanup and mmio management.

> -Original Message- > From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Saturday, April 2, 2016 3:23 PM > To: KY Srinivasan > Cc: linux-kernel@vger.kernel.org; de...@linuxdriverproject.org; > o...@aepfle.de; a...@canonical.com; vkuzn...@redhat.com; > jasow...@redhat.com >

RE: Staging: unisys/verisonic: Correct double unlock

> -Original Message- > From: Iban Rodriguez [mailto:iban.rodrig...@ono.com] > Sent: Saturday, April 02, 2016 1:47 PM > To: Kershner, David A; Greg Kroah-Hartman; Benjamin Romer; Sell, Timothy > C; Neil Horman > Cc: *S-Par-Maintainer; de...@driverdev.osuosl.org; linux- >

RE: Staging: unisys/verisonic: Correct double unlock

> -Original Message- > From: Iban Rodriguez [mailto:iban.rodrig...@ono.com] > Sent: Saturday, April 02, 2016 1:47 PM > To: Kershner, David A; Greg Kroah-Hartman; Benjamin Romer; Sell, Timothy > C; Neil Horman > Cc: *S-Par-Maintainer; de...@driverdev.osuosl.org; linux- >

[PATCH 1/6] Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer

Introduce separate functions for estimating how much can be read from and written to the ring buffer. Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 25 - include/linux/hyperv.h | 27 +++ 2 files changed,

[PATCH 4/6] Drivers: hv: vmbus: Export the vmbus_set_event() API

In preparation for moving some ring buffer functionality out of the vmbus driver, export the API for signaling the host. Signed-off-by: K. Y. Srinivasan --- drivers/hv/connection.c |1 + drivers/hv/hyperv_vmbus.h |2 -- include/linux/hyperv.h|1 + 3 files

[PATCH 1/6] Drivers: hv: vmbus: Introduce functions for estimating room in the ring buffer

Introduce separate functions for estimating how much can be read from and written to the ring buffer. Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 25 - include/linux/hyperv.h | 27 +++ 2 files changed, 31 insertions(+), 21

[PATCH 4/6] Drivers: hv: vmbus: Export the vmbus_set_event() API

In preparation for moving some ring buffer functionality out of the vmbus driver, export the API for signaling the host. Signed-off-by: K. Y. Srinivasan --- drivers/hv/connection.c |1 + drivers/hv/hyperv_vmbus.h |2 -- include/linux/hyperv.h|1 + 3 files changed, 2

[PATCH 5/6] Drivers: hv: vmbus: Move some ring buffer functions to hyperv.h

In preparation for implementing APIs for in-place consumption of VMBUS packets, movve some ring buffer functionality into hyperv.h Signed-off-by: K. Y. Srinivasan --- drivers/hv/ring_buffer.c | 55 -- include/linux/hyperv.h |

[PATCH 6/6] Drivers: hv: vmbus: Implement APIs to support "in place" consumption of vmbus packets

Implement APIs for in-place consumption of vmbus packets. Currently, each packet is copied and processed one at a time and as part of processing each packet we potentially may signal the host (if it is waiting for room to produce a packet). These APIs help batched in-place processing of vmbus

  1   2   3   4   5   >