Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on

Hi Peter, On Mon, Mar 6, 2017 at 3:28 PM, Peter De Schrijver wrote: > On Mon, Mar 06, 2017 at 09:58:29AM +, Jon Hunter wrote: >> On 06/03/17 08:38, Peter De Schrijver wrote: >> > On Thu, Mar 02, 2017 at 05:56:49PM +, Jon Hunter wrote: >> >> On 28/02/17 15:19,

Re: [PATCH] clk: tegra: mark TEGRA210_CLK_DBGAPB as always on

Hi Peter, On Mon, Mar 6, 2017 at 3:28 PM, Peter De Schrijver wrote: > On Mon, Mar 06, 2017 at 09:58:29AM +, Jon Hunter wrote: >> On 06/03/17 08:38, Peter De Schrijver wrote: >> > On Thu, Mar 02, 2017 at 05:56:49PM +, Jon Hunter wrote: >> >> On 28/02/17 15:19, Peter De Schrijver wrote: >>

Re: [PATCH] irqchip: crossbar: Fix incorrect type of register size

On Mon, Mar 06, 2017 at 02:56:14PM +, Marc Zyngier wrote: > On Mon, Mar 06 2017 at 1:41:06 pm GMT, Franck Demathieu > wrote: > > The 'size' variable is unsigned according to the dt-bindings. > > As this variable is used as integer in other places, create a new variable

Re: [PATCH] irqchip: crossbar: Fix incorrect type of register size

On Mon, Mar 06, 2017 at 02:56:14PM +, Marc Zyngier wrote: > On Mon, Mar 06 2017 at 1:41:06 pm GMT, Franck Demathieu > wrote: > > The 'size' variable is unsigned according to the dt-bindings. > > As this variable is used as integer in other places, create a new variable > > that allows to

Re: [PATCH 03/12] gpio: omap: use devm_irq_alloc_descs()

* Bartosz Golaszewski [170304 08:33]: > This driver never frees the allocated interrupt descriptors. Fix it by > using a resource managed variant of irq_alloc_descs(). > > Signed-off-by: Bartosz Golaszewski Would be good to get Aaro's ack

Re: [PATCH 03/12] gpio: omap: use devm_irq_alloc_descs()

* Bartosz Golaszewski [170304 08:33]: > This driver never frees the allocated interrupt descriptors. Fix it by > using a resource managed variant of irq_alloc_descs(). > > Signed-off-by: Bartosz Golaszewski Would be good to get Aaro's ack on this one. Regards, Tony > --- >

Re: stack frame unwindind KASAN errors

On Mon, Mar 06, 2017 at 02:52:01PM +0800, Daniel J Blueman wrote: > Thanks Josh! > > With this patch, the KASAN warning still occurs, but at > unwind_get_return_address+0x1d3/0x130 instead; the rest of the trace > is identical. > > (gdb) list *(unwind_get_return_address+0x1d3) >

Re: stack frame unwindind KASAN errors

On Mon, Mar 06, 2017 at 02:52:01PM +0800, Daniel J Blueman wrote: > Thanks Josh! > > With this patch, the KASAN warning still occurs, but at > unwind_get_return_address+0x1d3/0x130 instead; the rest of the trace > is identical. > > (gdb) list *(unwind_get_return_address+0x1d3) >

Re: [PATCH v2] pinctrl: samsung: Calculate GPIO base for pinctrl_add_gpio_range

On Sat, Mar 04, 2017 at 08:20:11PM +0900, Tomasz Figa wrote: > Hi Charles, > > 2017-03-01 2:04 GMT+09:00 Charles Keepax > : > > As the pinctrl is now added before the GPIOs are registered we need to > > manually calculate what the GPIO base will be, otherwise

Re: [PATCH v2] pinctrl: samsung: Calculate GPIO base for pinctrl_add_gpio_range

On Sat, Mar 04, 2017 at 08:20:11PM +0900, Tomasz Figa wrote: > Hi Charles, > > 2017-03-01 2:04 GMT+09:00 Charles Keepax > : > > As the pinctrl is now added before the GPIOs are registered we need to > > manually calculate what the GPIO base will be, otherwise the base for > > each gpio_range

Re: v4.10: kernel stack frame pointer .. has bad value (null)

On Thu 2017-03-02 17:45:14, Josh Poimboeuf wrote: > On Fri, Feb 24, 2017 at 11:04:39PM -0600, Josh Poimboeuf wrote: > > On Thu, Feb 23, 2017 at 09:10:39PM +0100, Pavel Machek wrote: > > > Hi! > > > > > > > > > > > > > Somehow, startup_32_smp() is on the stack twice. The stack > > > > > > >

