From: Johannes Berg <johannes@sipsolutions.net>
To: Max Schulze <max.schulze@online.de>, linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH v2 6.1] wifi: cfg80211: fix cqm_config access race
Date: Wed, 16 Aug 2023 09:30:29 +0200 [thread overview]
Message-ID: <dd3c90b687a933f3b2d467a0e3a2f918c26201f4.camel@sipsolutions.net> (raw)
In-Reply-To: <98456a69-d597-505c-6a1b-f33b5f6343e9@online.de>
Hi,
This is ... pretty odd?
> h63 kernel: Unable to handle kernel paging request at virtual address ffff8061d9850028
> h63 kernel: Mem abort info:
> h63 kernel: ESR = 0x0000000096000004
> h63 kernel: EC = 0x25: DABT (current EL), IL = 32 bits
> h63 kernel: SET = 0, FnV = 0
> h63 kernel: EA = 0, S1PTW = 0
> h63 kernel: FSC = 0x04: level 0 translation fault
> h63 kernel: Data abort info:
> h63 kernel: ISV = 0, ISS = 0x00000004
> h63 kernel: CM = 0, WnR = 0
> h63 kernel: [ffff8061d9850028] address between user and kernel address ranges
> h63 kernel: Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
> h63 kernel: Modules linked in: [...]
> h63 kernel: CPU: 3 PID: 493 Comm: Xorg Tainted: G C 6.1.45-v8-gdc69f9d60872 #3
> h63 kernel: Hardware name: Raspberry Pi Compute Module 4 Rev 1.0 (DT)
> h63 kernel: pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> h63 kernel: pc : dma_resv_add_fence+0x80/0x260
I mean, that's in some other code entirely?
> h63 kernel: Call trace:
> h63 kernel: dma_resv_add_fence+0x80/0x260
> h63 kernel: v3d_attach_fences_and_unlock_reservation+0x6c/0x1c0 [v3d]
> h63 kernel: v3d_submit_cl_ioctl+0x540/0x70c [v3d]
> h63 kernel: drm_ioctl_kernel+0xcc/0x180 [drm]
> h63 kernel: drm_ioctl+0x210/0x440 [drm]
> h63 kernel: __arm64_sys_ioctl+0xb0/0xf4
> h63 kernel: invoke_syscall+0x50/0x120
> h63 kernel: el0_svc_common.constprop.0+0x68/0x124
> h63 kernel: do_el0_svc+0x34/0xd0
> h63 kernel: el0_svc+0x30/0x94
> h63 kernel: el0t_64_sync_handler+0xb8/0xbc
> h63 kernel: el0t_64_sync+0x18c/0x190
> h63 kernel: Code: fa401044 54000061 d4210000 d503201f (f9401678)
Unless my code caused some really bad corruption somewhere, I'm not sure
I see how that would happen?
Were you able to reproduce it multiple times? Maybe we can see a pattern
out of multiple reports.
johannes
next prev parent reply other threads:[~2023-08-16 7:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 14:11 BCM43455: brcmf_notify_rssi / cfg80211_cqm_rssi_notify : Unable to handle kernel NULL pointer dereference Max Schulze
2023-08-10 8:34 ` BCM43455: brcmf_notify_rssi / cfg80211_cqm_rssi_notify : Unable to handle kernel NULL pointer dereference (RSSI notification after station disconnect?) Max Schulze
2023-08-11 7:30 ` [PATCH] wifi: nl80211: avoid NULL-ptr deref after cfg80211_cqm_rssi_update Max Schulze
2023-08-11 9:54 ` Johannes Berg
2023-08-12 9:35 ` Max Schulze
2023-08-12 9:23 ` BCM43455: brcmf_notify_rssi / cfg80211_cqm_rssi_notify : Unable to handle kernel NULL pointer dereference (RSSI notification after station disconnect?) Max Schulze
2023-08-13 13:18 ` [RFC PATCH] wifi: cfg80211: fix cqm_config access race Johannes Berg
2023-08-15 10:56 ` Max Schulze
2023-08-15 11:02 ` Johannes Berg
2023-08-15 11:42 ` [RFC PATCH v2] " Johannes Berg
2023-08-15 13:24 ` Max Schulze
2023-08-15 13:25 ` Johannes Berg
2023-08-15 13:37 ` [RFC PATCH v2 6.1] " Johannes Berg
2023-08-16 7:23 ` Max Schulze
2023-08-16 7:30 ` Johannes Berg [this message]
2023-08-16 11:24 ` Max Schulze
2023-08-16 13:08 ` Max Schulze
2023-08-16 13:17 ` Johannes Berg
2023-08-16 13:33 ` Max Schulze
2023-08-16 13:27 ` Johannes Berg
2023-08-16 13:32 ` [RFC PATCH v3 " Johannes Berg
2023-08-16 13:36 ` Johannes Berg
2023-08-16 13:38 ` [RFC PATCH v4 " Johannes Berg
2023-09-11 13:16 ` Max Schulze
2023-09-11 16:23 ` Max Schulze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd3c90b687a933f3b2d467a0e3a2f918c26201f4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=max.schulze@online.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox