Re: [RFC PATCH-tip v4 02/10] locking/rwsem: Stop active read lock ASAP

On Wed, Oct 12, 2016 at 08:06:40AM +1100, Dave Chinner wrote: > Um, I seem to have completely missed that change - when did that > happen and why? > > Oh, it was part of the misguided "enable DAX on block devices" > changes - o, that commit just switched it to use ->f_mapping: - return

Re: [RFC PATCH-tip v4 02/10] locking/rwsem: Stop active read lock ASAP

On Wed, Oct 12, 2016 at 08:06:40AM +1100, Dave Chinner wrote: > Um, I seem to have completely missed that change - when did that > happen and why? > > Oh, it was part of the misguided "enable DAX on block devices" > changes - o, that commit just switched it to use ->f_mapping: - return

[PATCH] aio: fix a use after free (and fix freeze protection of aio writes)

From: Jan Kara Currently we dropped freeze protection of aio writes just after IO was submitted. Thus aio write could be in flight while the filesystem was frozen and that could result in unexpected situation like aio completion wanting to convert extent type on frozen filesystem.

[PATCH] aio: fix a use after free (and fix freeze protection of aio writes)

From: Jan Kara Currently we dropped freeze protection of aio writes just after IO was submitted. Thus aio write could be in flight while the filesystem was frozen and that could result in unexpected situation like aio completion wanting to convert extent type on frozen filesystem. Testcase from

[PATCH v2] iio: light: ltr501: claim direct mode during raw writes

Driver was checking for direct mode but not locking it. Use claim/release helper functions to guarantee the device stays in direct mode during all raw write operations. Signed-off-by: Alison Schofield --- Changes in v2: Replaced 'goto release' statements with breaks.

[PATCH v2] iio: light: ltr501: claim direct mode during raw writes

Driver was checking for direct mode but not locking it. Use claim/release helper functions to guarantee the device stays in direct mode during all raw write operations. Signed-off-by: Alison Schofield --- Changes in v2: Replaced 'goto release' statements with breaks. The release helper

[PATCH v2] iio: light: ltr501: claim direct mode during select raw reads

Driver was checking for direct mode but not locking it. Use claim/release helper functions to guarantee the device stays in direct mode during required raw read cases. Signed-off-by: Alison Schofield --- Changes in v2: Reworked IIO_CHAN_INFO_RAW case so claim and release

[PATCH v2] iio: light: ltr501: claim direct mode during select raw reads

Driver was checking for direct mode but not locking it. Use claim/release helper functions to guarantee the device stays in direct mode during required raw read cases. Signed-off-by: Alison Schofield --- Changes in v2: Reworked IIO_CHAN_INFO_RAW case so claim and release are executed at same

cris-linux-objcopy: error: the input file 'arch/cris/boot/rescue/rescue.o' has no sections

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: f9f3f864b5e8c09d7837d8980edba4ad52969819 cris: Fix section mismatches in architecture startup code

cris-linux-objcopy: error: the input file 'arch/cris/boot/rescue/rescue.o' has no sections

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: f9f3f864b5e8c09d7837d8980edba4ad52969819 cris: Fix section mismatches in architecture startup code

drivers/regulator/lp872x.c:773: undefined reference to `devm_gpio_request_one'

Hi Linus, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 2527ecc9195e9c66252af24c4689e8a67cd4ccb9 gpio: Fix OF build problem on UM date: 8 weeks

drivers/regulator/lp872x.c:773: undefined reference to `devm_gpio_request_one'

Hi Linus, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 2527ecc9195e9c66252af24c4689e8a67cd4ccb9 gpio: Fix OF build problem on UM date: 8 weeks

Re: [PATCH 1/5] KVM: x86: avoid atomic operations on APICv vmentry

On Fri, Oct 14, 2016 at 08:21:27PM +0200, Paolo Bonzini wrote: > On some benchmarks (e.g. netperf with ioeventfd disabled), APICv > posted interrupts turn out to be slower than interrupt injection via > KVM_REQ_EVENT. > > This patch optimizes a bit the IRR update, avoiding expensive atomic >

Re: [PATCH 1/5] KVM: x86: avoid atomic operations on APICv vmentry

