linux-next: build failure after merge of the bpf-next tree

user space to query prog array on the same tp") CONFIG_BPF_SYSCALL is not set for this build. I have used the bpf-next tree from next-20171212 for today. -- Cheers, Stephen Rothwell

linux-next: build failure after merge of the bpf-next tree

user space to query prog array on the same tp") CONFIG_BPF_SYSCALL is not set for this build. I have used the bpf-next tree from next-20171212 for today. -- Cheers, Stephen Rothwell

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Tue, Dec 12, 2017 at 05:04:37PM -0800, Jakub Kicinski wrote: > On Wed, 13 Dec 2017 00:36:59 +, Al Viro wrote: > > On Tue, Dec 12, 2017 at 03:59:33PM -0800, Jakub Kicinski wrote: > > > > +static __always_inline __##type type##_replace_bits(__##type old, > > > > \ > > > > +

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Tue, Dec 12, 2017 at 05:04:37PM -0800, Jakub Kicinski wrote: > On Wed, 13 Dec 2017 00:36:59 +, Al Viro wrote: > > On Tue, Dec 12, 2017 at 03:59:33PM -0800, Jakub Kicinski wrote: > > > > +static __always_inline __##type type##_replace_bits(__##type old, > > > > \ > > > > +

Re: [PATCH net-next 1/3] net:tracepoint: replace tcp_set_state tracepoint with sock_set_state tracepoint

> On Dec 10, 2017, at 7:31 AM, Yafang Shao wrote: > > As sk_state is a common field for struct sock, so the state > transition should not be a TCP specific feature. > So I rename tcp_set_state tracepoint to sock_set_state tracepoint with > some minor changes and move it

Re: [PATCH net-next 1/3] net:tracepoint: replace tcp_set_state tracepoint with sock_set_state tracepoint

> On Dec 10, 2017, at 7:31 AM, Yafang Shao wrote: > > As sk_state is a common field for struct sock, so the state > transition should not be a TCP specific feature. > So I rename tcp_set_state tracepoint to sock_set_state tracepoint with > some minor changes and move it into file

Re: [PATCH] vfio: Simplify capability helper

On 13/12/17 06:59, Alex Williamson wrote: > The vfio_info_add_capability() helper requires the caller to pass a > capability ID, which it then uses to fill in header fields, assuming > hard coded versions. This makes for an awkward and rigid interface. > The only thing we want this helper to do

Re: [PATCH] vfio: Simplify capability helper

On 13/12/17 06:59, Alex Williamson wrote: > The vfio_info_add_capability() helper requires the caller to pass a > capability ID, which it then uses to fill in header fields, assuming > hard coded versions. This makes for an awkward and rigid interface. > The only thing we want this helper to do

Re: [PATCH 00/11] fs: use freeze_fs on suspend/hibernate

On Thursday, November 30, 2017 12:23:45 AM CET Luis R. Rodriguez wrote: > This is a followup from the original RFC which proposed to start > to kill kthread freezing all together [0]. Instead of going straight > out to the jugular for kthread freezing this series only addresses > killing freezer

Re: [PATCH 00/11] fs: use freeze_fs on suspend/hibernate

On Thursday, November 30, 2017 12:23:45 AM CET Luis R. Rodriguez wrote: > This is a followup from the original RFC which proposed to start > to kill kthread freezing all together [0]. Instead of going straight > out to the jugular for kthread freezing this series only addresses > killing freezer

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Wed, 13 Dec 2017 00:36:59 +, Al Viro wrote: > On Tue, Dec 12, 2017 at 03:59:33PM -0800, Jakub Kicinski wrote: > > > +static __always_inline __##type type##_replace_bits(__##type old, > > > \ > > > + base val, base mask)\ > > > +{

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Wed, 13 Dec 2017 00:36:59 +, Al Viro wrote: > On Tue, Dec 12, 2017 at 03:59:33PM -0800, Jakub Kicinski wrote: > > > +static __always_inline __##type type##_replace_bits(__##type old, > > > \ > > > + base val, base mask)\ > > > +{

Re: [PATCH] powercap: Remove reassignment

On Saturday, November 11, 2017 6:47:26 PM CET Arvind Yadav wrote: > It is not necessary to reassignment of 'result'. > Here, result is being initialized zero and then updated with > seed_constraint_attributes(). > class_register is enough to return successful and error value. > > Signed-off-by:

Re: [PATCH] powercap: Remove reassignment

