Here is another batch for warnings treated as error on ppc32. Tested with:
$ make ARCH=powerpc ppc32_defconfig
$ make -j8 ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- W=1
Using:
$ powerpc-linux-gnu-gcc --version
powerpc-linux-gnu-gcc (Debian 6.3.0-18) 6.3.0 20170516
Mathieu Malaterre (19):
Here is another batch for warnings treated as error on ppc32. Tested with:
$ make ARCH=powerpc ppc32_defconfig
$ make -j8 ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- W=1
Using:
$ powerpc-linux-gnu-gcc --version
powerpc-linux-gnu-gcc (Debian 6.3.0-18) 6.3.0 20170516
Mathieu Malaterre (19):
On Thu, Mar 22, 2018 at 11:06 AM, Patrick Bellasi
wrote:
[..]
>> > +static inline bool wake_energy(struct task_struct *p, int prev_cpu)
>> > +{
>> > + struct sched_domain *sd;
>> > +
>> > + if (!static_branch_unlikely(_energy_present))
>> > +
On Thu, Mar 22, 2018 at 11:06 AM, Patrick Bellasi
wrote:
[..]
>> > +static inline bool wake_energy(struct task_struct *p, int prev_cpu)
>> > +{
>> > + struct sched_domain *sd;
>> > +
>> > + if (!static_branch_unlikely(_energy_present))
>> > + return false;
>> > +
>> > +
Applying, thanks!--b.
On Mon, Mar 19, 2018 at 11:37:05PM +0100, Stefan Agner wrote:
> Use enum nfs_cb_opnum4 in decode_cb_op_status. This fixes warnings
> seen with clang:
> fs/nfsd/nfs4callback.c:451:36: warning: implicit conversion from
> enumeration type 'enum nfs_cb_opnum4' to
Applying, thanks!--b.
On Mon, Mar 19, 2018 at 11:37:05PM +0100, Stefan Agner wrote:
> Use enum nfs_cb_opnum4 in decode_cb_op_status. This fixes warnings
> seen with clang:
> fs/nfsd/nfs4callback.c:451:36: warning: implicit conversion from
> enumeration type 'enum nfs_cb_opnum4' to
On Thu, Mar 22, 2018 at 07:44:51PM +, Casey Leedom wrote:
> | From: Steve Wise
> | Sent: Thursday, March 22, 2018 9:28 AM
> |
> | | From: Sinan Kaya
> | | Date: Thursday, March 22, 2018 7:52 AM
> | |
> | | Isn't this a PowerPC problem? Why
On Thu, Mar 22, 2018 at 07:44:51PM +, Casey Leedom wrote:
> | From: Steve Wise
> | Sent: Thursday, March 22, 2018 9:28 AM
> |
> | | From: Sinan Kaya
> | | Date: Thursday, March 22, 2018 7:52 AM
> | |
> | | Isn't this a PowerPC problem? Why penalize other architectures?
> |
> | I worry it
On Thu, Mar 22, 2018 at 03:52:02PM +, Adam Thomson wrote:
> This commit adds code to handle requesting of PPS APDOs. Switching
> between standard PDOs and APDOs, and re-requesting an APDO to
> modify operating voltage/current will be triggered by an
> external call into TCPM.
>
>
On Thu, Mar 22, 2018 at 03:52:02PM +, Adam Thomson wrote:
> This commit adds code to handle requesting of PPS APDOs. Switching
> between standard PDOs and APDOs, and re-requesting an APDO to
> modify operating voltage/current will be triggered by an
> external call into TCPM.
>
>
On Thu, Mar 22, 2018 at 03:53:36PM +1030, Joel Stanley wrote:
> When debugging recent kernels, people will see '(ptrval)' but there
> isn't much information as to what that means. Briefly describe why it's
> there.
>
> Signed-off-by: Joel Stanley
> ---
>
On Thu, Mar 22, 2018 at 03:53:36PM +1030, Joel Stanley wrote:
> When debugging recent kernels, people will see '(ptrval)' but there
> isn't much information as to what that means. Briefly describe why it's
> there.
>
> Signed-off-by: Joel Stanley
> ---
>
On Wed, Mar 21, 2018 at 8:35 AM, Patrick Bellasi
wrote:
> [...]
>
>> @@ -6555,6 +6613,14 @@ select_task_rq_fair(struct task_struct *p, int
>> prev_cpu, int sd_flag, int wake_f
>> break;
>> }
>>
>> + /*
>> + *
On Wed, Mar 21, 2018 at 8:35 AM, Patrick Bellasi
wrote:
> [...]
>
>> @@ -6555,6 +6613,14 @@ select_task_rq_fair(struct task_struct *p, int
>> prev_cpu, int sd_flag, int wake_f
>> break;
>> }
>>
>> + /*
>> + * Energy-aware task
Assign true or false to boolean variables instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/ethernet/qlogic/qed/qed_dev.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
Assign true or false to boolean variables instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/ethernet/qlogic/qed/qed_dev.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
On Thu, 22 Mar 2018, Steven Rostedt wrote:
>
> The trace event trace_mm_vmscan_lru_shrink_inactive() currently has 12
> parameters! Seven of them are from the reclaim_stat structure. This
> structure is currently local to mm/vmscan.c. By moving it to the global
> vmstat.h header, we can also
On Thu, 22 Mar 2018, Steven Rostedt wrote:
>
> The trace event trace_mm_vmscan_lru_shrink_inactive() currently has 12
> parameters! Seven of them are from the reclaim_stat structure. This
> structure is currently local to mm/vmscan.c. By moving it to the global
> vmstat.h header, we can also
Oleksandr Natalenko wrote:
> Hi.
>
> On Mon, Mar 19, 2018 at 7:52 PM, Nadav Amit wrote:
>>> Oleksandr, if you can confirm that it fixes the bug you encountered, it
>>> would be great.
>>>
>>> Greg, Arnd, on your free time, please let me know if there is
Oleksandr Natalenko wrote:
> Hi.
>
> On Mon, Mar 19, 2018 at 7:52 PM, Nadav Amit wrote:
>>> Oleksandr, if you can confirm that it fixes the bug you encountered, it
>>> would be great.
>>>
>>> Greg, Arnd, on your free time, please let me know if there is any issue
>>> with the patch, and
Hi, are there any comments on this patch or the issue I described? I
have tested the FDGETPRM ioctl and confirmed that the struct it returns
does contain a pointer to kernel data. I also have tested my patch, and
with it applied the returned struct no longer contains a kernel pointer,
but all
Hi, are there any comments on this patch or the issue I described? I
have tested the FDGETPRM ioctl and confirmed that the struct it returns
does contain a pointer to kernel data. I also have tested my patch, and
with it applied the returned struct no longer contains a kernel pointer,
but all
From: Matthew Wilcox
free() can free many different kinds of memory.
Signed-off-by: Matthew Wilcox
---
include/linux/kernel.h | 2 ++
mm/util.c | 39 +++
2 files changed, 41 insertions(+)
diff
From: Matthew Wilcox
free() can free many different kinds of memory.
Signed-off-by: Matthew Wilcox
---
include/linux/kernel.h | 2 ++
mm/util.c | 39 +++
2 files changed, 41 insertions(+)
diff --git a/include/linux/kernel.h
Assign true or false to boolean variables instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/ethernet/freescale/dpaa/dpaa_ethtool.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Matthew Wilcox
Rename the trivial malloc and free implementations to tmalloc and tfree
to avoid a namespace collision with an in-kernel free() function.
Signed-off-by: Matthew Wilcox
---
include/linux/decompress/mm.h | 10 ++
1
From: Matthew Wilcox
Rename the trivial malloc and free implementations to tmalloc and tfree
to avoid a namespace collision with an in-kernel free() function.
Signed-off-by: Matthew Wilcox
---
include/linux/decompress/mm.h | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff
Assign true or false to boolean variables instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/ethernet/freescale/dpaa/dpaa_ethtool.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Matthew Wilcox
Today, kfree_rcu() can only free objects allocated using kmalloc().
There have been attempts to extend that to kvfree(), but I think we
should take it even further and allow freeing as many different objects
as possible.
It turns out many different
From: Matthew Wilcox
Today, kfree_rcu() can only free objects allocated using kmalloc().
There have been attempts to extend that to kvfree(), but I think we
should take it even further and allow freeing as many different objects
as possible.
It turns out many different kinds of memory
On Wed, 2018-03-21 at 21:42 -0700, Dan Williams wrote:
> Per the ACPI specification the only functional purpose for a DIMM
> Control Region to be mapped into the system physical address space, from
> an OSPM perspective, is to support block-apertures. However, there are
> some BIOSen that publish
From: Matthew Wilcox
The names of these static functions collide with a kernel-wide 'free'
function. Call them 'free_inst' instead.
Signed-off-by: Matthew Wilcox
---
crypto/lrw.c | 4 ++--
crypto/xts.c | 4 ++--
2 files changed, 4
On Wed, 2018-03-21 at 21:42 -0700, Dan Williams wrote:
> Per the ACPI specification the only functional purpose for a DIMM
> Control Region to be mapped into the system physical address space, from
> an OSPM perspective, is to support block-apertures. However, there are
> some BIOSen that publish
From: Matthew Wilcox
The names of these static functions collide with a kernel-wide 'free'
function. Call them 'free_inst' instead.
Signed-off-by: Matthew Wilcox
---
crypto/lrw.c | 4 ++--
crypto/xts.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/crypto/lrw.c
From: Matthew Wilcox
Now we can free memory allocated with all kinds of functions that aren't
kmalloc().
Signed-off-by: Matthew Wilcox
---
include/linux/rcupdate.h | 40 +++-
include/linux/rcutiny.h| 2
From: Matthew Wilcox
Now we can free memory allocated with all kinds of functions that aren't
kmalloc().
Signed-off-by: Matthew Wilcox
---
include/linux/rcupdate.h | 40 +++-
include/linux/rcutiny.h| 2 +-
include/linux/rcutree.h| 2 +-
Linus Torvalds wrote:
> On Thu, Mar 22, 2018 at 10:29 AM, Peter Zijlstra wrote:
>>
>> But why !? Either Cc me on more of the series such that the whole makes
>> sense, or better yet, write a proper Changelog.
>
> This is a common issue. We should encourage people to always
Linus Torvalds wrote:
> On Thu, Mar 22, 2018 at 10:29 AM, Peter Zijlstra wrote:
>>
>> But why !? Either Cc me on more of the series such that the whole makes
>> sense, or better yet, write a proper Changelog.
>
> This is a common issue. We should encourage people to always send at
> least the
Assign true or false to boolean variables instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/rtc/rtc-isl12022.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Assign true or false to boolean variables instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
---
drivers/rtc/rtc-isl12022.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-isl12022.c
On Thu, 22 Mar 2018 15:43:08 -0400 (EDT),
David Miller wrote :
> From: Maxime Chevallier
> Date: Thu, 22 Mar 2018 20:14:53 +0100
>
> > Hello David,
> >
> > On Thu, 22 Mar 2018 14:47:09 -0400 (EDT),
> > David Miller
On Thu, 22 Mar 2018 15:43:08 -0400 (EDT),
David Miller wrote :
> From: Maxime Chevallier
> Date: Thu, 22 Mar 2018 20:14:53 +0100
>
> > Hello David,
> >
> > On Thu, 22 Mar 2018 14:47:09 -0400 (EDT),
> > David Miller wrote :
> >
> >> From: Maxime Chevallier
> >> Date: Wed, 21 Mar 2018
| From: Steve Wise
| Sent: Thursday, March 22, 2018 9:28 AM
|
| | From: Sinan Kaya
| | Date: Thursday, March 22, 2018 7:52 AM
| |
| | Isn't this a PowerPC problem? Why penalize other architectures?
|
| I worry it breaks PPC.
And all other
| From: Steve Wise
| Sent: Thursday, March 22, 2018 9:28 AM
|
| | From: Sinan Kaya
| | Date: Thursday, March 22, 2018 7:52 AM
| |
| | Isn't this a PowerPC problem? Why penalize other architectures?
|
| I worry it breaks PPC.
And all other architectures. Aparraently there isn't a formal API
Recently I started to get the following sporadic errors. Maybe related:
When working with putty on the console then console frequently hangs
for few seconds.
linux-next from March 2nd still works fine.
Platform is x86_64, Zotac CI-321 with Intel 2961Y.
[ 9755.298719] INFO: rcu_sched detected
Recently I started to get the following sporadic errors. Maybe related:
When working with putty on the console then console frequently hangs
for few seconds.
linux-next from March 2nd still works fine.
Platform is x86_64, Zotac CI-321 with Intel 2961Y.
[ 9755.298719] INFO: rcu_sched detected
From: Maxime Chevallier
Date: Thu, 22 Mar 2018 20:14:53 +0100
> Hello David,
>
> On Thu, 22 Mar 2018 14:47:09 -0400 (EDT),
> David Miller wrote :
>
>> From: Maxime Chevallier
>> Date: Wed, 21 Mar 2018 16:14:00
From: Maxime Chevallier
Date: Thu, 22 Mar 2018 20:14:53 +0100
> Hello David,
>
> On Thu, 22 Mar 2018 14:47:09 -0400 (EDT),
> David Miller wrote :
>
>> From: Maxime Chevallier
>> Date: Wed, 21 Mar 2018 16:14:00 +0100
>>
>> In order to be an equivalent change you must bzero out this 'pe'
>>
Hi Marc,
On 03/22/2018 10:51 AM, Marc Zyngier wrote:
> On 22/03/18 01:58, Shanker Donthineni wrote:
>> The definition of the GICR_CTLR.RWP control bit was expanded to indicate
>> status of changing GICR_CTLR.EnableLPI from 1 to 0 is being in progress
>> or completed. Software must observe
Hi Marc,
On 03/22/2018 10:51 AM, Marc Zyngier wrote:
> On 22/03/18 01:58, Shanker Donthineni wrote:
>> The definition of the GICR_CTLR.RWP control bit was expanded to indicate
>> status of changing GICR_CTLR.EnableLPI from 1 to 0 is being in progress
>> or completed. Software must observe
From: Salil Mehta
Date: Thu, 22 Mar 2018 14:28:51 +
> This patch-set adds the support of VF reset to the existing VF driver.
> VF Reset can be triggered due to TX watchdog firing as a result of TX
> data-path not working. VF reset could also be a result of some
From: Salil Mehta
Date: Thu, 22 Mar 2018 14:28:51 +
> This patch-set adds the support of VF reset to the existing VF driver.
> VF Reset can be triggered due to TX watchdog firing as a result of TX
> data-path not working. VF reset could also be a result of some internal
> configuration
Hi!
> > user@devuan:/sys/devices/platform/4400.ocp/4a064000.usbhshost$
> > sudo lsusb
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > user@devuan:/sys/devices/platform/4400.ocp/4a064000.usbhshost$
>
Hi!
> > user@devuan:/sys/devices/platform/4400.ocp/4a064000.usbhshost$
> > sudo lsusb
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> > user@devuan:/sys/devices/platform/4400.ocp/4a064000.usbhshost$
>
Hi all,
I was just wondering about the status of this patch.
Thanks!
--
Gustavo
On 03/05/2018 04:05 PM, Gustavo A. R. Silva wrote:
Assign true or false to boolean variables instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
Hi all,
I was just wondering about the status of this patch.
Thanks!
--
Gustavo
On 03/05/2018 04:05 PM, Gustavo A. R. Silva wrote:
Assign true or false to boolean variables instead of an integer value.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
The efi_pgd is allocated as PGD_ALLOCATION_ORDER pages and so should
also be freed as PGD_ALLOCATION_ORDER pages with free_pages().
Fixes: d9e9a6418065 ("x86/mm/pti: Allocate a separate user PGD")
Signed-off-by: Waiman Long
---
arch/x86/platform/efi/efi_64.c | 2 +-
1 file
The efi_pgd is allocated as PGD_ALLOCATION_ORDER pages and so should
also be freed as PGD_ALLOCATION_ORDER pages with free_pages().
Fixes: d9e9a6418065 ("x86/mm/pti: Allocate a separate user PGD")
Signed-off-by: Waiman Long
---
arch/x86/platform/efi/efi_64.c | 2 +-
1 file changed, 1
Hello David,
On Thu, 22 Mar 2018 14:47:09 -0400 (EDT),
David Miller wrote :
> From: Maxime Chevallier
> Date: Wed, 21 Mar 2018 16:14:00 +0100
>
> > diff --git a/drivers/net/ethernet/marvell/mvpp2.c
> > b/drivers/net/ethernet/marvell/mvpp2.c
Hello David,
On Thu, 22 Mar 2018 14:47:09 -0400 (EDT),
David Miller wrote :
> From: Maxime Chevallier
> Date: Wed, 21 Mar 2018 16:14:00 +0100
>
> > diff --git a/drivers/net/ethernet/marvell/mvpp2.c
> > b/drivers/net/ethernet/marvell/mvpp2.c index
> > 9bd35f2291d6..28e33e139178 100644 ---
> >
2018-03-21 22:12 GMT-07:00 Srivatsa S. Bhat :
> On 3/21/18 7:02 PM, Steve French wrote:
>> Found a patch which solves the dependency issue. In my testing (on
>> 4.9, with Windows 2016, and also to Samba) as Pavel suggested this
>> appears to fix the problem, but I will let
2018-03-21 22:12 GMT-07:00 Srivatsa S. Bhat :
> On 3/21/18 7:02 PM, Steve French wrote:
>> Found a patch which solves the dependency issue. In my testing (on
>> 4.9, with Windows 2016, and also to Samba) as Pavel suggested this
>> appears to fix the problem, but I will let Srivatsa confirm that
From: Haiyang Zhang
As defined in hyperv_net.h, the NVSP_STAT_SUCCESS is one not zero.
Some functions returns 0 when it actually means NVSP_STAT_SUCCESS.
This patch fixes them.
In netvsc_receive(), it puts the last RNDIS packet's receive status
for all packets in a
From: Haiyang Zhang
As defined in hyperv_net.h, the NVSP_STAT_SUCCESS is one not zero.
Some functions returns 0 when it actually means NVSP_STAT_SUCCESS.
This patch fixes them.
In netvsc_receive(), it puts the last RNDIS packet's receive status
for all packets in a vmxferpage which may contain
From: Haiyang Zhang
Fix the status code returned to the host. Also add range
check for rx packet offset and length.
Haiyang Zhang (2):
hv_netvsc: Fix the return status in RX path
hv_netvsc: Add range checking for rx packet offset and length
From: Haiyang Zhang
This patch adds range checking for rx packet offset and length.
It may only happen if there is a host side bug.
Signed-off-by: Haiyang Zhang
---
drivers/net/hyperv/hyperv_net.h | 1 +
drivers/net/hyperv/netvsc.c | 17
From: Haiyang Zhang
Fix the status code returned to the host. Also add range
check for rx packet offset and length.
Haiyang Zhang (2):
hv_netvsc: Fix the return status in RX path
hv_netvsc: Add range checking for rx packet offset and length
drivers/net/hyperv/hyperv_net.h | 1 +
From: Haiyang Zhang
This patch adds range checking for rx packet offset and length.
It may only happen if there is a host side bug.
Signed-off-by: Haiyang Zhang
---
drivers/net/hyperv/hyperv_net.h | 1 +
drivers/net/hyperv/netvsc.c | 17 +++--
2 files changed, 16
Move adis16201 driver out of staging and merge into mainline
IIO subsystem.
Signed-off-by: Himanshu Jha
---
drivers/iio/accel/Kconfig | 12 ++
drivers/iio/accel/Makefile| 1 +
drivers/iio/accel/adis16201.c | 321
Move adis16201 driver out of staging and merge into mainline
IIO subsystem.
Signed-off-by: Himanshu Jha
---
drivers/iio/accel/Kconfig | 12 ++
drivers/iio/accel/Makefile| 1 +
drivers/iio/accel/adis16201.c | 321 ++
Use GENMASK to improve readability and remove the local variables used to
store intermediate data.
Signed-off-by: Himanshu Jha
---
drivers/staging/iio/accel/adis16201.c | 34 +++---
1 file changed, 15 insertions(+), 19 deletions(-)
diff
Use GENMASK to improve readability and remove the local variables used to
store intermediate data.
Signed-off-by: Himanshu Jha
---
drivers/staging/iio/accel/adis16201.c | 34 +++---
1 file changed, 15 insertions(+), 19 deletions(-)
diff --git
Remove few unused headers files since the adis core handles the buffer and
sysfs support.
Signed-off-by: Himanshu Jha
---
drivers/staging/iio/accel/adis16201.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/iio/accel/adis16201.c
Remove few unused headers files since the adis core handles the buffer and
sysfs support.
Signed-off-by: Himanshu Jha
---
drivers/staging/iio/accel/adis16201.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/iio/accel/adis16201.c
b/drivers/staging/iio/accel/adis16201.c
Split the line over 80 characters limit to fix checkpatch
warning.
Signed-off-by: Himanshu Jha
---
drivers/staging/iio/accel/adis16201.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/iio/accel/adis16201.c
Split the line over 80 characters limit to fix checkpatch
warning.
Signed-off-by: Himanshu Jha
---
drivers/staging/iio/accel/adis16201.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/iio/accel/adis16201.c
b/drivers/staging/iio/accel/adis16201.c
index
On Thu, Mar 22, 2018 at 12:32:18PM -0400, Rik van Riel wrote:
> On Wed, 2018-03-14 at 13:04 +0100, Peter Zijlstra wrote:
>
> > On x86 we don't have to use that time_check_counter thing,
> > sched_clock()
> > is really cheap, not sure if it makes sense on other platforms.
>
> Are you sure? I saw
On Thu, Mar 22, 2018 at 12:32:18PM -0400, Rik van Riel wrote:
> On Wed, 2018-03-14 at 13:04 +0100, Peter Zijlstra wrote:
>
> > On x86 we don't have to use that time_check_counter thing,
> > sched_clock()
> > is really cheap, not sure if it makes sense on other platforms.
>
> Are you sure? I saw
On 2018.03.22 09:32 Rik van Riel wrote:
> On Wed, 2018-03-14 at 13:04 +0100, Peter Zijlstra wrote:
>
>> On x86 we don't have to use that time_check_counter thing,
>> sched_clock()
>> is really cheap, not sure if it makes sense on other platforms.
>
> Are you sure? I saw a 5-10% increase in CPU
On 2018.03.22 09:32 Rik van Riel wrote:
> On Wed, 2018-03-14 at 13:04 +0100, Peter Zijlstra wrote:
>
>> On x86 we don't have to use that time_check_counter thing,
>> sched_clock()
>> is really cheap, not sure if it makes sense on other platforms.
>
> Are you sure? I saw a 5-10% increase in CPU
On 3/22/2018 1:48 PM, Jason Gunthorpe wrote:
>> AFAIS, even writeq won't compile on this arch. I started questioning this
>> build test.
> I have the same confusion. Did you figure out an explanation?
I did a compile test without the relaxed change. It built just fine.
CONFIG_64BIT is also not
On 3/22/2018 1:48 PM, Jason Gunthorpe wrote:
>> AFAIS, even writeq won't compile on this arch. I started questioning this
>> build test.
> I have the same confusion. Did you figure out an explanation?
I did a compile test without the relaxed change. It built just fine.
CONFIG_64BIT is also not
On Thu, Mar 22, 2018 at 06:52:51PM +0100, Greg Kroah-Hartman wrote:
[ ... ]
>
> And that't the point to drive home here. If you stay away from updating
> to stable patches, you have a huge boatload of KNOWN SECURITY HOLES in
> your product. If you take them, you have the _possiblity_ of some
On Thu, Mar 22, 2018 at 06:52:51PM +0100, Greg Kroah-Hartman wrote:
[ ... ]
>
> And that't the point to drive home here. If you stay away from updating
> to stable patches, you have a huge boatload of KNOWN SECURITY HOLES in
> your product. If you take them, you have the _possiblity_ of some
El Thu, Mar 01, 2018 at 10:31:02AM + Dave Martin ha dit:
> On Thu, Mar 01, 2018 at 09:45:24AM +, Robin Murphy wrote:
> > Hi Andrey,
> >
> > On 28/02/18 19:32, Andrey Konovalov wrote:
> > >Hi Marc!
> > >
> > >I've tried to pull in new upstream commits and the kernel build
> > >started
El Thu, Mar 01, 2018 at 10:31:02AM + Dave Martin ha dit:
> On Thu, Mar 01, 2018 at 09:45:24AM +, Robin Murphy wrote:
> > Hi Andrey,
> >
> > On 28/02/18 19:32, Andrey Konovalov wrote:
> > >Hi Marc!
> > >
> > >I've tried to pull in new upstream commits and the kernel build
> > >started
From: Colin King
Date: Wed, 21 Mar 2018 19:34:58 +
> From: Colin Ian King
>
> The current logic of flags | TUNNEL_SEQ is always non-zero and hence
> sequence numbers are always incremented no matter the setting of the
> TUNNEL_SEQ bit.
From: Colin King
Date: Wed, 21 Mar 2018 19:34:58 +
> From: Colin Ian King
>
> The current logic of flags | TUNNEL_SEQ is always non-zero and hence
> sequence numbers are always incremented no matter the setting of the
> TUNNEL_SEQ bit. Fix this by using & instead of |.
>
> Detected by
On Thu, Mar 22, 2018 at 02:39:17PM -0400, Daniel Jordan wrote:
> Shouldn't the anon column also contain lru?
Probably; I didn't finish investigating everything. There should probably
also be another column for swap pages. Maybe some other users use a
significant amount of the struct page ... ?
On Thu, Mar 22, 2018 at 02:39:17PM -0400, Daniel Jordan wrote:
> Shouldn't the anon column also contain lru?
Probably; I didn't finish investigating everything. There should probably
also be another column for swap pages. Maybe some other users use a
significant amount of the struct page ... ?
From: Colin King
Date: Wed, 21 Mar 2018 17:31:15 +
> From: Colin Ian King
>
> Array mvpp2_pools is being indexed by long_log_pool, however this
> looks like a cut-n-paste bug and in fact should be short_log_pool.
>
> Detected by
On Thu, Mar 22, 2018 at 08:48:35AM -0400, ok...@codeaurora.org wrote:
> On 2018-03-22 08:24, ok...@codeaurora.org wrote:
> >On 2018-03-22 02:44, kbuild test robot wrote:
> >>Hi Sinan,
> >>
> >>Thank you for the patch! Yet something to improve:
> >>
> >>[auto build test ERROR on linus/master]
>
On Thu, Mar 22, 2018 at 08:48:35AM -0400, ok...@codeaurora.org wrote:
> On 2018-03-22 08:24, ok...@codeaurora.org wrote:
> >On 2018-03-22 02:44, kbuild test robot wrote:
> >>Hi Sinan,
> >>
> >>Thank you for the patch! Yet something to improve:
> >>
> >>[auto build test ERROR on linus/master]
>
From: Colin King
Date: Wed, 21 Mar 2018 17:31:15 +
> From: Colin Ian King
>
> Array mvpp2_pools is being indexed by long_log_pool, however this
> looks like a cut-n-paste bug and in fact should be short_log_pool.
>
> Detected by CoverityScan, CID#1466113 ("Copy-paste error")
>
> Fixes:
On Thu, Mar 22, 2018 at 10:34:08AM -0700, Yang Shi wrote:
> On 3/21/18 10:29 AM, Matthew Wilcox wrote:
> > Take the mmap_sem for write
> > Find the VMA
> >If the VMA is large(*)
> > Mark the VMA as deleted
> > Drop the mmap_sem
> > zap all of the entries
> > Take the
On Thu, Mar 22, 2018 at 10:34:08AM -0700, Yang Shi wrote:
> On 3/21/18 10:29 AM, Matthew Wilcox wrote:
> > Take the mmap_sem for write
> > Find the VMA
> >If the VMA is large(*)
> > Mark the VMA as deleted
> > Drop the mmap_sem
> > zap all of the entries
> > Take the
From: Maxime Chevallier
Date: Wed, 21 Mar 2018 16:14:00 +0100
> diff --git a/drivers/net/ethernet/marvell/mvpp2.c
> b/drivers/net/ethernet/marvell/mvpp2.c
> index 9bd35f2291d6..28e33e139178 100644
> --- a/drivers/net/ethernet/marvell/mvpp2.c
> +++
From: Maxime Chevallier
Date: Wed, 21 Mar 2018 16:14:00 +0100
> diff --git a/drivers/net/ethernet/marvell/mvpp2.c
> b/drivers/net/ethernet/marvell/mvpp2.c
> index 9bd35f2291d6..28e33e139178 100644
> --- a/drivers/net/ethernet/marvell/mvpp2.c
> +++ b/drivers/net/ethernet/marvell/mvpp2.c
> @@
On Thu, Mar 22, 2018 at 10:28:13AM -0400, Sinan Kaya wrote:
>On 03/22/2018 08:48 AM, [1]ok...@codeaurora.org wrote:
>
> Jason,
> Can you remove the writeq change if it is too late for me to fix?
> This is an infrastructural issue on xtensa arch.
> Probably, it won't get
On Thu, Mar 22, 2018 at 10:28:13AM -0400, Sinan Kaya wrote:
>On 03/22/2018 08:48 AM, [1]ok...@codeaurora.org wrote:
>
> Jason,
> Can you remove the writeq change if it is too late for me to fix?
> This is an infrastructural issue on xtensa arch.
> Probably, it won't get
501 - 600 of 1678 matches
Mail list logo