From: jnf <xjnfx@doityourself.com>
To: Elias Athanasopoulos <eathan@otenet.gr>, jnf <xjnfx@doityourself.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: sock-ops->connect()
Date: Mon, 7 Oct 2002 03:51:45 -0700 (PDT) [thread overview]
Message-ID: <20021007105145.4061E3C3C@sitemail.everyone.net> (raw)
>I'm not very familiar with kernel internals, but I think you don't
>seem to allocate space for the sock structure.
>
its still failing even if i allocated space via (sock_alloc())
when i look through the source for sys_socket (/usr/src/linux/net/socket.c)
i see
...
// sock_create ...
retval = sock_map_fd(sock);
when i look through the source for sock_map_fd, it basically 'creates the file structure and maps it to fd space of the current process.'
which considering in the connect call i see sock->file->f_flags, which seems to make sense that i would want to use this i suppose, but i also got the impression that this was something done in a translation of sorts from user space to kernel land, but im already in kernel land, so im not really sure, and then not being able to find instances of it anywhere in my header files tells me maybe i dont?
But I am a tee bit confused and any help would be appreciated
again thanks
jnf
_____________________________________________________________
Sign up for FREE email from DoItYourself.com at http://doityourself.com
_____________________________________________________________
Select your own custom email address for FREE! Get you@yourchoice.com w/No Ads, 6MB, POP & more! http://www.everyone.net/selectmail?campaign=tag
next reply other threads:[~2002-10-07 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 10:51 jnf [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 10:15 sock-ops->connect() jnf
2002-10-06 14:36 ` sock-ops->connect() Elias Athanasopoulos
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=20021007105145.4061E3C3C@sitemail.everyone.net \
--to=xjnfx@doityourself.com \
--cc=eathan@otenet.gr \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).