audit,module: restore audit logging in load failure case#63
Open
modules-kpd-app[bot] wants to merge 2 commits into
Open
audit,module: restore audit logging in load failure case#63modules-kpd-app[bot] wants to merge 2 commits into
modules-kpd-app[bot] wants to merge 2 commits into
Conversation
Author
|
Upstream branch: 085c5e3 |
dagomez137
force-pushed
the
modules-next_base
branch
from
April 1, 2025 10:54
96f6e22 to
7c2b408
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
from
April 7, 2025 01:58
7c2b408 to
2996654
Compare
Author
|
Upstream branch: 897c0b4 |
modules-kpd-app
Bot
force-pushed
the
series/902422=>modules-next
branch
from
April 7, 2025 01:59
24925a0 to
fcae7d0
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
from
April 7, 2025 14:12
2996654 to
d4037eb
Compare
Author
|
Upstream branch: b464e57 |
modules-kpd-app
Bot
force-pushed
the
series/902422=>modules-next
branch
from
April 7, 2025 14:13
fcae7d0 to
026c504
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
from
May 5, 2025 08:22
d4037eb to
39f16b8
Compare
modules-kpd-app Bot
pushed a commit
that referenced
this pull request
May 5, 2025
Fix niu_try_msix() to not cause a fatal trap on sparc systems. Set PCI_DEV_FLAGS_MSIX_TOUCH_ENTRY_DATA_FIRST on the struct pci_dev to work around a bug in the hardware or firmware. For each vector entry in the msix table, niu chips will cause a fatal trap if any registers in that entry are read before that entries' ENTRY_DATA register is written to. Testing indicates writes to other registers are not sufficient to prevent the fatal trap, however the value does not appear to matter. This only needs to happen once after power up, so simply rebooting into a kernel lacking this fix will NOT cause the trap. NON-RESUMABLE ERROR: Reporting on cpu 64 NON-RESUMABLE ERROR: TPC [0x00000000005f6900] <msix_prepare_msi_desc+0x90/0xa0> NON-RESUMABLE ERROR: RAW [4010000000000016:00000e37f93e32ff:0000000202000080:ffffffffffffffff NON-RESUMABLE ERROR: 0000000800000000:0000000000000000:0000000000000000:0000000000000000] NON-RESUMABLE ERROR: handle [0x4010000000000016] stick [0x00000e37f93e32ff] NON-RESUMABLE ERROR: type [precise nonresumable] NON-RESUMABLE ERROR: attrs [0x02000080] < ASI sp-faulted priv > NON-RESUMABLE ERROR: raddr [0xffffffffffffffff] NON-RESUMABLE ERROR: insn effective address [0x000000c50020000c] NON-RESUMABLE ERROR: size [0x8] NON-RESUMABLE ERROR: asi [0x00] CPU: 64 UID: 0 PID: 745 Comm: kworker/64:1 Not tainted 6.11.5 #63 Workqueue: events work_for_cpu_fn TSTATE: 0000000011001602 TPC: 00000000005f6900 TNPC: 00000000005f6904 Y: 00000000 Not tainted TPC: <msix_prepare_msi_desc+0x90/0xa0> g0: 00000000000002e9 g1: 000000000000000c g2: 000000c50020000c g3: 0000000000000100 g4: ffff8000470307c0 g5: ffff800fec5be000 g6: ffff800047a08000 g7: 0000000000000000 o0: ffff800014feb000 o1: ffff800047a0b620 o2: 0000000000000011 o3: ffff800047a0b620 o4: 0000000000000080 o5: 0000000000000011 sp: ffff800047a0ad51 ret_pc: 00000000005f7128 RPC: <__pci_enable_msix_range+0x3cc/0x460> l0: 000000000000000d l1: 000000000000c01f l2: ffff800014feb0a8 l3: 0000000000000020 l4: 000000000000c000 l5: 0000000000000001 l6: 0000000020000000 l7: ffff800047a0b734 i0: ffff800014feb000 i1: ffff800047a0b730 i2: 0000000000000001 i3: 000000000000000d i4: 0000000000000000 i5: 0000000000000000 i6: ffff800047a0ae81 i7: 00000000101888b0 I7: <niu_try_msix.constprop.0+0xc0/0x130 [niu]> Call Trace: [<00000000101888b0>] niu_try_msix.constprop.0+0xc0/0x130 [niu] [<000000001018f840>] niu_get_invariants+0x183c/0x207c [niu] [<00000000101902fc>] niu_pci_init_one+0x27c/0x2fc [niu] [<00000000005ef3e4>] local_pci_probe+0x28/0x74 [<0000000000469240>] work_for_cpu_fn+0x8/0x1c [<000000000046b008>] process_scheduled_works+0x144/0x210 [<000000000046b518>] worker_thread+0x13c/0x1c0 [<00000000004710e0>] kthread+0xb8/0xc8 [<00000000004060c8>] ret_from_fork+0x1c/0x2c [<0000000000000000>] 0x0 Kernel panic - not syncing: Non-resumable error. Fixes: 7d5ec3d ("PCI/MSI: Mask all unused MSI-X entries") Signed-off-by: Jonathan Currier <dullfire@yahoo.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Cc: stable@vger.kernel.org Link: https://lore.kernel.org/all/20241117234843.19236-3-dullfire@yahoo.com
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
from
May 18, 2025 12:05
39f16b8 to
d6fb02c
Compare
Author
|
Upstream branch: a0b018a |
modules-kpd-app
Bot
force-pushed
the
series/902422=>modules-next
branch
from
May 18, 2025 12:06
026c504 to
2a65406
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
from
June 2, 2025 09:03
d6fb02c to
b788ac1
Compare
Author
|
Upstream branch: a0b018a |
The move of the module sanity check to earlier skipped the audit logging call in the case of failure and to a place where the previously used context is unavailable. Add an audit logging call for the module loading failure case and get the module name when possible. Link: https://issues.redhat.com/browse/RHEL-52839 Fixes: 02da2cb ("module: move check_modinfo() early to early_mod_check()") Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
modules-kpd-app
Bot
force-pushed
the
series/902422=>modules-next
branch
from
June 2, 2025 09:03
2a65406 to
0d7bb77
Compare
dagomez137
force-pushed
the
modules-next_base
branch
from
June 20, 2025 07:31
b788ac1 to
e04c78d
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
from
June 25, 2025 20:39
cbdca0b to
6a1a12c
Compare
dagomez137
force-pushed
the
modules-next_base
branch
from
June 26, 2025 12:20
6a1a12c to
7c2b408
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
2 times, most recently
from
June 26, 2025 18:03
6381fa5 to
aaa7ece
Compare
dagomez137
force-pushed
the
modules-next_base
branch
2 times, most recently
from
July 4, 2025 19:48
b4d1c4e to
61dc34e
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
2 times, most recently
from
July 8, 2025 19:00
1df8185 to
9aab33d
Compare
dagomez137
force-pushed
the
modules-next_base
branch
from
July 8, 2025 19:46
9aab33d to
99d099e
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
from
July 8, 2025 19:56
99d099e to
3aed49d
Compare
dagomez137
force-pushed
the
modules-next_base
branch
from
October 22, 2025 08:36
3aed49d to
856647c
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
from
October 22, 2025 09:38
856647c to
e1b99f5
Compare
dagomez137
force-pushed
the
modules-next_base
branch
from
October 22, 2025 09:53
e1b99f5 to
856647c
Compare
modules-kpd-app
Bot
force-pushed
the
modules-next_base
branch
4 times, most recently
from
October 22, 2025 11:40
cdc6b9e to
311def7
Compare
dagomez137
force-pushed
the
modules-next_base
branch
from
October 22, 2025 21:31
311def7 to
1107cb7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull request for series with
subject: audit,module: restore audit logging in load failure case
version: 2
url: https://patchwork.kernel.org/project/linux-modules/list/?series=944832