linux-kernel - Re: FDDI on Linux kernel 2.6

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1161698520.22348.27.camel@localhost.localdomain>
Date:	Tue, 24 Oct 2006 15:02:00 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Wouter de Waal <wrm@...i.co.za>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: FDDI on Linux kernel 2.6

Ar Maw, 2006-10-24 am 13:19 +0200, ysgrifennodd Wouter de Waal:
> We here at CCII Systems are probably the only company in the world still
> actively involved with FDDI. The Linux Syskonnect FDDI driver needs a
> patch. I have no idea who to speak to, but the g over at osdl said I
> must ask here.

This is the right starting point. There is a network development list
that might be better but I think essentially you might as well own the
driver if nobody else is laying any claim to it any more. 

> The second customer's problem could not be solved by the above. They
> eventually found that kernel 2.6 (specifically, 2.6.8) uses memory
> mapping, and that a check in the driver caused an exception because
> of the length of the PCI region being 2048 and not 16384 (0x4000).
> The customer reports that changing the compare to
> 
> >if (len < 2048) {
> 
> fixed the problem for them.
> 
> Can this patch be applied to the kernel please?

I suspect the correct check is (len < FP_IO_LEN)

Either you or your customer can send patches versus a current kernel to
update the driver.

Alan

-
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/