[Bug 241728] linuxkpi: panics after loading radeonkms kernel module (data storage interrupt trap)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241728

--- Comment #22 from Mark Millard <marklmi26-fbsd at yahoo.com> ---
(In reply to Piotr Kubaj from comment #0)

This defect is from /usr/src/sys/compat/linuxkpi/common/src/linux_idr.c using:

struct linux_idr_cache {
        spinlock_t lock;
        struct idr_layer *head;
        unsigned count;
};

DPCPU_DEFINE_STATIC(struct linux_idr_cache, linux_idr_cache);

The same type of problem as for:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232387

I'll quote the resolution from 232387, to indicate what
would likely be analogous here:

Author: luporl
Date: Tue Jun 25 17:15:45 UTC 2019
New revision: 349377
URL: https://svnweb.freebsd.org/changeset/base/349377

Log:
  [PowerPC64] Don't mark module data as static

  Fixes panic when loading ipfw.ko and if_epair.ko built with modern compiler.

  Similar to arm64 and riscv, when using a modern compiler (!gcc4.2), code
  generated tries to access data in the wrong location, causing kernel panic
  (data storage interrupt trap) when loading if_epair and ipfw.

  Issue was reproduced with kernel/module compiled using gcc8 and clang8. It
  affects both ELFv1 and ELFv2 ABI environments.

  PR:           232387
  Submitted by: alfredo.junior_eldorado.org.br
  Reported by:  Mark Millard
  Reviewed by:  jhibbits
  Differential Revision:        https://reviews.freebsd.org/D20461

Changes:
  head/sys/net/vnet.h
  head/sys/sys/pcpu.h

-- 
You are receiving this mail because:
You are the assignee for the bug.