From: Chris Friesen <chris.friesen@genband.com>
To: Ben Myers <bpm@sgi.com>, Alex Elder <elder@kernel.org>, xfs@oss.sgi.com
Subject: given a pointer to xfs_inode_t, how to determine path?
Date: Mon, 17 Sep 2012 09:51:37 -0600 [thread overview]
Message-ID: <50574709.9000301@genband.com> (raw)
Hi,
We're running 2.6.27 (upgrading not currently possible, embedded product).
We had a situation arise where we could see in stack traces that a
number of tasks were stuck in vn_iowait(). That function takes a
pointer to xfs_inode_t. Given that, would it be possible to work
backwards to determine a filesystem path corresponding to that inode? I
realize it would likely only go back to the head of the filesystem, but
that would be fine.
Thanks,
Chris
--
Chris Friesen
Software Designer
3500 Carling Avenue
Ottawa, Ontario K2H 8E9
www.genband.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-09-17 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 15:51 Chris Friesen [this message]
2012-09-17 16:21 ` given a pointer to xfs_inode_t, how to determine path? Ben Myers
2012-09-17 22:49 ` Dave Chinner
2012-09-19 15:15 ` Ben Myers
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=50574709.9000301@genband.com \
--to=chris.friesen@genband.com \
--cc=bpm@sgi.com \
--cc=elder@kernel.org \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.