Re: [PATCH 0157/1285] Replace numeric parameter like 0444 with macro

On Tue, Aug 02, 2016 at 11:54:47AM -0700, Olof Johansson wrote: > On Tue, Aug 02, 2016 at 06:45:15PM +0800, Baole Ni wrote: > > I find that the developers often just specified the numeric value > > when calling a macro which is defined with a parameter for access > > permission. > > As we know,

Re: [PATCH 0157/1285] Replace numeric parameter like 0444 with macro

On Tue, Aug 02, 2016 at 11:54:47AM -0700, Olof Johansson wrote: > On Tue, Aug 02, 2016 at 06:45:15PM +0800, Baole Ni wrote: > > I find that the developers often just specified the numeric value > > when calling a macro which is defined with a parameter for access > > permission. > > As we know,

[PATCH v2 1/3] nvmx: remove comment about missing nested vpid support

Nested vpid is already supported and both single/global modes are advertised to the guest Signed-off-by: Bandan Das --- arch/x86/kvm/vmx.c | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index df07a0a..1d5a3be 100644 ---

[PATCH v2 0/3] vmx: miscellaneous cleanups

v1 posted here https://lkml.org/lkml/2016/7/20/605 v2: 1/3 : Replacing BUG_ONs with WARN_ONs is not necessary 2/3 : No change 3/3 : Remove the kvm parameter from two other functions 4/3 : Removed, although the spec says to do it, it can't be triggered These are some very minor vmx cleanups. 2/4

[PATCH v2 1/3] nvmx: remove comment about missing nested vpid support

Nested vpid is already supported and both single/global modes are advertised to the guest Signed-off-by: Bandan Das --- arch/x86/kvm/vmx.c | 1 - 1 file changed, 1 deletion(-) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index df07a0a..1d5a3be 100644 --- a/arch/x86/kvm/vmx.c +++

[PATCH v2 0/3] vmx: miscellaneous cleanups

v1 posted here https://lkml.org/lkml/2016/7/20/605 v2: 1/3 : Replacing BUG_ONs with WARN_ONs is not necessary 2/3 : No change 3/3 : Remove the kvm parameter from two other functions 4/3 : Removed, although the spec says to do it, it can't be triggered These are some very minor vmx cleanups. 2/4

[RFC PATCH 4/4] usb: typec: Type-C Port Controller Interface driver (tcpci)

The port controller interface driver interconnects the Type-C Port Manager with a Type-C Port Controller Interface (TCPCI) compliant port controller. Signed-off-by: Guenter Roeck --- drivers/usb/typec/Kconfig | 9 + drivers/usb/typec/Makefile | 1 +

[PATCH v2 2/3] nvmx: mark ept single context invalidation as supported

Commit 4b855078601f ("KVM: nVMX: Don't advertise single context invalidation for invept") removed advertising single context invalidation since the spec does not mandate it. However, some hypervisors (such as ESX) require it to be present before willing to use ept in a nested environment.

[PATCH v2 2/3] nvmx: mark ept single context invalidation as supported

Commit 4b855078601f ("KVM: nVMX: Don't advertise single context invalidation for invept") removed advertising single context invalidation since the spec does not mandate it. However, some hypervisors (such as ESX) require it to be present before willing to use ept in a nested environment.

[RFC PATCH 4/4] usb: typec: Type-C Port Controller Interface driver (tcpci)

The port controller interface driver interconnects the Type-C Port Manager with a Type-C Port Controller Interface (TCPCI) compliant port controller. Signed-off-by: Guenter Roeck --- drivers/usb/typec/Kconfig | 9 + drivers/usb/typec/Makefile | 1 + drivers/usb/typec/tcpci.c | 498

[PATCH v12 04/11] genirq/msi: Allow MSI doorbell (un)registration

This new API aims at allowing irqchips to allocate & register the MSI doorbells likely to be iommu mapped. Later on, other services will be added allowing the VFIO layer to query information based on all registered doorbells. We count the number of doorbells that do not implement IRQ remapping.

Re: [GIT PULL] KVM changes for 4.8 merge window

On Tue, Aug 2, 2016 at 2:42 PM, Linus Torvalds wrote: > > No, I don't use the merge from linux-next directly. I just re-generate > the merge myself, and if the pull request then includes a merge > resolution (either as just a verbal description, or a patch or by >

[PATCH v12 04/11] genirq/msi: Allow MSI doorbell (un)registration

This new API aims at allowing irqchips to allocate & register the MSI doorbells likely to be iommu mapped. Later on, other services will be added allowing the VFIO layer to query information based on all registered doorbells. We count the number of doorbells that do not implement IRQ remapping.

Re: [GIT PULL] KVM changes for 4.8 merge window