On Saturday, November 11, 2017 6:47:26 PM CET Arvind Yadav wrote: > It is not necessary to reassignment of 'result'. > Here, result is being initialized zero and then updated with > seed_constraint_attributes(). > class_register is enough to return successful and error value. > > Signed-off-by:

Re: [PATCH] drivers/staging/irda: fix max dup length for kstrndup

On 12/13/2017 02:27 AM, Stephen Hemminger wrote: > On Tue, 12 Dec 2017 16:54:44 +0800 > Ma Shimiao wrote: > >> If source string longer than max, kstrndup will alloc max+1 space. >> So, we should make sure the result will not over limit. >> >> Signed-off-by: Ma

Re: [PATCH] drivers/staging/irda: fix max dup length for kstrndup

On 12/13/2017 02:27 AM, Stephen Hemminger wrote: > On Tue, 12 Dec 2017 16:54:44 +0800 > Ma Shimiao wrote: > >> If source string longer than max, kstrndup will alloc max+1 space. >> So, we should make sure the result will not over limit. >> >> Signed-off-by: Ma Shimiao > > Did you read the TODO

Re: linux-next: the drivers-x86 tree has moved?

Hi Darren, On Tue, 12 Dec 2017 15:43:30 -0800 Darren Hart wrote: > > On Wed, Dec 13, 2017 at 08:02:27AM +1100, Stephen Rothwell wrote: > > > > I noticed commit > > > > 960652046899 ("MAINTAINERS: Update tree for platform-drivers-x86") > > > > Should I also change

Re: linux-next: the drivers-x86 tree has moved?

Hi Darren, On Tue, 12 Dec 2017 15:43:30 -0800 Darren Hart wrote: > > On Wed, Dec 13, 2017 at 08:02:27AM +1100, Stephen Rothwell wrote: > > > > I noticed commit > > > > 960652046899 ("MAINTAINERS: Update tree for platform-drivers-x86") > > > > Should I also change linu-next to use the new

Re: [patches] [PATCH v2] riscv/ftrace: Add basic support

On Mon, Dec 11, 2017 at 10:15:58AM -0800, Palmer Dabbelt wrote: > On Wed, 06 Dec 2017 18:31:10 PST (-0800), noner...@gmail.com wrote: Hi Palmer, I forgot to explain this section in the previous reply: > > +ENTRY(_mcount) > > + la t4, ftrace_stub > > +#ifdef CONFIG_FUNCTION_GRAPH_TRACER

Re: [patches] [PATCH v2] riscv/ftrace: Add basic support

On Mon, Dec 11, 2017 at 10:15:58AM -0800, Palmer Dabbelt wrote: > On Wed, 06 Dec 2017 18:31:10 PST (-0800), noner...@gmail.com wrote: Hi Palmer, I forgot to explain this section in the previous reply: > > +ENTRY(_mcount) > > + la t4, ftrace_stub > > +#ifdef CONFIG_FUNCTION_GRAPH_TRACER

RE: [PATCH 3/6] x86/hyper-v: reenlightenment notifications support

On Fri, Dec 08, 2017 at 11:49:57AM +0100, Vitaly Kuznetsov wrote: > -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Friday, December 8, 2017 2:50 AM > To: k...@vger.kernel.org; x...@kernel.org > Cc: Paolo Bonzini ; Radim Krčmář

RE: [PATCH 3/6] x86/hyper-v: reenlightenment notifications support

On Fri, Dec 08, 2017 at 11:49:57AM +0100, Vitaly Kuznetsov wrote: > -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Friday, December 8, 2017 2:50 AM > To: k...@vger.kernel.org; x...@kernel.org > Cc: Paolo Bonzini ; Radim Krčmář ; > Thomas > Gleixner ;

[PATCH v7 2/4] MIPS: Octeon: Automatically provision CVMSEG space.

Remove CONFIG_CAVIUM_OCTEON_CVMSEG_SIZE and automatically calculate the amount of CVMSEG space needed. 1st 128-bytes: Use by IOBDMA 2nd 128-bytes: Reserved by kernel for scratch/TLS emulation. 3rd 128-bytes: OCTEON-III LMTLINE New config variable CONFIG_CAVIUM_OCTEON_EXTRA_CVMSEG provisions

[PATCH v7 2/4] MIPS: Octeon: Automatically provision CVMSEG space.

Remove CONFIG_CAVIUM_OCTEON_CVMSEG_SIZE and automatically calculate the amount of CVMSEG space needed. 1st 128-bytes: Use by IOBDMA 2nd 128-bytes: Reserved by kernel for scratch/TLS emulation. 3rd 128-bytes: OCTEON-III LMTLINE New config variable CONFIG_CAVIUM_OCTEON_EXTRA_CVMSEG provisions

[PATCH v7 1/4] MIPS: Octeon: Enable LMTDMA/LMTST operations.

From: Carlos Munoz LMTDMA/LMTST operations move data between cores and I/O devices: * LMTST operations can send an address and a variable length (up to 128 bytes) of data to an I/O device. * LMTDMA operations can send an address and a variable length (up to 128) of data

[PATCH v7 4/4] MIPS: Octeon: Add a global resource manager.

From: Carlos Munoz Add a global resource manager to manage tagged pointers within bootmem allocated memory. This is used by various functional blocks in the Octeon core like the FPA, Ethernet nexus, etc. Signed-off-by: Carlos Munoz Signed-off-by: Steven J.

[PATCH v7 1/4] MIPS: Octeon: Enable LMTDMA/LMTST operations.

From: Carlos Munoz LMTDMA/LMTST operations move data between cores and I/O devices: * LMTST operations can send an address and a variable length (up to 128 bytes) of data to an I/O device. * LMTDMA operations can send an address and a variable length (up to 128) of data to the I/O device

[PATCH v7 4/4] MIPS: Octeon: Add a global resource manager.

From: Carlos Munoz Add a global resource manager to manage tagged pointers within bootmem allocated memory. This is used by various functional blocks in the Octeon core like the FPA, Ethernet nexus, etc. Signed-off-by: Carlos Munoz Signed-off-by: Steven J. Hill Signed-off-by: David Daney ---

[PATCH v7 0/4] Prerequisites for Cavium OCTEON-III network driver.

We want to add the Cavium OCTEON-III network driver. But since interacting with the input and output queues is done via special CPU local memory, we also need to add support to the MIPS/Octeon architecture code. Aren't SoCs nice in this way? These are the prerequisite patches that are needed

[PATCH v7 0/4] Prerequisites for Cavium OCTEON-III network driver.

We want to add the Cavium OCTEON-III network driver. But since interacting with the input and output queues is done via special CPU local memory, we also need to add support to the MIPS/Octeon architecture code. Aren't SoCs nice in this way? These are the prerequisite patches that are needed

[PATCH v7 3/4] staging: octeon: Remove USE_ASYNC_IOBDMA macro.

Previous patch sets USE_ASYNC_IOBDMA to 1 unconditionally. Remove USE_ASYNC_IOBDMA from all if statements. Remove dead code caused by the change. Acked-by: Greg Kroah-Hartman Signed-off-by: David Daney ---

[PATCH v7 3/4] staging: octeon: Remove USE_ASYNC_IOBDMA macro.

Previous patch sets USE_ASYNC_IOBDMA to 1 unconditionally. Remove USE_ASYNC_IOBDMA from all if statements. Remove dead code caused by the change. Acked-by: Greg Kroah-Hartman Signed-off-by: David Daney --- drivers/staging/octeon/ethernet-defines.h | 6 ---

[PATCH 2/9] README: document group fsgqa is required

The group fsgqa is also required. Signed-off-by: Luis R. Rodriguez --- README | 1 + 1 file changed, 1 insertion(+) diff --git a/README b/README index e05142be1a87..271d7df22b56 100644 --- a/README +++ b/README @@ -20,6 +20,7 @@ ___ - run make - run

[PATCH 2/9] README: document group fsgqa is required

The group fsgqa is also required. Signed-off-by: Luis R. Rodriguez --- README | 1 + 1 file changed, 1 insertion(+) diff --git a/README b/README index e05142be1a87..271d7df22b56 100644 --- a/README +++ b/README @@ -20,6 +20,7 @@ ___ - run make - run make install - create

[PATCH 6/9] tests/ext4/group: add group for tests which require a logdev

This should make it easy to run these separately or exclude them. Signed-off-by: Luis R. Rodriguez --- tests/ext4/group | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/ext4/group b/tests/ext4/group index 257bb646f312..6fa2f06432f3 100644 ---

[PATCH 6/9] tests/ext4/group: add group for tests which require a logdev

This should make it easy to run these separately or exclude them. Signed-off-by: Luis R. Rodriguez --- tests/ext4/group | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/ext4/group b/tests/ext4/group index 257bb646f312..6fa2f06432f3 100644 --- a/tests/ext4/group +++

[PATCH 0/9] fstests: few updates

I've deployed fstests on a relatively new system and ran into a few setup snags which can be fixed easily. Other than this I also ran into a few issues running a few tests which can easily also be fixed. I've added a few new groups to help avoiding running tests with a basic section. Some of

[PATCH 4/9] build: update AC_PACKAGE_WANT_GDBM() and src/dbtest.c to build

Modern gdbm-devel packages bundle together gdbm.h and ndbm.h. The old m4 macro had detection support for some old gdbm libraries but not for new ones. We fix compilation of src/dbtest.c by making the autoconf helper check for this new arrangement: If both gdbm.h and gdbm.h are found define set

[PATCH 0/9] fstests: few updates

I've deployed fstests on a relatively new system and ran into a few setup snags which can be fixed easily. Other than this I also ran into a few issues running a few tests which can easily also be fixed. I've added a few new groups to help avoiding running tests with a basic section. Some of

[PATCH 4/9] build: update AC_PACKAGE_WANT_GDBM() and src/dbtest.c to build

Modern gdbm-devel packages bundle together gdbm.h and ndbm.h. The old m4 macro had detection support for some old gdbm libraries but not for new ones. We fix compilation of src/dbtest.c by making the autoconf helper check for this new arrangement: If both gdbm.h and gdbm.h are found define set

[PATCH 7/9] tests/xfs/group: add realtimedev group

This groups up tests which require an external realtime volume, ie, SCRATCH_RTDEV. This requires CONFIG_XFS_RT and not all kernels support this. Signed-off-by: Luis R. Rodriguez --- tests/xfs/group | 36 ++-- 1 file changed, 18 insertions(+),

[PATCH 7/9] tests/xfs/group: add realtimedev group

This groups up tests which require an external realtime volume, ie, SCRATCH_RTDEV. This requires CONFIG_XFS_RT and not all kernels support this. Signed-off-by: Luis R. Rodriguez --- tests/xfs/group | 36 ++-- 1 file changed, 18 insertions(+), 18 deletions(-)

[PATCH 8/9] tests/xfs/group: add group for tests which require mkfs v4_5

This lets us skip these tests on newer systems. Signed-off-by: Luis R. Rodriguez --- tests/xfs/group | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/xfs/group b/tests/xfs/group index 656b65f5fe7a..ebb1685e22eb 100644 --- a/tests/xfs/group +++

[PATCH 8/9] tests/xfs/group: add group for tests which require mkfs v4_5

This lets us skip these tests on newer systems. Signed-off-by: Luis R. Rodriguez --- tests/xfs/group | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/xfs/group b/tests/xfs/group index 656b65f5fe7a..ebb1685e22eb 100644 --- a/tests/xfs/group +++ b/tests/xfs/group @@ -93,7

[PATCH 9/9] tests/xfs/group: add injection group

XFS error injection requires CONFIG_XFS_DEBUG and not all kernels have this enabled. Signed-off-by: Luis R. Rodriguez --- tests/xfs/group | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tests/xfs/group b/tests/xfs/group index

[PATCH 9/9] tests/xfs/group: add injection group

XFS error injection requires CONFIG_XFS_DEBUG and not all kernels have this enabled. Signed-off-by: Luis R. Rodriguez --- tests/xfs/group | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tests/xfs/group b/tests/xfs/group index ebb1685e22eb..1df0ab32b71c 100644 ---

[PATCH 3/9] generic/group: add 304 to dedupe group

Signed-off-by: Luis R. Rodriguez --- tests/generic/group | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/generic/group b/tests/generic/group index 6c3bb03a9973..4e2fb0f720ba 100644 --- a/tests/generic/group +++ b/tests/generic/group @@ -306,7 +306,7

[PATCH 5/9] tests/xfs/group: add group for tests which require a logdev

This should make it easy to run these separately or exclude them. Signed-off-by: Luis R. Rodriguez --- tests/xfs/group | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/xfs/group b/tests/xfs/group index d23006041ea2..cce98847de53 100644 ---

[PATCH 1/9] generic/381: use username fsgqa-381

Some systems are not allowing usernames prefixed with a number now. One can however use numbers as a postfix so use that. Signed-off-by: Luis R. Rodriguez --- README| 2 +- tests/generic/381 | 16 tests/generic/381.out | 4 ++-- 3 files

[PATCH 3/9] generic/group: add 304 to dedupe group