On Fri, Oct 14, 2016 at 08:21:27PM +0200, Paolo Bonzini wrote: > On some benchmarks (e.g. netperf with ioeventfd disabled), APICv > posted interrupts turn out to be slower than interrupt injection via > KVM_REQ_EVENT. > > This patch optimizes a bit the IRR update, avoiding expensive atomic >

[patch ]mm/zs_malloc: Fix bit spinlock replacement

Do not alter HANDLE_SIZE, memory corruption ensues. The handle is a pointer, allocate space for the struct it points to and align it ZS_ALIGN. Also, when accessing the struct, mask HANDLE_PIN_BIT. Signed-off-by: Mike Galbraith --- mm/zsmalloc.c | 13 -

[patch ]mm/zs_malloc: Fix bit spinlock replacement

Do not alter HANDLE_SIZE, memory corruption ensues. The handle is a pointer, allocate space for the struct it points to and align it ZS_ALIGN. Also, when accessing the struct, mask HANDLE_PIN_BIT. Signed-off-by: Mike Galbraith --- mm/zsmalloc.c | 13 - 1 file changed, 8

[patch] drivers/zram: Don't disable preemption in zcomp_stream_get/put()

In v4.7, the driver switched to percpu compression streams, disabling preemption (get/put_cpu_ptr()). Use get/put_cpu_light() instead. Signed-off-by: Mike Galbraith --- drivers/block/zram/zcomp.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---

cc1: error: '-march=r3900' requires '-mfp32'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds date: 5 days ago config: mips-jmr3927_defconfig (attached as .config)

[patch] drivers/zram: Don't disable preemption in zcomp_stream_get/put()

In v4.7, the driver switched to percpu compression streams, disabling preemption (get/put_cpu_ptr()). Use get/put_cpu_light() instead. Signed-off-by: Mike Galbraith --- drivers/block/zram/zcomp.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) --- a/drivers/block/zram/zcomp.c

cc1: error: '-march=r3900' requires '-mfp32'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 034827c727f7f3946a18355b63995b402c226c82 MIPS: Fix -mabi=64 build of vdso.lds date: 5 days ago config: mips-jmr3927_defconfig (attached as .config)

[patch] drivers,connector: Protect send_msg() with a local lock for RT

[ 6496.323071] BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:931 [ 6496.323072] in_atomic(): 1, irqs_disabled(): 0, pid: 31807, name: sleep [ 6496.323077] Preemption disabled at:[] proc_exit_connector+0xbb/0x140 [ 6496.323077] [ 6496.323080] CPU: 4 PID: 31807

[patch] drivers,connector: Protect send_msg() with a local lock for RT

[ 6496.323071] BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:931 [ 6496.323072] in_atomic(): 1, irqs_disabled(): 0, pid: 31807, name: sleep [ 6496.323077] Preemption disabled at:[] proc_exit_connector+0xbb/0x140 [ 6496.323077] [ 6496.323080] CPU: 4 PID: 31807

[patch] ftrace: Fix latency trace header alignment

Line up helper arrows to the right column. Signed-off-by: Mike Galbraith --- kernel/trace/trace.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -2896,17 +2896,17 @@

[patch] ftrace: Fix latency trace header alignment

