linux-kernel - sun neptune driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <200802191453.35210.omar@crs4.it>
Date:	Tue, 19 Feb 2008 14:53:35 +0100
From:	Omar Schiaratura <omar@...4.it>
To:	linux-kernel@...r.kernel.org
Subject: sun neptune driver

Hi all,
i'm trying to write a back-porting of the Sun neptune NIC driver(niu module) in kernel 2.6.24 to the kernel 2.6.20
because i need that driver in a xen linux environment.
The driver now compile and goes up clearly, NIC is configured, but doesn't work properly.
If i send packets to another machine with the same NIC and kernel 2.6.24,I saw with tcpdump that the packets was received and the answer was sent,
but at the other end (kernel 2.6.20 with my backported driver, and without XEN) nothing appens (tcpdump report sent packages, but i can't see anything sent from other side)
Do you have some tricks for me or can you suggest me something to do?

Some of the problem i encountered during port is that i can't find a function equivalent to compound_head, and if i port it to the source i can't find a way to use
an equivalent variable like page->first_page found in compound_head.
another proble was the folowing function:

static inline unsigned char *skb_transport_header(const struct sk_buff *skb)
{
        return (unsigned char *)((unsigned int)skb->head + (unsigned int)skb->h.raw);
}

that get the error: "error: invalid operands to binary +"
if i can't cast it in unsigned int, the same in skb_network_header (both back-ported from include/skbuff.h)

thanks,
Omar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/