Christian Hohnstaedt wrote:
>
> However the scatterlist iteration in the arm implementation of
> dma_map_sg() uses neither of them, but simply sg++
>
> Please try the attached compile-tested patch.
The chaining is only allowed within the crypto layer (because
we haven't ported the generic chaini
Christian Hohnstaedt wrote:
>
>
> looks like there are different, incompatible sg chaining implementations:
>
> include/crypto/scatterwalk.h:scatterwalk_sg_chain() uses
> sg->lenght == 0 as indicator for a chained sg
>
> include/linux/scatterlist.h:sg_chain() uses
> bit 0 of sg->page_link to indic
On Wed, Feb 25, 2009 at 10:36:11AM +0100, Karl Hiramoto wrote:
> Christian Hohnstaedt wrote:
> > On Tue, Feb 24, 2009 at 02:19:54PM +0100, Karl Hiramoto wrote:
> >
> >> [42949542.25] count_sg:758 len=0 sg_is_last(sg)=0
> >> [42949542.26] kernel BUG at lib/scatterlist.c:26!
> >> [42949542
Christian Hohnstaedt wrote:
> On Tue, Feb 24, 2009 at 02:19:54PM +0100, Karl Hiramoto wrote:
>
>> The latest thing i found is kernel BUG at lib/scatterlist.c:26!
>>
>> ping -s 1800 host in a IPSec tunnel. Setup is 802.1Q VLAN -->
>> ixp4xx_eth --> IPSec Tunnel
>>
>> trace with some d
On Tue, Feb 24, 2009 at 02:19:54PM +0100, Karl Hiramoto wrote:
> The latest thing i found is kernel BUG at lib/scatterlist.c:26!
>
> ping -s 1800 host in a IPSec tunnel. Setup is 802.1Q VLAN -->
> ixp4xx_eth --> IPSec Tunnel
>
> trace with some debug printk's i added.printk("%s:%
The latest thing i found is kernel BUG at lib/scatterlist.c:26!
ping -s 1800 host in a IPSec tunnel. Setup is 802.1Q VLAN -->
ixp4xx_eth --> IPSec Tunnel
trace with some debug printk's i added.printk("%s:%d
values",__func__, __LINE__);
[42949542.17] esp_output:142 skb->le