Signed-off-by: Luis R. Rodriguez --- tests/generic/group | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/generic/group b/tests/generic/group index 6c3bb03a9973..4e2fb0f720ba 100644 --- a/tests/generic/group +++ b/tests/generic/group @@ -306,7 +306,7 @@ 301 auto quick

[PATCH 5/9] tests/xfs/group: add group for tests which require a logdev

This should make it easy to run these separately or exclude them. Signed-off-by: Luis R. Rodriguez --- tests/xfs/group | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/xfs/group b/tests/xfs/group index d23006041ea2..cce98847de53 100644 --- a/tests/xfs/group +++

[PATCH 1/9] generic/381: use username fsgqa-381

Some systems are not allowing usernames prefixed with a number now. One can however use numbers as a postfix so use that. Signed-off-by: Luis R. Rodriguez --- README| 2 +- tests/generic/381 | 16 tests/generic/381.out | 4 ++-- 3 files changed, 11

Re: [PATCH v2 06/13] dt-bindings: mips: Add bindings for Microsemi SoCs

On Fri, Dec 08, 2017 at 04:46:11PM +0100, Alexandre Belloni wrote: > Add bindings for Microsemi SoCs. Currently only Ocelot is supported. > > Cc: Rob Herring > Cc: devicet...@vger.kernel.org > Signed-off-by: Alexandre Belloni > --- >

Re: [PATCH v2 06/13] dt-bindings: mips: Add bindings for Microsemi SoCs

On Fri, Dec 08, 2017 at 04:46:11PM +0100, Alexandre Belloni wrote: > Add bindings for Microsemi SoCs. Currently only Ocelot is supported. > > Cc: Rob Herring > Cc: devicet...@vger.kernel.org > Signed-off-by: Alexandre Belloni > --- > Documentation/devicetree/bindings/mips/mscc.txt | 46 >

Crash in cgroup_procs_show

Hi, Fedora got a bug report on 4.14.4 of a crash on reboot https://bugzilla.redhat.com/show_bug.cgi?id=1525279 BUG: unable to handle kernel NULL pointer dereference at 0254 IP: __task_pid_nr_ns+0xc7/0xf0 PGD 0 P4D 0 Oops: [#1] SMP Modules linked in: fuse vhost_net vhost

Crash in cgroup_procs_show

Hi, Fedora got a bug report on 4.14.4 of a crash on reboot https://bugzilla.redhat.com/show_bug.cgi?id=1525279 BUG: unable to handle kernel NULL pointer dereference at 0254 IP: __task_pid_nr_ns+0xc7/0xf0 PGD 0 P4D 0 Oops: [#1] SMP Modules linked in: fuse vhost_net vhost

[PATCH V4] ACPI / GED: unregister interrupts during shutdown

Some GED interrupts could be pending by the time we are doing a reboot. Even though GED driver uses devm_request_irq() to register the interrupt handler, the handler is not being freed on time during a shutdown since the driver is missing a shutdown callback. If the ACPI handler is no longer

[PATCH V4] ACPI / GED: unregister interrupts during shutdown

Some GED interrupts could be pending by the time we are doing a reboot. Even though GED driver uses devm_request_irq() to register the interrupt handler, the handler is not being freed on time during a shutdown since the driver is missing a shutdown callback. If the ACPI handler is no longer

Re: [PATCH v2] riscv/ftrace: Add basic support

On Tue, 12 Dec 2017 09:47:03 -0800 Jim Wilson wrote: > As Alan mentioned, all gcc does is call mcount with two args, parent > pc and self pc, same as most other linux targets. Most of the > interesting features of prof/gprof profiling happen inside glibc, with > the special

Re: [PATCH v2] riscv/ftrace: Add basic support

On Tue, 12 Dec 2017 09:47:03 -0800 Jim Wilson wrote: > As Alan mentioned, all gcc does is call mcount with two args, parent > pc and self pc, same as most other linux targets. Most of the > interesting features of prof/gprof profiling happen inside glibc, with > the special start files

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Tue, Dec 12, 2017 at 03:59:33PM -0800, Jakub Kicinski wrote: > > +static __always_inline __##type type##_replace_bits(__##type old, \ > > + base val, base mask)\ > > +{ \ > > +

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Tue, Dec 12, 2017 at 03:59:33PM -0800, Jakub Kicinski wrote: > > +static __always_inline __##type type##_replace_bits(__##type old, \ > > + base val, base mask)\ > > +{ \ > > +

Re: [PATCH] mm, hugetlbfs: include mm.h for vm_operations_struct

