On 31/03/2025 18:31, Christian Kohlschütter wrote:
Whoa! Good eyes, Michael!
What is my Fritzbox doing to my initrd, and why does reverting the commit fix
it?
FWIW, I also have a capture with an ethernet frame from another device on my
network (ARP, ethertype 0x0806), so this is probably the
o me. Thank you for fixing this!
Reviewed-by: Michael Brown
Thanks,
Michael
On 03/04/2025 23:41, Simon Glass wrote:
On Fri, 4 Apr 2025 at 08:18, Christian Kohlschütter
wrote:
On 3. Apr 2025, at 19:54, Simon Glass wrote:
4. DMA traffic could then write over the malloc() region
I'm not seeing where the Ethernet device's stop() is called. The
dwmac_meson8b driver does
On 03/04/2025 20:18, Christian Kohlschütter wrote:
+Tom Rini (actually adding Tom to the conversation)
3. When the device is removed, the struct is freed, meaning that a
future malloc() can use that same space.
Yes, that sounds plausible. How can such allocations be prevented?
I assume U-Boot
On 31/03/2025 18:31, Christian Kohlschütter wrote:
Whoa! Good eyes, Michael!
What is my Fritzbox doing to my initrd, and why does reverting the commit fix
it?
FWIW, I also have a capture with an ethernet frame from another device on my
network (ARP, ethertype 0x0806), so this is probably the
On 31/03/2025 17:49, Christian Kohlschütter wrote:
# hexdump /.argh
000
*
0044100 15dc f9c8 6f16 e188
0044110 00a0 52b0 a01c 6d59
0044120
0044130 00
6 matches
Mail list logo
