[linux-f10] linux_socketcall... ERR#43 'Protocol not supported'

[Boris Samorodov]

On Tue, 5 May 2009 20:07:24 +0400 Chagin Dmitry wrote:
> On Tue, May 05, 2009 at 07:26:28PM +0400, Boris Samorodov wrote:

> > The diff is:
> > -----
> > --- linux_socket.c.orig	2009-05-05 18:35:31.000000000 +0400
> > +++ linux_socket.c	2009-05-05 19:02:42.000000000 +0400
> > @@ -595,9 +595,15 @@
> >  	} */ bsd_args;
> >  	int retval_socket;
> >  
> > +	printf("bsam: linux_socket (LINUX): domain: %d, type: %d, protocol: %d\n",
> > +		args->domain, args->type, args->protocol);
> > +
> >  	bsd_args.protocol = args->protocol;
> >  	bsd_args.type = args->type;
> >  	bsd_args.domain = linux_to_bsd_domain(args->domain);
> > +
> > +	printf("bsam: linux_socket (FreeBSD): domain: %d\n", bsd_args.domain);
> > +
> >  	if (bsd_args.domain == -1)
> >  		return (EINVAL);
> >  
> > @@ -1365,10 +1371,14 @@
> >  linux_socketcall(struct thread *td, struct linux_socketcall_args *args)
> >  {
> >  	void *arg = (void *)(intptr_t)args->args;
> > +	int ret;
> >  
> > +	printf("bsam: Entering linux_socketcall.\n");
> >  	switch (args->what) {
> >  	case LINUX_SOCKET:
> > -		return (linux_socket(td, arg));
> > +		ret = linux_socket(td, arg);
> > +		printf("bsam: LINUX_SOCKET: %d\n", ret);
> > +		return (ret);
> >  	case LINUX_BIND:
> >  		return (linux_bind(td, arg));
> >  	case LINUX_CONNECT:
> > -----
> > 
> > Console diagnistic is:
> > -----
> > May  5 19:10:33 bb kernel: bsam: Entering linux_socketcall.
> > May  5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 3, protocol: 1
> > May  5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 2
> > May  5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 1
> > May  5 19:10:33 bb kernel: bsam: Entering linux_socketcall.
> > May  5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 1, type: 526337, protocol: 0
> > May  5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 1
> > May  5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 43
> > May  5 19:10:33 bb kernel: bsam: Entering linux_socketcall.
> > May  5 19:10:33 bb kernel: bsam: linux_socket (LINUX): domain: 1, type: 526337, protocol: 0
> > May  5 19:10:33 bb kernel: bsam: linux_socket (FreeBSD): domain: 1
> > May  5 19:10:33 bb kernel: bsam: LINUX_SOCKET: 43
> > May  5 19:10:34 bb kernel: bsam: Entering linux_socketcall.
> > May  5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0
> > May  5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2
> > May  5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43
> > May  5 19:10:34 bb kernel: bsam: Entering linux_socketcall.
> > May  5 19:10:34 bb kernel: bsam: linux_socket (LINUX): domain: 2, type: 2050, protocol: 0
> > May  5 19:10:34 bb kernel: bsam: linux_socket (FreeBSD): domain: 2
> > May  5 19:10:34 bb kernel: bsam: LINUX_SOCKET: 43
> > -----
> > 
> > Corresponding text for linux_kdump and truss:
> > ftp://ftp.ipt.ru/pub/linux/linux_kdump.ping.txt
> > ftp://ftp.ipt.ru/pub/linux/truss.ping.txt
> > 

> heh, it seems to me that SOCK_CLOEXEC, SOCK_NONBLOCK bits used.
> should be fixed. socketpair() also uses it since 2.6.29

I'll be glad to test patches.


WBR
-- 
Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve