diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2026-01-15 15:13:05 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2026-01-15 15:13:05 -0800 |
| commit | 88e490913f079f0c0f9535e844077f9d31c369aa (patch) | |
| tree | 808d0d336752cd7ae68c197e8714cba2defe64fd /include/linux/pse-pd | |
| parent | 603c05a1639f60e0c52c5fdd25cf5e0b44b9bd8e (diff) | |
| parent | be55257fab181b93af38f8c4b1b3cb453a78d742 (diff) | |
Merge tag 'ftrace-v6.19-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace
Pull ftrace fix from Steven Rostedt:
- Fix allocation accounting on boot up
The ftrace records for each function that ftrace can attach to is
done in a group of pages. At boot up, the number of pages are
calculated and allocated. After that, the pages are filled with data.
It may allocate more than needed due to some functions not being
recorded (because they are unused weak functions), this too is
recorded.
After the data is filled in, a check is made to make sure the right
number of pages were allocated. But this was off due to the
assumption that the same number of entries fit per every page.
Because the size of an entry does not evenly divide into PAGE_SIZE,
there is a rounding error when a large number of pages is allocated
to hold the events. This causes the check to fail and triggers a
warning.
Fix the accounting by finding out how many pages are actually
allocated from the functions that allocate them and use that to see
if all the pages allocated were used and the ones not used are
properly freed.
* tag 'ftrace-v6.19-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace:
ftrace: Do not over-allocate ftrace memory
Diffstat (limited to 'include/linux/pse-pd')
0 files changed, 0 insertions, 0 deletions