On Tue, Aug 2, 2016 at 2:42 PM, Linus Torvalds wrote: > > No, I don't use the merge from linux-next directly. I just re-generate > the merge myself, and if the pull request then includes a merge > resolution (either as just a verbal description, or a patch or by > having a separate "merged"

Re: [v9 PATCH 3/6] phy: Add USB Type-C PHY driver for rk3399

On Tue, Aug 2, 2016 at 5:45 AM, Chris Zhong wrote: > Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB > Type-C PHY is designed to support the USB3 and DP applications. The > PHY basically has two main components: USB3 and DisplyPort. USB3 > operates in

Re: [v9 PATCH 3/6] phy: Add USB Type-C PHY driver for rk3399

On Tue, Aug 2, 2016 at 5:45 AM, Chris Zhong wrote: > Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB > Type-C PHY is designed to support the USB3 and DP applications. The > PHY basically has two main components: USB3 and DisplyPort. USB3 > operates in SuperSpeed mode and the DP

Re: [PATCH 0236/1285] Replace numeric parameter like 0444 with macro

Hi Baole, On Tue, 2 Aug 2016 18:52:08 +0800, Baole Ni wrote: > I find that the developers often just specified the numeric value > when calling a macro which is defined with a parameter for access permission. > As we know, these numeric value for access permission have had the > corresponding

Re: [PATCH 0236/1285] Replace numeric parameter like 0444 with macro

Hi Baole, On Tue, 2 Aug 2016 18:52:08 +0800, Baole Ni wrote: > I find that the developers often just specified the numeric value > when calling a macro which is defined with a parameter for access permission. > As we know, these numeric value for access permission have had the > corresponding

Re: [PATCH 0947/1285] Replace numeric parameter like 0444 with macro

On Tue, Aug 02, 2016 at 09:51:18AM -0300, Mauro Carvalho Chehab wrote: > Em Tue, 2 Aug 2016 20:01:34 +0800 Baole Ni escreveu: > > > I find that the developers often just specified the numeric value > > when calling a macro which is defined with a parameter for access > >

Re: [PATCH 0947/1285] Replace numeric parameter like 0444 with macro

On Tue, Aug 02, 2016 at 09:51:18AM -0300, Mauro Carvalho Chehab wrote: > Em Tue, 2 Aug 2016 20:01:34 +0800 Baole Ni escreveu: > > > I find that the developers often just specified the numeric value > > when calling a macro which is defined with a parameter for access > > permission. > > As we

Re: [PATCH] infiniband: shut up a maybe-uninitialized warning

On Tuesday, August 2, 2016 1:45:25 PM CEST Doug Ledford wrote: > On Mon, 2016-07-04 at 17:06 +0200, Arnd Bergmann wrote: > > The powerpc64 default configuration leads to warnings for the > > infiniband > > core code: > > > > infiniband/core/cma.c: In function 'cma_get_net_dev': > >

Re: [PATCH] infiniband: shut up a maybe-uninitialized warning

On Tuesday, August 2, 2016 1:45:25 PM CEST Doug Ledford wrote: > On Mon, 2016-07-04 at 17:06 +0200, Arnd Bergmann wrote: > > The powerpc64 default configuration leads to warnings for the > > infiniband > > core code: > > > > infiniband/core/cma.c: In function 'cma_get_net_dev': > >

Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process

On Tue, Aug 2, 2016 at 11:01 PM, Jeff Layton wrote: > On Tue, 2016-08-02 at 15:44 -0400, J. Bruce Fields wrote: >> On Tue, Aug 02, 2016 at 02:09:22PM -0500, Eric W. Biederman wrote: >> > >> > > > "J. Bruce Fields" writes: >> > >> > > >> > > On Tue,

Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process

On Tue, Aug 2, 2016 at 11:01 PM, Jeff Layton wrote: > On Tue, 2016-08-02 at 15:44 -0400, J. Bruce Fields wrote: >> On Tue, Aug 02, 2016 at 02:09:22PM -0500, Eric W. Biederman wrote: >> > >> > > > "J. Bruce Fields" writes: >> > >> > > >> > > On Tue, Aug 02, 2016 at 11:00:39AM -0500, Eric W.

Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process

On Tue, 2016-08-02 at 15:44 -0400, J. Bruce Fields wrote: > On Tue, Aug 02, 2016 at 02:09:22PM -0500, Eric W. Biederman wrote: > > > > > > "J. Bruce Fields" writes: > > > > > > > > On Tue, Aug 02, 2016 at 11:00:39AM -0500, Eric W. Biederman wrote: > > > > > > > > > > > >

[PATCH] Input: ili210x - fix permissions on "calibrate" attribute