Re: v4.10: kernel stack frame pointer .. has bad value (null)

On Thu 2017-03-02 17:45:14, Josh Poimboeuf wrote: > On Fri, Feb 24, 2017 at 11:04:39PM -0600, Josh Poimboeuf wrote: > > On Thu, Feb 23, 2017 at 09:10:39PM +0100, Pavel Machek wrote: > > > Hi! > > > > > > > > > > > > > Somehow, startup_32_smp() is on the stack twice. The stack > > > > > > >

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On 03/06/2017 05:24 PM, Dmitry Vyukov wrote: > Let me provide more context and design alternatives. > > There are also other archs, at least arm64 for now. > There are also other tools. For KTSAN (race detector) we will > absolutely need to hook into atomic ops. For KMSAN (uses of unit > values)

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On 03/06/2017 05:24 PM, Dmitry Vyukov wrote: > Let me provide more context and design alternatives. > > There are also other archs, at least arm64 for now. > There are also other tools. For KTSAN (race detector) we will > absolutely need to hook into atomic ops. For KMSAN (uses of unit > values)

[PATCH v3 2/3] gpio: wm831x: Add basic device tree support

Now the wm831x-core has basic DT support we can update this driver to allow use of the GPIOs within a device tree system. Signed-off-by: Charles Keepax Acked-by: Linus Walleij --- No changes since v2. drivers/gpio/gpio-wm831x.c |

[PATCH v3 2/3] gpio: wm831x: Add basic device tree support

Now the wm831x-core has basic DT support we can update this driver to allow use of the GPIOs within a device tree system. Signed-off-by: Charles Keepax Acked-by: Linus Walleij --- No changes since v2. drivers/gpio/gpio-wm831x.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff

[PATCH v3 3/3] mfd: wm831x: Add device tree binding document

Add a device tree binding document for the wm831x series of PMICs. Currently only support for the registering the device and the GPIOs are actually implemented in the driver. Signed-off-by: Charles Keepax --- Changes since v2: - Flesh the binding some more

[PATCH v3 1/3] mfd: wm831x: Add basic device tree binding

Add the basic ability to register the device through device tree, more work is needed to get each individual sub-driver functioning correctly but this is enough to get the device to probe from device tree. Signed-off-by: Charles Keepax --- No changes since

[PATCH v3 3/3] mfd: wm831x: Add device tree binding document

Add a device tree binding document for the wm831x series of PMICs. Currently only support for the registering the device and the GPIOs are actually implemented in the driver. Signed-off-by: Charles Keepax --- Changes since v2: - Flesh the binding some more with some additional features of the

[PATCH v3 1/3] mfd: wm831x: Add basic device tree binding

Add the basic ability to register the device through device tree, more work is needed to get each individual sub-driver functioning correctly but this is enough to get the device to probe from device tree. Signed-off-by: Charles Keepax --- No changes since v2. drivers/mfd/wm831x-core.c

[PATCH 1/2] regulator: tps65132: add regulator driver for TI TPS65132

Adding regulator driver for the device TI TPS65132 which is single inductor - dual output power supply device. TPS65132 device is designed to support general positive/negative driven applications like TFT display panels. TPS65132 regulator driver supports to enable/disable and set voltage on its

[PATCH 1/2] regulator: tps65132: add regulator driver for TI TPS65132

Adding regulator driver for the device TI TPS65132 which is single inductor - dual output power supply device. TPS65132 device is designed to support general positive/negative driven applications like TFT display panels. TPS65132 regulator driver supports to enable/disable and set voltage on its

[PATCH 2/2] drm: mali-dp: Fix smart layer not going to composition

From: Mihail Atanassov Use rectangle 1 as a generic plane. Existing code already sets the smart layer bounding box size + offset. The rectangles' offsets are relative to the bounding box, so there is no need to set R1's offset (reset value is 0), just its size which is

[PATCH 1/2] drm: mali-dp: Remove mclk rate management

From: Mihail Atanassov The rate of mclk depends on the use-case. If no downscaling is required, then mclk == pxlclk is a valid option; with downscaling however, the rate at which mclk runs determines how much a plane can be downscaled before composition. This is a

[PATCH 0/2] drm: mali-dp: Fixes for v4.11-rc2

A couple of fixes that I have queued in my tree waiting for the dust to settle on the main drm pull request. Best regards, Liviu Mihail Atanassov (2): drm: mali-dp: Remove mclk rate management drm: mali-dp: Fix smart layer not going to composition drivers/gpu/drm/arm/malidp_crtc.c | 3

[PATCH 2/2] drm: mali-dp: Fix smart layer not going to composition

From: Mihail Atanassov Use rectangle 1 as a generic plane. Existing code already sets the smart layer bounding box size + offset. The rectangles' offsets are relative to the bounding box, so there is no need to set R1's offset (reset value is 0), just its size which is the same as the bounding

[PATCH 1/2] drm: mali-dp: Remove mclk rate management

From: Mihail Atanassov The rate of mclk depends on the use-case. If no downscaling is required, then mclk == pxlclk is a valid option; with downscaling however, the rate at which mclk runs determines how much a plane can be downscaled before composition. This is a system integration + power

[PATCH 0/2] drm: mali-dp: Fixes for v4.11-rc2

A couple of fixes that I have queued in my tree waiting for the dust to settle on the main drm pull request. Best regards, Liviu Mihail Atanassov (2): drm: mali-dp: Remove mclk rate management drm: mali-dp: Fix smart layer not going to composition drivers/gpu/drm/arm/malidp_crtc.c | 3

Re: [PATCH 10/26] brcmsmac: reindent split functions

Arend Van Spriel writes: > On 2-3-2017 17:38, Arnd Bergmann wrote: >> In the previous commit I left the indentation alone to help reviewing >> the patch, this one now runs the three new functions through 'indent -kr -8' >> with some manual fixups to avoid silliness.

Re: [PATCH 10/26] brcmsmac: reindent split functions

Arend Van Spriel writes: > On 2-3-2017 17:38, Arnd Bergmann wrote: >> In the previous commit I left the indentation alone to help reviewing >> the patch, this one now runs the three new functions through 'indent -kr -8' >> with some manual fixups to avoid silliness. >> >> No changes other than

Re: [PATCH 08/26] brcmsmac: make some local variables 'static const' to reduce stack size

Arend Van Spriel writes: > On 2-3-2017 17:38, Arnd Bergmann wrote: >> With KASAN and a couple of other patches applied, this driver is one >> of the few remaining ones that actually use more than 2048 bytes of >> kernel stack: >> >>

Re: [PATCH] EDAC, xgene: fix spelling mistake: "procesing" -> "processing"

On Wed, Feb 22, 2017 at 08:52:15PM -0800, Loc Ho wrote: > Hi, > > > > > trivial fix to spelling mistake in dev_err message > > > > Signed-off-by: Colin Ian King > > Reviewed-by: Loc Ho Applied, thanks. -- Regards/Gruss, Boris. Good mailing

Re: [PATCH 08/26] brcmsmac: make some local variables 'static const' to reduce stack size

Arend Van Spriel writes: > On 2-3-2017 17:38, Arnd Bergmann wrote: >> With KASAN and a couple of other patches applied, this driver is one >> of the few remaining ones that actually use more than 2048 bytes of >> kernel stack: >> >> broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function >>

Re: [PATCH] EDAC, xgene: fix spelling mistake: "procesing" -> "processing"

On Wed, Feb 22, 2017 at 08:52:15PM -0800, Loc Ho wrote: > Hi, > > > > > trivial fix to spelling mistake in dev_err message > > > > Signed-off-by: Colin Ian King > > Reviewed-by: Loc Ho Applied, thanks. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim

Re: [PATCH 1/9] mm: fix 100% CPU kswapd busyloop on unreclaimable nodes

On Mon, Mar 06, 2017 at 10:37:40AM +0900, Minchan Kim wrote: > On Fri, Mar 03, 2017 at 08:59:54AM +0100, Michal Hocko wrote: > > On Fri 03-03-17 10:26:09, Minchan Kim wrote: > > > On Tue, Feb 28, 2017 at 04:39:59PM -0500, Johannes Weiner wrote: > > > > @@ -3316,6 +3325,9 @@ static int

Re: [PATCH 1/9] mm: fix 100% CPU kswapd busyloop on unreclaimable nodes

On Mon, Mar 06, 2017 at 10:37:40AM +0900, Minchan Kim wrote: > On Fri, Mar 03, 2017 at 08:59:54AM +0100, Michal Hocko wrote: > > On Fri 03-03-17 10:26:09, Minchan Kim wrote: > > > On Tue, Feb 28, 2017 at 04:39:59PM -0500, Johannes Weiner wrote: > > > > @@ -3316,6 +3325,9 @@ static int

Re: [PATCH 1/4] net: thunderx: Fix IOMMU translation faults

