From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Irfan Ullah (울라 이르판) <irfan@dke.khu.ac.kr>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Getting netlink socket creation returns NULL in the kernel
Date: Wed, 16 Oct 2019 10:29:41 -0400 [thread overview]
Message-ID: <148442.1571236181@turing-police> (raw)
In-Reply-To: <CA+mB8OxW4zAHMY4qg_m0AzHc++jiyesNZLPAtsfMBz9XNRDJtg@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset=us-ascii, Size: 680 bytes --]
On Wed, 16 Oct 2019 13:54:08 +0900, Irfan Ullah said:
> developed kernel space, and user space programs. Kernel and user space
> programs working perfectly when I load and run these modules from the
> terminal using “sudo insmod kernelmodule.ko”, and “./userspaceApp”
> respectively. But, when I try to use kernel program (directly as a header
> file #include "kernelmodule.h") with the kernel original file that is
> “vmx.c” then it returns “NULL” while creating socket (nl_sk = NULL in nl_sk
You're going to have to explain in more detail what you're doing, and possibly
share your code. "when I try to use kernel program directly" doesn't make sense....
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-10-16 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 4:54 Getting netlink socket creation returns NULL in the kernel Irfan Ullah (울라 이르판)
2019-10-16 14:29 ` Valdis Klētnieks [this message]
2019-10-17 6:23 ` Irfan Ullah (울라 이르판)
2019-10-22 8:31 ` Irfan Ullah (울라 이르판)
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=148442.1571236181@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=irfan@dke.khu.ac.kr \
--cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).