"calibrate" attribute does not provide "show" methods and thus we should not mark it as readable. Signed-off-by: Dmitry Torokhov --- drivers/input/touchscreen/ili210x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

Are linux-next builds being tested for powerpc with allyesconfig and allmodconfig ? I have some changes I'm making and while debugging my build issues I decided to give a clean build a shot and see linux-next next-20160729 up to next-20160729 all have build failures without my changes. I get:

Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process

On Tue, 2016-08-02 at 15:44 -0400, J. Bruce Fields wrote: > On Tue, Aug 02, 2016 at 02:09:22PM -0500, Eric W. Biederman wrote: > > > > > > "J. Bruce Fields" writes: > > > > > > > > On Tue, Aug 02, 2016 at 11:00:39AM -0500, Eric W. Biederman wrote: > > > > > > > > > > > > Nikolay Borisov

[PATCH] Input: ili210x - fix permissions on "calibrate" attribute

"calibrate" attribute does not provide "show" methods and thus we should not mark it as readable. Signed-off-by: Dmitry Torokhov --- drivers/input/touchscreen/ili210x.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/input/touchscreen/ili210x.c

powerpc allyesconfig / allmodconfig linux-next next-20160729 - next-20160729 build failures

Are linux-next builds being tested for powerpc with allyesconfig and allmodconfig ? I have some changes I'm making and while debugging my build issues I decided to give a clean build a shot and see linux-next next-20160729 up to next-20160729 all have build failures without my changes. I get:

[PATCH] vfio/pci: Fix NULL pointer oops in error interrupt setup handling

There are multiple cases in vfio_pci_set_ctx_trigger_single() where we assume we can safely read from our data pointer without actually checking whether the user has passed any data via the count field. VFIO_IRQ_SET_DATA_NONE in particular is entirely broken since we attempt to pull an int32_t

[PATCH] vfio/pci: Fix NULL pointer oops in error interrupt setup handling

There are multiple cases in vfio_pci_set_ctx_trigger_single() where we assume we can safely read from our data pointer without actually checking whether the user has passed any data via the count field. VFIO_IRQ_SET_DATA_NONE in particular is entirely broken since we attempt to pull an int32_t

Re: [GIT PULL] orangefs: kernel side caching and executable bugfix

Linus, Here is another copy of the previous request to fix a few problems. I have rebased my changes on top of the point where Al Viro's recent change to OrangeFS, among other things, was merged. (i.e. f7b32e4c021fd788f13f6785e17efbc3eb05b351) I have also fixed a whitespace error in my own

Re: [GIT PULL] orangefs: kernel side caching and executable bugfix

Linus, Here is another copy of the previous request to fix a few problems. I have rebased my changes on top of the point where Al Viro's recent change to OrangeFS, among other things, was merged. (i.e. f7b32e4c021fd788f13f6785e17efbc3eb05b351) I have also fixed a whitespace error in my own

Re: [PATCH v1 1/2] x86/power/64: Support unaligned addresses for temporary mapping

On Tue, Aug 2, 2016 at 10:48 AM, Thomas Garnier wrote: > On Tue, Aug 2, 2016 at 10:36 AM, Yinghai Lu wrote: >> >> Looks like we need to change the loop from phys address to virtual >> address instead. >> to avoid the overflow. something like attached.

Re: [PATCH] perf tests: objdump output can contain multi byte chunks

Em Tue, Aug 02, 2016 at 04:33:16PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Tue, Aug 02, 2016 at 04:07:00PM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Wed, Jan 13, 2016 at 10:22:04AM +0200, Adrian Hunter escreveu: > > > Acked-by: Adrian Hunter > > Oops, this

Re: [PATCH v1 1/2] x86/power/64: Support unaligned addresses for temporary mapping

On Tue, Aug 2, 2016 at 10:48 AM, Thomas Garnier wrote: > On Tue, Aug 2, 2016 at 10:36 AM, Yinghai Lu wrote: >> >> Looks like we need to change the loop from phys address to virtual >> address instead. >> to avoid the overflow. something like attached. --- arch/x86/mm/ident_map.c | 54

Re: [PATCH] perf tests: objdump output can contain multi byte chunks

Em Tue, Aug 02, 2016 at 04:33:16PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Tue, Aug 02, 2016 at 04:07:00PM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Wed, Jan 13, 2016 at 10:22:04AM +0200, Adrian Hunter escreveu: > > > Acked-by: Adrian Hunter > > Oops, this one got lost, finally

Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process

On Tue, Aug 02, 2016 at 02:09:22PM -0500, Eric W. Biederman wrote: > "J. Bruce Fields" writes: > > > On Tue, Aug 02, 2016 at 11:00:39AM -0500, Eric W. Biederman wrote: > >> Nikolay Borisov writes: > >> > >> > Currently when /proc/locks is read it will

Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process

