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

[Chagin Dmitry]

On Tue, May 05, 2009 at 08:41:01PM +0400, Boris Samorodov wrote:
> 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:
> 
> > > 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.
> 

dchagin# ./ping ya.ru
WARNING: setsockopt(ICMP_FILTER): Protocol not available
WARNING: your kernel is veeery old. No problems.
PING ya.ru (213.180.204.8) 56(84) bytes of data.
ping: recvmsg: Invalid argument
ping: recvmsg: Invalid argument


So, more work nedeed. At least from 2.6.16 to 2.6.23 :)

-- 
Have fun!
chd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20090505/549f6d1e/attachment.pgp