mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 0/4] KASan: print output directly to stderr
Date: Mon, 11 Sep 2023 14:56:15 +0200	[thread overview]
Message-ID: <20230911125619.2782229-1-a.fatoum@pengutronix.de> (raw)

I recently hunted down a heap memory corruption and this was somewhat
complicated by KASan and dump_stack() themselves allocating memory
off the heap. This series switches them to directly write to the
consoles associated with stderr, while skipping the log.

Ahmad Fatoum (4):
  ARM: unwind: don't allocate while printing stack trace
  ARM64: backtrace: print stacktrace to stderr
  KASan: only print to stderr
  KASan: don't allocate memory while printing report

 arch/arm/lib32/unwind.c     | 20 ++++++++++----------
 arch/arm/lib64/stacktrace.c |  6 +++---
 lib/kasan/generic.c         |  2 --
 lib/kasan/report.c          | 22 +++++++++++-----------
 4 files changed, 24 insertions(+), 26 deletions(-)

-- 
2.39.2




             reply	other threads:[~2023-09-11 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 12:56 Ahmad Fatoum [this message]
2023-09-11 12:56 ` [PATCH 1/4] ARM: unwind: don't allocate while printing stack trace Ahmad Fatoum
2023-09-11 12:56 ` [PATCH 2/4] ARM64: backtrace: print stacktrace to stderr Ahmad Fatoum
2023-09-11 12:56 ` [PATCH 3/4] KASan: only print " Ahmad Fatoum
2023-09-11 12:56 ` [PATCH 4/4] KASan: don't allocate memory while printing report Ahmad Fatoum
2023-09-12  9:36 ` [PATCH 0/4] KASan: print output directly to stderr 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=20230911125619.2782229-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /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