linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: linux-next: Tree for Apr 10 (lib/test_printf.ko)
Date: Fri, 10 Apr 2020 11:11:04 -0700	[thread overview]
Message-ID: <CAHk-=wjhsM-n_NzSh=cSdpThX+62-x3EmyKjhMqGHFYEyG0nPg@mail.gmail.com> (raw)
In-Reply-To: <27c212c4-b522-561d-411c-e74dc0ff0b74@infradead.org>

On Fri, Apr 10, 2020 at 9:35 AM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> KASAN detects a use-after-free in _raw_spin_lock_irqsave while
> running lib/test_printf.ko.

Btw, can you run these kinds of reports through scripts/decode_stacktrace.sh?

If you have debug info in your build, it will give much more
meaningful backtraces with file names and line numbers (and points to
inlining decisions etc too)

(For individual symbols, use scripts/faddr2line, but the
decode_stacktrace script does them all in one go).

I wonder if these scripts aren't well enough known, I see a lot of raw
dumps that could be immensely improved with a little scripting - but
they need the original vmlinux binary with debug info, so you can't do
it after-the-fact somewhere else..

                Linus

  reply	other threads:[~2020-04-10 18:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10  3:27 linux-next: Tree for Apr 10 Stephen Rothwell
2020-04-10 16:35 ` linux-next: Tree for Apr 10 (lib/test_printf.ko) Randy Dunlap
2020-04-10 18:11   ` Linus Torvalds [this message]
2020-04-10 18:29     ` Randy Dunlap
2020-04-10 19:05       ` Linus Torvalds
2020-04-10 19:41         ` Randy Dunlap
2020-04-10 20:13           ` Linus Torvalds
2020-04-12  5:36             ` Naresh Kamboju
2020-04-12  6:22               ` Randy Dunlap
2020-04-14 19:26                 ` Brendan Higgins
2020-04-15 18:55                   ` Steven Rostedt
2020-04-15 19:16                     ` Randy Dunlap
2020-04-15 19:28                       ` Steven Rostedt
2020-04-12  3:46 ` linux-next: Tree for Apr 10 (warning: objtool: ___bpf_prog_run()) Randy Dunlap

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='CAHk-=wjhsM-n_NzSh=cSdpThX+62-x3EmyKjhMqGHFYEyG0nPg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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).