netdev - Re: [PATCH net-next] wan: dlci/sdla transmit return dehacking

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]

Date:	Fri, 4 Sep 2009 19:38:10 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Krzysztof Halasa <khc@...waw.pl>
Cc:	David Miller <davem@...emloft.net>, sfr@...b.auug.org.au,
	linux-next@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] wan: dlci/sdla transmit return dehacking

On Fri, 04 Sep 2009 20:48:50 +0200
Krzysztof Halasa <khc@...waw.pl> wrote:

> Stephen Hemminger <shemminger@...tta.com> writes:
> 
> > This is a brute force removal of the wierd slave interface done for
> > DLCI -> SDLA transmit. Before it was using non-standard return values
> > and freeing skb in caller. This changes it to using normal return
> > values, and freeing in the callee. Luckly only one driver pair was
> > doing this. Not tested on real hardware, in fact I wonder if this
> > driver pair is even being used by any users.
> 
> The only hardware which seems to be driven by dlci.c is sdla.c =
> old Sangoma ISA cards.
> 
> Sangoma seems to maintain their own drivers for their hw (including
> these ISA cards).
> 
> Are the in-kernel drivers functional after all those years? I don't
> know.

In the Vyatta product we use the Sangoma drivers, so we actually have
to make and not configure in the existing WAN drivers.



-- 
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html