Hi Dan, On Tue, 12 Dec 2017 00:05:08 -0800 Dan Williams wrote: > > On Mon, Dec 11, 2017 at 11:47 PM, Michal Hocko wrote: > > On Mon 11-12-17 17:21:27, Arnd Bergmann wrote: > >> The infiniband umem code causes a build failure in some

Re: [PATCH] mm, hugetlbfs: include mm.h for vm_operations_struct

Hi Dan, On Tue, 12 Dec 2017 00:05:08 -0800 Dan Williams wrote: > > On Mon, Dec 11, 2017 at 11:47 PM, Michal Hocko wrote: > > On Mon 11-12-17 17:21:27, Arnd Bergmann wrote: > >> The infiniband umem code causes a build failure in some configurations: > >> > >> In file included from

Re: [RFC PATCH 2/5] mm, hugetlb: integrate giga hugetlb more naturally to the allocation path

On 12/04/2017 06:01 AM, Michal Hocko wrote: > From: Michal Hocko > > Gigantic hugetlb pages were ingrown to the hugetlb code as an alien > specie with a lot of special casing. The allocation path is not an > exception. Unnecessarily so to be honest. It is true that the

Re: [RFC PATCH 2/5] mm, hugetlb: integrate giga hugetlb more naturally to the allocation path

On 12/04/2017 06:01 AM, Michal Hocko wrote: > From: Michal Hocko > > Gigantic hugetlb pages were ingrown to the hugetlb code as an alien > specie with a lot of special casing. The allocation path is not an > exception. Unnecessarily so to be honest. It is true that the underlying > allocator is

Re: [PATCH v2] riscv/ftrace: Add basic support

On Tue, 12 Dec 2017 15:08:00 +0800 Alan Kao wrote: > > It's not a big deal, though -- we can fix these later. The more interesting > > thing here is that this code means our `-pg` stuff is now part of the GCC > > ABI, which is something I'd never though of before. I've

Re: [PATCH v2] riscv/ftrace: Add basic support

On Tue, 12 Dec 2017 15:08:00 +0800 Alan Kao wrote: > > It's not a big deal, though -- we can fix these later. The more interesting > > thing here is that this code means our `-pg` stuff is now part of the GCC > > ABI, which is something I'd never though of before. I've added Jim, our GCC > >

mmotm 2017-12-12-16-32 uploaded

The mm-of-the-moment snapshot 2017-12-12-16-32 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

mmotm 2017-12-12-16-32 uploaded

The mm-of-the-moment snapshot 2017-12-12-16-32 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH 3/3][RFC/RFT] PM / sleep: Do not delay the synchronization of MTRR during resume

On Tuesday, October 31, 2017 10:58:50 AM CET Yu Chen wrote: > From: Chen Yu > > Sometimes it is too late for the APs to synchronize the MTRR > after all the APs have been brought up. In some cases the BIOS > might scribble the MTRR across suspend/resume, as a result we >

Re: [PATCH 3/3][RFC/RFT] PM / sleep: Do not delay the synchronization of MTRR during resume

On Tuesday, October 31, 2017 10:58:50 AM CET Yu Chen wrote: > From: Chen Yu > > Sometimes it is too late for the APs to synchronize the MTRR > after all the APs have been brought up. In some cases the BIOS > might scribble the MTRR across suspend/resume, as a result we > might get insane MTRR

Re: [PATCH 4.9 000/148] 4.9.69-stable review

On Tue, Dec 12, 2017 at 04:22:36PM -0800, Guenter Roeck wrote: > On 12/12/2017 04:43 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.69 release. > > There are 148 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.9 000/148] 4.9.69-stable review

On Tue, Dec 12, 2017 at 04:22:36PM -0800, Guenter Roeck wrote: > On 12/12/2017 04:43 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.69 release. > > There are 148 patches in this series, all will be posted as a response > > to this one. If anyone has any

[PATCH 1/2] dt-bindings: net: add TI CC2560 Bluetooth chip

This adds a compatible string for the Texas Instruments CC2560 Bluetooth chip to the existing TI WiLink shared transport bindings. These chips are similar enough that the same bindings work for both. The file is renamed to ti-bluetooth.txt to make it more generic. Signed-off-by: David Lechner

[PATCH 1/2] dt-bindings: net: add TI CC2560 Bluetooth chip

This adds a compatible string for the Texas Instruments CC2560 Bluetooth chip to the existing TI WiLink shared transport bindings. These chips are similar enough that the same bindings work for both. The file is renamed to ti-bluetooth.txt to make it more generic. Signed-off-by: David Lechner

[PATCH 2/2] Bluetooth: hci_ll: add "ti,cc2560" compatible string

This adds the "ti,cc2560" compatible string for a TI CC2560 chip. Signed-off-by: David Lechner --- drivers/bluetooth/hci_ll.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/bluetooth/hci_ll.c b/drivers/bluetooth/hci_ll.c index 9de106f..1b4417a 100644 ---

[PATCH 0/2] Bluetooth: Add device tree compatible for TI CC2560

This series updates the bindings TI WiLink 7/8 Bluetooth to add TI CC256x chips as well. A compatible string is also added to the hci_ll driver for TI CC2560. David Lechner (2): dt-bindings: net: add TI CC2560 Bluetooth chip Bluetooth: hci_ll: add "ti,cc2560" compatible string

[PATCH 2/2] Bluetooth: hci_ll: add "ti,cc2560" compatible string

This adds the "ti,cc2560" compatible string for a TI CC2560 chip. Signed-off-by: David Lechner --- drivers/bluetooth/hci_ll.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/bluetooth/hci_ll.c b/drivers/bluetooth/hci_ll.c index 9de106f..1b4417a 100644 ---

[PATCH 0/2] Bluetooth: Add device tree compatible for TI CC2560

This series updates the bindings TI WiLink 7/8 Bluetooth to add TI CC256x chips as well. A compatible string is also added to the hci_ll driver for TI CC2560. David Lechner (2): dt-bindings: net: add TI CC2560 Bluetooth chip Bluetooth: hci_ll: add "ti,cc2560" compatible string

Re: [RFC PATCH 1/5] mm, hugetlb: unify core page allocation accounting and initialization

On 12/04/2017 06:01 AM, Michal Hocko wrote: > From: Michal Hocko > > hugetlb allocator has two entry points to the page allocator > - alloc_fresh_huge_page_node > - __hugetlb_alloc_buddy_huge_page > > The two differ very subtly in two aspects. The first one doesn't care > about

Re: [RFC PATCH 1/5] mm, hugetlb: unify core page allocation accounting and initialization

On 12/04/2017 06:01 AM, Michal Hocko wrote: > From: Michal Hocko > > hugetlb allocator has two entry points to the page allocator > - alloc_fresh_huge_page_node > - __hugetlb_alloc_buddy_huge_page > > The two differ very subtly in two aspects. The first one doesn't care > about HTLB_BUDDY_*

Re: [PATCH v2 1/2] acpi, spcr: Make SPCR avialable to other architectures

On Monday, December 11, 2017 4:50:58 PM CET Prarit Bhargava wrote: > Other architectures can use SPCR to setup an early console or console > but the current code is ARM64 specific. > > Change the name of parse_spcr() to acpi_parse_spcr(). Add a weak > function acpi_arch_setup_console() that can

Re: [PATCH v2 1/2] acpi, spcr: Make SPCR avialable to other architectures

On Monday, December 11, 2017 4:50:58 PM CET Prarit Bhargava wrote: > Other architectures can use SPCR to setup an early console or console > but the current code is ARM64 specific. > > Change the name of parse_spcr() to acpi_parse_spcr(). Add a weak > function acpi_arch_setup_console() that can

Re: [PATCH 4.9 000/148] 4.9.69-stable review

On 12/12/2017 04:43 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.69 release. There are 148 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.9 000/148] 4.9.69-stable review

On 12/12/2017 04:43 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.69 release. There are 148 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH] ACPI, APEI, Fix use resource_size

On Monday, December 11, 2017 4:44:31 PM CET Vasyl Gomonovych wrote: > Use resource_size function on resource object > Underneath __request_region set res->end to start + n - 1 > Lets use resourse_size to set value properly. > > Signed-off-by: Vasyl Gomonovych Boris, what

Re: [PATCH] ACPI, APEI, Fix use resource_size

On Monday, December 11, 2017 4:44:31 PM CET Vasyl Gomonovych wrote: > Use resource_size function on resource object > Underneath __request_region set res->end to start + n - 1 > Lets use resourse_size to set value properly. > > Signed-off-by: Vasyl Gomonovych Boris, what do you think? > --- >

Re: [PATCH V3 09/29] drm/i915: deprecate pci_get_bus_and_slot()

On 12/12/2017 9:04 AM, Joonas Lahtinen wrote: > Hi, > > I sent this individual i915 patch to our CI, and it is passing on all > platforms: > > https://patchwork.freedesktop.org/series/34822/ > > Is it ok if I merge this to drm-tip already? As long as you have this change in your tree, it

Re: [PATCH V3 09/29] drm/i915: deprecate pci_get_bus_and_slot()

On 12/12/2017 9:04 AM, Joonas Lahtinen wrote: > Hi, > > I sent this individual i915 patch to our CI, and it is passing on all > platforms: > > https://patchwork.freedesktop.org/series/34822/ > > Is it ok if I merge this to drm-tip already? As long as you have this change in your tree, it

binder epoll bug (was KASAN: use-after-free Read in __lock_acquire (2))

[+Cc binder maintainers and list] [-Cc lockdep maintainers, USB maintainers, and other random people] On Sat, Dec 02, 2017 at 08:08:01AM -0800, syzbot wrote: > BUG: KASAN: use-after-free in __lock_acquire+0x465e/0x47f0 > kernel/locking/lockdep.c:3378 > Read of size 8 at addr 8801cd8e13f0 by

binder epoll bug (was KASAN: use-after-free Read in __lock_acquire (2))

[+Cc binder maintainers and list] [-Cc lockdep maintainers, USB maintainers, and other random people] On Sat, Dec 02, 2017 at 08:08:01AM -0800, syzbot wrote: > BUG: KASAN: use-after-free in __lock_acquire+0x465e/0x47f0 > kernel/locking/lockdep.c:3378 > Read of size 8 at addr 8801cd8e13f0 by

Re: KASAN: use-after-free Read in __lock_acquire (2)

On Sat, Dec 02, 2017 at 08:08:01AM -0800, syzbot wrote: > Allocated by task 3086: > save_stack+0x43/0xd0 mm/kasan/kasan.c:447 > set_track mm/kasan/kasan.c:459 [inline] > kasan_kmalloc+0xad/0xe0 mm/kasan/kasan.c:551 > kmem_cache_alloc_trace+0x136/0x750 mm/slab.c:3613 > kmalloc

Re: KASAN: use-after-free Read in __lock_acquire (2)

On Sat, Dec 02, 2017 at 08:08:01AM -0800, syzbot wrote: > Allocated by task 3086: > save_stack+0x43/0xd0 mm/kasan/kasan.c:447 > set_track mm/kasan/kasan.c:459 [inline] > kasan_kmalloc+0xad/0xe0 mm/kasan/kasan.c:551 > kmem_cache_alloc_trace+0x136/0x750 mm/slab.c:3613 > kmalloc

[PATCH 1/5] rpmsg: smd: Perform handshake during open

Validate the the remote side is opening the channel that we've found by performing a handshake when opening the channel. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_smd.c | 30 ++ 1 file changed, 30 insertions(+) diff --git

[PATCH 1/5] rpmsg: smd: Perform handshake during open

Validate the the remote side is opening the channel that we've found by performing a handshake when opening the channel. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_smd.c | 30 ++ 1 file changed, 30 insertions(+) diff --git a/drivers/rpmsg/qcom_smd.c

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Tue, 12 Dec 2017 23:48:56 +, Al Viro wrote: > On Tue, Dec 12, 2017 at 12:04:09PM -0800, Jakub Kicinski wrote: > > > > static __always_inline u64 mask_to_multiplier(u64 mask) > > > { > > > return mask & (mask ^ (mask - 1)); > > > } > > D'oh. Even simpler than that, of course - > >

Re: [RFC][PATCH] new byteorder primitives - ..._{replace,get}_bits()

On Tue, 12 Dec 2017 23:48:56 +, Al Viro wrote: > On Tue, Dec 12, 2017 at 12:04:09PM -0800, Jakub Kicinski wrote: > > > > static __always_inline u64 mask_to_multiplier(u64 mask) > > > { > > > return mask & (mask ^ (mask - 1)); > > > } > > D'oh. Even simpler than that, of course - > >

[PATCH 5/5] rpmsg: smd: Don't hold the tx lock during wait

Holding the tx lock while waiting for tx-drain events from the remote side blocks try_send requests from failing quickly, so temporarily drop the tx lock while waiting. While this allows try_send to fail quickly it also could allow a subsequent send to succeed putting a smaller packet in the FIFO

[PATCH 4/5] rpmsg: smd: Fail send on a closed channel

Move the check for a closed channel out from the tx-full loop to fail any send request on a non-open channel. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_smd.c | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git

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