mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <sha@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/4] KASan: print output directly to stderr
Date: Tue, 12 Sep 2023 11:36:38 +0200	[thread overview]
Message-ID: <20230912093638.GZ637806@pengutronix.de> (raw)
In-Reply-To: <20230911125619.2782229-1-a.fatoum@pengutronix.de>

On Mon, Sep 11, 2023 at 02:56:15PM +0200, Ahmad Fatoum wrote:
> 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

Applied, thanks

Sascha

> 
>  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
> 
> 
> 

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



      parent reply	other threads:[~2023-09-12  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 12:56 Ahmad Fatoum
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 ` Sascha Hauer [this message]

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=20230912093638.GZ637806@pengutronix.de \
    --to=sha@pengutronix.de \
    --cc=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