From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/17688] probe nfs.fop.aio_read no longer valid
Date: Mon, 08 Dec 2014 21:57:00 -0000 [thread overview]
Message-ID: <bug-17688-6586-qb0iJy7wgY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17688-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17688
--- Comment #1 from David Smith <dsmith at redhat dot com> ---
It looks like kernel commit edaf43694898c5d7deb9a394335c60e888039100 does the
same thing for nfs_file_write():
<https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/fs/nfs/file.c?id=edaf43694898c5d7deb9a394335c60e888039100>
Similar changes to nfs_file_read() will be needed for nfs_file_write().
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-12-08 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 21:53 [Bug tapsets/17688] New: " dsmith at redhat dot com
2014-12-08 21:57 ` dsmith at redhat dot com [this message]
2014-12-16 16:58 ` [Bug tapsets/17688] " 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-17688-6586-qb0iJy7wgY@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).