From: "Denis V. Lunev" <den@sw.ru>
To: kernel coder <lhrkernelcoder@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cann't dump info to user file from kernel
Date: Tue, 02 Oct 2007 11:38:05 +0400 [thread overview]
Message-ID: <4701F55D.7040908@sw.ru> (raw)
In-Reply-To: <f69849430710020028l64379652q77e3c9428ef4de79@mail.gmail.com>
This will never work, as you call blocking (non-atomic) functions from
atomic context.
kernel coder wrote:
> hi,
> I'm trying to dump some information from dev.c to user space
> file.Following is the code which i'm using to write to user spcae
> file.I'm using 2.6.22.x86_64 kernel.
>
>
> #define _write(f, buf, sz) (f->f_op->write(f, buf, sz, &f->f_pos))
> #define WRITABLE(f) (f->f_op && f->f_op->write)
>
> int write_to_file(char *logfile, char *buf,int size)
> {
> int ret = 0;
> struct file *f=NULL;
> mm_segment_t old_fs = get_fs();
> set_fs(get_ds());
> f = filp_open(logfile, O_CREAT|O_APPEND,00600);
> if(IS_ERR(f)){
> DPRINT("Error %ld openeing %s\n",-PTR_ERR(f), logfile);
> ret = -1;
> } else {
> if (WRITABLE(f))
> _write(f, buf, size);
> else {
> DPRINT("%s does not have a write method\n",
> logfile);
> ret = -1;
> }
>
> if ((ret = filp_close(f,NULL)))
> DPRINT("Error %d closing %s\n", -ret, logfile);
> }
> END_KMEM;
>
> return ret;
> }
>
>
> I'm calling this function from netif_recieve_skb in dev.c
>
> int netif_recieve_skb(struct sk_buff *skb){
>
> ---------------------
> write_to_file("/root/kernel_log","hello_world",12);
> ----------------------
>
> }
>
> But whenever this function is called ,the kernel simply halts.Please
> tell me what might be the reason.
>
> I just want to dump some information to user spcace file from dev.c
> .Is there some better way to do it.
use something like ipt_LOG or packet sockets
prev parent reply other threads:[~2007-10-02 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 7:28 cann't dump info to user file from kernel kernel coder
2007-10-02 7:38 ` Denis V. Lunev [this message]
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=4701F55D.7040908@sw.ru \
--to=den@sw.ru \
--cc=lhrkernelcoder@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox