From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/16991] infinite loop in task_dentry_path
Date: Wed, 28 May 2014 14:35:00 -0000 [thread overview]
Message-ID: <bug-16991-6586-23VclJViDJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16991-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16991
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
Created attachment 7619
--> https://sourceware.org/bugzilla/attachment.cgi?id=7619&action=edit
potential patch
Here's a potential patch, which includes a test case. The good news about this
patch is that it seems to fix the problem. When task_dentry_path() now hits a
dentry from a pipe filesystem, it returns something like:
pipe:[105988]
The only problem that I know of with this patch is the requirement of the
'buffer' argument to the new __dentry_generate_dname() function. It is a bit
ugly, but the only other potential solution I can think of (embedding that
temporary buffer in the context structure) is even uglier.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-05-28 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 13:46 [Bug tapsets/16991] New: " dsmith at redhat dot com
2014-05-28 14:35 ` dsmith at redhat dot com [this message]
2014-05-28 15:58 ` [Bug tapsets/16991] " dsmith at redhat dot com
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=bug-16991-6586-23VclJViDJ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).