From: "Jianpeng Ma" <majianpeng@gmail.com>
To: gregkh <gregkh@linuxfoundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: About function __create_file in debugfs
Date: Sat, 8 Sep 2012 17:41:05 +0800 [thread overview]
Message-ID: <201209081741013286843@gmail.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 1211 bytes --]
Hi:
At present,i used blktrace to trace block io.But i always met error, the message like:
>BLKTRACESETUP(2) /dev/sdc failed: 2/No such file or directory
>Thread 0 failed open /sys/kernel/debug/block/(null)/trace0: 2/No such file or directory
>Thread 2 failed open /sys/kernel/debug/block/(null)/trace2: 2/No such file or directory
>Thread 3 failed open /sys/kernel/debug/block/(null)/trace3: 2/No such file or directory
>Thread 1 failed open /sys/kernel/debug/block/(null)/trace1: 2/No such file or directory
>FAILED to start thread on CPU 0: 1/Operation not permitted
>FAILED to start thread on CPU 1: 1/Operation not permitted
>FAILED to start thread on CPU 2: 1/Operation not permitted
>FAILED to start thread on CPU 3: 1/Operation not permitted
But those isn't important. I add some message in kernel and found the reason is inode already existed.
But the function __create_file dosen't return correctly errno.So blktrace tool can't print correctly message.
I think func __create_file should return correctly message(ERR_PTR(error)) not NULL.
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2012-09-08 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 9:41 Jianpeng Ma [this message]
2012-09-08 15:25 ` About function __create_file in debugfs gregkh
2012-09-10 11:49 ` Jianpeng Ma
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=201209081741013286843@gmail.com \
--to=majianpeng@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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 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.