From: Tejun Heo <tj@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>
Subject: Re: fs: GPF in locked_inode_to_wb_and_lock_list
Date: Thu, 21 Apr 2016 12:14:00 -0400 [thread overview]
Message-ID: <20160421161400.GN7822@mtj.duckdns.org> (raw)
In-Reply-To: <CACT4Y+bXBZZxksEo_Zx1pRk1zpsb16UjUJY8=RK+2zoqjNj2=A@mail.gmail.com>
Hello,
On Thu, Apr 21, 2016 at 10:25:12AM +0200, Dmitry Vyukov wrote:
> I use this script for symbolization:
> https://github.com/google/sanitizers/blob/master/address-sanitizer/tools/kasan_symbolize.py
> It invokes addr2line to provide file:line info, adds inline frames,
> strips ? frames (are they ever useful?) and strips timestamps.
Heh, sometimes they are. They obviously are useful when backlinks are
broken for some reason. Through the remnants of the old call stacks,
they also can sometimes tell the history of the task - where it was
before it got to the current backtrace. It isn't reliable at all but
I can recall several occasions where they were useful in root causing
issues. It *might* make a sense to have an option to not strip them.
And, yeah, I'm all for it being in the kernel tree.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-04-21 16:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 9:44 fs: GPF in locked_inode_to_wb_and_lock_list Dmitry Vyukov
2016-04-20 21:14 ` Tejun Heo
2016-04-21 8:25 ` Dmitry Vyukov
2016-04-21 9:10 ` Andrey Ryabinin
2016-04-21 9:29 ` Dmitry Vyukov
2016-04-21 16:14 ` Tejun Heo [this message]
2016-04-21 8:35 ` Dmitry Vyukov
2016-04-21 9:45 ` Andrey Ryabinin
2016-04-21 10:00 ` Dmitry Vyukov
2016-04-21 17:06 ` Tejun Heo
2016-04-22 18:55 ` Dmitry Vyukov
2016-06-06 17:46 ` Dmitry Vyukov
2016-06-17 16:04 ` [PATCH] block: flush writeback dwork before detaching a bdev inode from it Tejun Heo
2016-06-20 13:31 ` Jan Kara
2016-06-20 13:38 ` Dmitry Vyukov
2016-06-20 17:40 ` Tejun Heo
2016-06-21 12:58 ` Dmitry Vyukov
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=20160421161400.GN7822@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=viro@zeniv.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).