# Re: \[PATCH v7 0/4\] alloc\_tag and module codetag section fixes

- From: Andrew Morton \<akpm@linux-foundation.org\>
- Date: 2026-09-02 22:05:07 
- List: linux-modules
- Page: https://ratatoskr.run/linux-modules/2026/09/17501055
- Thread: https://ratatoskr.run/linux-modules/2026/09/17496394/t.md

```text
On Wed,  2 Sep 2026 16:17:58 +0800 Hao Ge [ref] wrote:

> I ran into an overflow problem in the module tag area. With profiling
> toggled off, the overflow check in reserve_module_tags() did not
> run, a module could load with more tags than the page flags can
> address, and re-enabling profiling then silently corrupted
> /proc/allocinfo. On overflow the fix shuts profiling down, releases
> the reservation and returns -EAGAIN, and the codetag section lands
> as regular module data in the same load, so the module loads without
> profiling.
> 
> Review of the earlier series by Sashiko turned up two more problems.

Thanks.  Sashiko had a lot more to say, as I assume you've seen:
	https://sashiko.dev/#/patchset/20260902081802.146145-1-hao.ge@linux.dev

Also, "Based-on-a-patch-by:" isn't a recognized thing, although it's
been used ~30 times in the past.

I'm ambivalent about ad-hoc invention of new tags, although it happens
a lot.  Perhaps it would be better to do


	Based on a patch by Petr Pavlu [1].
	...
	Link: ... [1]

?
```
