linux-um archives
 help / color / mirror / Atom feed
From: Patrick Kilian <petschge@gmx.de>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>,
	user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [uml-user] UNIX socket networking
Date: Sun, 7 Mar 2004 12:56:18 +0100	[thread overview]
Message-ID: <200403071256.18134.petschge@gmx.de> (raw)
In-Reply-To: <200403071228.15509.blaisorblade_spam@yahoo.it>

Hi all,

> You refer to bind in the guest, right? Well, you call the
> socket->ops->bind, while you should probably at least call sys_bind.
Ok. I'll give it a try.

> Your kernel thread is simply a process running in kernel mode - so
> instead of calling bind(), you just call sys_bind() skipping some
> useless code (int 0x80, userspace/kernelspace transition and so on).
> But you cannot, in general, skip anything else unless you have a
> reason to do so.
I didn't know what the exact difference between bind(), sys_bind() and 
sockert->ops->bind() was.

> Probably, the same reasoning applies to a lot of other code - why
> sock_create instead of sys_socket, why sock_recvmsg  ... and so on.
> Please, at least change both sys_socket and sys_bind before asking
> again.
Ok the next version will be updated.

> I *do not* understand how ENOENT is actually returned, but probably
> something that normally fails for a missing file failed for the lack
> of coherency.
Yeah that could be the reason.

>> Most of the above code should probably be edited with rm
> What is that? Indentation cleanup?
rm as in "man 1 rm". 

>> , but you wanted to have my results so far. Now go and find a brown
>> paper bag.
> No, do not - seeing the code is very useful indeed.
If you say so...
I'll give you sugestions a try and be back in some days with Yet Another 
Version of my code.

mfg,
Patrick "Petschge" Kilian


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-03-07 12:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200402290158.54770.jdizzl@xs4all.nl>
     [not found] ` <20040229120513.934193BCB7@home.petschge.de>
     [not found]   ` <200402291720.12216.blaisorblade_spam@yahoo.it>
2004-02-29 17:13     ` [uml-devel] Re: [uml-user] UNIX socket networking Patrick Kilian
2004-03-01 20:14       ` Patrick "Petschge" Kilian
2004-03-02 18:09         ` BlaisorBlade
2004-03-02 21:40           ` Patrick Kilian
2004-03-07 10:54             ` Patrick "Petschge" Kilian
2004-03-08 21:33               ` Jeff Dike
2004-03-07 11:28             ` BlaisorBlade
2004-03-07 11:56               ` Patrick Kilian [this message]
2004-03-07 12:12                 ` BlaisorBlade
2004-03-07 13:06                   ` [uml-devel] " Patrick Kilian

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=200403071256.18134.petschge@gmx.de \
    --to=petschge@gmx.de \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=petschge@web.de \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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