[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c4d0f291-ef92-3166-2da6-b461a7403da6@seti.kr.ua>
Date: Wed, 6 Feb 2019 01:09:47 +0200
From: Andrew <nitr0@...i.kr.ua>
To: Netdev <netdev@...r.kernel.org>
Subject: Re: Kernel panic in eth_header
Thanks. At least, IPv4 tests passed (IPv4 overlapped - fails at first
time, but passes on next times; on IPv6 I've got 'send_fragment:
operation not permitted', I didn't look deeply because I don't use
IPv6). No KASAN warnings in dmesg.
On 05.02.2019 22:28, Eric Dumazet wrote:
>
> On 02/05/2019 12:21 PM, Andrew wrote:
>
>> I think that backport will be trivial - at least patch lays smoothly on 4.9 (just with offsets difference).
>>
>> I'll test it.
>>
>> Btw, maybe there's a some test conditions to quickly check if patch helps? Crash is reproducible with unpredictable interval (tens of hours of quite heavy load).
>>
> Build your kernel with CONFIG_KASAN=y
>
> Then run the tests Peter wrote.
>
> 4c3510483d26420d2c2c7cc075ad872286cc5932 selftests: net: ip_defrag: cover new IPv6 defrag behavior
> 3271a4821882a64214acc1bd7b173900ec70c9bf selftests: net: fix/improve ip_defrag selftest
> bccc17118bcf3c62c947361d51760334f6602f43 selftests/net: add ipv6 tests to ip_defrag selftest
> 02c7f38b7ace9f1b2ddb7a88139127eef4cf8706 selftests/net: add ip_defrag selftest
>
>
Powered by blists - more mailing lists