mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: gregkh <gregkh@linuxfoundation.org>
To: Jianpeng Ma <majianpeng@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: About function __create_file  in debugfs
Date: Sat, 8 Sep 2012 08:25:33 -0700	[thread overview]
Message-ID: <20120908152533.GB1838@kroah.com> (raw)
In-Reply-To: <201209081741013286843@gmail.com>

On Sat, Sep 08, 2012 at 05:41:05PM +0800, Jianpeng Ma wrote:
> 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.

Patches are always welcome :)

greg k-h

  reply	other threads:[~2012-09-08 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08  9:41 Jianpeng Ma
2012-09-08 15:25 ` gregkh [this message]
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=20120908152533.GB1838@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=majianpeng@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome