mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: mfe@pengutronix.de, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 0/5] malloc: add __free() cleanup handlers
Date: Tue, 22 Sep 2026 12:47:51 +0200	[thread overview]
Message-ID: <20260922104813.317584-1-a.fatoum@pengutronix.de> (raw)

The cleanup infrastructure was added to barebox a while back in
commit 332e3542e5ed ("Port Linux __cleanup() based guard
infrastructure"), but without any DEFINE_FREE() handlers, so nothing
could be passed to __free() so far.

Let's start with malloc and kmalloc, so buffers can be tied to the
scope they are used in:

	void *buf __free(free)  =  malloc(size);
	void *foo __free(kfree) = kzalloc(size, GFP_KERNEL);

[k]free_sensitive() looks up the usable size of the buffer before
zeroing it, so it gets the same test rather than just a NULL check
to avoid an error pointer dereference inside the allocator.

Ahmad Fatoum (5):
  commands: rksecure: exit if invalid integer passed to -b
  firmware-zynqmp: don't ignore the kstrtouint() result in parse_reg()
  include: compiler: make __must_check a yes-op
  malloc: add __free() cleanup handlers
  test: self: add cleanup selftest

 arch/arm/mach-zynqmp/firmware-zynqmp.c |  6 +-
 commands/rksecure.c                    |  4 +-
 include/linux/compiler_types.h         |  4 --
 include/linux/slab.h                   |  5 ++
 include/malloc.h                       |  5 ++
 test/self/Kconfig                      | 10 +++
 test/self/Makefile                     |  1 +
 test/self/cleanup.c                    | 89 ++++++++++++++++++++++++++
 8 files changed, 118 insertions(+), 6 deletions(-)
 create mode 100644 test/self/cleanup.c

-- 
2.47.3




             reply	other threads:[~2026-09-22 10:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 10:47 Ahmad Fatoum [this message]
2026-09-22 10:47 ` [PATCH 1/5] commands: rksecure: exit if invalid integer passed to -b Ahmad Fatoum
2026-09-22 10:47 ` [PATCH 2/5] firmware-zynqmp: don't ignore the kstrtouint() result in parse_reg() Ahmad Fatoum
2026-09-22 10:47 ` [PATCH 3/5] include: compiler: make __must_check a yes-op Ahmad Fatoum
2026-09-22 10:47 ` [PATCH 4/5] malloc: add __free() cleanup handlers Ahmad Fatoum
2026-09-22 10:47 ` [PATCH 5/5] test: self: add cleanup selftest Ahmad Fatoum
2026-09-23  6:33 ` [PATCH 0/5] malloc: add __free() cleanup handlers Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260922104813.317584-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=mfe@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox