From: Alvin Starr <alvin@Iplink.net>
To: xen-devel@lists.xensource.com
Subject: Odd Xen Kernel module interaction
Date: Thu, 07 Feb 2008 14:12:20 -0500 [thread overview]
Message-ID: <47AB5814.5060803@Iplink.net> (raw)
In-Reply-To: <20080207144045.M84031@fastserv.com>
I have a network kernel module that I am trying to debug.
It is trying to query the file information for a socket that a userland
progrm has opened.
So it is accessing current->files and getting back 0x0(null).
This seems to work on a non xen kernel.
It has been quite a while since I have done any kernel hacking so I
would not be supprised if I am missing something obvious.
I believe the module is compiling correctly. It loads correctly and at
least some of the information pointed to by current-> is correct.
The calling application has got a bunch of file handles open so there
should be something in current->files.
Any help,pointers or even "you idiot look here" would be greatly
appreciated.
--
Alvin Starr || voice: (416)585-9971
Interlink Connectivity || fax: (416)585-9974
alvin@iplink.net ||
prev parent reply other threads:[~2008-02-07 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1JN2P3-000527-KW@host-192-168-0-1-bcn-london>
2008-02-07 14:41 ` 3ware I/O error Randy McAnally
2008-02-07 19:12 ` Alvin Starr [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=47AB5814.5060803@Iplink.net \
--to=alvin@iplink.net \
--cc=xen-devel@lists.xensource.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 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.