Bug 277416 - LinuxKPI w/ LKPI_80211_HW_CRYPTO: add/organize crypto debug flag in LinuxKPI
Summary: LinuxKPI w/ LKPI_80211_HW_CRYPTO: add/organize crypto debug flag in LinuxKPI
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: Cheng Cui
URL:
Keywords: tracking
Depends on:
Blocks: 276095
  Show dependency tree / graph
 
Reported: 2024-03-01 16:18 UTC by Cheng Cui
Modified: 2024-12-31 13:37 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cheng Cui freebsd_committer freebsd_triage 2024-03-01 16:18:30 UTC 
There is `IEEE80211_MSG_CRYPTO` debug flag when `IEEE80211_DEBUG` is defined, but there is no `D80211_TRACE_CRYPTO` debug flag when `LINUXKPI_DEBUG_80211` is defined. Currently, some of the *lkpi* crypto debug message is using `D80211_TRACE`, which mixes with other debug purpose messages. This makes it hard debugging and swimming in the mess of messages.

This PR is tracking such issue as the subject describes.
Comment 1 Cheng Cui freebsd_committer freebsd_triage 2024-03-04 19:39:39 UTC 
(In reply to Cheng Cui from comment #0)

My mistake, currently all the `LKPI_80211_HW_CRYPTO` code blocks do not use any trace flag. So I must have made a mistake with the `D80211_TRACE` when working with some of the crypto patches in review.

But maybe this PR can still be used to track future crypto debug flag. Just not a high priority.
Comment 2 Bjoern A. Zeeb freebsd_committer freebsd_triage 2024-12-31 13:37:46 UTC 
Closing this (along with the others) as they seem to be overcome by events.