Marks on a citation
A source citation is matched on the platform release your capture states. Some captures say more than their release, and when what they say doesn’t line up with the source, the citation or the file carries a mark. A mark never removes a citation. Read it as a prompt to check the cited file against the code your device runs; an unmarked citation has not been cleared.
The kernel tree
A kernel log can state a release you have source for while coming from a different vendor’s tree at that release. Check the vendor tree the citation names (as in “Linux 6.1 source for the vendor tree”) against the machine the log came from; if they don’t match, treat the citation as wrong.
A manufacturer or aftermarket build
A manufacturer’s own build or an aftermarket distribution carries changes over the platform release, so a line the manufacturer changed can be shown as code that ran when it did not. Where the build says it is one of those, the capture is marked manufacturer build or aftermarket build.
A different build
Source is matched on the release first. Where the capture states its exact build and we hold source taken from that build, that source is used. Where we hold source for the release taken from a different build, the capture is marked different build: a cited line may differ from the code this device ran. Most source we hold doesn’t record which build it was taken from, and a capture is not marked for that.
Vendor partition code
A device’s vendor partition (its hardware support and board code) can run an older release than the rest of the platform. A citation into that code is checked against the release the same capture states for its vendor partition. Where the source records which partition the cited file installs into, the check is decisive; where it doesn’t, which is true of most source we hold today, the file’s location suggests it and the mark is softer:
| Mark | What it means for you |
|---|---|
| reference only: vendor release differs | The source records this file as vendor partition code, and your vendor partition states a different release. The line is shown for reference, not as the code that ran, and no candidate fix is offered for it |
| reference only: vendor release not comparable | The source records this file as vendor partition code, and the release your vendor partition states isn’t a release of that source (a codename, or another platform’s numbering), so the two can’t be compared. The line is shown for reference and no candidate fix is offered for it |
| likely vendor code; vendor release N | The file’s location suggests vendor partition code, and the source it was matched against may not be what that partition runs. Nothing is withheld; check the line against your vendor tree. Hover the mark for whether your vendor release differs, isn’t comparable, is unstated or couldn’t be read |
| vendor release unknown | The capture doesn’t state its vendor partition’s release |
| vendor release not trusted | The capture states a vendor release that can’t be relied on, such as two different values |
| vendor release not checked | The vendor release couldn’t be checked just now. Reload to try again |
Kernel source carries none of these marks: its modules are built with the kernel, and the kernel source is already matched on the kernel release the capture states.
What the fix-proposal API answers for a line marked reference only, or one whose vendor release couldn’t be checked, is on Candidate fixes.
The source can move after a capture is analyzed
A citation is resolved once, when the capture is uploaded. Source updated since means the tree was re-read after that; most files survive unchanged. Source code changed since means the files themselves differ from the ones the citations were read against. Neither removes anything. Upload the capture again to refresh them.