On 06/03/17 12:57, Sunil Kovvuri wrote: >>> >>> We are seeing a 0.75Mpps drop with IP forwarding rate due to that. >>> Hence I have restricted calling DMA interfaces to only when IOMMU is >>> enabled. >> >> What's 0.07Mpps as a percentage of baseline? On a correctly configured >> coherent arm64

Re: [PATCH 1/4] net: thunderx: Fix IOMMU translation faults

On 06/03/17 12:57, Sunil Kovvuri wrote: >>> >>> We are seeing a 0.75Mpps drop with IP forwarding rate due to that. >>> Hence I have restricted calling DMA interfaces to only when IOMMU is >>> enabled. >> >> What's 0.07Mpps as a percentage of baseline? On a correctly configured >> coherent arm64

[PATCH v4 4/7] perf/sdt: Clean uprobe_events when event(out of multiple events) parsing fails

User may ask for multiple events in the same record command like, perf record -a -e sdt_1:* -e sdt_2:* If sdt_1:* events are already added to uprobe_events and sdt_2:* event parsing fails, clean sdt_1:* events from uprobe_events. Signed-off-by: Ravi Bangoria

[PATCH v4 4/7] perf/sdt: Clean uprobe_events when event(out of multiple events) parsing fails

User may ask for multiple events in the same record command like, perf record -a -e sdt_1:* -e sdt_2:* If sdt_1:* events are already added to uprobe_events and sdt_2:* event parsing fails, clean sdt_1:* events from uprobe_events. Signed-off-by: Ravi Bangoria --- tools/perf/builtin-record.c

[PATCH] regulator: core: use snprintf() instead of scnprintf()

When creating the link to the device sysfs entry, the regulator core calls scnprintf() and then checks if the returned value is greater or equal than the buffer size. The former can never happen as scnprintf() returns the number of bytes that were actually written to the buffer, not the bytes

[PATCH] regulator: core: use snprintf() instead of scnprintf()

When creating the link to the device sysfs entry, the regulator core calls scnprintf() and then checks if the returned value is greater or equal than the buffer size. The former can never happen as scnprintf() returns the number of bytes that were actually written to the buffer, not the bytes

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On Mon, Mar 06, 2017 at 05:02:05PM +0200, Laurent Pinchart wrote: > Hi Daniel, > > On Monday 06 Mar 2017 11:38:20 Daniel Vetter wrote: > > On Fri, Mar 03, 2017 at 06:45:40PM +0200, Laurent Pinchart wrote: > > > - I haven't seen any proposal how a heap-based solution could be used in a > > >

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On Mon, Mar 06, 2017 at 05:02:05PM +0200, Laurent Pinchart wrote: > Hi Daniel, > > On Monday 06 Mar 2017 11:38:20 Daniel Vetter wrote: > > On Fri, Mar 03, 2017 at 06:45:40PM +0200, Laurent Pinchart wrote: > > > - I haven't seen any proposal how a heap-based solution could be used in a > > >

Re: [PATCH 11/29] drivers, media: convert cx88_core.refcount from atomic_t to refcount_t

Hello. On 03/06/2017 05:20 PM, Elena Reshetova wrote: refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by:

Re: [PATCH 11/29] drivers, media: convert cx88_core.refcount from atomic_t to refcount_t

Hello. On 03/06/2017 05:20 PM, Elena Reshetova wrote: refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by:

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Mon, Mar 6, 2017 at 5:20 PM, Mark Rutland wrote: > Hi, > > [roping in Will, since he loves atomics] > > On Mon, Mar 06, 2017 at 03:24:23PM +0100, Dmitry Vyukov wrote: >> On Mon, Mar 6, 2017 at 2:01 PM, Peter Zijlstra wrote: >> > On Mon, Mar 06, 2017

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Mon, Mar 6, 2017 at 5:20 PM, Mark Rutland wrote: > Hi, > > [roping in Will, since he loves atomics] > > On Mon, Mar 06, 2017 at 03:24:23PM +0100, Dmitry Vyukov wrote: >> On Mon, Mar 6, 2017 at 2:01 PM, Peter Zijlstra wrote: >> > On Mon, Mar 06, 2017 at 01:58:51PM +0100, Peter Zijlstra wrote:

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

Hi, [roping in Will, since he loves atomics] On Mon, Mar 06, 2017 at 03:24:23PM +0100, Dmitry Vyukov wrote: > On Mon, Mar 6, 2017 at 2:01 PM, Peter Zijlstra wrote: > > On Mon, Mar 06, 2017 at 01:58:51PM +0100, Peter Zijlstra wrote: > >> On Mon, Mar 06, 2017 at 01:50:47PM

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

Hi, [roping in Will, since he loves atomics] On Mon, Mar 06, 2017 at 03:24:23PM +0100, Dmitry Vyukov wrote: > On Mon, Mar 6, 2017 at 2:01 PM, Peter Zijlstra wrote: > > On Mon, Mar 06, 2017 at 01:58:51PM +0100, Peter Zijlstra wrote: > >> On Mon, Mar 06, 2017 at 01:50:47PM +0100, Dmitry Vyukov

Re: [PATCH] mmc: sunxi: mask all Response Timeout error messages

On Mon, Mar 06, 2017 at 06:32:41PM +0800, Icenowy Zheng wrote: > 06.03.2017, 18:04, "Maxime Ripard" : > > Hi, > > > > On Mon, Mar 06, 2017 at 12:45:35AM +0800, Icenowy Zheng wrote: > >>  Response Timeout is very usual: it will happen when trying to run some > >>  

[PATCH] arm64: dts: NS2: convert "ok" to "okay"

Per e-mail from Sergei Shtylyov, the DT spec dictates it should be "okay" (although "ok" is also recognized). Thus, changing all "ok" to "okay" in NS2 device tree files Suggested-by: Sergei Shtylyov Signed-off-by: Jon Mason ---

[PATCH] arm64: dts: NS2: convert "ok" to "okay"

Per e-mail from Sergei Shtylyov, the DT spec dictates it should be "okay" (although "ok" is also recognized). Thus, changing all "ok" to "okay" in NS2 device tree files Suggested-by: Sergei Shtylyov Signed-off-by: Jon Mason --- arch/arm64/boot/dts/broadcom/ns2-svk.dts | 38

Re: [PATCH] mmc: sunxi: mask all Response Timeout error messages

On Mon, Mar 06, 2017 at 06:32:41PM +0800, Icenowy Zheng wrote: > 06.03.2017, 18:04, "Maxime Ripard" : > > Hi, > > > > On Mon, Mar 06, 2017 at 12:45:35AM +0800, Icenowy Zheng wrote: > >>  Response Timeout is very usual: it will happen when trying to run some > >>  commands that do not belong to the

[PATCH v3 2/2] ARM: dts: bcm5301x: Add I2C support to the DT

From: Jon Mason Add I2C support to the bcm5301x Device Tree. Since no driver changes are needed to enable this hardware, only the device tree changes are required to make this functional. Signed-off-by: Jon Mason ---

[PATCH v3 2/2] ARM: dts: bcm5301x: Add I2C support to the DT

From: Jon Mason Add I2C support to the bcm5301x Device Tree. Since no driver changes are needed to enable this hardware, only the device tree changes are required to make this functional. Signed-off-by: Jon Mason --- arch/arm/boot/dts/bcm5301x.dtsi | 10 ++ 1 file changed, 10

[PATCH v3 1/2] ARM: dts: bcm5301x: Add TWD WD Support to DT

From: Jon Mason Add support for the ARM TWD Watchdog to the bcm5301x device tree. The ARM TWD timer allocated the register space for the WDT, so this patch necessitated shrinking that. Also, the GIC masks were added for these. Signed-off-by: Jon Mason

[PATCH v3 0/2] ARM: dts: BCM5301X: TWD WD and i2c Support

Changes in v3: * Dropped the "Correct GIC_PPI interrupt flags" patch from the series, as it was already accepted * Disabled the i2c bus by default, to follow current convention (per Florian) Changes in v2: * Rafal discovered an issue with the GIC_PPI flags being incorrect. Since there was a

[PATCH v3 1/2] ARM: dts: bcm5301x: Add TWD WD Support to DT

From: Jon Mason Add support for the ARM TWD Watchdog to the bcm5301x device tree. The ARM TWD timer allocated the register space for the WDT, so this patch necessitated shrinking that. Also, the GIC masks were added for these. Signed-off-by: Jon Mason --- arch/arm/boot/dts/bcm5301x.dtsi |

[PATCH v3 0/2] ARM: dts: BCM5301X: TWD WD and i2c Support

Changes in v3: * Dropped the "Correct GIC_PPI interrupt flags" patch from the series, as it was already accepted * Disabled the i2c bus by default, to follow current convention (per Florian) Changes in v2: * Rafal discovered an issue with the GIC_PPI flags being incorrect. Since there was a

Re: XTS Crypto Not Found In /proc/crypto Even After Compiled for 4.10.1.

