Re: hung task in 4.14 (syzbot bug from 2018 April 17)

f0 }, timer = { entry = { next = 0xdead0200, pprev = 0x0 }, expires = 4295020559, function = 0xa80778c0, data = 18446744072250514272, flags = 69206020 }, wq = 0x95443f011400, cpu = 128 } Any input is welcome. -- Sebastian Kuzminsky

hung task in 4.14 (syzbot bug from 2018 April 17)

wq = 0x9d2680411400, cpu = 128 } I'd appreciate help or pointers on how to debug and fix this problem. -- Sebastian Kuzminsky

Re: fix for bnx2x panic during ethtool reporting

Here's an updated version of the patch that is checkpatch.pl clean (I had forgotten to sign off...). -- Sebastian Kuzminsky From 45fe6fb1f6a187233bd1304b031bed20b3819d26 Mon Sep 17 00:00:00 2001 From: Sebastian Kuzminsky Date: Mon, 16 Apr 2018 23:24:07 + Subject: [PATCH] bnx2x: make f

fix for bnx2x panic during ethtool reporting

"ethtool -i" on a bnx2x interface causes kernel panic when the firmware version is longer than expected. The attached patch fixes the problem by simplifying the string handling in bnx2x_fill_fw_str(). It applies cleanly to 4.14 and 4.17-rc1. -- Sebastian Kuzm

linux 2.4.32: kernel BUG in slab.c:1582

indicative of memory corruption? -- Sebastian Kuzminsky There are two kinds of people in this world: Those who finish what they begin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECT

2.6.12.5 bug? per-socket TCP keepalive settings

se(). Pull the network cable and watch the packet sniffer. Let me know if I can do anything to help track this down, though I'm going to be traveling and will be slow to respond until Monday August 29. -- Sebastian Kuzminsky #include #include #include #include #include #include