On Tue, Aug 02, 2016 at 02:09:22PM -0500, Eric W. Biederman wrote: > "J. Bruce Fields" writes: > > > On Tue, Aug 02, 2016 at 11:00:39AM -0500, Eric W. Biederman wrote: > >> Nikolay Borisov writes: > >> > >> > Currently when /proc/locks is read it will show all the file locks > >> > which are

Re: [v5,1/6] drm/i915/skl: Add support for the SAGV, fix underrun hangs

Hi, On 08/02/2016 08:52 PM, cp...@redhat.com wrote: Since the watermark calculations for Skylake are still broken, we're apt to hitting underruns very easily under multi-monitor configurations. While it would be lovely if this was fixed, it's not. Another problem that's been coming from this

Re: [v5,1/6] drm/i915/skl: Add support for the SAGV, fix underrun hangs

Hi, On 08/02/2016 08:52 PM, cp...@redhat.com wrote: Since the watermark calculations for Skylake are still broken, we're apt to hitting underruns very easily under multi-monitor configurations. While it would be lovely if this was fixed, it's not. Another problem that's been coming from this

perf test BPF failing on f24: fix

Hi Wang, Something changed and a function used in a perf test for BPF is not anymore appearing on vmlinux, albeit still available on /proc/kallsyms: # readelf -wi /lib/modules/4.7.0+/build/vmlinux | grep -w sys_epoll_wait # But: [root@jouet ~]# grep -i sys_epoll_wait /proc/kallsyms

perf test BPF failing on f24: fix

Hi Wang, Something changed and a function used in a perf test for BPF is not anymore appearing on vmlinux, albeit still available on /proc/kallsyms: # readelf -wi /lib/modules/4.7.0+/build/vmlinux | grep -w sys_epoll_wait # But: [root@jouet ~]# grep -i sys_epoll_wait /proc/kallsyms

[PATCH 1/1] modpost: free allocated memory

valgrind complains that memory is not freed after allocation with realloc() called from main() and write_dump(). So let us free the allocated memory properly. Signed-off-by: Heinrich Schuchardt --- scripts/mod/modpost.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 1/1] modpost: free allocated memory

valgrind complains that memory is not freed after allocation with realloc() called from main() and write_dump(). So let us free the allocated memory properly. Signed-off-by: Heinrich Schuchardt --- scripts/mod/modpost.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [PATCH 1116/1285] Replace numeric parameter like 0444 with macro

On Tue, Aug 02, 2016 at 08:07:11PM +0200, Jan Engelhardt wrote: > > On Tuesday 2016-08-02 14:17, Baole Ni wrote: > > >I find that the developers often just specified the numeric value > >when calling a macro which is defined with a parameter for access permission. > >As we know, these numeric

Re: [PATCH 1116/1285] Replace numeric parameter like 0444 with macro

On Tue, Aug 02, 2016 at 08:07:11PM +0200, Jan Engelhardt wrote: > > On Tuesday 2016-08-02 14:17, Baole Ni wrote: > > >I find that the developers often just specified the numeric value > >when calling a macro which is defined with a parameter for access permission. > >As we know, these numeric

Re: [PATCH] ASoC: simple-card-utils: add missing MODULE_xxx()

On Tue, Aug 02, 2016 at 11:50:48AM -0700, Kevin Hilman wrote: > Your patch works, but as Mark pointed out, I didn't think that this was > the right fix as this isn't a module, but just library. I think building the library as a module is fine, that way we can load it only in situations where

Re: [PATCH] ASoC: simple-card-utils: add missing MODULE_xxx()

On Tue, Aug 02, 2016 at 11:50:48AM -0700, Kevin Hilman wrote: > Your patch works, but as Mark pointed out, I didn't think that this was > the right fix as this isn't a module, but just library. I think building the library as a module is fine, that way we can load it only in situations where

Re: [PATCH] perf tests: objdump output can contain multi byte chunks

Em Tue, Aug 02, 2016 at 04:07:00PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Jan 13, 2016 at 10:22:04AM +0200, Adrian Hunter escreveu: > > On 12/01/16 17:30, Arnaldo Carvalho de Melo wrote: > > > Em Tue, Jan 12, 2016 at 11:07:44AM +0100, Jan Stancek escreveu: > > >> objdump's raw insn

Re: [PATCH] perf tests: objdump output can contain multi byte chunks

Em Tue, Aug 02, 2016 at 04:07:00PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Jan 13, 2016 at 10:22:04AM +0200, Adrian Hunter escreveu: > > On 12/01/16 17:30, Arnaldo Carvalho de Melo wrote: > > > Em Tue, Jan 12, 2016 at 11:07:44AM +0100, Jan Stancek escreveu: > > >> objdump's raw insn

