Re: [drm:qxl] BUG: sleeping function called from invalid context - qxl_bo_kmap_atomic_page()...splat

On Tue, 2017-05-09 at 04:37 +0200, Mike Galbraith wrote: > On Mon, 2017-05-08 at 16:48 -0300, Gabriel Krisman Bertazi wrote: > > > Thanks for reporting this. Can you confirm the following patch prevents > > the issue? > > Nope, it still gripes. The reason for this gripe is that we find that we

Re: [drm:qxl] BUG: sleeping function called from invalid context - qxl_bo_kmap_atomic_page()...splat

On Tue, 2017-05-09 at 04:37 +0200, Mike Galbraith wrote: > On Mon, 2017-05-08 at 16:48 -0300, Gabriel Krisman Bertazi wrote: > > > Thanks for reporting this. Can you confirm the following patch prevents > > the issue? > > Nope, it still gripes. The reason for this gripe is that we find that we

Re: [PATCH v9 4/9] MAINTAINERS: update file entries for Coresight subsystem

On Tue, May 09, 2017 at 10:49:57AM +0800, Leo Yan wrote: > Update document file entries for Coresight debug module. > > Signed-off-by: Leo Yan Reviewed-by: Mathieu Poirier > --- > MAINTAINERS | 2 ++ > 1 file changed, 2 insertions(+) > > diff

Re: [PATCH] staging: typec: Fix sparse warnings about incorrect types

On Wed, May 10, 2017 at 10:51:35PM -0700, Guru Das Srinagesh wrote: > Fix the following sparse warnings about incorrect type usage: > > fusb302.c:1028:32: warning: incorrect type in argument 1 (different base > types) > fusb302.c:1028:32:expected unsigned short [unsigned] [usertype] header >

Re: [PATCH v9 4/9] MAINTAINERS: update file entries for Coresight subsystem

On Tue, May 09, 2017 at 10:49:57AM +0800, Leo Yan wrote: > Update document file entries for Coresight debug module. > > Signed-off-by: Leo Yan Reviewed-by: Mathieu Poirier > --- > MAINTAINERS | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/MAINTAINERS b/MAINTAINERS > index

Re: [PATCH] staging: typec: Fix sparse warnings about incorrect types

On Wed, May 10, 2017 at 10:51:35PM -0700, Guru Das Srinagesh wrote: > Fix the following sparse warnings about incorrect type usage: > > fusb302.c:1028:32: warning: incorrect type in argument 1 (different base > types) > fusb302.c:1028:32:expected unsigned short [unsigned] [usertype] header >

Re: [PATCH] mdio: mux: Correct mdio_mux_init error path issues

From: Florian Fainelli Date: Thu, 11 May 2017 10:05:27 -0700 > On 05/10/2017 08:20 AM, Jon Mason wrote: >> There is a potential unnecessary refcount decriment on error path of >> put_device(>mii_bus->dev), as it is possible to avoid the >> of_mdio_find_bus() call if mux_bus

Re: [PATCH] mdio: mux: Correct mdio_mux_init error path issues

From: Florian Fainelli Date: Thu, 11 May 2017 10:05:27 -0700 > On 05/10/2017 08:20 AM, Jon Mason wrote: >> There is a potential unnecessary refcount decriment on error path of >> put_device(>mii_bus->dev), as it is possible to avoid the >> of_mdio_find_bus() call if mux_bus is specified by the

Re: [PATCH v9 3/9] doc: Add coresight_cpu_debug.enable to kernel-parameters.txt

On Tue, May 09, 2017 at 10:49:56AM +0800, Leo Yan wrote: > Add coresight_cpu_debug.enable to kernel-parameters.txt, this flag is > used to enable/disable the CPU sampling based debugging. > > Signed-off-by: Leo Yan Reviewed-by: Mathieu Poirier >

Re: [PATCH v9 3/9] doc: Add coresight_cpu_debug.enable to kernel-parameters.txt

On Tue, May 09, 2017 at 10:49:56AM +0800, Leo Yan wrote: > Add coresight_cpu_debug.enable to kernel-parameters.txt, this flag is > used to enable/disable the CPU sampling based debugging. > > Signed-off-by: Leo Yan Reviewed-by: Mathieu Poirier > --- >

Re: [PATCH] ARM: remove duplicate 'const' annotations'

