On Sat, May 27, 2023 at 12:01 AM Frank Scheiner <frank.scheiner@xxxxxx> wrote: > > If it is of any help, my initial report is available for example via: > > https://marc.info/?l=linux-ia64&m=168509859125505&w=2 > > ...the whole thread is currently at: > > https://marc.info/?t=168509868200003&r=1&w=2 This does make it clear just how great a mailing list archive lore is. Konstantin, is there any particular reason why linux-ia64@xxxxxxxxxxxxxxx isn't in lore? Is it just a rational hatred of all things itanium? Anyway, the WARN_ON() is likely related, but the bug is clearly an unexpected page fault in __copy_user() when called by load_module(). The ia64 oops output is nasty, presumably because ia64 aggressively inlines things. It would help a lot if you enabled debug info (maybe you already do?) and then run the oops through ./scripts/decode_stacktrace.sh which will figure out line numbers, inlining etc. Because I don't even see why it would call __copy_user() in the first place. This is 'finit_module()' that loads the module data from a file, not user space. So I guess it must be the strndup_user() in mod->args = strndup_user(uargs, ~0UL >> 1); but that doesn't look like it should even care about any module layout. Plus I would have expected to see strndup_user() in the call trace, but whatever. End result: that ia64 trace is very hard to read, and _maybe_ running it through the decode script might give more information about what it is that triggers... Linus
![]() |