Re: [PATCH 0269/1285] Replace numeric parameter like 0444 with macro

[ removed most the Cc list ] On Tue, Aug 02, 2016 at 08:14:10AM -0700, Bart Van Assche wrote: > > Hello Baole, > > Please change 0444 into S_IRUGO and 0644 into S_IRUGO | S_IWUSR. The latter > form is more compact and hence makes the code easier to read. > FYI, Linus already NACKed the entire

Re: [PATCH] usb: dwc2: Remove deprecated create_singlethread_workqueue

++ Felipe On 7/28/2016 1:27 AM, Bhaktipriya Shridhar wrote: > alloc_ordered_workqueue replaces the deprecated > create_singlethread_workqueue. > > There are multiple work items on the work queue, which require > ordering. Hence, an ordered workqueue has been used. > > The workqueue "wq_otg" is

Re: [PATCH 0269/1285] Replace numeric parameter like 0444 with macro

[ removed most the Cc list ] On Tue, Aug 02, 2016 at 08:14:10AM -0700, Bart Van Assche wrote: > > Hello Baole, > > Please change 0444 into S_IRUGO and 0644 into S_IRUGO | S_IWUSR. The latter > form is more compact and hence makes the code easier to read. > FYI, Linus already NACKed the entire

Re: [PATCH] usb: dwc2: Remove deprecated create_singlethread_workqueue

++ Felipe On 7/28/2016 1:27 AM, Bhaktipriya Shridhar wrote: > alloc_ordered_workqueue replaces the deprecated > create_singlethread_workqueue. > > There are multiple work items on the work queue, which require > ordering. Hence, an ordered workqueue has been used. > > The workqueue "wq_otg" is

Re: [PATCH v2 2/2] livepatch/x86: apply alternatives and paravirt patches after relocations

On Tue, 2 Aug 2016, Miroslav Benes wrote: > > +#include > > +#include > > +#include > > +#include > > It seems I don't have such header file here and it causes a build error. > Shouldn't it be ? I've now refreshed our for-next branch so that it's based on v4.7 to allow for it being used

Re: [PATCH v2 2/2] livepatch/x86: apply alternatives and paravirt patches after relocations

On Tue, 2 Aug 2016, Miroslav Benes wrote: > > +#include > > +#include > > +#include > > +#include > > It seems I don't have such header file here and it causes a build error. > Shouldn't it be ? I've now refreshed our for-next branch so that it's based on v4.7 to allow for it being used

[PATCH 1/1 v2] rtlwifi: remove superfluous condition

If sta == NULL, the changed line will not be reached. So no need to check that sta != NULL here. v2: fix typo Signed-off-by: Heinrich Schuchardt Acked-by: Larry Finger --- drivers/net/wireless/realtek/rtlwifi/core.c | 2 +- 1 file

[PATCH 1/1 v2] rtlwifi: remove superfluous condition

If sta == NULL, the changed line will not be reached. So no need to check that sta != NULL here. v2: fix typo Signed-off-by: Heinrich Schuchardt Acked-by: Larry Finger --- drivers/net/wireless/realtek/rtlwifi/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH -next] powerpc/fsl_rio: apply changes for RIO spec rev 3 fix2

On Tue, 2 Aug 2016 14:49:32 -0400 Alexandre Bounine wrote: > Fix compile error reported by Michael Ellerman: > https://lkml.org/lkml/2016/7/27/14 > also corrects fix: https://lkml.org/lkml/2016/7/27/488 > > --- a/arch/powerpc/sysdev/fsl_rio.c > +++

Re: [PATCH -next] powerpc/fsl_rio: apply changes for RIO spec rev 3 fix2

On Tue, 2 Aug 2016 14:49:32 -0400 Alexandre Bounine wrote: > Fix compile error reported by Michael Ellerman: > https://lkml.org/lkml/2016/7/27/14 > also corrects fix: https://lkml.org/lkml/2016/7/27/488 > > --- a/arch/powerpc/sysdev/fsl_rio.c > +++

Re: rcu_sched stalls in idle task introduced in pre-4.8?

On Tue, Aug 02, 2016 at 11:16:36AM -0700, Paul E. McKenney wrote: > On Tue, Aug 02, 2016 at 01:04:15PM -0400, Rich Felker wrote: > > Hi Paul, > > > > As I mentioned on Twitter, I'm experiencing (otherwise benign) rcu > > stall messages since rebasing my tree on Linus's in-progress merge for > >

Re: rcu_sched stalls in idle task introduced in pre-4.8?

