From: Tejun Heo <tj@kernel.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
chavey@google.com, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] vfs: make fcheck_files() an exported functions
Date: Tue, 12 Feb 2013 09:41:52 -0800 [thread overview]
Message-ID: <20130212174152.GH7348@htj.dyndns.org> (raw)
In-Reply-To: <20130210001811.GH4503@ZenIV.linux.org.uk>
Hey, Al.
On Sun, Feb 10, 2013 at 12:18:12AM +0000, Al Viro wrote:
> > Andrew, can you please pick up these two patches? They were posted a
> > month ago and at least nobody seems violently against them. The
> > original patches are,
>
> Consider *any* tracepoints in that area blanketly NAKed. Sorry, I thought
> I made it clear, but just in case:
Heh, this is the first time I hear about it.
> As far as I'm concerned, *the* *only* interface stability warranties in VFS
> are those for syscalls. Which means that no tracepoints are going to be
> acceptable there. End of story.
I see, it's about API stability. This TP is expected to be used by
internal tracer to approxmiately match generated IOs to specific
files, so at least the proposed usage is inside the kernel. I suppose
there's no way to mark TPs internal, Steven?
Anyways, I haven't looked at the tracer code for a while, and am not
sure whether the information can be acquired differently. Will take
another look.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-02-12 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 17:01 [PATCH 1/2] vfs: make fcheck_files() an exported functions Tejun Heo
2013-01-09 17:01 ` [PATCH 2/2] vfs: add fcheck tracepoint Tejun Heo
2013-02-09 19:24 ` [PATCH 1/2] vfs: make fcheck_files() an exported functions Tejun Heo
2013-02-10 0:18 ` Al Viro
2013-02-12 17:41 ` Tejun Heo [this message]
2013-02-12 18:21 ` Steven Rostedt
2013-02-12 20:21 ` Steven Rostedt
2013-02-12 20:44 ` Al Viro
2013-02-12 20:57 ` Steven Rostedt
2013-02-12 20:43 ` Al Viro
2013-02-12 21:03 ` Steven Rostedt
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=20130212174152.GH7348@htj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chavey@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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).