5
>> ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
>
> The free and use-after-free are both via the same do_enable_set() path
> which implies there are racing writes to the debugfs write handler. It
> seems locking is missing for both listen_chan and enable_6lowpan. The
> latter seems misused in is_bt_6lowpan(), which should likely just be
> checking for chan->ops == &bt_6lowpan_chan_ops, I think?
>
> I have no way to actually test changes to this code...
>
I do have limited hardware for testing bluetooth 6lowpan connections,
but am a little busy these weeks. So some time by the end of this month
I should be able to at least verify if my use-case would be broken by a
change, if somebody were to propose one ;)
br
Josua Mayer
From: Josua Mayer
Allow up to four clocks to be specified and enabled for the orion-mdio
interface, which are required by the Armada 8k and defined in
armada-cp110.dtsi.
Fixes a hang in probing the mvmdio driver that was encountered on the
Clearfog GT 8K with all drivers built as modules, but
From: Josua Mayer
Defer probing of the orion-mdio interface when getting a clock returns
EPROBE_DEFER. This avoids locking up the Armada 8k SoC when mdio is used
before all clocks have been enabled.
Signed-off-by: Josua Mayer
---
drivers/net/ethernet/marvell/mvmdio.c | 5 +
1 file changed
From: Josua Mayer
With a modular kernel as configured by Debian a hang was observed with
the Armada 8040 SoC in the Clearfog GT and Macchiatobin boards.
The 8040 SoC actually requires four clocks to be enabled for the mdio
interface to function. All 4 clocks are already specified in
armada
From: Josua Mayer
Armada 8040 needs four clocks to be enabled for MDIO accesses to work.
Update the binding to allow the extra clock to be specified.
Cc: sta...@vger.kernel.org
Fixes: 6d6a331f44a1 ("dt-bindings: allow up to three clocks for orion-mdio")
Reviewed-by: Andrew Lunn
Sig
From: Josua Mayer
Print a warning when device tree specifies more than the maximum of four
clocks supported by orion-mdio. Because reading from mdio can lock up
the Armada 8k when a required clock is not initialized, it is important
to notify the user when a specified clock is ignored.
Signed
Hi Andrew,
Am 06.07.19 um 18:09 schrieb Andrew Lunn:
> On Sat, Jul 06, 2019 at 05:18:59PM +0200, jo...@solid-run.com wrote:
>> From: Josua Mayer
>>
>> Print a warning when device tree specifies more than the maximum of four
>> clocks supported by orion-mdio. Because re
From: Josua Mayer
Print a warning when device tree specifies more than the maximum of four
clocks supported by orion-mdio. Because reading from mdio can lock up
the Armada 8k when a required clock is not initialized, it is important
to notify the user when a specified clock is ignored.
Signed
From: Josua Mayer
With a modular kernel as configured by Debian a hang was observed with
the Armada 8040 SoC in the Clearfog GT and Macchiatobin boards.
The 8040 SoC actually requires four clocks to be enabled for the mdio
interface to function. All 4 clocks are already specified in
armada
From: Josua Mayer
Armada 8040 needs four clocks to be enabled for MDIO accesses to work.
Update the binding to allow the extra clock to be specified.
Cc: sta...@vger.kernel.org
Fixes: 6d6a331f44a1 ("dt-bindings: allow up to three clocks for orion-mdio")
Signed-off-by: J
From: Josua Mayer
Allow up to four clocks to be specified and enabled for the orion-mdio
interface, which are required by the Armada 8k and defined in
armada-cp110.dtsi.
Fixes a hang in probing the mvmdio driver that was encountered on the
Clearfog GT 8K with all drivers built as modules, but
From: Josua Mayer
Defer probing of the orion-mdio interface when enabling of either of the
clocks defer probing. This avoids locking up the Armada 8k SoC when mdio
is used before all clocks have been enabled.
Signed-off-by: Josua Mayer
---
drivers/net/ethernet/marvell/mvmdio.c | 5 +
1
12 matches
Mail list logo