On Tue, Aug 02, 2016 at 11:16:36AM -0700, Paul E. McKenney wrote: > On Tue, Aug 02, 2016 at 01:04:15PM -0400, Rich Felker wrote: > > Hi Paul, > > > > As I mentioned on Twitter, I'm experiencing (otherwise benign) rcu > > stall messages since rebasing my tree on Linus's in-progress merge for > >

Re: Linux 4.1.28

On Tue, Aug 02, 2016 at 06:14:22PM +0200, Thomas Voegtle wrote: > On Wed, 20 Jul 2016, Michal Kubecek wrote: > > >On Fri, Jul 15, 2016 at 03:04:48PM +0200, Thomas Voegtle wrote: > >>And that one? > >>Happens while trying to start a firewall script with iptables-restore. > >> > >>[ 180.071999]

Re: Linux 4.1.28

On Tue, Aug 02, 2016 at 06:14:22PM +0200, Thomas Voegtle wrote: > On Wed, 20 Jul 2016, Michal Kubecek wrote: > > >On Fri, Jul 15, 2016 at 03:04:48PM +0200, Thomas Voegtle wrote: > >>And that one? > >>Happens while trying to start a firewall script with iptables-restore. > >> > >>[ 180.071999]

[GIT PULL] kbuild misc changes for v4.8-rc1

Hi Linus, these is the non-critical part of kbuild for v4.8-rc1: - coccicheck script improvements by Luis R. Rodriguez and Deepa Dinamani - new coccinelle patches by Yann Droneaud and Vaishali Thakkar - debian packaging fixes by Wilfried Klaebe, Henning Schild and Marcin Mielniczuk. Thanks,

[GIT PULL] kbuild misc changes for v4.8-rc1

Hi Linus, these is the non-critical part of kbuild for v4.8-rc1: - coccicheck script improvements by Luis R. Rodriguez and Deepa Dinamani - new coccinelle patches by Yann Droneaud and Vaishali Thakkar - debian packaging fixes by Wilfried Klaebe, Henning Schild and Marcin Mielniczuk. Thanks,

Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process

"J. Bruce Fields" writes: > On Tue, Aug 02, 2016 at 11:00:39AM -0500, Eric W. Biederman wrote: >> Nikolay Borisov writes: >> >> > Currently when /proc/locks is read it will show all the file locks >> > which are currently created on the machine. On

Re: [RFC PATCH] locks: Show only file_locks created in the same pidns as current process

"J. Bruce Fields" writes: > On Tue, Aug 02, 2016 at 11:00:39AM -0500, Eric W. Biederman wrote: >> Nikolay Borisov writes: >> >> > Currently when /proc/locks is read it will show all the file locks >> > which are currently created on the machine. On containers, hosted >> > on busy servers this

[PATCH v12 05/11] genirq/msi: msi_doorbell_calc_pages

msi_doorbell_calc_pages() sum up the number of iommu pages of a given order requested to map all the registered doorbells. This function will allow to dimension the intermediate physical address (IPA) aperture requested to map the MSI doorbells. Signed-off-by: Eric Auger

[PATCH v12 05/11] genirq/msi: msi_doorbell_calc_pages

msi_doorbell_calc_pages() sum up the number of iommu pages of a given order requested to map all the registered doorbells. This function will allow to dimension the intermediate physical address (IPA) aperture requested to map the MSI doorbells. Signed-off-by: Eric Auger --- v11 -> v12: - fix

Re: [GIT PULL] KVM changes for 4.8 merge window

en? AFAIK it's a mixture between looking at histories himself and relying on explanations from submaintainers (which in turn may refer to linux-next). > > I have pushed my resolution at refs/heads/merge-20160802 (commit > > 3d1f53419842) at git://git.kernel.org/pub/scm/virt/kvm/kvm.gi

Re: [GIT PULL] KVM changes for 4.8 merge window

en? AFAIK it's a mixture between looking at histories himself and relying on explanations from submaintainers (which in turn may refer to linux-next). > > I have pushed my resolution at refs/heads/merge-20160802 (commit > > 3d1f53419842) at git://git.kernel.org/pub/scm/virt/kvm/kvm.gi

Re: [PATCH] powerpc: Do not make the entire heap executable

On Mon, Aug 01, 2016 at 11:07:21PM +0200, Denys Vlasenko wrote: > On 32-bit powerps the ELF PLT sections of binaries (built with --bss-plt, > or with a toolchain which defaults to it) look like this: Hi Denys, Thanks for resurrecting this, I am still interested here, we have been using this

Re: [PATCH] powerpc: Do not make the entire heap executable

On Mon, Aug 01, 2016 at 11:07:21PM +0200, Denys Vlasenko wrote: > On 32-bit powerps the ELF PLT sections of binaries (built with --bss-plt, > or with a toolchain which defaults to it) look like this: Hi Denys, Thanks for resurrecting this, I am still interested here, we have been using this

