From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] proc entry path name
Date: Sat, 16 Sep 2006 10:58:23 +0000 [thread overview]
Message-ID: <450BD8CF.2000008@bfs.de> (raw)
In-Reply-To: <1158320370.26510.62.camel@amol.verismonetworks.com>
hi all,
so far i understand the question was how to:
entry = create_proc_entry("alexey", 0644, NULL);
if (!entry) {
printk(KERN_ERR "foo: create_proc_entry >%s< failed\n",realpath);
}
KERN_ERR "foo: create_proc_entry >/proc/maintainers/janitor/alexey< failed
in very nested configurations (that you should not have) there may be more than
one alexey. and you end up with a knowledge that one of them failed.
something like getcwd() would be helpful.
re,
walter
Alexey Dobriyan wrote:
> On Fri, Sep 15, 2006 at 05:09:30PM +0530, Amol Lad wrote:
>> I'm doing create_proc_entry return code audit. On failure I would like
>> to print "Unable to create /proc/foo/bar".
>>
>> Is there a function that takes struct proc_dir_entry * and returns
>> fullpathname ?
>
> Me not understand why would you want it.
>
> entry = create_proc_entry("alexey", 0644, NULL);
> if (!entry) {
> printk(KERN_ERR "foo: create_proc_entry alexey failed\n");
> ...
> }
>
> Alexey #define KERN_ERR "" Dobriyan
>
> _______________________________________________
> Kernel-janitors mailing list
> Kernel-janitors@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/kernel-janitors
>
>
>
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2006-09-16 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 11:51 [KJ] proc entry path name Amol Lad
2006-09-15 23:42 ` Alexey Dobriyan
2006-09-16 10:58 ` walter harms [this message]
2006-09-18 13:39 ` steve
2006-09-19 6:18 ` Amol Lad
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=450BD8CF.2000008@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@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.