linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qian Cai <cai@lca.pw>
To: Marco Elver <elver@google.com>
Cc: Michal Hocko <mhocko@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] mm/page_counter: mark intentional data races
Date: Wed, 29 Jan 2020 04:33:03 -0500	[thread overview]
Message-ID: <DE8391CD-A9CF-4D16-A41B-F563F2AE8D57@lca.pw> (raw)
In-Reply-To: <CANpmjNNaCtL+vqpPKug9_DoFUue=PdoTyQFXLOx5H_BYCyDMzA@mail.gmail.com>



> On Jan 29, 2020, at 4:06 AM, Marco Elver <elver@google.com> wrote:
> 
> Why are the line numbers for the remaining symbols missing?  Doesn't
> scripts/decode_stacktrace.sh give you all line numbers?

I used scripts/faddr2line and never used decode_stacktrace.sh before. I did not insert other line numbers because it can be easily determined by looking at the function itself through an code browser.

> 
> [ As an aside: if you want to use what syzbot uses to put line numbers
> on symbols, which is a bit faster:
> https://github.com/google/syzkaller/tree/master/tools/syz-symbolize
> https://github.com/google/syzkaller/blob/master/docs/linux/setup.md
> then 'go build tools/syz-symbolize'. ]

That is good to know.

  reply	other threads:[~2020-01-29  9:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29  4:20 [PATCH -next] mm/page_counter: mark intentional data races Qian Cai
2020-01-29  8:51 ` Michal Hocko
2020-01-29  9:06   ` Marco Elver
2020-01-29  9:33     ` Qian Cai [this message]
2020-01-29  9:51     ` Qian Cai

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=DE8391CD-A9CF-4D16-A41B-F563F2AE8D57@lca.pw \
    --to=cai@lca.pw \
    --cc=akpm@linux-foundation.org \
    --cc=elver@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.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;
as well as URLs for NNTP newsgroup(s).