In D59710#1385456, @jrtc27 wrote:

Alternatively, why not just adjust the existing loop that populates segs to instead take min(p_vaddr) and max(p_vaddr + p_memsz)? It wouldn't be hard to do and would remove the need for this restriction (and without any complex sorting). The only thing you'd miss is handling overlapping segments, but to be honest I don't think that would necessarily be a problem, we'd do exactly what the file asked for and load the segments in that order, but it just might result in the module shooting itself in the foot, which I don't see as any different from the countless other ways a module can corrupt its own internal state and panic your kernel. At the end of the day if you're loading a module into the kernel you're trusting the module to not itself be a panic-fest, all the kernel linker should be doing is avoiding confusing/corrupting things *outside* the module.

Shorten copyright notice

since the code that caused the panic has already been fixed on main, maybe we should rename this commit to "fix edgecases" or similar?

Rebase against main. Apparently some of these fixes were pushed already

done

Add copyright text

Clean up

Added test cases

Fix other panics found during testing

Check that segments are already sorted

Fix null check

Original bugzilla report:217432

Address comment

Addresses Bug 289923

Use strcasecmp instead of strcmp to check class name.

• buildpatch: Add kpatch ELF post-processing tool
• kpatch: Add example patch module