Re: [PATCH 1/2] dt-bindings: qoriq-clock: Add coreclk

On Wed, Feb 15, 2017 at 01:47:35PM +0800, yuantian.t...@nxp.com wrote: > From: Tang Yuantian > > ls1012a has separate input root clocks for core PLLs versus the platform > PLL, with the latter described as sysclk in the hw docs. > Update the qoriq-clock binding to allow a second input clock,

RE: [PATCH] Drivers: hv: util: on deinit, don't wait the release event, if we shouldn't

The patch looks good. I don't understand the exact semantics here and therefore have a couple of naïve questions Is it possible device could be opened multiple times? Is reference counting done above? If device was never opened do you even have to do all the cleanup steps at all?

__queue_work oops.

Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.10.0-think+ #9 task: 88017f105440 task.stack: c9094000 RIP: 0010:__queue_work+0x2d/0x700 RSP: 0018:880507c03df8 EFLAGS: 00010046 RAX: 0082 RBX: 0101 RCX:

__queue_work oops.

Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.10.0-think+ #9 task: 88017f105440 task.stack: c9094000 RIP: 0010:__queue_work+0x2d/0x700 RSP: 0018:880507c03df8 EFLAGS: 00010046 RAX: 0082 RBX: 0101 RCX:

Re: mm: GPF in bdi_put

f880064a7f0b0 > RIP: bdi_put+0x8b/0x1d0 mm/backing-dev.c:914 RSP: 880064a7f0b0 > ---[ end trace 8991b3d16ac9bf93 ]--- > > On commit e5d56efc97f8240d0b5d66c03949382b6d7e5570. I also wee the following WARNING. Do you think it' the same underlying bug? [ cut here ]---

Re: [PATCH v2 14/22] dt-bindings: PCI: dra7xx: Add dt bindings to enable legacy mode

On Fri, Feb 17, 2017 at 03:20:34PM +0530, Kishon Vijay Abraham I wrote: > Update device tree binding documentation of TI's dra7xx PCI > controller to include property for enabling legacy mode. > > Signed-off-by: Kishon Vijay Abraham I > --- >

Re: mm: GPF in bdi_put

t; RIP: bdi_put+0x8b/0x1d0 mm/backing-dev.c:914 RSP: 880064a7f0b0 > ---[ end trace 8991b3d16ac9bf93 ]--- > > On commit e5d56efc97f8240d0b5d66c03949382b6d7e5570. I also wee the following WARNING. Do you think it' the same underlying bug? [ cut here ]---- WARNING: CPU: 1 PI

Re: [PATCH v2 14/22] dt-bindings: PCI: dra7xx: Add dt bindings to enable legacy mode

On Fri, Feb 17, 2017 at 03:20:34PM +0530, Kishon Vijay Abraham I wrote: > Update device tree binding documentation of TI's dra7xx PCI > controller to include property for enabling legacy mode. > > Signed-off-by: Kishon Vijay Abraham I > --- > Documentation/devicetree/bindings/pci/ti-pci.txt |

Re: [PATCH] sd: close hole in > 2T device rejection when !CONFIG_LBDAF

Hi Bart - Thanks for taking the time to look this over. On 02/27/2017 10:13 AM, Bart Van Assche wrote: On Mon, 2017-02-27 at 09:22 -0600, Steven J. Magnani wrote: @@ -2122,7 +2122,10 @@ static int read_capacity_16(struct scsi_ return -ENODEV; } - if

Re: [PATCH] sd: close hole in > 2T device rejection when !CONFIG_LBDAF

Hi Bart - Thanks for taking the time to look this over. On 02/27/2017 10:13 AM, Bart Van Assche wrote: On Mon, 2017-02-27 at 09:22 -0600, Steven J. Magnani wrote: @@ -2122,7 +2122,10 @@ static int read_capacity_16(struct scsi_ return -ENODEV; } - if

Re: [REGRESSION] pinctrl, of, unable to find hogs

On Mon, Feb 27, 2017 at 05:27:47PM +0100, Gary Bisson wrote: > Mika, Tony, All, > > On Mon, Feb 27, 2017 at 07:53:53AM -0800, Tony Lindgren wrote: > > * Mika Penttilä [170226 21:46]: > > > > > > With current linus git (pre 4.11), unable to find the pinctrl hogs : > >

Re: [REGRESSION] pinctrl, of, unable to find hogs

On Mon, Feb 27, 2017 at 05:27:47PM +0100, Gary Bisson wrote: > Mika, Tony, All, > > On Mon, Feb 27, 2017 at 07:53:53AM -0800, Tony Lindgren wrote: > > * Mika Penttilä [170226 21:46]: > > > > > > With current linus git (pre 4.11), unable to find the pinctrl hogs : > > > > > > > > >

Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages

On Mon, Feb 27, 2017 at 03:33:15PM +0900, Minchan Kim wrote: > Hi Shaohua, > > On Fri, Feb 24, 2017 at 01:31:47PM -0800, Shaohua Li wrote: > > When memory pressure is high, we free MADV_FREE pages. If the pages are > > not dirty in pte, the pages could be freed immediately. Otherwise we > > can't

Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages

On Mon, Feb 27, 2017 at 03:33:15PM +0900, Minchan Kim wrote: > Hi Shaohua, > > On Fri, Feb 24, 2017 at 01:31:47PM -0800, Shaohua Li wrote: > > When memory pressure is high, we free MADV_FREE pages. If the pages are > > not dirty in pte, the pages could be freed immediately. Otherwise we > > can't

Re: [PATCH v5] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

在 2017/2/23 22:13, Waiman Long 写道: All the locking related cmpxchg's in the following functions are replaced with the _acquire variants: - pv_queued_spin_steal_lock() - trylock_clear_pending() This change should help performance on architectures that use LL/SC. On a 2-core 16-thread Power8

Re: [PATCH v5] locking/pvqspinlock: Relax cmpxchg's to improve performance on some archs

在 2017/2/23 22:13, Waiman Long 写道: All the locking related cmpxchg's in the following functions are replaced with the _acquire variants: - pv_queued_spin_steal_lock() - trylock_clear_pending() This change should help performance on architectures that use LL/SC. On a 2-core 16-thread Power8

Re: [PATCH v2 3/3] percpu: improve allocation success rate for non-GFP_KERNEL callers

On Mon 27-02-17 09:01:09, Tahsin Erdogan wrote: > On Mon, Feb 27, 2017 at 7:25 AM, Michal Hocko wrote: > > /* > > * No space left. Create a new chunk. We don't want multiple > > * tasks to create chunks simultaneously. Serialize and create iff > >

Re: [PATCH v2 3/3] percpu: improve allocation success rate for non-GFP_KERNEL callers

On Mon 27-02-17 09:01:09, Tahsin Erdogan wrote: > On Mon, Feb 27, 2017 at 7:25 AM, Michal Hocko wrote: > > /* > > * No space left. Create a new chunk. We don't want multiple > > * tasks to create chunks simultaneously. Serialize and create iff > > * there's

Re: [WARNING: A/V UNSCANNABLE][Merge tag 'media/v4.11-1' of git] ff58d005cd: BUG: unable to handle kernel NULL pointer dereference at 0000039c

On Mon, 27 Feb 2017, Tony Lindgren wrote: > * Ingo Molnar [170227 07:44]: > > Because it's not the requirement that hurts primarily, but the resulting > > non-determinism and the sporadic crashes. Which can be solved by making the > > race > > deterministic via the debug

Re: [WARNING: A/V UNSCANNABLE][Merge tag 'media/v4.11-1' of git] ff58d005cd: BUG: unable to handle kernel NULL pointer dereference at 0000039c

On Mon, 27 Feb 2017, Tony Lindgren wrote: > * Ingo Molnar [170227 07:44]: > > Because it's not the requirement that hurts primarily, but the resulting > > non-determinism and the sporadic crashes. Which can be solved by making the > > race > > deterministic via the debug facility. > > > > If

Re: [WARNING: A/V UNSCANNABLE][Merge tag 'media/v4.11-1' of git] ff58d005cd: BUG: unable to handle kernel NULL pointer dereference at 0000039c

On Mon, 27 Feb 2017, Ingo Molnar wrote: > * Thomas Gleixner wrote: > > > The pending interrupt issue happens, at least on my test boxen, mostly on > > the 'legacy' interrupts (0 - 15). But even the IOAPIC interrupts >=16 > > happen occasionally. > > > > > > - Spurious

Re: [WARNING: A/V UNSCANNABLE][Merge tag 'media/v4.11-1' of git] ff58d005cd: BUG: unable to handle kernel NULL pointer dereference at 0000039c

On Mon, 27 Feb 2017, Ingo Molnar wrote: > * Thomas Gleixner wrote: > > > The pending interrupt issue happens, at least on my test boxen, mostly on > > the 'legacy' interrupts (0 - 15). But even the IOAPIC interrupts >=16 > > happen occasionally. > > > > > > - Spurious interrupts on IRQ7, which

Re: [PATCH 1/2] dts: mfd: axp20x: Add xpowers,master-mode property for AXP806 PMICs

On Sat, Feb 18, 2017 at 08:51:18PM +0100, Rask Ingemann Lambertsen wrote: > commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot") > was intended to fix the case where a board uses an AXP806 in slave mode, > but the boot loader leaves it in master mode for lack of AXP806

Re: [PATCH 1/2] dts: mfd: axp20x: Add xpowers,master-mode property for AXP806 PMICs

On Sat, Feb 18, 2017 at 08:51:18PM +0100, Rask Ingemann Lambertsen wrote: > commit b101829a029a ("mfd: axp20x: Fix AXP806 access errors on cold boot") > was intended to fix the case where a board uses an AXP806 in slave mode, > but the boot loader leaves it in master mode for lack of AXP806

[PATCH v2 3.5/5] trace/kprobes: Add back warning about offset in return probes

Let's not remove the warning about offsets and return probes when the offset is invalid. Signed-off-by: Steven Rostedt (VMware) --- diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c index 3f4f788..f626235 100644 --- a/kernel/trace/trace_kprobe.c +++

[PATCH v2 3.5/5] trace/kprobes: Add back warning about offset in return probes

Let's not remove the warning about offsets and return probes when the offset is invalid. Signed-off-by: Steven Rostedt (VMware) --- diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c index 3f4f788..f626235 100644 --- a/kernel/trace/trace_kprobe.c +++

Re: [PATCH v2 3/3] percpu: improve allocation success rate for non-GFP_KERNEL callers

On Mon, Feb 27, 2017 at 7:25 AM, Michal Hocko wrote: > /* > * No space left. Create a new chunk. We don't want multiple > * tasks to create chunks simultaneously. Serialize and create iff > * there's still no empty chunk after grabbing the

Re: [PATCH v2 3/3] percpu: improve allocation success rate for non-GFP_KERNEL callers

On Mon, Feb 27, 2017 at 7:25 AM, Michal Hocko wrote: > /* > * No space left. Create a new chunk. We don't want multiple > * tasks to create chunks simultaneously. Serialize and create iff > * there's still no empty chunk after grabbing the mutex. >

Re: [PATCH] mm, add_memory_resource: hold device_hotplug lock over mem_hotplug_{begin, done}

[CC Rafael] I've got lost in the acpi indirection (again). I can see acpi_device_hotplug calling lock_device_hotplug() but i cannot find a path down to add_memory() which might call add_memory_resource. But the patch below sounds suspicious to me. Is it possible that this could lead to a

Re: [PATCH] mm, add_memory_resource: hold device_hotplug lock over mem_hotplug_{begin, done}

[CC Rafael] I've got lost in the acpi indirection (again). I can see acpi_device_hotplug calling lock_device_hotplug() but i cannot find a path down to add_memory() which might call add_memory_resource. But the patch below sounds suspicious to me. Is it possible that this could lead to a

Re: [PATCH v2 1/2] of: add devm_ functions for populate and depopulate

On Mon, Feb 27, 2017 at 07:30:24AM -0600, Rob Herring wrote: > On Sun, Feb 26, 2017 at 2:11 PM, Daniel Vetter wrote: > > On Fri, Feb 24, 2017 at 10:31:25AM -0600, Rob Herring wrote: > >> On Fri, Feb 24, 2017 at 10:14 AM, Benjamin Gaignard > >>

Re: [PATCH v2 1/2] of: add devm_ functions for populate and depopulate

On Mon, Feb 27, 2017 at 07:30:24AM -0600, Rob Herring wrote: > On Sun, Feb 26, 2017 at 2:11 PM, Daniel Vetter wrote: > > On Fri, Feb 24, 2017 at 10:31:25AM -0600, Rob Herring wrote: > >> On Fri, Feb 24, 2017 at 10:14 AM, Benjamin Gaignard > >> wrote: > >> > Lots of calls to

Re: [REGRESSION] pinctrl, of, unable to find hogs

* Mika Penttilä [170226 21:46]: > > With current linus git (pre 4.11), unable to find the pinctrl hogs : > > > imx6q-pinctrl 20e.iomuxc: unable to find group for node hoggrp > > > Device is i.MX6 based. Sorry to hear about that, maybe imx_pinctrl_probe_dt()

Re: [REGRESSION] pinctrl, of, unable to find hogs

* Mika Penttilä [170226 21:46]: > > With current linus git (pre 4.11), unable to find the pinctrl hogs : > > > imx6q-pinctrl 20e.iomuxc: unable to find group for node hoggrp > > > Device is i.MX6 based. Sorry to hear about that, maybe imx_pinctrl_probe_dt() should be called before

Re: [PATCH 0/6] ARM: dts: socfpga: Fix dtc warnings

On 02/24/2017 11:54 PM, Florian Vaussard wrote: > We get a bunch of warnings when compiling the SoCFPGA device trees with W=1. > This warnings happens because some nodes have a unit name but no 'reg' > property, > or are missing a unit name while having a 'reg' property. This series enables >

Re: [PATCH 0/6] ARM: dts: socfpga: Fix dtc warnings

On 02/24/2017 11:54 PM, Florian Vaussard wrote: > We get a bunch of warnings when compiling the SoCFPGA device trees with W=1. > This warnings happens because some nodes have a unit name but no 'reg' > property, > or are missing a unit name while having a 'reg' property. This series enables >

Re: [PATCH] input: arizona-haptics - Add device property for HAP_ACT

On Thu, Feb 16, 2017 at 05:35:58PM +, Richard Fitzgerald wrote: > This adds a device property for setting the configuration for the > HAP_ACT register field so that the connected actuator type can be > configured on systems that are not using pdata. > > Signed-off-by: Richard Fitzgerald

Re: [PATCH] input: arizona-haptics - Add device property for HAP_ACT

On Thu, Feb 16, 2017 at 05:35:58PM +, Richard Fitzgerald wrote: > This adds a device property for setting the configuration for the > HAP_ACT register field so that the connected actuator type can be > configured on systems that are not using pdata. > > Signed-off-by: Richard Fitzgerald >

Re: [PATCH V5 2/6] mm: don't assume anonymous pages have SwapBacked flag

On Mon 27-02-17 08:10:24, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:35:34PM +0100, Michal Hocko wrote: > > On Fri 24-02-17 13:31:45, Shaohua Li wrote: > > > There are a few places the code assumes anonymous pages should have > > > SwapBacked flag set. MADV_FREE pages are anonymous pages but

Re: [PATCH V5 2/6] mm: don't assume anonymous pages have SwapBacked flag

On Mon 27-02-17 08:10:24, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:35:34PM +0100, Michal Hocko wrote: > > On Fri 24-02-17 13:31:45, Shaohua Li wrote: > > > There are a few places the code assumes anonymous pages should have > > > SwapBacked flag set. MADV_FREE pages are anonymous pages but

Re: [ANNOUNCE] Git v2.12.0

On Fri, Feb 24, 2017 at 8:28 PM, Junio C Hamano wrote: > The latest feature release Git v2.12.0 is now available at the > usual places. It is comprised of 517 non-merge commits since > v2.11.0, contributed by 80 people, 24 of which are new faces. Yay, some explanations /

Re: [ANNOUNCE] Git v2.12.0

On Fri, Feb 24, 2017 at 8:28 PM, Junio C Hamano wrote: > The latest feature release Git v2.12.0 is now available at the > usual places. It is comprised of 517 non-merge commits since > v2.11.0, contributed by 80 people, 24 of which are new faces. Yay, some explanations / notes / elaborations:

Re: tip.today - scheduler bam boom crash (cpu hotplug)

On Mon, Feb 27, 2017 at 04:27:32PM +0100, Paolo Bonzini wrote: > > > On 27/02/2017 14:04, Peter Zijlstra wrote: > This results in sched clock always unstable for kvm guest since there > is no invariant tsc cpuid bit exposed for kvm guest currently. > >>> What the heck is

Re: tip.today - scheduler bam boom crash (cpu hotplug)

On Mon, Feb 27, 2017 at 04:27:32PM +0100, Paolo Bonzini wrote: > > > On 27/02/2017 14:04, Peter Zijlstra wrote: > This results in sched clock always unstable for kvm guest since there > is no invariant tsc cpuid bit exposed for kvm guest currently. > >>> What the heck is

Re: [PATCH] [linux-next] xenbus: Remove duplicate inclusion of linux/init.h

On 02/27/2017 02:56 AM, Juergen Gross wrote: > On 26/02/17 08:15, Masanari Iida wrote: >> This patch remove duplicate inclusion of linux/init.h in >> xenbus_dev_frontend.c. >> Confirm successfully compile after remove the line. >> >> Signed-off-by: Masanari Iida >

Re: [PATCH] [linux-next] xenbus: Remove duplicate inclusion of linux/init.h

On 02/27/2017 02:56 AM, Juergen Gross wrote: > On 26/02/17 08:15, Masanari Iida wrote: >> This patch remove duplicate inclusion of linux/init.h in >> xenbus_dev_frontend.c. >> Confirm successfully compile after remove the line. >> >> Signed-off-by: Masanari Iida > Reviewed-by: Juergen Gross

Re: stack frame unwindind KASAN errors

On Mon, Feb 27, 2017 at 12:49:59PM +0800, Daniel J Blueman wrote: > On 4.9.13 with KASAN enabled [1], we see a number of stack unwinding > errors reported [2,3]. > > This seems to occur at half of boots. > > Let me know for further debug info/patch testing and thanks, > Daniel > > [1]

Re: stack frame unwindind KASAN errors

On Mon, Feb 27, 2017 at 12:49:59PM +0800, Daniel J Blueman wrote: > On 4.9.13 with KASAN enabled [1], we see a number of stack unwinding > errors reported [2,3]. > > This seems to occur at half of boots. > > Let me know for further debug info/patch testing and thanks, > Daniel > > [1]

Re: [PATCH v2 3/5] trace/kprobes: allow return probes with offsets and absolute addresses

On Wed, 22 Feb 2017 19:23:39 +0530 "Naveen N. Rao" wrote: > Since the kernel includes many non-global functions with same names, we > will need to use offsets from other symbols (typically _text/_stext) or > absolute addresses to place return probes on specific

Re: [PATCH v2 3/5] trace/kprobes: allow return probes with offsets and absolute addresses

On Wed, 22 Feb 2017 19:23:39 +0530 "Naveen N. Rao" wrote: > Since the kernel includes many non-global functions with same names, we > will need to use offsets from other symbols (typically _text/_stext) or > absolute addresses to place return probes on specific functions. Also, > the core

Re: [REGRESSION] pinctrl, of, unable to find hogs

Mika, Tony, All, On Mon, Feb 27, 2017 at 07:53:53AM -0800, Tony Lindgren wrote: > * Mika Penttilä [170226 21:46]: > > > > With current linus git (pre 4.11), unable to find the pinctrl hogs : > > > > > > imx6q-pinctrl 20e.iomuxc: unable to find group for node

Re: tip.today - scheduler bam boom crash (cpu hotplug)

On Mon, Feb 27, 2017 at 05:11:34PM +0100, Paolo Bonzini wrote: > On 27/02/2017 16:59, Peter Zijlstra wrote: > > Now, I've not yet figured out the ordering between when we set > > pv_time_ops.sched_clock and when we do the 'normal' TSC init stuff. > > I think the ordering is fine: > > -

Re: [REGRESSION] pinctrl, of, unable to find hogs

Mika, Tony, All, On Mon, Feb 27, 2017 at 07:53:53AM -0800, Tony Lindgren wrote: > * Mika Penttilä [170226 21:46]: > > > > With current linus git (pre 4.11), unable to find the pinctrl hogs : > > > > > > imx6q-pinctrl 20e.iomuxc: unable to find group for node hoggrp > > > > > > Device

Re: tip.today - scheduler bam boom crash (cpu hotplug)

On Mon, Feb 27, 2017 at 05:11:34PM +0100, Paolo Bonzini wrote: > On 27/02/2017 16:59, Peter Zijlstra wrote: > > Now, I've not yet figured out the ordering between when we set > > pv_time_ops.sched_clock and when we do the 'normal' TSC init stuff. > > I think the ordering is fine: > > -

Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages

On Mon 27-02-17 08:19:08, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:33:15PM +0900, Minchan Kim wrote: [...] > > > --- a/include/linux/rmap.h > > > +++ b/include/linux/rmap.h > > > @@ -298,6 +298,6 @@ static inline int page_mkclean(struct page *page) > > > #define SWAP_AGAIN 1 > > >

Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages

On Mon 27-02-17 08:19:08, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:33:15PM +0900, Minchan Kim wrote: [...] > > > --- a/include/linux/rmap.h > > > +++ b/include/linux/rmap.h > > > @@ -298,6 +298,6 @@ static inline int page_mkclean(struct page *page) > > > #define SWAP_AGAIN 1 > > >

Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list

On Mon 27-02-17 08:13:10, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:28:01PM +0900, Minchan Kim wrote: [...] > > This patch doesn't address I pointed out in v4. > > > > https://marc.info/?i=20170224233752.GB4635%40bbox > > > > Let's discuss it if you still are against. > > I really think a

Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list

On Mon 27-02-17 08:13:10, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:28:01PM +0900, Minchan Kim wrote: [...] > > This patch doesn't address I pointed out in v4. > > > > https://marc.info/?i=20170224233752.GB4635%40bbox > > > > Let's discuss it if you still are against. > > I really think a

Re: [PATCH 3/4] fpga dt: bindings for Altera Partial Reconfiguraion IP.

On Mon, 27 Feb 2017, Rob Herring wrote: Hi Rob, On Wed, Feb 15, 2017 at 01:10:37PM -0800, matthew.gerl...@linux.intel.com wrote: From: Matthew Gerlach Device Tree bindings for Altera Partial Reconfiguraion IP? Signed-off-by: Matthew Gerlach

Re: [PATCH 3/4] fpga dt: bindings for Altera Partial Reconfiguraion IP.

On Mon, 27 Feb 2017, Rob Herring wrote: Hi Rob, On Wed, Feb 15, 2017 at 01:10:37PM -0800, matthew.gerl...@linux.intel.com wrote: From: Matthew Gerlach Device Tree bindings for Altera Partial Reconfiguraion IP? Signed-off-by: Matthew Gerlach ---

Re: [WARNING: A/V UNSCANNABLE][Merge tag 'media/v4.11-1' of git] ff58d005cd: BUG: unable to handle kernel NULL pointer dereference at 0000039c

* Thomas Gleixner [170227 08:20]: > On Mon, 27 Feb 2017, Tony Lindgren wrote: > > * Ingo Molnar [170227 07:44]: > > > Because it's not the requirement that hurts primarily, but the resulting > > > non-determinism and the sporadic crashes. Which can be

Re: [WARNING: A/V UNSCANNABLE][Merge tag 'media/v4.11-1' of git] ff58d005cd: BUG: unable to handle kernel NULL pointer dereference at 0000039c

* Thomas Gleixner [170227 08:20]: > On Mon, 27 Feb 2017, Tony Lindgren wrote: > > * Ingo Molnar [170227 07:44]: > > > Because it's not the requirement that hurts primarily, but the resulting > > > non-determinism and the sporadic crashes. Which can be solved by making > > > the race > > >

Re: net/sctp: use-after-free in sctp_hash_transport

On Mon, Feb 27, 2017 at 11:45 PM, Andrey Konovalov wrote: > Hi, > > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit e5d56efc97f8240d0b5d66c03949382b6d7e5570 (Feb 26). > > A reproducer and .config are attached. > >

Re: net/sctp: use-after-free in sctp_hash_transport

On Mon, Feb 27, 2017 at 11:45 PM, Andrey Konovalov wrote: > Hi, > > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit e5d56efc97f8240d0b5d66c03949382b6d7e5570 (Feb 26). > > A reproducer and .config are attached. > > === > [ ERR:

RE: [PATCH] checkpatch: add warning on %pk instead of %pK usage

> -Original Message- > From: Roberts, William C [mailto:william.c.robe...@intel.com] > Sent: Wednesday, February 15, 2017 3:49 PM > To: Joe Perches > Cc: linux-kernel@vger.kernel.org; a...@canonical.com; kernel- > harden...@lists.openwall.com > Subject:

RE: [PATCH] checkpatch: add warning on %pk instead of %pK usage

> -Original Message- > From: Roberts, William C [mailto:william.c.robe...@intel.com] > Sent: Wednesday, February 15, 2017 3:49 PM > To: Joe Perches > Cc: linux-kernel@vger.kernel.org; a...@canonical.com; kernel- > harden...@lists.openwall.com > Subject: [kernel-hardening] RE: [PATCH]

Re: [PATCH V5 2/6] mm: don't assume anonymous pages have SwapBacked flag

On Mon, Feb 27, 2017 at 03:35:34PM +0100, Michal Hocko wrote: > On Fri 24-02-17 13:31:45, Shaohua Li wrote: > > There are a few places the code assumes anonymous pages should have > > SwapBacked flag set. MADV_FREE pages are anonymous pages but we are > > going to add them to LRU_INACTIVE_FILE

Re: [PATCH V5 2/6] mm: don't assume anonymous pages have SwapBacked flag

On Mon, Feb 27, 2017 at 03:35:34PM +0100, Michal Hocko wrote: > On Fri 24-02-17 13:31:45, Shaohua Li wrote: > > There are a few places the code assumes anonymous pages should have > > SwapBacked flag set. MADV_FREE pages are anonymous pages but we are > > going to add them to LRU_INACTIVE_FILE

Re: [PATCH 1/4] dt-bindings: dma: uart: add uart dma bindings

On Thu, Feb 16, 2017 at 07:07:28PM +0800, Long Cheng wrote: > add uart dma bindings This and the subject need to be more specific in that this is for Mediatek. > > Signed-off-by: Long Cheng > --- > .../devicetree/bindings/dma/mtk_uart_dma.txt | 32 >

Re: tip.today - scheduler bam boom crash (cpu hotplug)

On 27/02/2017 16:59, Peter Zijlstra wrote: > OK, so if !KVM_FEATURE_CLOCKSOURCE_STABLE_BIT nothing is stable, but if > it is set, TSC might still not be stable, but kvm_clock_read() is. > >> However, if kvmclock is stable, we know that the sched clock is stable. > Right, so the problem is that

Re: [PATCH 1/4] dt-bindings: dma: uart: add uart dma bindings

On Thu, Feb 16, 2017 at 07:07:28PM +0800, Long Cheng wrote: > add uart dma bindings This and the subject need to be more specific in that this is for Mediatek. > > Signed-off-by: Long Cheng > --- > .../devicetree/bindings/dma/mtk_uart_dma.txt | 32 >

Re: tip.today - scheduler bam boom crash (cpu hotplug)

On 27/02/2017 16:59, Peter Zijlstra wrote: > OK, so if !KVM_FEATURE_CLOCKSOURCE_STABLE_BIT nothing is stable, but if > it is set, TSC might still not be stable, but kvm_clock_read() is. > >> However, if kvmclock is stable, we know that the sched clock is stable. > Right, so the problem is that

[PATCH 1/2] ASoC: es7134: add es7134 DAC driver

The es7134 is 24bit, 192Khz i2s DA converter for PCM audio. Datasheet is available here : http://www.everest-semi.com/pdf/ES7134LV%20DS.pdf This driver is also compatible with the es7144, which is the same as the es7134, with 2 additional pins for filtering capacitors. Signed-off-by: Jerome

[PATCH 1/2] ASoC: es7134: add es7134 DAC driver

The es7134 is 24bit, 192Khz i2s DA converter for PCM audio. Datasheet is available here : http://www.everest-semi.com/pdf/ES7134LV%20DS.pdf This driver is also compatible with the es7144, which is the same as the es7134, with 2 additional pins for filtering capacitors. Signed-off-by: Jerome

[RFC PATCH 2/2] kprobes/x86: Exit single-stepping before trying fixup_exception

Exit single-stepping out of line and get back regs->ip to original (probed) address before trying fixup_exception() if the exception happened on the singlestep buffer, since the fixup_exception() depends on regs->ip to search an entry on __ex_table. Signed-off-by: Masami Hiramatsu

[RFC PATCH 2/2] kprobes/x86: Exit single-stepping before trying fixup_exception

Exit single-stepping out of line and get back regs->ip to original (probed) address before trying fixup_exception() if the exception happened on the singlestep buffer, since the fixup_exception() depends on regs->ip to search an entry on __ex_table. Signed-off-by: Masami Hiramatsu ---

Re: [PATCH] vfio pci: kernel support of error recovery only for non fatal error

On Mon, Feb 27, 2017 at 03:28:43PM +0800, Cao jin wrote: > Subject: Re: [PATCH] vfio pci: kernel support of error recovery only for non > fatal error Don't make the subject so long. This is why I had [PATCH v3] vfio error recovery: kernel support you also want to add versioning as you

[PATCH 0/2] Add es7134 DAC driver support

This patchset adds the support for the es7134 from Everest Semiconductor. The es7134 is simple i2s DAC with no configuration interface. It has been tested on Amlogic's meson-gxbb-p200 board. Jerome Brunet (2): ASoC: es7134: add es7134 DAC driver ASoC: es7134: add dt-bindings for the es7134

[PATCH 0/2] Add es7134 DAC driver support

This patchset adds the support for the es7134 from Everest Semiconductor. The es7134 is simple i2s DAC with no configuration interface. It has been tested on Amlogic's meson-gxbb-p200 board. Jerome Brunet (2): ASoC: es7134: add es7134 DAC driver ASoC: es7134: add dt-bindings for the es7134

Re: [PATCH] vfio pci: kernel support of error recovery only for non fatal error

On Mon, Feb 27, 2017 at 03:28:43PM +0800, Cao jin wrote: > Subject: Re: [PATCH] vfio pci: kernel support of error recovery only for non > fatal error Don't make the subject so long. This is why I had [PATCH v3] vfio error recovery: kernel support you also want to add versioning as you

Re: [WARNING: A/V UNSCANNABLE][Merge tag 'media/v4.11-1' of git] ff58d005cd: BUG: unable to handle kernel NULL pointer dereference at 0000039c

* Ingo Molnar [170227 07:44]: > > * Thomas Gleixner wrote: > > > The pending interrupt issue happens, at least on my test boxen, mostly on > > the 'legacy' interrupts (0 - 15). But even the IOAPIC interrupts >=16 > > happen occasionally. > > > > > > -

[PATCH net] rxrpc: Fix deadlock between call creation and sendmsg/recvmsg

All the routines by which rxrpc is accessed from the outside are serialised by means of the socket lock (sendmsg, recvmsg, bind, rxrpc_kernel_begin_call(), ...) and this presents a problem: (1) If a number of calls on the same socket are in the process of connection to the same peer, a

Re: [WARNING: A/V UNSCANNABLE][Merge tag 'media/v4.11-1' of git] ff58d005cd: BUG: unable to handle kernel NULL pointer dereference at 0000039c

* Ingo Molnar [170227 07:44]: > > * Thomas Gleixner wrote: > > > The pending interrupt issue happens, at least on my test boxen, mostly on > > the 'legacy' interrupts (0 - 15). But even the IOAPIC interrupts >=16 > > happen occasionally. > > > > > > - Spurious interrupts on IRQ7, which are

[PATCH net] rxrpc: Fix deadlock between call creation and sendmsg/recvmsg

All the routines by which rxrpc is accessed from the outside are serialised by means of the socket lock (sendmsg, recvmsg, bind, rxrpc_kernel_begin_call(), ...) and this presents a problem: (1) If a number of calls on the same socket are in the process of connection to the same peer, a

Re: [PATCH] sd: close hole in > 2T device rejection when !CONFIG_LBDAF

On Mon, 2017-02-27 at 09:22 -0600, Steven J. Magnani wrote: > @@ -2122,7 +2122,10 @@ static int read_capacity_16(struct scsi_ > return -ENODEV; > } > > - if ((sizeof(sdkp->capacity) == 4) && (lba >= 0xULL)) { > + /* Make sure logical_to_sectors() won't

Re: [PATCH] sd: close hole in > 2T device rejection when !CONFIG_LBDAF

On Mon, 2017-02-27 at 09:22 -0600, Steven J. Magnani wrote: > @@ -2122,7 +2122,10 @@ static int read_capacity_16(struct scsi_ > return -ENODEV; > } > > - if ((sizeof(sdkp->capacity) == 4) && (lba >= 0xULL)) { > + /* Make sure logical_to_sectors() won't

Re: LTP write03 writev07 xfs failures

cc Christoph On Mon, Feb 27, 2017 at 12:22:20PM +0800, Xiong Zhou wrote: > Hi, > > These 2 tests PASS on Linus tree commit: > 37c8596 Merge tag 'tty-4.11-rc1' of git://git.kernel.org/pub/scm/linux... > FAIL on commit: > 60e8d3e Merge tag 'pci-v4.11-changes' of

Re: [PATCH] tracing: Fix code comment for ftrace_ops_get_func

On Wed, 22 Feb 2017 08:29:26 +0800 Chunyu Hu wrote: > There is no function 'ftrace_ops_recurs_func' existing in the code, it > should be ftrace_ops_assist_func. Fix the comment to avoid misleading. Applied, thanks! I'm not sure it will go in this merge window. It might, I'll

Re: LTP write03 writev07 xfs failures

cc Christoph On Mon, Feb 27, 2017 at 12:22:20PM +0800, Xiong Zhou wrote: > Hi, > > These 2 tests PASS on Linus tree commit: > 37c8596 Merge tag 'tty-4.11-rc1' of git://git.kernel.org/pub/scm/linux... > FAIL on commit: > 60e8d3e Merge tag 'pci-v4.11-changes' of

Re: [PATCH] tracing: Fix code comment for ftrace_ops_get_func

On Wed, 22 Feb 2017 08:29:26 +0800 Chunyu Hu wrote: > There is no function 'ftrace_ops_recurs_func' existing in the code, it > should be ftrace_ops_assist_func. Fix the comment to avoid misleading. Applied, thanks! I'm not sure it will go in this merge window. It might, I'll have to see what

[PATCH 2/2] ASoC: es7134: add dt-bindings for the es7134 dac

Signed-off-by: Jerome Brunet --- Documentation/devicetree/bindings/sound/everest,es7134.txt | 10 ++ 1 file changed, 10 insertions(+) create mode 100644 Documentation/devicetree/bindings/sound/everest,es7134.txt diff --git

[PATCH 2/2] ASoC: es7134: add dt-bindings for the es7134 dac

Signed-off-by: Jerome Brunet --- Documentation/devicetree/bindings/sound/everest,es7134.txt | 10 ++ 1 file changed, 10 insertions(+) create mode 100644 Documentation/devicetree/bindings/sound/everest,es7134.txt diff --git a/Documentation/devicetree/bindings/sound/everest,es7134.txt

[RFC PATCH 1/2] kprobes/x86: Use probe_kernel_read instead of memcpy

Use probe_kernel_read() for avoiding unexpected faults while copying kernel text in both of __recover_probed_insn() and __recover_optprobed_insn(). Signed-off-by: Masami Hiramatsu --- arch/x86/kernel/kprobes/core.c |7 +-- arch/x86/kernel/kprobes/opt.c |5 -

[RFC PATCH 1/2] kprobes/x86: Use probe_kernel_read instead of memcpy

Use probe_kernel_read() for avoiding unexpected faults while copying kernel text in both of __recover_probed_insn() and __recover_optprobed_insn(). Signed-off-by: Masami Hiramatsu --- arch/x86/kernel/kprobes/core.c |7 +-- arch/x86/kernel/kprobes/opt.c |5 - 2 files changed, 9

Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list

On Mon, Feb 27, 2017 at 03:28:01PM +0900, Minchan Kim wrote: > Hello Shaohua, > > On Fri, Feb 24, 2017 at 01:31:46PM -0800, Shaohua Li wrote: > > madv MADV_FREE indicate pages are 'lazyfree'. They are still anonymous > > pages, but they can be freed without pageout. To destinguish them > >

Re: [PATCH V5 3/6] mm: move MADV_FREE pages into LRU_INACTIVE_FILE list

On Mon, Feb 27, 2017 at 03:28:01PM +0900, Minchan Kim wrote: > Hello Shaohua, > > On Fri, Feb 24, 2017 at 01:31:46PM -0800, Shaohua Li wrote: > > madv MADV_FREE indicate pages are 'lazyfree'. They are still anonymous > > pages, but they can be freed without pageout. To destinguish them > >

[RFC PATCH 0/2] kprobes/x86: Handle probing on ex_table cases

Hi Peter, Here, I've tried to handle kprobes on exception expected instructions which are recorded in __ex_table. 1st patch fixes recover_probed_instruction() to use probe_kernel_read() instead of memcpy kernel text. So, if you need to get the original instruction for checking the cause of #UD,

[RFC PATCH 0/2] kprobes/x86: Handle probing on ex_table cases

Hi Peter, Here, I've tried to handle kprobes on exception expected instructions which are recorded in __ex_table. 1st patch fixes recover_probed_instruction() to use probe_kernel_read() instead of memcpy kernel text. So, if you need to get the original instruction for checking the cause of #UD,

BENEFIT

You are a recipient to Mrs Julie Leach Donation of $3 million USD. Contact(julieleac...@gmail.com) for claims.

BENEFIT

You are a recipient to Mrs Julie Leach Donation of $3 million USD. Contact(julieleac...@gmail.com) for claims.

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