On 05/11/2017 04:50 AM, Arnd Bergmann wrote: > gcc-7 warns about some declarations that are more 'const' than necessary: > > arch/arm/mach-at91/pm.c:338:34: error: duplicate 'const' declaration > specifier [-Werror=duplicate-decl-specifier] > static const struct of_device_id const ramc_ids[]

Re: [PATCH] ARM: remove duplicate 'const' annotations'

On 05/11/2017 04:50 AM, Arnd Bergmann wrote: > gcc-7 warns about some declarations that are more 'const' than necessary: > > arch/arm/mach-at91/pm.c:338:34: error: duplicate 'const' declaration > specifier [-Werror=duplicate-decl-specifier] > static const struct of_device_id const ramc_ids[]

Re: [PATCH v9 2/9] doc: Add documentation for Coresight CPU debug

On Tue, May 09, 2017 at 10:49:55AM +0800, Leo Yan wrote: > Add detailed documentation for Coresight CPU debug driver, which > contains the info for driver implementation, Mike Leach excellent > summary for "clock and power domain". At the end some examples on how > to enable the debugging

Re: [PATCH v9 2/9] doc: Add documentation for Coresight CPU debug

On Tue, May 09, 2017 at 10:49:55AM +0800, Leo Yan wrote: > Add detailed documentation for Coresight CPU debug driver, which > contains the info for driver implementation, Mike Leach excellent > summary for "clock and power domain". At the end some examples on how > to enable the debugging

[GIT PULL] arm64 2nd set of updates for 4.12

Hi Linus, Please pull the arm64 updates below. The mm/vmalloc.c change was acked by Michal Hocko and the arch/arm one by Russell King. Thanks. The following changes since commit 92f66f84d9695d07adf9bc987bbcce4bf9b8e87c: arm64: Fix the DMA mmap and get_sgtable API with

[GIT PULL] arm64 2nd set of updates for 4.12

Hi Linus, Please pull the arm64 updates below. The mm/vmalloc.c change was acked by Michal Hocko and the arch/arm one by Russell King. Thanks. The following changes since commit 92f66f84d9695d07adf9bc987bbcce4bf9b8e87c: arm64: Fix the DMA mmap and get_sgtable API with

Re: [PATCH v9 9/9] arm64: dts: qcom: msm8916: Add debug unit

On Tue, May 09, 2017 at 10:50:02AM +0800, Leo Yan wrote: > Add debug unit on Qualcomm msm8916 based platforms, including the > DragonBoard 410c board. > > Signed-off-by: Leo Yan Reviewed-by: Mathieu Poirier > --- >

Re: [PATCH v9 9/9] arm64: dts: qcom: msm8916: Add debug unit

On Tue, May 09, 2017 at 10:50:02AM +0800, Leo Yan wrote: > Add debug unit on Qualcomm msm8916 based platforms, including the > DragonBoard 410c board. > > Signed-off-by: Leo Yan Reviewed-by: Mathieu Poirier > --- > arch/arm64/boot/dts/qcom/msm8916.dtsi | 32 >

Re: [PATCH v9 8/9] arm64: dts: hi6220: register debug module

On Tue, May 09, 2017 at 10:50:01AM +0800, Leo Yan wrote: > Bind debug module driver for Hi6220. > > Signed-off-by: Leo Yan Reviewed-by: Mathieu Poirier > --- > arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 64 > +++ >

Re: [PATCH v9 8/9] arm64: dts: hi6220: register debug module

On Tue, May 09, 2017 at 10:50:01AM +0800, Leo Yan wrote: > Bind debug module driver for Hi6220. > > Signed-off-by: Leo Yan Reviewed-by: Mathieu Poirier > --- > arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 64 > +++ > 1 file changed, 64 insertions(+) > > diff

Re: [PATCH] input: cros_ec_keyb: remove extraneous 'const'

On Thu, May 11, 2017 at 01:48:04PM +0200, Arnd Bergmann wrote: > gcc-7 warns about 'const SIMPLE_DEV_PM_OPS', as that macro already constains > a 'const' keyword: > > drivers/input/keyboard/cros_ec_keyb.c:663:14: error: duplicate 'const' > declaration specifier [-Werror=duplicate-decl-specifier]

Re: [PATCH] input: cros_ec_keyb: remove extraneous 'const'

On Thu, May 11, 2017 at 01:48:04PM +0200, Arnd Bergmann wrote: > gcc-7 warns about 'const SIMPLE_DEV_PM_OPS', as that macro already constains > a 'const' keyword: > > drivers/input/keyboard/cros_ec_keyb.c:663:14: error: duplicate 'const' > declaration specifier [-Werror=duplicate-decl-specifier]