Line up helper arrows to the right column. Signed-off-by: Mike Galbraith --- kernel/trace/trace.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) --- a/kernel/trace/trace.c +++ b/kernel/trace/trace.c @@ -2896,17 +2896,17 @@ get_total_entries(struct trace_buffer

vgacon.c:undefined reference to `screen_info'

Hi Chen, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: f69405ce6c0fc9f4a039011007371b31f80b470d openrisc: include: asm: Kbuild: add default "vga.h"

vgacon.c:undefined reference to `screen_info'

Hi Chen, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: f69405ce6c0fc9f4a039011007371b31f80b470d openrisc: include: asm: Kbuild: add default "vga.h"

drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new lightweight SGL iterators date: 5

drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function

Hi Dave, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new lightweight SGL iterators date: 5

arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3900' requires '-mfp32'

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error with binutils 2.24 and earlier

arch/mips/vdso/gettimeofday.c:1:0: error: '-march=r3900' requires '-mfp32'

Hi Guenter, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 398c7500a1f5f74e207bd2edca1b1721b3cc1f1e MIPS: VDSO: Fix build error with binutils 2.24 and earlier

arch/mips/vdso/elf.S:1:0: error: '-march=r3900' requires '-mfp32'

Hi Alex, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO date: 11 months ago

arch/mips/vdso/elf.S:1:0: error: '-march=r3900' requires '-mfp32'

Hi Alex, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: ebb5e78cc63417a35254a791de66e1cc84f963cc MIPS: Initial implementation of a VDSO date: 11 months ago

Re: [PATCH 1/5] KVM: x86: avoid atomic operations on APICv vmentry

On Sat, Oct 15, 2016 at 03:47:45AM -0400, Paolo Bonzini wrote: > > > > On Oct 14, 2016, at 11:56 AM, Paolo Bonzini wrote: > > >>> > > >>> for (i = 0; i <= 7; i++) { > > >>> - pir_val = xchg([i], 0); > > >>> - if (pir_val) > > >>> +

Re: [PATCH 1/5] KVM: x86: avoid atomic operations on APICv vmentry

On Sat, Oct 15, 2016 at 03:47:45AM -0400, Paolo Bonzini wrote: > > > > On Oct 14, 2016, at 11:56 AM, Paolo Bonzini wrote: > > >>> > > >>> for (i = 0; i <= 7; i++) { > > >>> - pir_val = xchg([i], 0); > > >>> - if (pir_val) > > >>> + pir_val =

Re: when to size_t for representing length instead of int ?

Le 2016-10-14 01:37, Al Viro a écrit : On Fri, Oct 14, 2016 at 12:12:43AM +0200, none wrote: Hello, I wanted to known the rules in coding guidelines concerning the use of size_t. It seems the signed int type is used most of the time for representing string sizes, including in some parts

Re: when to size_t for representing length instead of int ?

Le 2016-10-14 01:37, Al Viro a écrit : On Fri, Oct 14, 2016 at 12:12:43AM +0200, none wrote: Hello, I wanted to known the rules in coding guidelines concerning the use of size_t. It seems the signed int type is used most of the time for representing string sizes, including in some parts

[patch] perf_event_open.2: PERF_RECORD_LOST_SAMPLES record type

Linux 4.2 added a new record type: PERF_RECORD_LOST_SAMPLES It is generated when hardware samples (currently only Intel PEBS) are lost. Signed-off-by: Vince Weaver diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2 index 9f33122..a47df2d 100644 ---

[patch] perf_event_open.2: PERF_RECORD_LOST_SAMPLES record type

Linux 4.2 added a new record type: PERF_RECORD_LOST_SAMPLES It is generated when hardware samples (currently only Intel PEBS) are lost. Signed-off-by: Vince Weaver diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2 index 9f33122..a47df2d 100644 --- a/man2/perf_event_open.2 +++

virtio-rng scatterlist null pointer dereference with VMAP_STACK=y

With VMAP_STACK=y and HW_RANDOM_VIRTIO=y, I get the following crash: [1.470437] BUG: unable to handle kernel NULL pointer dereference at (null) [1.473350] IP: [] sg_init_one+0x65/0x90 [1.474658] PGD 0 [1.475169] Oops: [#1] SMP Entering kdb (current=0x880069b0c980, pid

virtio-rng scatterlist null pointer dereference with VMAP_STACK=y

With VMAP_STACK=y and HW_RANDOM_VIRTIO=y, I get the following crash: [1.470437] BUG: unable to handle kernel NULL pointer dereference at (null) [1.473350] IP: [] sg_init_one+0x65/0x90 [1.474658] PGD 0 [1.475169] Oops: [#1] SMP Entering kdb (current=0x880069b0c980, pid

Re: btrfs bio linked list corruption.

On Thu, Oct 13, 2016 at 05:18:46PM -0400, Chris Mason wrote: > > > > .. and of course the first thing that happens is a completely > > different > > > > btrfs trace.. > > > > > > > > > > > > WARNING: CPU: 1 PID: 21706 at fs/btrfs/transaction.c:489 > > start_transaction+0x40a/0x440

Re: btrfs bio linked list corruption.

On Thu, Oct 13, 2016 at 05:18:46PM -0400, Chris Mason wrote: > > > > .. and of course the first thing that happens is a completely > > different > > > > btrfs trace.. > > > > > > > > > > > > WARNING: CPU: 1 PID: 21706 at fs/btrfs/transaction.c:489 > > start_transaction+0x40a/0x440

Re: [GIT PULL] kbuild changes for v4.9-rc1

On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek wrote: > Hi Linus, > > please pull these kbuild changes for v4.9-rc1: > > - EXPORT_SYMBOL for asm source by Al Viro. This does bring a regression, > because genksyms no longer generates checksums for these symbols > (CONFIG_MODVERSIONS).

Re: [GIT PULL] kbuild changes for v4.9-rc1

On Fri, Oct 14, 2016 at 10:12:46PM +0200, Michal Marek wrote: > Hi Linus, > > please pull these kbuild changes for v4.9-rc1: > > - EXPORT_SYMBOL for asm source by Al Viro. This does bring a regression, > because genksyms no longer generates checksums for these symbols > (CONFIG_MODVERSIONS).

linux-next: Tree for Oct 16

Hi all, Changes since 20161014: The net tree gained a conflict against Linus' tree. The akpm-current tree still had its build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 389 614 files changed, 17748 insertions(+), 3167 deletions(-)

linux-next: Tree for Oct 16

Hi all, Changes since 20161014: The net tree gained a conflict against Linus' tree. The akpm-current tree still had its build failures for which I applied 2 patches. Non-merge commits (relative to Linus' tree): 389 614 files changed, 17748 insertions(+), 3167 deletions(-)

Re: [RFC] scripts: Include postprocessing script for memory allocation tracing

> On Oct 11, 2016, at 10:43 AM, Janani Ravichandran > wrote: > > Alright. I’ll add a starting tracepoint, change the script accordingly and > send a v2. Thanks! > I looked at it again and I think that the context information we need can be obtained from the

Re: [RFC] scripts: Include postprocessing script for memory allocation tracing

> On Oct 11, 2016, at 10:43 AM, Janani Ravichandran > wrote: > > Alright. I’ll add a starting tracepoint, change the script accordingly and > send a v2. Thanks! > I looked at it again and I think that the context information we need can be obtained from the tracepoint trace_mm_page_alloc in

Re: [PATCH 0/2] net: Fix compiler warnings

On 10/15/2016 02:48 PM, David Miller wrote: From: Tushar Dave Date: Fri, 14 Oct 2016 17:06:04 -0700 Recently, ATU (iommu) changes are submitted to linux-sparc that enables 64bit DMA on SPARC. However, this change also makes 'incompatible pointer type' compiler

Re: [PATCH 0/2] net: Fix compiler warnings

On 10/15/2016 02:48 PM, David Miller wrote: From: Tushar Dave Date: Fri, 14 Oct 2016 17:06:04 -0700 Recently, ATU (iommu) changes are submitted to linux-sparc that enables 64bit DMA on SPARC. However, this change also makes 'incompatible pointer type' compiler warnings inevitable on sunqe

[PATCH] uapi: adfs_fs: Clean up code

From: Chen Gang Use tab instead of 4 white spaces for indent, and remove redundant empty line. Put constant macro definition before structure definition, so that the structure definition can use the constant macro, e.g. ADFS_DR_SIZE. And still left hardcode number

[PATCH] uapi: adfs_fs: Clean up code

From: Chen Gang Use tab instead of 4 white spaces for indent, and remove redundant empty line. Put constant macro definition before structure definition, so that the structure definition can use the constant macro, e.g. ADFS_DR_SIZE. And still left hardcode number "52" for unused52, since the

Re: [PATCH v3] mm: vmalloc: Replace purge_lock spinlock with atomic refcount

Hi Christoph, On Sat, Oct 15, 2016 at 9:54 AM, Christoph Hellwig wrote: > And now with a proper changelog, and the accidentall dropped call to > flush_tlb_kernel_range reinstated: > > --- > From f720cc324498ab5e7931c7ccb1653bd9b8cddc63 Mon Sep 17 00:00:00 2001 > From:

Re: [PATCH v3] mm: vmalloc: Replace purge_lock spinlock with atomic refcount

Hi Christoph, On Sat, Oct 15, 2016 at 9:54 AM, Christoph Hellwig wrote: > And now with a proper changelog, and the accidentall dropped call to > flush_tlb_kernel_range reinstated: > > --- > From f720cc324498ab5e7931c7ccb1653bd9b8cddc63 Mon Sep 17 00:00:00 2001 > From: Christoph Hellwig > Date:

drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108 bytes is larger than 1024 bytes

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 0766f788eb727e2e330d55d30545db65bcf2623f latent_entropy: Mark functions with __latent_entropy date: 5 days ago config: i386-randconfig-c0-10160635

drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108 bytes is larger than 1024 bytes

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: 0766f788eb727e2e330d55d30545db65bcf2623f latent_entropy: Mark functions with __latent_entropy date: 5 days ago config: i386-randconfig-c0-10160635

Re: [PATCH] ipvlan: constify l3mdev_ops structure

From: Julia Lawall Date: Sat, 15 Oct 2016 17:40:30 +0200 > This l3mdev_ops structure is only stored in the l3mdev_ops field of a > net_device structure. This field is declared const, so the l3mdev_ops > structure can be declared as const also. Additionally drop the >

Re: [PATCH] ipvlan: constify l3mdev_ops structure

From: Julia Lawall Date: Sat, 15 Oct 2016 17:40:30 +0200 > This l3mdev_ops structure is only stored in the l3mdev_ops field of a > net_device structure. This field is declared const, so the l3mdev_ops > structure can be declared as const also. Additionally drop the > __read_mostly annotation.

Re: [PATCH 0/2] net: Fix compiler warnings

From: Tushar Dave Date: Fri, 14 Oct 2016 17:06:04 -0700 > Recently, ATU (iommu) changes are submitted to linux-sparc that > enables 64bit DMA on SPARC. However, this change also makes > 'incompatible pointer type' compiler warnings inevitable on sunqe > and sunbmac

Re: [PATCH 0/2] net: Fix compiler warnings

From: Tushar Dave Date: Fri, 14 Oct 2016 17:06:04 -0700 > Recently, ATU (iommu) changes are submitted to linux-sparc that > enables 64bit DMA on SPARC. However, this change also makes > 'incompatible pointer type' compiler warnings inevitable on sunqe > and sunbmac driver. > > The two patches

Re: [PATCH v2] vmxnet3: avoid assumption about invalid dma_pa in vmxnet3_set_mc()

From: Alexey Khoroshilov Date: Sat, 15 Oct 2016 00:01:20 +0300 > vmxnet3_set_mc() checks new_table_pa returned by dma_map_single() > with dma_mapping_error(), but even there it assumes zero is invalid pa > (it assumes dma_mapping_error(...,0) returns true if new_table is

Re: [PATCH v2] vmxnet3: avoid assumption about invalid dma_pa in vmxnet3_set_mc()

From: Alexey Khoroshilov Date: Sat, 15 Oct 2016 00:01:20 +0300 > vmxnet3_set_mc() checks new_table_pa returned by dma_map_single() > with dma_mapping_error(), but even there it assumes zero is invalid pa > (it assumes dma_mapping_error(...,0) returns true if new_table is NULL). > > The patch

[git pull] tree-wide switch to linux/uaccess.h

Now everything can be switched from asm/uaccess.h to linux/uaccess.h *and* the merges of this window have settled, we can do the actual switchover. The thing is automatically generated (by PATT='^[[:blank:]]*#[[:blank:]]*include[[:blank:]]*' sed -i -e "s!$PATT!#include !" \

[git pull] tree-wide switch to linux/uaccess.h

Now everything can be switched from asm/uaccess.h to linux/uaccess.h *and* the merges of this window have settled, we can do the actual switchover. The thing is automatically generated (by PATT='^[[:blank:]]*#[[:blank:]]*include[[:blank:]]*' sed -i -e "s!$PATT!#include !" \

WARNING: SOMEONE RECEIVING THIS HAS BEEN HACKED (was: Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API)

Guys, Looks like gmail's been hacked (or something). Within 50 minutes of sending the reply below, I've received at least 10 replies with the following headers: In-Reply-To: <20161015203421.gg1...@n2100.armlinux.org.uk> References: <1476561450-28407-1-git-send-email-robert.jarz...@free.fr>

WARNING: SOMEONE RECEIVING THIS HAS BEEN HACKED (was: Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API)

Guys, Looks like gmail's been hacked (or something). Within 50 minutes of sending the reply below, I've received at least 10 replies with the following headers: In-Reply-To: <20161015203421.gg1...@n2100.armlinux.org.uk> References: <1476561450-28407-1-git-send-email-robert.jarz...@free.fr>

ca54678efb: BUG: kernel hang in boot stage

FYI, we noticed the following commit: https://github.com/0day-ci/linux Grzegorz-Andrejczuk/Enabling-Ring-3-MONITOR-MWAIT-feature-for-Knights-Landing/20161012-202414 commit ca54678efb1a9e8b0ff83fb488175103d6616a81 ("Add R3MWAIT to CPU features") in testcase: boot on test machine:

ca54678efb: BUG: kernel hang in boot stage

FYI, we noticed the following commit: https://github.com/0day-ci/linux Grzegorz-Andrejczuk/Enabling-Ring-3-MONITOR-MWAIT-feature-for-Knights-Landing/20161012-202414 commit ca54678efb1a9e8b0ff83fb488175103d6616a81 ("Add R3MWAIT to CPU features") in testcase: boot on test machine:

arch/mips/kernel/mips-cpc.c:47: undefined reference to `mips_cpc_default_phys_base'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: eed0eabd12ef061821cbfa20d903476e07645320 MIPS: generic: Introduce generic DT-based board support date: 9 days ago config: mips-generic_defconfig (attached

arch/mips/kernel/mips-cpc.c:47: undefined reference to `mips_cpc_default_phys_base'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1001354ca34179f3db924eb66672442a173147dc commit: eed0eabd12ef061821cbfa20d903476e07645320 MIPS: generic: Introduce generic DT-based board support date: 9 days ago config: mips-generic_defconfig (attached

Re: [PATCH v2] r8169: set coherent DMA mask as well as streaming DMA mask

From: Ard Biesheuvel Date: Fri, 14 Oct 2016 14:48:51 +0100 > >> On 14 Oct 2016, at 14:42, David Laight wrote: >> >> From: Of Ard Biesheuvel >>> Sent: 14 October 2016 14:41 >>> PCI devices that are 64-bit DMA capable should set the coherent

Re: [PATCH v2] r8169: set coherent DMA mask as well as streaming DMA mask

From: Ard Biesheuvel Date: Fri, 14 Oct 2016 14:48:51 +0100 > >> On 14 Oct 2016, at 14:42, David Laight wrote: >> >> From: Of Ard Biesheuvel >>> Sent: 14 October 2016 14:41 >>> PCI devices that are 64-bit DMA capable should set the coherent >>> DMA mask as well as the streaming DMA mask. On

Re: [PATCH v2] r8169: set coherent DMA mask as well as streaming DMA mask

From: Ard Biesheuvel Date: Fri, 14 Oct 2016 14:40:33 +0100 > PCI devices that are 64-bit DMA capable should set the coherent > DMA mask as well as the streaming DMA mask. On some architectures, > these are managed separately, and so the coherent DMA mask will be > left

Re: [PATCH v2] r8169: set coherent DMA mask as well as streaming DMA mask

From: Ard Biesheuvel Date: Fri, 14 Oct 2016 14:40:33 +0100 > PCI devices that are 64-bit DMA capable should set the coherent > DMA mask as well as the streaming DMA mask. On some architectures, > these are managed separately, and so the coherent DMA mask will be > left at its default value of 32

Re:Private Donation To You(Reply)

Dear Beneficiary, I am Julie Leach, 50 years old lucky woman from Three Rivers, Michigan who won $310.5 Million Dollars Powerball Jackpot on September 30, 2015. I wish to inform you that your email was randomly selected via Google & Facebook sponsored email-draws as one of our beneficiaries to

Re:Private Donation To You(Reply)

Dear Beneficiary, I am Julie Leach, 50 years old lucky woman from Three Rivers, Michigan who won $310.5 Million Dollars Powerball Jackpot on September 30, 2015. I wish to inform you that your email was randomly selected via Google & Facebook sponsored email-draws as one of our beneficiaries to

Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API

Russell King - ARM Linux writes: > On Sat, Oct 15, 2016 at 09:57:26PM +0200, Robert Jarzmik wrote: >> Hi, >> >> This serie is a preparation to shift the cpufreq of pxa2xx platforms to >> clocks >> API. >> >> The first 3 patches are review and merge material : >> -

Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API

Russell King - ARM Linux writes: > On Sat, Oct 15, 2016 at 09:57:26PM +0200, Robert Jarzmik wrote: >> Hi, >> >> This serie is a preparation to shift the cpufreq of pxa2xx platforms to >> clocks >> API. >> >> The first 3 patches are review and merge material : >> - patch 1/4 for Viresh and

linux-next: manual merge of the net tree with Linus' tree

Hi all, Today's linux-next merge of the net tree got a conflict in: drivers/net/ethernet/qlogic/Kconfig between commit: 2e0cbc4dd077 ("qedr: Add RoCE driver framework") from Linus' tree and commit: 0189efb8f4f8 ("qed*: Fix Kconfig dependencies with INFINIBAND_QEDR") from the net tree.

linux-next: manual merge of the net tree with Linus' tree

Hi all, Today's linux-next merge of the net tree got a conflict in: drivers/net/ethernet/qlogic/Kconfig between commit: 2e0cbc4dd077 ("qedr: Add RoCE driver framework") from Linus' tree and commit: 0189efb8f4f8 ("qed*: Fix Kconfig dependencies with INFINIBAND_QEDR") from the net tree.

Re: [PATCH v2 1/3] net: smc91x: isolate u16 writes alignment workaround

Sorry David, I just noticed you weren't in the "To:" of this serie, but I won't forget you for the v3 I need to release anyway (https://lkml.org/lkml/2016/10/15/104). Robert Jarzmik writes: > + lp->half_word_align4 = > + machine_is_mainstone() ||

Re: [PATCH v2 1/3] net: smc91x: isolate u16 writes alignment workaround

Sorry David, I just noticed you weren't in the "To:" of this serie, but I won't forget you for the v3 I need to release anyway (https://lkml.org/lkml/2016/10/15/104). Robert Jarzmik writes: > + lp->half_word_align4 = > + machine_is_mainstone() || machine_is_stargate2() || > +

[PATCH] sunrpc & nfs: Add and use dprintk_cont macros

Allow line continuations to work properly with KERN_CONT. Signed-off-by: Joe Perches --- fs/nfs/write.c | 6 ++--- include/linux/sunrpc/debug.h | 57 ++-- 2 files changed, 42 insertions(+), 21 deletions(-) diff --git

[PATCH] sunrpc & nfs: Add and use dprintk_cont macros

Allow line continuations to work properly with KERN_CONT. Signed-off-by: Joe Perches --- fs/nfs/write.c | 6 ++--- include/linux/sunrpc/debug.h | 57 ++-- 2 files changed, 42 insertions(+), 21 deletions(-) diff --git a/fs/nfs/write.c

Re: [PATCH] perf: Fix typo "No enough" to "Not enough"

On Fri, Oct 14, 2016 at 12:46:04PM -0300, Arnaldo Carvalho de Melo wrote: > > Thanks, applied, but please next time add to the CC list people that > last touched this code, like Wang, that I'm CC'ing here and in the patch > I just applied. > Sorry, will do that next time. -- Mit freundlichen

[PATCH 3/3] ARM-OMAP2+: pm-debug: Use seq_putc() in two functions

From: Markus Elfring Date: Sat, 15 Oct 2016 22:30:44 +0200 A single character (line break) should be put into a sequence at the end. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus

[PATCH 3/3] ARM-OMAP2+: pm-debug: Use seq_putc() in two functions

From: Markus Elfring Date: Sat, 15 Oct 2016 22:30:44 +0200 A single character (line break) should be put into a sequence at the end. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

Re: [PATCH] perf: Fix typo "No enough" to "Not enough"

On Fri, Oct 14, 2016 at 12:46:04PM -0300, Arnaldo Carvalho de Melo wrote: > > Thanks, applied, but please next time add to the CC list people that > last touched this code, like Wang, that I'm CC'ing here and in the patch > I just applied. > Sorry, will do that next time. -- Mit freundlichen

Re: [PATCH v2 02/31] cinergyT2-core: don't do DMA on stack

On Tue, Oct 11, 2016 at 07:09:17AM -0300, Mauro Carvalho Chehab wrote: > --- a/drivers/media/usb/dvb-usb/cinergyT2-core.c > +++ b/drivers/media/usb/dvb-usb/cinergyT2-core.c > @@ -41,6 +41,8 @@ DVB_DEFINE_MOD_OPT_ADAPTER_NR(adapter_nr); > > struct cinergyt2_state { > u8 rc_counter; > +

Re: [PATCH v2 02/31] cinergyT2-core: don't do DMA on stack

On Tue, Oct 11, 2016 at 07:09:17AM -0300, Mauro Carvalho Chehab wrote: > --- a/drivers/media/usb/dvb-usb/cinergyT2-core.c > +++ b/drivers/media/usb/dvb-usb/cinergyT2-core.c > @@ -41,6 +41,8 @@ DVB_DEFINE_MOD_OPT_ADAPTER_NR(adapter_nr); > > struct cinergyt2_state { > u8 rc_counter; > +

[PATCH 2/3] ARM-OMAP2+: mux: Use seq_putc() in omap_mux_dbg_signal_show()

From: Markus Elfring Date: Sat, 15 Oct 2016 22:24:29 +0200 A single character (line break) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring

[PATCH 2/3] ARM-OMAP2+: mux: Use seq_putc() in omap_mux_dbg_signal_show()

From: Markus Elfring Date: Sat, 15 Oct 2016 22:24:29 +0200 A single character (line break) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- arch/arm/mach-omap2/mux.c | 2

[PATCH 1/3] ARM-OMAP2+: mux: Replace three seq_printf() calls by seq_puts()

From: Markus Elfring Date: Sat, 15 Oct 2016 22:22:09 +0200 Strings which did not contain data format specification should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software.

[PATCH 1/3] ARM-OMAP2+: mux: Replace three seq_printf() calls by seq_puts()

From: Markus Elfring Date: Sat, 15 Oct 2016 22:22:09 +0200 Strings which did not contain data format specification should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 0/3] ARM-OMAP2+: Fine-tuning for five function implementations

From: Markus Elfring Date: Sat, 15 Oct 2016 22:44:22 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (3): mux: Replace three seq_printf() calls by seq_puts() mux: Use seq_putc() in

[PATCH 0/3] ARM-OMAP2+: Fine-tuning for five function implementations

From: Markus Elfring Date: Sat, 15 Oct 2016 22:44:22 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (3): mux: Replace three seq_printf() calls by seq_puts() mux: Use seq_putc() in omap_mux_dbg_signal_show() pm-debug: Use seq_putc()

Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API

On Sat, Oct 15, 2016 at 09:57:26PM +0200, Robert Jarzmik wrote: > Hi, > > This serie is a preparation to shift the cpufreq of pxa2xx platforms to clocks > API. > > The first 3 patches are review and merge material : > - patch 1/4 for Viresh and Rafael > - patches 2/4 and 3/4 for me > > The

Re: [PATCH v2 0/4] PXA cpufreq conversion to clock API

On Sat, Oct 15, 2016 at 09:57:26PM +0200, Robert Jarzmik wrote: > Hi, > > This serie is a preparation to shift the cpufreq of pxa2xx platforms to clocks > API. > > The first 3 patches are review and merge material : > - patch 1/4 for Viresh and Rafael > - patches 2/4 and 3/4 for me > > The

[PATCH v2 4/4] cpufreq: pxa: convert to clock API

As the clock settings have been introduced into the clock pxa drivers, which are now available to change the CPU clock by themselves, remove the clock handling from this driver, and rely on pxa clock drivers. Signed-off-by: Robert Jarzmik --- Since v1: added !OF Kconfig

[PATCH v2 4/4] cpufreq: pxa: convert to clock API

As the clock settings have been introduced into the clock pxa drivers, which are now available to change the CPU clock by themselves, remove the clock handling from this driver, and rely on pxa clock drivers. Signed-off-by: Robert Jarzmik --- Since v1: added !OF Kconfig dependency ---

  1   2   3   4   >