I tried the patch you submitted, however it also fails for the most part. "For the most part" because "xts" is now found. $ grep xts /proc/crypto name : xts(aes) driver : xts(ecb-aes-s5p) Fail: * [ 21.057756] xor: using function: neon (352.000 MB/sec) [ 21.064243] Unable to

Re: XTS Crypto Not Found In /proc/crypto Even After Compiled for 4.10.1.

I tried the patch you submitted, however it also fails for the most part. "For the most part" because "xts" is now found. $ grep xts /proc/crypto name : xts(aes) driver : xts(ecb-aes-s5p) Fail: * [ 21.057756] xor: using function: neon (352.000 MB/sec) [ 21.064243] Unable to

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Mon, Mar 06, 2017 at 04:20:13PM +0100, Peter Zijlstra wrote: > On Mon, Mar 06, 2017 at 03:24:23PM +0100, Dmitry Vyukov wrote: > > We could also provide a parallel implementation of atomic ops based on > > the new compiler builtins (__atomic_load_n and friends): > >

Re: [PATCH] x86, kasan: add KASAN checks to atomic operations

On Mon, Mar 06, 2017 at 04:20:13PM +0100, Peter Zijlstra wrote: > On Mon, Mar 06, 2017 at 03:24:23PM +0100, Dmitry Vyukov wrote: > > We could also provide a parallel implementation of atomic ops based on > > the new compiler builtins (__atomic_load_n and friends): > >

Re: [bdi_unregister] 165a5e22fa INFO: task swapper:1 blocked for more than 120 seconds.

On Mon 06-03-17 07:44:55, James Bottomley wrote: > On Mon, 2017-03-06 at 16:14 +0100, Jan Kara wrote: > > On Mon 06-03-17 06:35:21, James Bottomley wrote: > > > On Mon, 2017-03-06 at 13:01 +0100, Jan Kara wrote: > > > > On Mon 06-03-17 11:27:33, Jan Kara wrote: > > > > > Hi, > > > > > > > > > >

Re: [bdi_unregister] 165a5e22fa INFO: task swapper:1 blocked for more than 120 seconds.

On Mon 06-03-17 07:44:55, James Bottomley wrote: > On Mon, 2017-03-06 at 16:14 +0100, Jan Kara wrote: > > On Mon 06-03-17 06:35:21, James Bottomley wrote: > > > On Mon, 2017-03-06 at 13:01 +0100, Jan Kara wrote: > > > > On Mon 06-03-17 11:27:33, Jan Kara wrote: > > > > > Hi, > > > > > > > > > >

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On Mon, Mar 06, 2017 at 11:58:05AM +0100, Mark Brown wrote: > On Mon, Mar 06, 2017 at 11:40:41AM +0100, Daniel Vetter wrote: > > > No one gave a thing about android in upstream, so Greg KH just dumped it > > all into staging/android/. We've discussed ION a bunch of times, recorded > > anything

Re: [RFC PATCH 00/12] Ion cleanup in preparation for moving out of staging

On Mon, Mar 06, 2017 at 11:58:05AM +0100, Mark Brown wrote: > On Mon, Mar 06, 2017 at 11:40:41AM +0100, Daniel Vetter wrote: > > > No one gave a thing about android in upstream, so Greg KH just dumped it > > all into staging/android/. We've discussed ION a bunch of times, recorded > > anything

Re: [PATCH 2/2] ARM: dts: motorola-cpcap-mapphone: add LEDs

* Sebastian Reichel [170305 09:24]: > Signed-off-by: Sebastian Reichel > --- > arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi | 30 > ++ > 1 file changed, 30 insertions(+) > > diff --git a/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi

Re: [PATCH 2/2] ARM: dts: motorola-cpcap-mapphone: add LEDs

* Sebastian Reichel [170305 09:24]: > Signed-off-by: Sebastian Reichel > --- > arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi | 30 > ++ > 1 file changed, 30 insertions(+) > > diff --git a/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi >

Re: [PATCH v2 6/9] kasan: improve slab object description

On 03/06/2017 04:45 PM, Andrey Konovalov wrote: > On Fri, Mar 3, 2017 at 3:39 PM, Andrey Ryabinin > wrote: >> >> >> On 03/03/2017 04:52 PM, Alexander Potapenko wrote: >>> On Fri, Mar 3, 2017 at 2:31 PM, Andrey Ryabinin >>> wrote: On

Re: [PATCH v2 6/9] kasan: improve slab object description