Re: [PATCH v9 7/9] coresight: add support for CPU debug module

On Tue, May 09, 2017 at 10:50:00AM +0800, Leo Yan wrote: > Coresight includes debug module and usually the module connects with CPU > debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has > description for related info in "Part H: External Debug". > > Chapter H7 "The Sample-based

Re: [PATCH v9 7/9] coresight: add support for CPU debug module

On Tue, May 09, 2017 at 10:50:00AM +0800, Leo Yan wrote: > Coresight includes debug module and usually the module connects with CPU > debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has > description for related info in "Part H: External Debug". > > Chapter H7 "The Sample-based

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 07:46:27PM +0900, AKASHI Takahiro wrote: > Luis, > > On Fri, Apr 28, 2017 at 03:45:35AM +0200, Luis R. Rodriguez wrote: > > > > +To test an async call one could do:: > > > > + > > > > +echo anything > /lib/firmware/test-driver_data.bin > > > > > > Your current

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 07:46:27PM +0900, AKASHI Takahiro wrote: > Luis, > > On Fri, Apr 28, 2017 at 03:45:35AM +0200, Luis R. Rodriguez wrote: > > > > +To test an async call one could do:: > > > > + > > > > +echo anything > /lib/firmware/test-driver_data.bin > > > > > > Your current

Threads stuck in zap_pid_ns_processes()

Hi all, the test program attached below almost always results in one of the child processes being stuck in zap_pid_ns_processes(). When this happens, I can see from test logs that nr_hashed == 2 and init_pids==1, but there is only a single thread left in the pid namespace (the one that is stuck).

Threads stuck in zap_pid_ns_processes()

Hi all, the test program attached below almost always results in one of the child processes being stuck in zap_pid_ns_processes(). When this happens, I can see from test logs that nr_hashed == 2 and init_pids==1, but there is only a single thread left in the pid namespace (the one that is stuck).

Re: [PATCH RFC] sched/deadline: Use the revised wakeup rule for suspending constrained dl tasks

On 05/04/2017 04:26 PM, Peter Zijlstra wrote: > On Thu, May 04, 2017 at 04:17:21PM +0200, Peter Zijlstra wrote: >> We use two difference CBS rules: >> >> 1) the original CBS rule for implicit deadline tasks; >> 2) the revised CBS rule for constrained deadline tasks. >>> @@ -500,6 +550,14 @@

Re: [PATCH RFC] sched/deadline: Use the revised wakeup rule for suspending constrained dl tasks

On 05/04/2017 04:26 PM, Peter Zijlstra wrote: > On Thu, May 04, 2017 at 04:17:21PM +0200, Peter Zijlstra wrote: >> We use two difference CBS rules: >> >> 1) the original CBS rule for implicit deadline tasks; >> 2) the revised CBS rule for constrained deadline tasks. >>> @@ -500,6 +550,14 @@

Re: [PATCH RFC] sched/deadline: Use the revised wakeup rule for suspending constrained dl tasks

On 05/04/2017 04:23 PM, Peter Zijlstra wrote: > On Thu, May 04, 2017 at 04:17:21PM +0200, Peter Zijlstra wrote: >> On Mon, Apr 24, 2017 at 05:18:35PM +0200, Daniel Bristot de Oliveira wrote: >>> +static void >>> +update_dl_revised_wakeup(struct sched_dl_entity *dl_se, struct rq *rq) >>> +{ >>> +

Re: [PATCH RFC] sched/deadline: Use the revised wakeup rule for suspending constrained dl tasks

On 05/04/2017 04:23 PM, Peter Zijlstra wrote: > On Thu, May 04, 2017 at 04:17:21PM +0200, Peter Zijlstra wrote: >> On Mon, Apr 24, 2017 at 05:18:35PM +0200, Daniel Bristot de Oliveira wrote: >>> +static void >>> +update_dl_revised_wakeup(struct sched_dl_entity *dl_se, struct rq *rq) >>> +{ >>> +

Re: [PATCH] mdio: mux: Correct mdio_mux_init error path issues

On 05/10/2017 08:20 AM, Jon Mason wrote: > There is a potential unnecessary refcount decriment on error path of > put_device(>mii_bus->dev), as it is possible to avoid the > of_mdio_find_bus() call if mux_bus is specified by the calling function. > > The same put_device() is not called in the

Re: [PATCH] mdio: mux: Correct mdio_mux_init error path issues

On 05/10/2017 08:20 AM, Jon Mason wrote: > There is a potential unnecessary refcount decriment on error path of > put_device(>mii_bus->dev), as it is possible to avoid the > of_mdio_find_bus() call if mux_bus is specified by the calling function. > > The same put_device() is not called in the

Re: [PATCH 4.4 16/60] x86/ioapic: Restore IO-APIC irq_chip retrigger callback

On Thu, 2017-05-11 at 16:12 +0200, Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Ruslan Ruslichenko > > commit a9b4f08770b415f30f2fb0f8329a370c8f554aa3 upstream. > > commit

Re: [PATCH 4.4 16/60] x86/ioapic: Restore IO-APIC irq_chip retrigger callback

On Thu, 2017-05-11 at 16:12 +0200, Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Ruslan Ruslichenko > > commit a9b4f08770b415f30f2fb0f8329a370c8f554aa3 upstream. > > commit d32932d02e18 removed the

[PATCHv2] Make initramfs honor CONFIG_DEVTMPFS_MOUNT

From: Rob Landley Make initramfs honor CONFIG_DEVTMPFS_MOUNT, move /dev/console open after devtmpfs mount, and update help text. Signed-off-by: Rob Landley --- drivers/base/Kconfig | 14 -- init/main.c | 15 +-- 2 files

[PATCHv2] Make initramfs honor CONFIG_DEVTMPFS_MOUNT

From: Rob Landley Make initramfs honor CONFIG_DEVTMPFS_MOUNT, move /dev/console open after devtmpfs mount, and update help text. Signed-off-by: Rob Landley --- drivers/base/Kconfig | 14 -- init/main.c | 15 +-- 2 files changed, 13 insertions(+), 16

Re: [PATCH RFC] sched/deadline: Use the revised wakeup rule for suspending constrained dl tasks

On 05/04/2017 04:17 PM, Peter Zijlstra wrote: > On Mon, Apr 24, 2017 at 05:18:35PM +0200, Daniel Bristot de Oliveira wrote: >> We have been facing some problems with self-suspending constrained >> deadline tasks. The main reason is that the original CBS was not >> designed for such sort of tasks.

Re: [PATCH RFC] sched/deadline: Use the revised wakeup rule for suspending constrained dl tasks

On 05/04/2017 04:17 PM, Peter Zijlstra wrote: > On Mon, Apr 24, 2017 at 05:18:35PM +0200, Daniel Bristot de Oliveira wrote: >> We have been facing some problems with self-suspending constrained >> deadline tasks. The main reason is that the original CBS was not >> designed for such sort of tasks.

Re: [PATCH v5 5/6] mtd: dataflash: Make use of "extened device information"

On Fri, Apr 21, 2017 at 07:19:21PM +0200, Marek Vasut wrote: > On 04/21/2017 06:30 PM, Andrey Smirnov wrote: > > In anticipation of supporting chips that need it, extend the size of > > struct flash_info's 'jedec_id' field to make room 2 byte of extended > > device information as well as add code

Re: [PATCH v5 5/6] mtd: dataflash: Make use of "extened device information"

On Fri, Apr 21, 2017 at 07:19:21PM +0200, Marek Vasut wrote: > On 04/21/2017 06:30 PM, Andrey Smirnov wrote: > > In anticipation of supporting chips that need it, extend the size of > > struct flash_info's 'jedec_id' field to make room 2 byte of extended > > device information as well as add code

Re: [PATCH] Make initramfs honor CONFIG_DEVTMPFS_MOUNT

On 05/09/2017 04:31 PM, Andrew Morton wrote: > On Thu, 4 May 2017 16:09:06 -0500 Rob Landley wrote: > >> From: Rob Landley >> >> Make initramfs honor CONFIG_DEVTMPFS_MOUNT, and move >> /dev/console open after devtmpfs mount. > > > Could we please see

Re: [PATCH] Make initramfs honor CONFIG_DEVTMPFS_MOUNT

On 05/09/2017 04:31 PM, Andrew Morton wrote: > On Thu, 4 May 2017 16:09:06 -0500 Rob Landley wrote: > >> From: Rob Landley >> >> Make initramfs honor CONFIG_DEVTMPFS_MOUNT, and move >> /dev/console open after devtmpfs mount. > > > Could we please see complete description of the runtime

Re: [PATCH v7 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 07:10:18PM +0900, AKASHI Takahiro wrote: > Luis, > > On Tue, May 02, 2017 at 01:49:12AM -0700, Luis R. Rodriguez wrote: > > > > diff --git a/lib/test_driver_data.c b/lib/test_driver_data.c > > new file mode 100644 > > index ..488cc6e9eed4 > > --- /dev/null > >

Re: [PATCH v7 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 07:10:18PM +0900, AKASHI Takahiro wrote: > Luis, > > On Tue, May 02, 2017 at 01:49:12AM -0700, Luis R. Rodriguez wrote: > > > > diff --git a/lib/test_driver_data.c b/lib/test_driver_data.c > > new file mode 100644 > > index ..488cc6e9eed4 > > --- /dev/null > >

Re: pinctrl-sx150x.c broken in 4.11

>>> Hmm maybe yeah. I don't quite follow the above the "pinctrl-0 property >>> of sx150x device tree node, is misinterpreted as hog" part though. >> >> sx150x is i2c-gpio device. It has 16 GPIO lines that are communicated >> with via i2c bus, and an interrupt line. >> >> Interrupt line is

Re: pinctrl-sx150x.c broken in 4.11

>>> Hmm maybe yeah. I don't quite follow the above the "pinctrl-0 property >>> of sx150x device tree node, is misinterpreted as hog" part though. >> >> sx150x is i2c-gpio device. It has 16 GPIO lines that are communicated >> with via i2c bus, and an interrupt line. >> >> Interrupt line is

Re: [PATCH v4] sd: Ignore sync cache failures when not supported

On Thu, 2017-05-11 at 14:34 +0200, Thierry Escande wrote: > From: Derek Basehore > > Some external hard drives don't support the sync command even though the > hard drive has write cache enabled. In this case, upon suspend request, > sync cache failures are ignored if the

Re: [PATCH v4] sd: Ignore sync cache failures when not supported

On Thu, 2017-05-11 at 14:34 +0200, Thierry Escande wrote: > From: Derek Basehore > > Some external hard drives don't support the sync command even though the > hard drive has write cache enabled. In this case, upon suspend request, > sync cache failures are ignored if the error code in the sense

Re: vmbus: Delete an error message for a failed memory allocation in vmbus_device_create()

On Thu, 11 May 2017 18:36:44 +0200 SF Markus Elfring wrote: > > Taking out the message assumes that all callers of this function either log > > an > > error or pass appropriate error code back to userspace. > > Do you like the default error response by Linux

Re: vmbus: Delete an error message for a failed memory allocation in vmbus_device_create()

On Thu, 11 May 2017 18:36:44 +0200 SF Markus Elfring wrote: > > Taking out the message assumes that all callers of this function either log > > an > > error or pass appropriate error code back to userspace. > > Do you like the default error response by Linux memory allocation functions? The

Re: [PATCH] net: ethernet: ti: netcp_core: return error while dma channel open issue

From: Ivan Khoronzhuk Date: Wed, 10 May 2017 10:28:05 -0700 > Fix error path while dma open channel issue. Also, no need to check output > on NULL if it's never returned. > > Signed-off-by: Ivan Khoronzhuk Applied.

Re: [PATCH] net: ethernet: ti: netcp_core: return error while dma channel open issue

From: Ivan Khoronzhuk Date: Wed, 10 May 2017 10:28:05 -0700 > Fix error path while dma open channel issue. Also, no need to check output > on NULL if it's never returned. > > Signed-off-by: Ivan Khoronzhuk Applied.

Re: vmbus: Delete an error message for a failed memory allocation in vmbus_device_create()

> Taking out the message assumes that all callers of this function either log an > error or pass appropriate error code back to userspace. Do you like the default error response by Linux memory allocation functions? Regards, Markus

Re: vmbus: Delete an error message for a failed memory allocation in vmbus_device_create()

> Taking out the message assumes that all callers of this function either log an > error or pass appropriate error code back to userspace. Do you like the default error response by Linux memory allocation functions? Regards, Markus

Re: pull request: linux-firmware: update cxgb4 firmware

On Wed, Apr 26, 2017 at 08:06:53PM +0530, Ganesh Goudar wrote: > Hi, > > Kindly pull the new firmware from the following URL. > git://git.chelsio.net/pub/git/linux-firmware.git for-upstream > > Thanks, > Ganesh > > The following changes since commit

Re: pull request: linux-firmware: update cxgb4 firmware

On Wed, Apr 26, 2017 at 08:06:53PM +0530, Ganesh Goudar wrote: > Hi, > > Kindly pull the new firmware from the following URL. > git://git.chelsio.net/pub/git/linux-firmware.git for-upstream > > Thanks, > Ganesh > > The following changes since commit

Re: pinctrl-sx150x.c broken in 4.11

* Nikita Yushchenko [170511 09:27]: > > Hmm maybe yeah. I don't quite follow the above the "pinctrl-0 property > > of sx150x device tree node, is misinterpreted as hog" part though. > > sx150x is i2c-gpio device. It has 16 GPIO lines that are communicated > with

Re: pinctrl-sx150x.c broken in 4.11

* Nikita Yushchenko [170511 09:27]: > > Hmm maybe yeah. I don't quite follow the above the "pinctrl-0 property > > of sx150x device tree node, is misinterpreted as hog" part though. > > sx150x is i2c-gpio device. It has 16 GPIO lines that are communicated > with via i2c bus, and an interrupt

Re: [PATCH 4/4] vmbus: Adjust five checks for null pointers

On Thu, 11 May 2017 18:19:21 +0200 SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 11 May 2017 17:52:38 +0200 > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > The

Re: [PATCH 4/4] vmbus: Adjust five checks for null pointers

On Thu, 11 May 2017 18:19:21 +0200 SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 11 May 2017 17:52:38 +0200 > MIME-Version: 1.0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: 8bit > > The script “checkpatch.pl” pointed information out like the following.

Re: [PATCH 3/4] vmbus: Fix a typo in a comment line

On Thu, 11 May 2017 18:18:12 +0200 SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 11 May 2017 17:43:55 +0200 > > Add a missing character in this description. > > Signed-off-by: Markus Elfring

Re: [PATCH 3/4] vmbus: Fix a typo in a comment line

On Thu, 11 May 2017 18:18:12 +0200 SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 11 May 2017 17:43:55 +0200 > > Add a missing character in this description. > > Signed-off-by: Markus Elfring > --- > drivers/hv/vmbus_drv.c | 2 +- > 1 file changed, 1 insertion(+), 1

[RFC 07/11] ima: new namespace policy structure to track initial namespace policy data

Adding the global ima_initial_namespace_policy which will be used when the initial namespace IMA policy data must be referred or when CONFIG_IMA_PER_NAMESPACE is not defined. New functions which will be used to retrieve the correct namespace IMA policy data from the radix tree map or from the

[RFC 07/11] ima: new namespace policy structure to track initial namespace policy data

Adding the global ima_initial_namespace_policy which will be used when the initial namespace IMA policy data must be referred or when CONFIG_IMA_PER_NAMESPACE is not defined. New functions which will be used to retrieve the correct namespace IMA policy data from the radix tree map or from the

[RFC 06/11] ima, fs: release namespace policy resources

Release all namespace IMA policy resources when the mount namespace is released. This is the suggested mechanism to release namespace policy resources, but we still can discuss other methods to avoid cross-component changes. Signed-off-by: Guilherme Magalhaes ---

[RFC 06/11] ima, fs: release namespace policy resources

Release all namespace IMA policy resources when the mount namespace is released. This is the suggested mechanism to release namespace policy resources, but we still can discuss other methods to avoid cross-component changes. Signed-off-by: Guilherme Magalhaes --- fs/namespace.c

[PATCH 09/14] Sample program for driving fsopen/fsmount [ver #2]

--- samples/fsmount/test-fsmount.c | 79 1 file changed, 79 insertions(+) create mode 100644 samples/fsmount/test-fsmount.c diff --git a/samples/fsmount/test-fsmount.c b/samples/fsmount/test-fsmount.c new file mode 100644 index

[PATCH 09/14] Sample program for driving fsopen/fsmount [ver #2]

--- samples/fsmount/test-fsmount.c | 79 1 file changed, 79 insertions(+) create mode 100644 samples/fsmount/test-fsmount.c diff --git a/samples/fsmount/test-fsmount.c b/samples/fsmount/test-fsmount.c new file mode 100644 index

[PATCH 08/14] Implement fsmount() to effect a pre-configured mount [ver #2]

Provide a system call by which a filesystem opened with fsopen() and configured by a series of writes can be mounted: int ret = fsmount(int fsfd, int dfd, const char *path, unsigned int at_flags, unsigned int flags); where fsfd is the fd returned by fsopen(),

[PATCH 08/14] Implement fsmount() to effect a pre-configured mount [ver #2]

Provide a system call by which a filesystem opened with fsopen() and configured by a series of writes can be mounted: int ret = fsmount(int fsfd, int dfd, const char *path, unsigned int at_flags, unsigned int flags); where fsfd is the fd returned by fsopen(),

[RFC 08/11] ima: block initial namespace id on the namespace policy interface

The initial namespace policy is set through the existent interface in the ima/policy securityfs file. Block the initial namespace id when it is written to the ima/namespace securityfs file. Signed-off-by: Guilherme Magalhaes --- security/integrity/ima/ima_fs.c | 18

[RFC 08/11] ima: block initial namespace id on the namespace policy interface

The initial namespace policy is set through the existent interface in the ima/policy securityfs file. Block the initial namespace id when it is written to the ima/namespace securityfs file. Signed-off-by: Guilherme Magalhaes --- security/integrity/ima/ima_fs.c | 18 ++ 1 file

Re: [PATCH 1/4] vmbus: Improve a size determination in vmbus_device_create()

On Thu, 11 May 2017 18:15:46 +0200 SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 11 May 2017 17:30:10 +0200 > > Replace the specification of a data structure by a pointer dereference > as the parameter for the

Re: [PATCH 1/4] vmbus: Improve a size determination in vmbus_device_create()

On Thu, 11 May 2017 18:15:46 +0200 SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 11 May 2017 17:30:10 +0200 > > Replace the specification of a data structure by a pointer dereference > as the parameter for the operator "sizeof" to make the corresponding size > determination a

[RFC 05/11] ima: store new namespace policy structure in a radix tree

New ima_ns_policy structure to describe IMA policy data per namespace. Using a radix tree to map namespace ids to a respective ima_ns_policy structure. When it is needed to retrieve IMA policy rules/flags, the target ima_ns_policy structure is retrieved from the radix tree by getting the namespace

[RFC 05/11] ima: store new namespace policy structure in a radix tree

New ima_ns_policy structure to describe IMA policy data per namespace. Using a radix tree to map namespace ids to a respective ima_ns_policy structure. When it is needed to retrieve IMA policy rules/flags, the target ima_ns_policy structure is retrieved from the radix tree by getting the namespace

[RFC 04/11] ima: add support to namespace securityfs file

Creating the namespace securityfs file under ima folder. When a mount namespace id is written to the namespace file, a new folder is created and with a policy file for that specified namespace. Then, user defined policy for namespaces may be set by writing rules to this namespace policy file. With

Re: [PATCH 2/4] vmbus: Delete an error message for a failed memory allocation in vmbus_device_create()

On Thu, 11 May 2017 18:17:01 +0200 SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 11 May 2017 17:33:14 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by

[RFC 04/11] ima: add support to namespace securityfs file

Creating the namespace securityfs file under ima folder. When a mount namespace id is written to the namespace file, a new folder is created and with a policy file for that specified namespace. Then, user defined policy for namespaces may be set by writing rules to this namespace policy file. With

Re: [PATCH 2/4] vmbus: Delete an error message for a failed memory allocation in vmbus_device_create()

On Thu, 11 May 2017 18:17:01 +0200 SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 11 May 2017 17:33:14 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Link: >

Re: [PATCH 5/5] phy: bcm-ns-usb3: add MDIO driver using proper bus layer

On 05/11/2017 06:29 AM, Rafał Miłecki wrote: > From: Rafał Miłecki > > As USB 3.0 PHY is attached to the MDIO bus this module should provide a > MDIO driver and use a proper bus layer. This is a proper (cleaner) > solution which doesn't require code to know this specific MDIO

[RFC 09/11] ima: delete namespace policy securityfs file in write-once mode

When policy file is written and write-once is enabled, the policy file must be deleted. Select the namespace policy structure to get the correct policy file descriptor. Signed-off-by: Guilherme Magalhaes --- security/integrity/ima/ima_fs.c | 27

Re: [PATCH 5/5] phy: bcm-ns-usb3: add MDIO driver using proper bus layer

On 05/11/2017 06:29 AM, Rafał Miłecki wrote: > From: Rafał Miłecki > > As USB 3.0 PHY is attached to the MDIO bus this module should provide a > MDIO driver and use a proper bus layer. This is a proper (cleaner) > solution which doesn't require code to know this specific MDIO bus > details. It

[RFC 09/11] ima: delete namespace policy securityfs file in write-once mode

When policy file is written and write-once is enabled, the policy file must be deleted. Select the namespace policy structure to get the correct policy file descriptor. Signed-off-by: Guilherme Magalhaes --- security/integrity/ima/ima_fs.c | 27 +-- 1 file changed, 25

[PATCH 07/14] Implement fsopen() to prepare for a mount [ver #2]

Provide an fsopen() system call that starts the process of preparing to mount, using an fd as a context handle. fsopen() is given the name of the filesystem that will be used: int mfd = fsopen(const char *fsname, int reserved, int open_flags); where reserved

[PATCH 07/14] Implement fsopen() to prepare for a mount [ver #2]

Provide an fsopen() system call that starts the process of preparing to mount, using an fd as a context handle. fsopen() is given the name of the filesystem that will be used: int mfd = fsopen(const char *fsname, int reserved, int open_flags); where reserved

Re: [PATCH] arm64/cpufeature: don't use mutex in bringup path

On 11/05/17 14:12, Mark Rutland wrote: > Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which > must take the jump_label mutex. > > We call cpus_set_cap() in the secondary bringup path, from the idle > thread where interrupts are disabled. Taking a mutex in this path "is a >

[RFC 02/11] ima: qualify pathname in audit measurement record

Adding new fields (mount namespace id, file inode and device name) to uniquely identify a pathname considering different mount namespaces. The file inode on a given device is unique and these fields are required to identify a namespace id since this id can be released and later reused by a

Re: [PATCH] arm64/cpufeature: don't use mutex in bringup path

On 11/05/17 14:12, Mark Rutland wrote: > Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which > must take the jump_label mutex. > > We call cpus_set_cap() in the secondary bringup path, from the idle > thread where interrupts are disabled. Taking a mutex in this path "is a >

[RFC 02/11] ima: qualify pathname in audit measurement record

Adding new fields (mount namespace id, file inode and device name) to uniquely identify a pathname considering different mount namespaces. The file inode on a given device is unique and these fields are required to identify a namespace id since this id can be released and later reused by a

[RFC 03/11] ima: qualify pathname in measurement file

Adding new fields (mount namespace id, file inode and device name) to uniquely identify a pathname in the measurement file considering multiple mount namespaces. The file inode on a given device is unique and these fields are required to identify a namespace id since this id can be released and

[RFC 03/11] ima: qualify pathname in measurement file

Adding new fields (mount namespace id, file inode and device name) to uniquely identify a pathname in the measurement file considering multiple mount namespaces. The file inode on a given device is unique and these fields are required to identify a namespace id since this id can be released and

Re: [RFC][PATCH] sched/deadline: Remove if statement before clearing throttle and yielded

Hi, On 10/05/17 09:50, Steven Rostedt wrote: > [ > This is an RFC as I didn't run any benchmarks. It just seemed a bit > weird to me that we would add such a check instead of just clearing > these variables out regardless. > ] > > The function replenish_dl_entity() clears dl_throttled and

[PATCH 06/14] VFS: Introduce a superblock configuration context [ver #2]

Introduce a superblock configuration context concept to be used during superblock creation for mount and superblock reconfiguration for remount. This is allocated at the beginning of the mount procedure and into it is placed: (1) Filesystem type. (2) Namespaces. (3) Device name. (4)

[RFC 01/11] ima: qualify pathname in audit info record

Adding new field (mount namespace id, along with already existent file inode and device name) to uniquely identify a pathname considering different mount namespaces. The file inode on a given device is unique and these fields are required to identify a namespace id since this id can be released

Re: [RFC][PATCH] sched/deadline: Remove if statement before clearing throttle and yielded

Hi, On 10/05/17 09:50, Steven Rostedt wrote: > [ > This is an RFC as I didn't run any benchmarks. It just seemed a bit > weird to me that we would add such a check instead of just clearing > these variables out regardless. > ] > > The function replenish_dl_entity() clears dl_throttled and

[PATCH 06/14] VFS: Introduce a superblock configuration context [ver #2]

Introduce a superblock configuration context concept to be used during superblock creation for mount and superblock reconfiguration for remount. This is allocated at the beginning of the mount procedure and into it is placed: (1) Filesystem type. (2) Namespaces. (3) Device name. (4)

[RFC 01/11] ima: qualify pathname in audit info record

Adding new field (mount namespace id, along with already existent file inode and device name) to uniquely identify a pathname considering different mount namespaces. The file inode on a given device is unique and these fields are required to identify a namespace id since this id can be released

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