[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200708.101321.1049330296069021543.davem@davemloft.net>
Date: Wed, 08 Jul 2020 10:13:21 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: xie.he.0141@...il.com
Cc: kuba@...nel.org, hkallweit1@...il.com, snelson@...sando.io,
mhabets@...arflare.com, mst@...hat.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-x25@...r.kernel.org
Subject: Re: [PATCH] drivers/net/wan/x25_asy: Fix to make it work
From: Xie He <xie.he.0141@...il.com>
Date: Tue, 7 Jul 2020 21:37:54 -0700
> This driver is not working because of problems of its receiving code.
> This patch fixes it to make it work.
>
> When the driver receives an LAPB frame, it should first pass the frame
> to the LAPB module to process. After processing, the LAPB module passes
> the data (the packet) back to the driver, the driver should then add a
> one-byte pseudo header and pass the data to upper layers.
>
> The changes to the "x25_asy_bump" function and the
> "x25_asy_data_indication" function are to correctly implement this
> procedure.
>
> Also, the "x25_asy_unesc" function ignores any frame that is shorter
> than 3 bytes. However the shortest frames are 2-byte long. So we need
> to change it to allow 2-byte frames to pass.
>
> Signed-off-by: Xie He <xie.he.0141@...il.com>
Something's not right, because I find it hard to believe this has been
so fundamentally broken for such a long period of time.
Maybe the drivers all handle things differently, and whilst your change
might fix some drivers, it will break others.
I'm not applying this until this situation is better understood.
Powered by blists - more mailing lists