From: Catalin Marinas <catalin.marinas@arm.com>
To: Phil Carmody <ext-phil.2.carmody@nokia.com>
Cc: linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] ARM: module - additional unwind tables for exit/devexit sections
Date: Thu, 10 Jun 2010 15:48:16 +0100 [thread overview]
Message-ID: <1276181296.24535.51.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <1275567442-11370-4-git-send-email-ext-phil.2.carmody@nokia.com>
On Thu, 2010-06-03 at 13:17 +0100, Phil Carmody wrote:
> Without these, exit functions cannot be stack-traced, so to speak.
> This implies that module unloads that perform allocations (don't
> laugh) will cause noisy warnings on the console when kmemleak is
> enabled, as it presumes that all code's call chains are traceable.
> Similarly, BUGs and WARN_ONs will give additional console spam.
>
> Signed-off-by: Phil Carmody <ext-phil.2.carmody@nokia.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
--
Catalin
next prev parent reply other threads:[~2010-06-10 14:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 12:17 [PATCH 0/3] ARM: unwind extension Phil Carmody
2010-06-03 12:17 ` [PATCH 1/3] ARM: module - simplify code with temporaries Phil Carmody
2010-06-03 12:17 ` [PATCH 2/3] ARM: module - simplify unwind table handling Phil Carmody
2010-06-03 12:17 ` [PATCH 3/3] ARM: module - additional unwind tables for exit/devexit sections Phil Carmody
2010-06-10 14:48 ` Catalin Marinas [this message]
2010-06-10 14:43 ` [PATCH 2/3] ARM: module - simplify unwind table handling Catalin Marinas
2010-06-24 9:05 ` Russell King - ARM Linux
2010-06-24 9:08 ` Catalin Marinas
2010-06-10 14:42 ` [PATCH 1/3] ARM: module - simplify code with temporaries Catalin Marinas
2010-06-10 14:14 ` [PATCH 0/3] ARM: unwind extension Phil Carmody
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=1276181296.24535.51.camel@e102109-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=ext-phil.2.carmody@nokia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).