On 03/06/2017 04:45 PM, Andrey Konovalov wrote: > On Fri, Mar 3, 2017 at 3:39 PM, Andrey Ryabinin > wrote: >> >> >> On 03/03/2017 04:52 PM, Alexander Potapenko wrote: >>> On Fri, Mar 3, 2017 at 2:31 PM, Andrey Ryabinin >>> wrote: On 03/02/2017 04:48 PM, Andrey Konovalov wrote: >

Re: [PATCH 02/10] ARM: dts: N900: Add bluetooth

* Sebastian Reichel [170304 04:00]: > Add bcm2048 node and its system clock to the N900 device tree file. > Apart from that a reference to the new clock has been added to > wl1251 (which uses it, too). > > Signed-off-by: Sebastian Reichel Picking this patch

Re: [PATCH 02/10] ARM: dts: N900: Add bluetooth

* Sebastian Reichel [170304 04:00]: > Add bcm2048 node and its system clock to the N900 device tree file. > Apart from that a reference to the new clock has been added to > wl1251 (which uses it, too). > > Signed-off-by: Sebastian Reichel Picking this patch into omap-for-v4.12/dt thanks.

[PATCH v3 2/9] kasan: unify report headers

Unify KASAN report header format for different kinds of bad memory accesses. Makes the code simpler. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 26 +- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/mm/kasan/report.c

[PATCH v3 2/9] kasan: unify report headers

Unify KASAN report header format for different kinds of bad memory accesses. Makes the code simpler. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 26 +- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/mm/kasan/report.c b/mm/kasan/report.c index

Re: [PATCH 01/10] ARM: dts: N9/N950: add bluetooth

* Sebastian Reichel [170304 04:00]: > The Nokia N950 and N9 have a wl1271 (with nokia bootloader) bluetooth > module connected to second UART. > > Signed-off-by: Sebastian Reichel Picking this patch into omap-for-v4.12/dt thanks. Regards, Tony

Re: [PATCH 01/10] ARM: dts: N9/N950: add bluetooth

* Sebastian Reichel [170304 04:00]: > The Nokia N950 and N9 have a wl1271 (with nokia bootloader) bluetooth > module connected to second UART. > > Signed-off-by: Sebastian Reichel Picking this patch into omap-for-v4.12/dt thanks. Regards, Tony

[PATCH] genirq: Fix handling of nested shared IRQs

When an IRQ is nested the nested handler is called directly from within the threaded handler of the parent IRQ, however, the code in handle_nested_irq only calls a single handler. This means when a shared IRQ is nested only the first of the shared IRQ handlers will be run. This patch adds a loop

[PATCH] genirq: Fix handling of nested shared IRQs

When an IRQ is nested the nested handler is called directly from within the threaded handler of the parent IRQ, however, the code in handle_nested_irq only calls a single handler. This means when a shared IRQ is nested only the first of the shared IRQ handlers will be run. This patch adds a loop

[PATCH v3 6/9] kasan: improve slab object description

Changes slab object description from: Object at 880068388540, in cache kmalloc-128 size: 128 to: Object at 880068388540 belongs to cache kmalloc-128 of size 128 Access 123 bytes inside of 128-byte region [880068388540, 8800683885c0) This adds information about relative offset

[PATCH v3 6/9] kasan: improve slab object description

Changes slab object description from: Object at 880068388540, in cache kmalloc-128 size: 128 to: Object at 880068388540 belongs to cache kmalloc-128 of size 128 Access 123 bytes inside of 128-byte region [880068388540, 8800683885c0) This adds information about relative offset

[PATCH v3 7/9] kasan: print page description after stacks

Moves page description after the stacks since it's less important. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/mm/kasan/report.c b/mm/kasan/report.c index

[PATCH v3 7/9] kasan: print page description after stacks

Moves page description after the stacks since it's less important. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/mm/kasan/report.c b/mm/kasan/report.c index 87f8293d7b79..09a5f5b4bc79 100644 ---

[PATCH v3 3/9] kasan: change allocation and freeing stack traces headers

Change stack traces headers from: Allocated: PID = 42 to: Allocated by task 42: Makes the report one line shorter and look better. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git

[PATCH v3 1/9] kasan: introduce helper functions for determining bug type

Introduce get_shadow_bug_type() function, which determines bug type based on the shadow value for a particular kernel address. Introduce get_wild_bug_type() function, which determines bug type for addresses which don't have a corresponding shadow value. Signed-off-by: Andrey Konovalov

[PATCH v3 3/9] kasan: change allocation and freeing stack traces headers

Change stack traces headers from: Allocated: PID = 42 to: Allocated by task 42: Makes the report one line shorter and look better. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/mm/kasan/report.c

[PATCH v3 1/9] kasan: introduce helper functions for determining bug type

Introduce get_shadow_bug_type() function, which determines bug type based on the shadow value for a particular kernel address. Introduce get_wild_bug_type() function, which determines bug type for addresses which don't have a corresponding shadow value. Signed-off-by: Andrey Konovalov ---

[PATCH v3 9/9] kasan: separate report parts by empty lines

Makes the report easier to read. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/mm/kasan/report.c b/mm/kasan/report.c index e5b762f4a6a4..2f3ff28b4d76 100644 --- a/mm/kasan/report.c +++ b/mm/kasan/report.c

[PATCH v3 5/9] kasan: change report header

Change report header format from: BUG: KASAN: use-after-free in unwind_get_return_address+0x28a/0x2c0 at addr 880069437950 Read of size 8 by task insmod/3925 to: BUG: KASAN: use-after-free in unwind_get_return_address+0x28a/0x2c0 Read of size 8 at addr 880069437950 by task insmod/3925

[PATCH v3 9/9] kasan: separate report parts by empty lines

Makes the report easier to read. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/mm/kasan/report.c b/mm/kasan/report.c index e5b762f4a6a4..2f3ff28b4d76 100644 --- a/mm/kasan/report.c +++ b/mm/kasan/report.c @@ -231,7 +231,9 @@

[PATCH v3 5/9] kasan: change report header

Change report header format from: BUG: KASAN: use-after-free in unwind_get_return_address+0x28a/0x2c0 at addr 880069437950 Read of size 8 by task insmod/3925 to: BUG: KASAN: use-after-free in unwind_get_return_address+0x28a/0x2c0 Read of size 8 at addr 880069437950 by task insmod/3925

[PATCH v3 8/9] kasan: improve double-free report format

Changes double-free report header from: BUG: Double free or freeing an invalid pointer Unexpected shadow byte: 0xFB to: BUG: KASAN: double-free or invalid-free in kmalloc_oob_left+0xe5/0xef This makes a bug uniquely identifiable by the first report line. To account for removing of the

[PATCH v3 8/9] kasan: improve double-free report format

Changes double-free report header from: BUG: Double free or freeing an invalid pointer Unexpected shadow byte: 0xFB to: BUG: KASAN: double-free or invalid-free in kmalloc_oob_left+0xe5/0xef This makes a bug uniquely identifiable by the first report line. To account for removing of the

[PATCH v3 4/9] kasan: simplify address description logic

Simplify logic for describing a memory address. Add addr_to_page() helper function. Makes the code easier to follow. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 36 1 file changed, 20 insertions(+), 16 deletions(-) diff

[PATCH v3 4/9] kasan: simplify address description logic

Simplify logic for describing a memory address. Add addr_to_page() helper function. Makes the code easier to follow. Signed-off-by: Andrey Konovalov --- mm/kasan/report.c | 36 1 file changed, 20 insertions(+), 16 deletions(-) diff --git

[PATCH v3 0/9] kasan: improve error reports

This patchset improves KASAN reports by making them easier to read and a little more detailed. Also improves mm/kasan/report.c readability. Effectively changes a use-after-free report to: == BUG: KASAN: use-after-free in

[PATCH v3 0/9] kasan: improve error reports

This patchset improves KASAN reports by making them easier to read and a little more detailed. Also improves mm/kasan/report.c readability. Effectively changes a use-after-free report to: == BUG: KASAN: use-after-free in

Re: [RFC PATCH 10/12] staging: android: ion: Use CMA APIs directly

On Mon, Mar 06, 2017 at 03:43:53PM +0200, Laurent Pinchart wrote: > Hi Daniel, > > On Monday 06 Mar 2017 11:32:04 Daniel Vetter wrote: > > On Fri, Mar 03, 2017 at 10:50:20AM -0800, Laura Abbott wrote: > > > On 03/03/2017 08:41 AM, Laurent Pinchart wrote: > > >> On Thursday 02 Mar 2017 13:44:42

Re: [RFC PATCH 10/12] staging: android: ion: Use CMA APIs directly

On Mon, Mar 06, 2017 at 03:43:53PM +0200, Laurent Pinchart wrote: > Hi Daniel, > > On Monday 06 Mar 2017 11:32:04 Daniel Vetter wrote: > > On Fri, Mar 03, 2017 at 10:50:20AM -0800, Laura Abbott wrote: > > > On 03/03/2017 08:41 AM, Laurent Pinchart wrote: > > >> On Thursday 02 Mar 2017 13:44:42

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