[PATCH] perf/x86/intel/uncore: correct uncore num_counters

From: Kan Liang Some uncore boxes' num_counters for Haswell server and Broadwell server are not correct. This patch make them consistent with the uncore document. Reported-by: Lukasz Odzioba Signed-off-by: Kan Liang ---

[PATCH] perf/x86/intel/uncore: correct uncore num_counters

From: Kan Liang Some uncore boxes' num_counters for Haswell server and Broadwell server are not correct. This patch make them consistent with the uncore document. Reported-by: Lukasz Odzioba Signed-off-by: Kan Liang --- arch/x86/events/intel/uncore_snbep.c | 10 +- 1 file changed, 5

Re: [PATCH 0/2] tracing: hist trigger KASAN fixes

On Tue, 02 Aug 2016 13:57:13 -0500 Tom Zanussi wrote: > Hi Steve, > > It looks like these two patches were never merged.. > Because they got buried in my INBOX. :-( -- Steve

Re: [kernel-hardening] Re: Linker segfault on powerpc when CONFIG_LKDTM=y (was Re: [kernel-hardening] [PATCH 3/5] lkdtm: add function for testing .rodata section)

On Mon, Aug 1, 2016 at 8:12 PM, Michael Ellerman wrote: > Kees Cook writes: > >> On Mon, Aug 1, 2016 at 5:37 AM, Michael Ellerman wrote: >>> Kees Cook writes: >>> This adds a function that lives in the

Re: [PATCH 0/2] tracing: hist trigger KASAN fixes

On Tue, 02 Aug 2016 13:57:13 -0500 Tom Zanussi wrote: > Hi Steve, > > It looks like these two patches were never merged.. > Because they got buried in my INBOX. :-( -- Steve

Re: [kernel-hardening] Re: Linker segfault on powerpc when CONFIG_LKDTM=y (was Re: [kernel-hardening] [PATCH 3/5] lkdtm: add function for testing .rodata section)

On Mon, Aug 1, 2016 at 8:12 PM, Michael Ellerman wrote: > Kees Cook writes: > >> On Mon, Aug 1, 2016 at 5:37 AM, Michael Ellerman wrote: >>> Kees Cook writes: >>> This adds a function that lives in the .rodata section. The section flags are corrected using objcopy since there is no

Re: [git pull] drm for v4.8

On Tue, Aug 2, 2016 at 6:40 PM, Linus Torvalds wrote: > On Tue, Aug 2, 2016 at 4:10 AM, Ville Syrjälä > wrote: >> >> So PSR seems more likely. The underruns might point at some watermark >> fail though :( >> >> I have a couple of

Re: [RFC] usb: host: u132-hcd: Remove deprecated create_singlethread_workqueue

Hello, On Tue, Aug 02, 2016 at 03:29:48PM +0200, Oliver Neukum wrote: > Apparently if that is the requirement USB will have to define its own > set of flags to use in such contexts. But still the calls as currently > executed work. Taking away WQ_MEM_RECLAIM would create danger of > introducing a

Re: [git pull] drm for v4.8

On Tue, Aug 2, 2016 at 6:40 PM, Linus Torvalds wrote: > On Tue, Aug 2, 2016 at 4:10 AM, Ville Syrjälä > wrote: >> >> So PSR seems more likely. The underruns might point at some watermark >> fail though :( >> >> I have a couple of pending PSR patches you may want to try as well, >> if

Re: [RFC] usb: host: u132-hcd: Remove deprecated create_singlethread_workqueue

Hello, On Tue, Aug 02, 2016 at 03:29:48PM +0200, Oliver Neukum wrote: > Apparently if that is the requirement USB will have to define its own > set of flags to use in such contexts. But still the calls as currently > executed work. Taking away WQ_MEM_RECLAIM would create danger of > introducing a

Re: [PATCH] perf tests: objdump output can contain multi byte chunks

Em Wed, Jan 13, 2016 at 10:22:04AM +0200, Adrian Hunter escreveu: > On 12/01/16 17:30, Arnaldo Carvalho de Melo wrote: > > Em Tue, Jan 12, 2016 at 11:07:44AM +0100, Jan Stancek escreveu: > >> objdump's raw insn output can vary across architectures on number of > >> bytes per chunk (bpc) displayed

[PATCH] Staging: rtl8723au: rtw_xmit: fixed coding style issues

Fixed some coding style issues that were detected as errors. Signed-off-by: Shiva Kerdel --- drivers/staging/rtl8723au/core/rtw_xmit.c | 26 ++ 1 file changed, 10 insertions(+), 16 deletions(-) diff --git a/drivers/staging/rtl8723au/core/rtw_xmit.c

Re: [PATCH v1 1/2] x86/power/64: Support unaligned addresses for temporary mapping

On Mon, Aug 1, 2016 at 5:36 PM, Rafael J. Wysocki wrote: > On Monday, August 01, 2016 10:07:59 AM Thomas Garnier wrote: >> Correctly setup the temporary mapping for hibernation. Previous >> implementation assumed the address was aligned on the PGD level. With >> KASLR memory

Re: [PATCH] perf tests: objdump output can contain multi byte chunks

Em Wed, Jan 13, 2016 at 10:22:04AM +0200, Adrian Hunter escreveu: > On 12/01/16 17:30, Arnaldo Carvalho de Melo wrote: > > Em Tue, Jan 12, 2016 at 11:07:44AM +0100, Jan Stancek escreveu: > >> objdump's raw insn output can vary across architectures on number of > >> bytes per chunk (bpc) displayed

[PATCH] Staging: rtl8723au: rtw_xmit: fixed coding style issues

Fixed some coding style issues that were detected as errors. Signed-off-by: Shiva Kerdel --- drivers/staging/rtl8723au/core/rtw_xmit.c | 26 ++ 1 file changed, 10 insertions(+), 16 deletions(-) diff --git a/drivers/staging/rtl8723au/core/rtw_xmit.c

Re: [PATCH v1 1/2] x86/power/64: Support unaligned addresses for temporary mapping

On Mon, Aug 1, 2016 at 5:36 PM, Rafael J. Wysocki wrote: > On Monday, August 01, 2016 10:07:59 AM Thomas Garnier wrote: >> Correctly setup the temporary mapping for hibernation. Previous >> implementation assumed the address was aligned on the PGD level. With >> KASLR memory randomization

Re: [PATCH 1116/1285] Replace numeric parameter like 0444 with macro

On Tuesday 2016-08-02 14:17, Baole Ni wrote: >I find that the developers often just specified the numeric value >when calling a macro which is defined with a parameter for access permission. >As we know, these numeric value for access permission have had the >corresponding macro, >and that

Re: [PATCH 1116/1285] Replace numeric parameter like 0444 with macro

On Tuesday 2016-08-02 14:17, Baole Ni wrote: >I find that the developers often just specified the numeric value >when calling a macro which is defined with a parameter for access permission. >As we know, these numeric value for access permission have had the >corresponding macro, >and that

[PATCH] Staging: rtl8723au: rtw_xmit: Fixed operators spacing style issues

Fixed spaces around operators to fix their coding style issues. Signed-off-by: Shiva Kerdel --- drivers/staging/rtl8723au/core/rtw_xmit.c | 24 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/drivers/staging/rtl8723au/core/rtw_xmit.c

[PATCH] Staging: rtl8723au: rtw_xmit: Fixed operators spacing style issues

Fixed spaces around operators to fix their coding style issues. Signed-off-by: Shiva Kerdel --- drivers/staging/rtl8723au/core/rtw_xmit.c | 24 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/drivers/staging/rtl8723au/core/rtw_xmit.c

Re: [PATCH 0/2] tracing: hist trigger KASAN fixes

Hi Steve, It looks like these two patches were never merged.. Thanks, Tom On 06/29/2016 07:55 PM, Tom Zanussi wrote: > Dmitry Vyukov found and reported an issue with hist triggers when > running the hist trigger selftests, which Steve Rostedt sent a patch > for and which fixed part of the

Re: [Regression?] fib_rules: Added NLM_F_EXCL support to fib_nl_newrule breaks Android userspace

On Tue, Aug 2, 2016 at 10:09 AM, David Ahern wrote: > On 8/2/16 11:03 AM, John Stultz wrote: >> >> So bisecting between v4.7 and linus/HEAD with the test above, it seems >> like: >> 96c63fa7393d ("net: Add l3mdev rule") is what breaks the tests. >> >> The l3mdev rule

Re: [PATCH 0/2] tracing: hist trigger KASAN fixes

Hi Steve, It looks like these two patches were never merged.. Thanks, Tom On 06/29/2016 07:55 PM, Tom Zanussi wrote: > Dmitry Vyukov found and reported an issue with hist triggers when > running the hist trigger selftests, which Steve Rostedt sent a patch > for and which fixed part of the

Re: [Regression?] fib_rules: Added NLM_F_EXCL support to fib_nl_newrule breaks Android userspace

On Tue, Aug 2, 2016 at 10:09 AM, David Ahern wrote: > On 8/2/16 11:03 AM, John Stultz wrote: >> >> So bisecting between v4.7 and linus/HEAD with the test above, it seems >> like: >> 96c63fa7393d ("net: Add l3mdev rule") is what breaks the tests. >> >> The l3mdev rule patch is a bit tangled with

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