Commit 88e490913f07 for kernel

commit 88e490913f079f0c0f9535e844077f9d31c369aa
Merge: 603c05a1639f be55257fab18
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu Jan 15 15:13:05 2026 -0800

    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