linux-kernel - Is there a different memory allocation path other than the buddy allocator?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 28 Apr 2021 13:07:50 +0530
From:   Shivank Garg <shivankgarg98@...il.com>
To:     linux-kernel@...r.kernel.org, linux-mm@...ck.org,
        akpm@...ux-foundation.org, gregkh@...uxfoundation.org,
        sergey.senozhatsky@...il.com, pmladek@...e.com
Subject: Is there a different memory allocation path other than the buddy allocator?

Hi Everyone!

I'm understanding memory allocation in Linux and doing some changes in
buddy allocator (__alloc_pages_nodemask) for my experiments. I create
a new flag in `struct page->flags` (by adding a new flag in `enum
pageflags` in `page-flags.h`. I set this bit permanently in
__alloc_pages_nodemask (to not to be cleared once set and survive all
further allocation and freeing). But I'm not able to see expected
behavior.

I'm guessing this is because Linux is also using some different path
to allocate memory (probably during boot). Is my hypothesis correct?

Is there any different memory allocation path other than buddy
allocator? Where can I find it?

To keep the newly added bit in the page_flag set for 'struct page'
lifetime.  I make sure not to clear it while freeing by unsetting it
in "#define PAGE_FLAGS_CHECK_AT_PREP       \
-       (((1UL << NR_PAGEFLAGS) - 1) & ~__PG_HWPOISON & ~(1UL <<
PG_NEWEXPFLAG))" I know  adding new bits in page->flag is probably not
a good idea but this if for better understanding :)

Thank You and stay safe!

Best Regards,
Shivank