My laptop's a Lenovo ThinkPad T430 with an i7-3520M CPU.
I'd love to do the same hex edit you're using, but it's above my knowledge level: I don't know how to work out the address and raw values that need to be set... Comparing disassemblies of 4.13, 4.14 and 4.15-rc5 , there seem to be differences in addresses. But if I understand correctly it's somewhere between 0x2273 - 0x2278 (in 4.13), or 0x2458 - 0x245d (in 4.15-rc5)?
I'm having trouble understanding the gdb disassembly output, but it also looks like the compiler optimized out the "err = -EFAULT" line? If so, how do you insert a return call without shifting other addresses and breaking the .ko?
And to work out what "return -EFAULT" looks like in hex, I suppose you copy bytes from one of the other places it's used?
Thank you for reading this, and don't feel bad if you don't have the time to explain!
[^] # Re: Not in 4.15-RC5 yet
Posté par razorb . En réponse au journal D'un kernel panic à un patch.... Évalué à 1.
Alright! I've submitted a Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886556. Hopefully it'll help give the patch an extra push, in Debian at least.
My laptop's a Lenovo ThinkPad T430 with an i7-3520M CPU.
I'd love to do the same hex edit you're using, but it's above my knowledge level: I don't know how to work out the address and raw values that need to be set... Comparing disassemblies of 4.13, 4.14 and 4.15-rc5 , there seem to be differences in addresses. But if I understand correctly it's somewhere between 0x2273 - 0x2278 (in 4.13), or 0x2458 - 0x245d (in 4.15-rc5)?
I'm having trouble understanding the gdb disassembly output, but it also looks like the compiler optimized out the "err = -EFAULT" line? If so, how do you insert a return call without shifting other addresses and breaking the .ko?
And to work out what "return -EFAULT" looks like in hex, I suppose you copy bytes from one of the other places it's used?
Thank you for reading this, and don't feel bad if you don't have the time to explain!