Kernel panic on x86_64 machine running mainline 4.17.0 kernel while testing
selftests bpf test_tunnel.sh test caused this kernel panic.
I have noticed this kernel panic start happening from
4.17.0-rc7-next-20180529 and still happening on 4.17.0-next-20180608.
[ 213.638287] BUG: unable to handle kernel NULL pointer dereference
at 0000000000000008
++[ ip xfrm poli 213.674036] PGD 0 P4D 0
[ 213.674118] audit: type=1327 audit(1528917683.623:7):
proctitle=6970007866726D00706F6C69637900616464007372630031302E312E312E3130302F3332006473740031302E312E312E3230302F33320064697200696E00746D706C00737263003137322E31362E312E31303000647374003137322E31362E312E3230300070726F746F006573700072657169640031006D6F64650074756E6E
[ 213.677950] Oops: 0000 [#1] SMP PTI
cy[ add src 10.1. 213.677952] CPU: 2 PID: 0 Comm: swapper/2 Tainted:
G W 4.17.0-next-20180608 #1
[ 213.677953] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
2.0b 07/27/2017
[ 213.726998] RIP: 0010:__xfrm_policy_check+0xcb/0x690
[ 213.731962] Code: 80 3d 0a d8 f1 00 00 0f 84 c1 02 00 00 4c 8b 25
2b af f4 00 e8 66 a6 6a ff 85 c0 74 0d 80 3d eb d7 f1 00 00 0f 84 d5
02 00 00 <49> 8b 44 24 08 48 85 c0 74 0c 48 8d b5 78 ff ff ff 4c 89 ff
ff d0
1.[100/32 dst 10. 213.750836] RSP: 0018:ffff91cf6fd03a48 EFLAGS: 00010246
[ 213.757441] RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000002
[ 213.764566] RDX: ffffffffb863ebe0 RSI: 0000000000000000 RDI: 0000000000000000
[ 213.771688] RBP: ffff91cf6fd03b18 R08: ffffffffb863ebe0 R09: 0000000000000000
[ 213.778813] R10: ffff91cf6fd039d0 R11: 0000000000000000 R12: 0000000000000000
[ 213.785935] R13: ffff91cf5b23d84e R14: ffff91cf5b779f80 R15: ffff91cf5589cc00
[ 213.793062] FS: 0000000000000000(0000) GS:ffff91cf6fd00000(0000)
knlGS:0000000000000000
[ 213.801162] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 213.806900] CR2: 0000000000000008 CR3: 000000004201e001 CR4: 00000000003606e0
[ 213.814025] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 213.821200] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 213.828324] Call Trace:
[ 213.830769] <IRQ>
[ 213.832783] ? trace_hardirqs_on+0xd/0x10
[ 213.836819] __xfrm_policy_check2.constprop.36+0x6c/0xc0
[ 213.842131] tcp_v4_rcv+0x9ef/0xbd0
[ 213.845615] ? ip_local_deliver_finish+0x26/0x340
[ 213.850314] ip_local_deliver_finish+0xc1/0x340
[ 213.854843] ip_local_deliver+0x74/0x220
[ 213.858761] ? inet_del_offload+0x40/0x40
[ 213.862767] ip_rcv_finish+0x1f0/0x550
[ 213.866519] ip_rcv+0x282/0x480
[ 213.869657] ? ip_local_deliver_finish+0x340/0x340
[ 213.874448] __netif_receive_skb_core+0x3b2/0xd30
[ 213.879145] ? lock_acquire+0xd5/0x1c0
[ 213.882891] __netif_receive_skb+0x18/0x60
[ 213.886990] ? __netif_receive_skb+0x18/0x60
[ 213.891252] netif_receive_skb_internal+0x79/0x370
[ 213.896062] napi_gro_receive+0x138/0x1b0
[ 213.900121] igb_poll+0x610/0xe70
[ 213.903440] net_rx_action+0x246/0x4b0
[ 213.907190] ? lock_acquire+0xd5/0x1c0
[ 213.910933] ? igb_msix_ring+0x5e/0x70
[ 213.914681] __do_softirq+0xbf/0x493
[ 213.918260] irq_exit+0xc3/0xd0
[ 213.921405] do_IRQ+0x65/0x110
[ 213.924464] common_interrupt+0xf/0xf
[ 213.928128] </IRQ>
[ 213.930225] RIP: 0010:cpuidle_enter_state+0xa7/0x370
1.[1.200/32 dir i 213.935182] Code: 47 e8 bd 9a 7f ff 48 89 45 d0 0f
1f 44 00 00 31 ff e8 2d a9 7f ff 80 7d c7 00 0f 85 ee 01 00 00 e8 ae
9f 81 ff fb 48 8b 4d d0 <48> 2b 4d c8 48 ba cf f7 53 e3 a5 9b c4 20 48
89 c8 48 c1 f9 3f 48
[ 213.955445] RSP: 0018:ffffab2c01943e38 EFLAGS: 00000246 ORIG_RAX:
ffffffffffffffdc
[ 213.963002] RAX: ffff91cf6fd21ec0 RBX: 0000000000000002 RCX: 00000031bdd50c87
[ 213.970127] RDX: 00000031bdd50c87 RSI: 000000002aaaaaaa RDI: ffffffffb84ab752
[ 213.977250] RBP: ffffab2c01943e78 R08: 0000000000000061 R09: 0000000000000018
[ 213.984375] R10: ffffab2c01943e18 R11: 0000000000000092 R12: ffff91cf5ce88000
[ 213.991497] R13: ffffffffb94cf278 R14: 0000000000000002 R15: ffffffffb94cf260
[ 213.998624] ? cpuidle_enter_state+0xa2/0x370
[ 214.002982] ? cpuidle_enter_state+0xa2/0x370
[ 214.007332] cpuidle_enter+0x17/0x20
[ 214.010902] call_cpuidle+0x23/0x40
[ 214.014387] do_idle+0x1f0/0x250
[ 214.017613] cpu_startup_entry+0x73/0x80
[ 214.021538] start_secondary+0x175/0x1a0
[ 214.025465] secondary_startup_64+0xa5/0xb0
[ 214.029651] Modules linked in: cls_bpf xt_mark algif_hash af_alg
x86_pkg_temp_thermal fuse
[ 214.037941] CR2: 0000000000000008
[ 214.041255] ---[ end trace a0b077febc9b99ca ]---
[ 214.045874] RIP: 0010:__xfrm_policy_check+0xcb/0x690
n tmpl src 172.1[ 214.050838] Code: 80 3d 0a d8 f1 00 00 0f 84 c1 02
00 00 4c 8b 25 2b af f4 00 e8 66 a6 6a ff 85 c0 74 0d 80 3d eb d7 f1
00 00 0f 84 d5 02 00 00 <49> 8b 44 24 08 48 85 c0 74 0c 48 8d b5 78 ff
ff ff 4c 89 ff ff d0
[ 214.071103] RSP: 0018:ffff91cf6fd03a48 EFLAGS: 00010246
[ 214.076327] RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000002
[ 214.083451] RDX: ffffffffb863ebe0 RSI: 0000000000000000 RDI: 0000000000000000
[ 214.090574] RBP: ffff91cf6fd03b18 R08: ffffffffb863ebe0 R09: 0000000000000000
[ 214.097699] R10: ffff91cf6fd039d0 R11: 0000000000000000 R12: 0000000000000000
[ 214.104821] R13: ffff91cf5b23d84e R14: ffff91cf5b779f80 R15: ffff91cf5589cc00
[ 214.111945] FS: 0000000000000000(0000) GS:ffff91cf6fd00000(0000)
knlGS:0000000000000000
[ 214.120022] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 214.125760] CR2: 0000000000000008 CR3: 000000004201e001 CR4: 00000000003606e0
[ 214.132885] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 214.140009] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 214.147131] Kernel panic - not syncing: Fatal exception in interrupt
[ 214.153519] Kernel Offset: 0x36c00000 from 0xffffffff81000000
(relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 214.164292] ---[ end Kernel panic - not syncing: Fatal exception in
interrupt ]---
[ 214.171852] ------------[ cut here ]------------
Kconfigs on this kernel,
-------------------------------
CONFIG_XFRM=y
CONFIG_XFRM_ALGO=y
CONFIG_XFRM_USER=y
# CONFIG_XFRM_SUB_POLICY is not set
# CONFIG_XFRM_MIGRATE is not set
# CONFIG_XFRM_STATISTICS is not set
http://snapshots.linaro.org/openembedded/lkft/morty/intel-core2-32/rpb/linux-next/274/config
Test case source:
--------------------------
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/tools/testing/selftests/bpf/test_tunnel.sh#n565
steps to reproduce:
--------------------------
cd /tools/testing/selftests/bpf/
./test_tunnel.sh
Debugging shows it is coming from function
setup_xfrm_tunnel() {
<trim>
ip xfrm state add src 172.16.1.100 dst 172.16.1.200 proto esp spi 0x1 \
reqid 1 mode tunnel auth-trunc 'hmac(sha1)' \
0x1111111111111111111111111111111111111111 96 enc 'cbc(aes)' \
0x22222222222222222222222222222222
<trim>
}
Complete test log can be found in this location,
https://lkft.validation.linaro.org/scheduler/job/269604#L2092
Best regards
Naresh Kamboju
On Mon, Jun 11, 2018 at 10:11:46PM +0530, Naresh Kamboju wrote:
> Kernel panic on x86_64 machine running mainline 4.17.0 kernel while testing
> selftests bpf test_tunnel.sh test caused this kernel panic.
> I have noticed this kernel panic start happening from
> 4.17.0-rc7-next-20180529 and still happening on 4.17.0-next-20180608.
>
> [ 213.638287] BUG: unable to handle kernel NULL pointer dereference
> at 0000000000000008
> ++[ ip xfrm poli 213.674036] PGD 0 P4D 0
> [ 213.674118] audit: type=1327 audit(1528917683.623:7):
> proctitle=6970007866726D00706F6C69637900616464007372630031302E312E312E3130302F3332006473740031302E312E312E3230302F33320064697200696E00746D706C00737263003137322E31362E312E31303000647374003137322E31362E312E3230300070726F746F006573700072657169640031006D6F64650074756E6E
> [ 213.677950] Oops: 0000 [#1] SMP PTI
> cy[ add src 10.1. 213.677952] CPU: 2 PID: 0 Comm: swapper/2 Tainted:
> G W 4.17.0-next-20180608 #1
> [ 213.677953] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
> 2.0b 07/27/2017
> [ 213.726998] RIP: 0010:__xfrm_policy_check+0xcb/0x690
> [ 213.731962] Code: 80 3d 0a d8 f1 00 00 0f 84 c1 02 00 00 4c 8b 25
> 2b af f4 00 e8 66 a6 6a ff 85 c0 74 0d 80 3d eb d7 f1 00 00 0f 84 d5
> 02 00 00 <49> 8b 44 24 08 48 85 c0 74 0c 48 8d b5 78 ff ff ff 4c 89 ff
> ff d0
This looks like a bug that I've seen already. If it is what I think,
then commit 2c205dd3981f ("netfilter: add struct nf_nat_hook and use
it") introduced this bug.
There was already a fix for this on the netdev list, but
I don't know the current status of that patch:
https://patchwork.ozlabs.org/patch/921387/
On 12 June 2018 at 10:34, Steffen Klassert <[email protected]> wrote:
> On Mon, Jun 11, 2018 at 10:11:46PM +0530, Naresh Kamboju wrote:
>> Kernel panic on x86_64 machine running mainline 4.17.0 kernel while testing
>> selftests bpf test_tunnel.sh test caused this kernel panic.
>> I have noticed this kernel panic start happening from
>> 4.17.0-rc7-next-20180529 and still happening on 4.17.0-next-20180608.
>>
>> [ 213.638287] BUG: unable to handle kernel NULL pointer dereference
>> at 0000000000000008
>> ++[ ip xfrm poli 213.674036] PGD 0 P4D 0
>> [ 213.674118] audit: type=1327 audit(1528917683.623:7):
>> proctitle=6970007866726D00706F6C69637900616464007372630031302E312E312E3130302F3332006473740031302E312E312E3230302F33320064697200696E00746D706C00737263003137322E31362E312E31303000647374003137322E31362E312E3230300070726F746F006573700072657169640031006D6F64650074756E6E
>> [ 213.677950] Oops: 0000 [#1] SMP PTI
>> cy[ add src 10.1. 213.677952] CPU: 2 PID: 0 Comm: swapper/2 Tainted:
>> G W 4.17.0-next-20180608 #1
>> [ 213.677953] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
>> 2.0b 07/27/2017
>> [ 213.726998] RIP: 0010:__xfrm_policy_check+0xcb/0x690
>> [ 213.731962] Code: 80 3d 0a d8 f1 00 00 0f 84 c1 02 00 00 4c 8b 25
>> 2b af f4 00 e8 66 a6 6a ff 85 c0 74 0d 80 3d eb d7 f1 00 00 0f 84 d5
>> 02 00 00 <49> 8b 44 24 08 48 85 c0 74 0c 48 8d b5 78 ff ff ff 4c 89 ff
>> ff d0
>
> This looks like a bug that I've seen already. If it is what I think,
> then commit 2c205dd3981f ("netfilter: add struct nf_nat_hook and use
> it") introduced this bug.
>
> There was already a fix for this on the netdev list, but
> I don't know the current status of that patch:
>
> https://patchwork.ozlabs.org/patch/921387/
Hi, I applied the patch and ran bpf/test_tunnel.sh and I I couldn't
see any crash.
However, the script never returned (I had to Ctrl+c to get back), any ideas ?
See log from the test below.
Cheers,
Anders
Testing IPSec tunnel...
[ 269.060050] IPv6: ADDRCONF(NETDEV_UP): veth0: link is not ready
[ 269.090000] IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
<idle>-0 [000] ..s3 190.987095: 0: key 2 remote ip 0xac100164
ping-3043 [000] ..s3 190.988715: 0: key 2 remote ip 0xac100164
ksoftirqd/0-9 [000] ..s2 190.988986: 0: key 2 remote ip 0xac100164
systemd-resolve-2664 [003] ..s3 191.083771: 0: ERROR line:77 ret:-22
systemd-resolve-2664 [003] ..s3 191.333763: 0: ERROR line:77 ret:-22
kworker/0:1-33 [000] ..s4 191.419445: 0: key 2 remote ip 0xac100164
ping-3043 [000] ..s3 191.989437: 0: key 2 remote ip 0xac100164
kworker/0:1-33 [000] ..s4 192.443460: 0: key 2 remote ip 0xac100164
kworker/0:1-33 [000] ..s4 192.443508: 0: key 2 remote ip 0xac100164
<idle>-0 [000] ..s3 192.446318: 0: key 2 remote ip 0xac100164
systemd-resolve-2664 [000] ..s3 192.768767: 0: ERROR line:77 ret:-22
ping-3043 [000] ..s3 192.989902: 0: key 2 remote ip 0xac100164
ping-3044 [000] ..s3 193.025776: 0: key 2 remote ip 0xac100164
systemd-resolve-2664 [000] ..s3 193.083650: 0: ERROR line:77 ret:-22
systemd-resolve-2664 [000] ..s3 193.333865: 0: ERROR line:77 ret:-22
ping-3044 [000] ..s3 194.026240: 0: key 2 remote ip 0xac100164
ping-3044 [000] ..s3 195.026707: 0: key 2 remote ip 0xac100164
ksoftirqd/2-21 [002] ..s2 198.075583: 0: key 2 remote ip6
::11000000 label bcdef
ksoftirqd/2-21 [002] ..s2 198.075597: 0: key 2 remot[
269.270883] audit: type=1415 audit(1532018021.150:6): op=SAD-add
auid=0 ses=2 subj=kerne
l src=172.16.1.100 dst=172.16.1.200 spi=1(0x1) res=1
[ 269.284308] audit: type=1300 audit(1532018021.150:6): arch=c000003e
syscall=46 success=yes exit=424 a0=4 a1=7ffff18d1ba0 a2=0 a3=5e9
items=0 ppid=2924
pid=4333 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0
fsgid=0 tty=pts0 ses=2 comm=\"ip\" exe=\"/sbin/ip.iproute2\"
subj=kernel key=(null)
[ 269.310249] audit: type=1327 audit(1532018021.150:6):
proctitle=6970007866726D0073746174650061646400737263003137322E31362E312E31303000647374003137322E
31362E312E3230300070726F746F0065737000737069003078310072657169640031006D6F64650074756E6E656C00617574682D7472756E6300686D616328736861312900307831313131313
13131313131313131
e ip6 ::11000000 label bcdef
ping-3164 [003] ..s3 198.113160: 0: key 2 remote ip6
::11000000 label bcdef
ping-3164 [003] ..s3 199.113661: 0: key 2 remote ip6
::11000000 label bcdef
<idle>-0 [000] ..s3 199.931430: 0: key 2 remote ip6
::11000000 label bcdef
ping-3164 [003] ..s3 200.114432: 0: key 2 remote ip6
::11000000 label bcdef
ping-3[ 269.374987] audit: type=1415
audit(1532018021.373:7): op=SPD-add auid=0 ses=2 subj=kernel res=1
src=10.1.1.100 dst=10.1.1.200
165 [002] ..s3 [ 269.386787] audit: type=1300
audit(1532018021.373:7): arch=c000003e syscall=46 success=yes exit=252
a0=4 a1=7ffe1e400ff0 a2=0 a3=5e9 i
tems=0 ppid=2924 pid=4354 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0
egid=0 sgid=0 fsgid=0 tty=pts0 ses=2 comm=\"ip\"
exe=\"/sbin/ip.iproute2\" subj=kernel
key=(null)
[ 269.414124] audit: type=1327 audit(1532018021.373:7):
proctitle=6970007866726D00706F6C69637900616464007372630031302E312E312E3130302F333200647374003130
2E312E312E3230302F333200646972006F757400746D706C00737263003137322E31362E312E31303000647374003137322E31362E312E3230300070726F746F0065737000726571696400310
06D6F64650074756E
200.133573: 0: key 2 remote ip6 ::11000000 label bcdef
ping-3165 [002] ..s3 201.134091: 0: key 2 remote ip6
::11000000 label bcdef
ping-3165 [002] ..s3 202.134600: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3167 [000] ..s3 202.172808: 0: key 2 remote ip6
::11000000 label bcdef
[ 269.471306] audit: type=1415 audit(1532018021.470:8): op=SAD-add
auid=0 ses=2 subj=kernel src=172.16.1.200 dst=172.16.1.100 spi=2(0x2)
res=1
[ 269.484439] audit: type=1300 audit(1532018021.470:8): arch=c000003e
syscall=46 success=yes exit=424 a0=4 a1=7ffc79931450 a2=0 a3=5e9
items=0 ppid=2924
pid=4355 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0
fsgid=0 tty=pts0 ses=2 comm=\"ip\" exe=\"/sbin/ip.iproute2\"
subj=kernel key=(null)
[ 269.510375] audit: type=1327 audit(1532018021.470:8):
proctitle=6970007866726D0073746174650061646400737263003137322E31362E312E32303000647374003137322E
31362E312E3130300070726F746F0065737000737069003078320072657169640032006D6F64650074756E6E656C00617574682D7472756E6300686D616328736861312900307831313131313
13131313131313131
ping6-3167 [000] ..s3 203.173251: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3167 [000] ..s3 204.173741: 0: key 2 remote ip6
::11000000 label bcdef
systemd-resolve-2664 [001] ..s3 205.333801: 0: ERROR line:119 ret:-22
systemd-resolve-2664 [001] ..s3 205.583819: 0: ERROR line:119 ret:-22
systemd-resolve-2664 [001] ..s3 205.833437: 0: E[ 269.572155]
audit: type=1415 audit(1532018021.571:9): op=SPD-add auid=0 ses=2
subj=kernel res=1 sr
c=10.1.1.200 dst=10.1.1.100
RROR line:119 ret:-22
systemd-resolve-2664 [001] ..s3 206.583819: 0: ERROR line:119 ret:-22
systemd-resolve-2664 [003] ..s3 206.782769: 0: ERROR line:119 ret:-22
kworker/3:2-1537 [003] ..s4 207.035785: 0: key 2 remote ip6
::11000000 label bcdef
kworker/3:2-1537 [003] ..s4 207.035796: 0: key 2 remote ip6
::11000000 label bcdef
kworker/3:2-1537 [003] ..s4 207.035890: 0: key 2 remote ip6
::11000000 label bcdef
kworker/3:2-1537 [003] ..s4 207.035926: 0: key 2 remote ip6
::11000000 label bcdef
systemd-resolve-2664 [000] ..s3 207.083608: 0: ERROR line:119 ret:-22
ksoftirqd/3-26 [003] ..s2 207.739454: 0: key 2 remote ip6
::11000000 label bcdef
ping-3298 [000] ..s3 208.263120: 0: key 2 remote ip6
::11000000 label bcdef
ping-3298 [000] ..s3 208.263224: 0: key 2 remote ip6
::11000000 label bcdef
ping-3298 [000] ..s3 209.263703: 0: key 2 remote ip6
::11000000 label bcdef
ping-3298 [000] ..s3 210.264203: 0: key 2 remote ip6
::11000000 label bcdef
ping-3299 [002] ..s3 210.279710: 0: key 2 remote ip6
::11000000 label bcdef
<idle>-0 [003] ..s3 210.875420: 0: key 2 remote ip6
::11000000 label bcdef
ping-3299 [002] ..s3 211.280241: 0: key 2 remote ip6
::11000000 label bcdef
ksoftirqd/3-26 [003] ..s2 212.219559: 0: key 2 remote ip6
::11000000 label bcdef
ping-3299 [002] ..s3 212.280741: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 212.315807: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 213.316255: 0: key 2 remote ip6
::11000000 label bcdef
<idle>-0 [000] ..s3 213.755462: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 214.316506: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 215.316951: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 216.317320: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 217.317765: 0: key 2 remote ip6
::11000000 label bcdef
ksoftirqd/3-26 [003] ..s2 217.339464: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 218.318227: 0: key 2 remote ip6
::11000000 label bcdef
ksoftirqd/3-26 [003] ..s2 218.875455: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 219.318671: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 220.319141: 0: key 2 remote ip6
::11000000 label bcdef
ping6-3300 [002] ..s3 221.319585: 0: key 2 remote ip6
::11000000 label bcdef
ping-3419 [002] ..s3 223.036234: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3419 [002] ..s3 223.036236: 0: direction 1
hwid 3 timestamp 31402699
ping-3419 [002] ..s3 223.036256: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3419 [002] ..s3 223.036256: 0: direction 1
hwid 3 timestamp 31402699
<idle>-0 [000] ..s3 223.067438: 0: key 2 remote ip
0xac100164 erspan version 2
<idle>-0 [000] ..s3 223.067443: 0: direction 1
hwid 3 timestamp 31403010
systemd-resolve-2664 [000] ..s3 223.083837: 0: ERROR line:183 ret:-22
kworker/0:1-33 [000] ..s4 223.283447: 0: key 2 remote ip
0xac100164 erspan version 2
kworker/0:1-33 [000] ..s4 223.283452: 0: direction 1
hwid 3 timestamp 31405171
systemd-resolve-2664 [000] ..s3 223.333807: 0: ERROR line:183 ret:-22
systemd-resolve-2664 [000] ..s3 223.583816: 0: ERROR line:183 ret:-22
ping-3419 [002] ..s3 224.036713: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3419 [002] ..s3 224.036718: 0: direction 1
hwid 3 timestamp 31412704
kworker/0:1-33 [000] ..s4 224.315459: 0: key 2 remote ip
0xac100164 erspan version 2
kworker/0:1-33 [000] ..s4 224.315464: 0: direction 1
hwid 3 timestamp 31415491
kworker/0:1-33 [000] ..s4 224.315514: 0: key 2 remote ip
0xac100164 erspan version 2
kworker/0:1-33 [000] ..s4 224.315516: 0: direction 1
hwid 3 timestamp 31415492
<idle>-0 [000] ..s3 224.675428: 0: key 2 remote ip
0xac100164 erspan version 2
<idle>-0 [000] ..s3 224.675433: 0: direction 1
hwid 3 timestamp 31419090
ping-3419 [002] ..s3 225.036920: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3419 [002] ..s3 225.036925: 0: direction 1
hwid 3 timestamp 31422706
ping-3420 [003] ..s3 225.064293: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3420 [003] ..s3 225.064298: 0: direction 1
hwid 3 timestamp 31422979
systemd-resolve-2664 [000] ..s3 225.083664: 0: ERROR line:183 ret:-22
systemd-resolve-2664 [000] ..s3 225.333742: 0: ERROR line:183 ret:-22
systemd-resolve-2664 [000] ..s3 225.583778: 0: ERROR line:183 ret:-22
ping-3420 [003] ..s3 226.064761: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3420 [003] ..s3 226.064765: 0: direction 1
hwid 3 timestamp 31432984
ping-3420 [003] ..s3 227.065237: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3420 [003] ..s3 227.065242: 0: direction 1
hwid 3 timestamp 31442989
systemd-resolve-2664 [003] ..s3 228.186369: 0: ERROR line:269 ret:-22
systemd-resolve-2664 [003] ..s3 228.333716: 0: ERROR line:269 ret:-22
systemd-resolve-2664 [003] ..s3 228.583747: 0: ERROR line:269 ret:-22
systemd-resolve-2664 [001] ..s3 229.833537: 0: ERROR line:269 ret:-22
kworker/0:1-33 [000] ..s4 229.947659: 0: ip6erspan get key 2
remote ip6 ::0 erspan version 2
kworker/0:1-33 [000] ..s4 229.947664: 0: direction 1
hwid 7 timestamp 31471811
kworker/0:1-33 [000] ..s4 229.947708: 0: ip6erspan get key 2
remote ip6 ::0 erspan version 2
kworker/0:1-33 [000] ..s4 229.947711: 0: direction 1
hwid 7 timestamp 31471814
systemd-resolve-2664 [001] ..s3 230.083782: 0: ERROR line:269 ret:-22
systemd-resolve-2664 [001] ..s3 230.333523: 0: ERROR line:269 ret:-22
<idle>-0 [000] ..s3 230.779419: 0: ip6erspan get key 2
remote ip6 ::0 erspan version 2
<idle>-0 [000] ..s3 230.779424: 0: direction 1
hwid 7 timestamp 31480130
ping-3540 [003] ..s3 231.091633: 0: ip6erspan get key 2
remote ip6 ::0 erspan version 2
ping-3540 [003] ..s3 231.091638: 0: direction 1
hwid 7 timestamp 31483253
ping-3540 [003] ..s3 231.091737: 0: ip6erspan get key 2
remote ip6 ::0 erspan version 2
ping-3540 [003] ..s3 231.091739: 0: direction 1
hwid 7 timestamp 31483254
ping-3540 [003] ..s3 232.092227: 0: ip6erspan get key 2
remote ip6 ::0 erspan version 2
ping-3540 [003] ..s3 232.092232: 0: direction 1
hwid 7 timestamp 31493259
ping-3540 [003] ..s3 233.092737: 0: ip6erspan get key 2
remote ip6 ::0 erspan version 2
ping-3540 [003] ..s3 233.092742: 0: direction 1
hwid 7 timestamp 31503264
ping-3655 [000] ..s3 233.957186: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
systemd-resolve-2664 [001] ..s3 234.065463: 0: ERROR line:339 ret:-22
<idle>-0 [000] ..s3 234.171427: 0: key 2 remote ip
0xac100164 vxlan gbp 0x94
kworker/0:1-33 [000] ..s4 234.235502: 0: ERROR line:345 ret:-2
systemd-resolve-2664 [001] ..s3 234.333813: 0: ERROR line:339 ret:-22
systemd-resolve-2664 [001] ..s3 234.583761: 0: ERROR line:339 ret:-22
ping-3655 [000] ..s3 234.957640: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
kworker/0:1-33 [000] ..s4 235.259475: 0: key 2 remote ip
0xac100164 vxlan gbp 0x94
kworker/0:1-33 [000] ..s4 235.259528: 0: ERROR line:345 ret:-2
systemd-resolve-2664 [001] ..s3 235.752142: 0: ERROR line:339 ret:-22
ping-3655 [000] ..s3 235.958144: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
<idle>-0 [000] ..s3 235.963159: 0: key 2 remote ip
0xac100164 vxlan gbp 0x94
ping-3663 [002] ..s3 235.990422: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
systemd-resolve-2664 [001] ..s3 236.083782: 0: ERROR line:339 ret:-22
systemd-resolve-2664 [001] ..s3 236.333591: 0: ERROR line:339 ret:-22
ping-3663 [002] ..s3 236.990900: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
ping-3663 [002] ..s3 237.991370: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
systemd-resolve-2664 [002] ..s3 239.083778: 0: ERROR line:387 ret:-22
systemd-resolve-2664 [002] ..s3 239.333765: 0: ERROR line:387 ret:-22
systemd-resolve-2664 [002] ..s3 239.583765: 0: ERROR line:387 ret:-22
systemd-resolve-2664 [001] ..s3 240.194218: 0: ERROR line:387 ret:-22
systemd-resolve-2664 [001] ..s3 240.333718: 0: ERROR line:387 ret:-22
systemd-resolve-2664 [001] ..s3 240.583708: 0: ERROR line:387 ret:-22
<idle>-0 [002] ..s3 240.955492: 0: key 22 remote ip6
::11000000 label 0
<idle>-0 [002] ..s3 240.955505: 0: key 22 remote ip6
::11000000 label 0
<idle>-0 [002] ..s3 240.955512: 0: key 22 remote ip6
::11000000 label 0
<idle>-0 [002] ..s3 240.955518: 0: key 22 remote ip6
::11000000 label 0
<idle>-0 [002] ..s3 240.955524: 0: key 22 remote ip6
::11000000 label 0
<idle>-0 [002] ..s3 241.211432: 0: key 22 remote ip6
::11000000 label 0
ksoftirqd/1-16 [001] ..s2 242.012579: 0: key 22 remote ip6
::11000000 label 0
ksoftirqd/1-16 [001] ..s2 242.026381: 0: key 22 remote ip6
::11000000 label 0
ksoftirqd/3-26 [003] ..s2 243.028099: 0: key 22 remote ip6
::11000000 label 0
ksoftirqd/3-26 [003] ..s2 244.040809: 0: key 22 remote ip6
::11000000 label 0
ping-3774 [001] ..s3 244.062314: 0: key 22 remote ip6
::11000000 label 0
<idle>-0 [002] ..s3 244.219413: 0: key 22 remote ip6
::11000000 label 0
ping-3774 [001] ..s3 245.075208: 0: key 22 remote ip6
::11000000 label 0
ping-3774 [001] ..s3 246.088218: 0: key 22 remote ip6
::11000000 label 0
ping-3887 [002] ..s3 246.831153: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3887 [002] ..s3 246.831226: 0: key 2 remote ip
0xac100164 geneve class 0x0
systemd-resolve-2664 [003] ..s3 246.963398: 0: ERROR line:445 ret:-22
systemd-resolve-2664 [003] ..s3 247.083859: 0: ERROR line:445 ret:-22
systemd-resolve-2664 [003] ..s3 247.333815: 0: ERROR line:445 ret:-22
kworker/1:2-1480 [001] ..s4 247.355451: 0: key 2 remote ip
0xac100164 geneve class 0x0
<idle>-0 [001] ..s3 247.419431: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3887 [002] ..s3 247.831692: 0: key 2 remote ip
0xac100164 geneve class 0x0
kworker/1:2-1480 [001] ..s4 248.379561: 0: key 2 remote ip
0xac100164 geneve class 0x0
kworker/1:2-1480 [001] ..s4 248.379605: 0: key 2 remote ip
0xac100164 geneve class 0x0
systemd-resolve-2664 [001] ..s3 248.440767: 0: ERROR line:445 ret:-22
<idle>-0 [001] ..s3 248.459429: 0: key 2 remote ip
0xac100164 geneve class 0x0
systemd-resolve-2664 [001] ..s3 248.583784: 0: ERROR line:445 ret:-22
ping-3887 [002] ..s3 248.832187: 0: key 2 remote ip
0xac100164 geneve class 0x0
systemd-resolve-2664 [001] ..s3 248.833517: 0: ERROR line:445 ret:-22
ping-3888 [000] ..s3 248.874871: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3888 [000] ..s3 249.875339: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3888 [000] ..s3 250.875805: 0: key 2 remote ip
0xac100164 geneve class 0x0
systemd-resolve-2664 [003] ..s3 252.032344: 0: ERROR line:509 ret:-22
systemd-resolve-2664 [003] ..s3 252.333767: 0: ERROR line:509 ret:-22
systemd-resolve-2664 [003] ..s3 252.583766: 0: ERROR line:509 ret:-22
kworker/0:1-33 [000] ..s4 253.627615: 0: key 22 remote ip
0x0 geneve class 0x0
kworker/0:1-33 [000] ..s4 253.627634: 0: key 22 remote ip
0x0 geneve class 0x0
kworker/0:1-33 [000] ..s4 253.627766: 0: key 22 remote ip
0x0 geneve class 0x0
kworker/0:1-33 [000] ..s4 253.627797: 0: key 22 remote ip
0x0 geneve class 0x0
kworker/0:1-33 [000] ..s4 253.627833: 0: key 22 remote ip
0x0 geneve class 0x0
ping-3997 [001] ..s3 253.915594: 0: key 22 remote ip
0x0 geneve class 0x0
ping-3998 [002] ..s3 253.946604: 0: key 22 remote ip
0x0 geneve class 0x0
systemd-resolve-2664 [002] ..s3 253.956160: 0: ERROR line:509 ret:-22
systemd-resolve-2664 [002] ..s3 254.083777: 0: ERROR line:509 ret:-22
<idle>-0 [000] ..s3 254.331437: 0: key 22 remote ip
0x0 geneve class 0x0
systemd-resolve-2664 [002] ..s3 254.333628: 0: ERROR line:509 ret:-22
ping-3998 [002] ..s3 254.947116: 0: key 22 remote ip
0x0 geneve class 0x0
ping-3998 [001] ..s3 255.947392: 0: key 22 remote ip
0x0 geneve class 0x0
ping-4118 [002] ..s3 256.654930: 0: remote ip 0xac100164
ping-4118 [002] ..s3 257.655393: 0: remote ip 0xac100164
ping-4118 [002] ..s3 258.655851: 0: remote ip 0xac100164
ping-4119 [000] ..s3 258.695970: 0: remote ip 0xac100164
ping-4119 [000] ..s3 259.696426: 0: remote ip 0xac100164
ping-4119 [000] ..s3 260.696886: 0: remote ip 0xac100164
ping-4231 [002] ..s3 264.713834: 0: remote ip6 0::11
ping-4231 [002] ..s3 265.714327: 0: remote ip6 0::11
<idle>-0 [002] ..s3 265.979423: 0: remote ip6 0::11
ping-4231 [002] ..s3 266.714822: 0: remote ip6 0::11
ping-4239 [001] ..s3 266.748758: 0: remote ip6 0::11
ping-4239 [001] ..s3 267.749244: 0: remote ip6 0::11
ping-4239 [001] ..s3 268.749737: 0: remote ip6 0::11
ping-4367 [003] ..s3 270.047776: 0: reqid 1 spi 0x1
remote ip 0xac100164
ksoftirqd/3-26 [003] ..s2 271.048427: 0: reqid 1 spi 0x1
remote ip 0xac100164
PING 10.1.1.200 (10.1.1.200): 56 data bytes
--- 10.1.1.200 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.263/0.370/0.579 ms
ping-4367 [003] ..s3 272.048870: 0: reqid 1 spi 0x1
remote ip 0xac100164
ping-4367 [003] ..s3 270.047776: 0: reqid 1 spi 0x1
remote ip 0xac100164
ksoftirqd/3-26 [003] ..s2 271.048427: 0: reqid 1 spi 0x1
remote ip 0xac100164
ping-4367 [003] ..s3 272.048870: 0: reqid 1 spi 0x1
remote ip 0xac100164
ping-4367 [003] ..s3 270.047776: 0: reqid 1 spi 0x1
remote ip 0xac100164
ksoftirqd/3-26 [003] ..s2 271.048427: 0: reqid 1 spi 0x1
remote ip 0xac100164
ping-4367 [003] ..s3 272.048870: 0: reqid 1 spi 0x1
remote ip 0xac100164
<idle>-0 [000] ..s3 190.987095: 0: key 2 remote ip 0xac100164
ping-3043 [000] ..s3 190.988715: 0: key 2 remote ip 0xac100164
ksoftirqd/0-9 [000] ..s2 190.988986: 0: key 2 remote ip 0xac100164
kworker/0:1-33 [000] ..s4 191.419445: 0: key 2 remote ip 0xac100164
ping-3043 [000] ..s3 191.989437: 0: key 2 remote ip 0xac100164
kworker/0:1-33 [000] ..s4 192.443460: 0: key 2 remote ip 0xac100164
kworker/0:1-33 [000] ..s4 192.443508: 0: key 2 remote ip 0xac100164
<idle>-0 [000] ..s3 192.446318: 0: key 2 remote ip 0xac100164
ping-3043 [000] ..s3 192.989902: 0: key 2 remote ip 0xac100164
ping-3044 [000] ..s3 193.025776: 0: key 2 remote ip 0xac100164
ping-3044 [000] ..s3 194.026240: 0: key 2 remote ip 0xac100164
ping-3044 [000] ..s3 195.026707: 0: key 2 remote ip 0xac100164
ping-3419 [002] ..s3 223.036234: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3419 [002] ..s3 223.036256: 0: key 2 remote ip
0xac100164 erspan version 2
<idle>-0 [000] ..s3 223.067438: 0: key 2 remote ip
0xac100164 erspan version 2
kworker/0:1-33 [000] ..s4 223.283447: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3419 [002] ..s3 224.036713: 0: key 2 remote ip
0xac100164 erspan version 2
kworker/0:1-33 [000] ..s4 224.315459: 0: key 2 remote ip
0xac100164 erspan version 2
kworker/0:1-33 [000] ..s4 224.315514: 0: key 2 remote ip
0xac100164 erspan version 2
<idle>-0 [000] ..s3 224.675428: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3419 [002] ..s3 225.036920: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3420 [003] ..s3 225.064293: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3420 [003] ..s3 226.064761: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3420 [003] ..s3 227.065237: 0: key 2 remote ip
0xac100164 erspan version 2
ping-3655 [000] ..s3 233.957186: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
<idle>-0 [000] ..s3 234.171427: 0: key 2 remote ip
0xac100164 vxlan gbp 0x94
ping-3655 [000] ..s3 234.957640: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
kworker/0:1-33 [000] ..s4 235.259475: 0: key 2 remote ip
0xac100164 vxlan gbp 0x94
ping-3655 [000] ..s3 235.958144: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
<idle>-0 [000] ..s3 235.963159: 0: key 2 remote ip
0xac100164 vxlan gbp 0x94
ping-3663 [002] ..s3 235.990422: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
ping-3663 [002] ..s3 236.990900: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
ping-3663 [002] ..s3 237.991370: 0: key 2 remote ip
0xac100164 vxlan gbp 0x800ff
ping-3887 [002] ..s3 246.831153: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3887 [002] ..s3 246.831226: 0: key 2 remote ip
0xac100164 geneve class 0x0
kworker/1:2-1480 [001] ..s4 247.355451: 0: key 2 remote ip
0xac100164 geneve class 0x0
<idle>-0 [001] ..s3 247.419431: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3887 [002] ..s3 247.831692: 0: key 2 remote ip
0xac100164 geneve class 0x0
kworker/1:2-1480 [001] ..s4 248.379561: 0: key 2 remote ip
0xac100164 geneve class 0x0
kworker/1:2-1480 [001] ..s4 248.379605: 0: key 2 remote ip
0xac100164 geneve class 0x0
<idle>-0 [001] ..s3 248.459429: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3887 [002] ..s3 248.832187: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3888 [000] ..s3 248.874871: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3888 [000] ..s3 249.875339: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-3888 [000] ..s3 250.875805: 0: key 2 remote ip
0xac100164 geneve class 0x0
ping-4118 [002] ..s3 256.654930: 0: remote ip 0xac100164
ping-4118 [002] ..s3 257.655393: 0: remote ip 0xac100164
ping-4118 [002] ..s3 258.655851: 0: remote ip 0xac100164
ping-4119 [000] ..s3 258.695970: 0: remote ip 0xac100164
ping-4119 [000] ..s3 259.696426: 0: remote ip 0xac100164
ping-4119 [000] ..s3 260.696886: 0: remote ip 0xac100164
ping-4367 [003] ..s3 270.047776: 0: reqid 1 spi 0x1
remote ip 0xac100164
ksoftirqd/3-26 [003] ..s2 271.048427: 0: reqid 1 spi 0x1
remote ip 0xac100164
ping-4367 [003] ..s3 272.048870: 0: reqid 1 spi 0x1
remote ip 0xac100164
[0;92mPASS: xfrm tunnel[0m
On Tue, Jun 12, 2018 at 5:09 AM, Anders Roxell <[email protected]> wrote:
> On 12 June 2018 at 10:34, Steffen Klassert <[email protected]> wrote:
>> On Mon, Jun 11, 2018 at 10:11:46PM +0530, Naresh Kamboju wrote:
>>> Kernel panic on x86_64 machine running mainline 4.17.0 kernel while testing
>>> selftests bpf test_tunnel.sh test caused this kernel panic.
>>> I have noticed this kernel panic start happening from
>>> 4.17.0-rc7-next-20180529 and still happening on 4.17.0-next-20180608.
>>>
>>> [ 213.638287] BUG: unable to handle kernel NULL pointer dereference
>>> at 0000000000000008
>>> ++[ ip xfrm poli 213.674036] PGD 0 P4D 0
>>> [ 213.674118] audit: type=1327 audit(1528917683.623:7):
>>> proctitle=6970007866726D00706F6C69637900616464007372630031302E312E312E3130302F3332006473740031302E312E312E3230302F33320064697200696E00746D706C00737263003137322E31362E312E31303000647374003137322E31362E312E3230300070726F746F006573700072657169640031006D6F64650074756E6E
>>> [ 213.677950] Oops: 0000 [#1] SMP PTI
>>> cy[ add src 10.1. 213.677952] CPU: 2 PID: 0 Comm: swapper/2 Tainted:
>>> G W 4.17.0-next-20180608 #1
>>> [ 213.677953] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
>>> 2.0b 07/27/2017
>>> [ 213.726998] RIP: 0010:__xfrm_policy_check+0xcb/0x690
>>> [ 213.731962] Code: 80 3d 0a d8 f1 00 00 0f 84 c1 02 00 00 4c 8b 25
>>> 2b af f4 00 e8 66 a6 6a ff 85 c0 74 0d 80 3d eb d7 f1 00 00 0f 84 d5
>>> 02 00 00 <49> 8b 44 24 08 48 85 c0 74 0c 48 8d b5 78 ff ff ff 4c 89 ff
>>> ff d0
>>
>> This looks like a bug that I've seen already. If it is what I think,
>> then commit 2c205dd3981f ("netfilter: add struct nf_nat_hook and use
>> it") introduced this bug.
>>
>> There was already a fix for this on the netdev list, but
>> I don't know the current status of that patch:
>>
>> https://patchwork.ozlabs.org/patch/921387/
>
> Hi, I applied the patch and ran bpf/test_tunnel.sh and I I couldn't
> see any crash.
> However, the script never returned (I had to Ctrl+c to get back), any ideas ?
> See log from the test below.
>
> Cheers,
> Anders
>
> [0;92mPASS: xfrm tunnel[0m
Hi Anders,
I think it should return 0 if you reach the above line.
The console output looks pretty messy due to using 'tee'
I will send a patch to make the output more readable.
Thanks
William
On 14 June 2018 at 13:15, William Tu <[email protected]> wrote:
> On Tue, Jun 12, 2018 at 5:09 AM, Anders Roxell <[email protected]> wrote:
>> On 12 June 2018 at 10:34, Steffen Klassert <[email protected]> wrote:
>>> On Mon, Jun 11, 2018 at 10:11:46PM +0530, Naresh Kamboju wrote:
>>>> Kernel panic on x86_64 machine running mainline 4.17.0 kernel while testing
>>>> selftests bpf test_tunnel.sh test caused this kernel panic.
>>>> I have noticed this kernel panic start happening from
>>>> 4.17.0-rc7-next-20180529 and still happening on 4.17.0-next-20180608.
>>>>
>>>> [ 213.638287] BUG: unable to handle kernel NULL pointer dereference
>>>> at 0000000000000008
>>>> ++[ ip xfrm poli 213.674036] PGD 0 P4D 0
>>>> [ 213.674118] audit: type=1327 audit(1528917683.623:7):
>>>> proctitle=6970007866726D00706F6C69637900616464007372630031302E312E312E3130302F3332006473740031302E312E312E3230302F33320064697200696E00746D706C00737263003137322E31362E312E31303000647374003137322E31362E312E3230300070726F746F006573700072657169640031006D6F64650074756E6E
>>>> [ 213.677950] Oops: 0000 [#1] SMP PTI
>>>> cy[ add src 10.1. 213.677952] CPU: 2 PID: 0 Comm: swapper/2 Tainted:
>>>> G W 4.17.0-next-20180608 #1
>>>> [ 213.677953] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
>>>> 2.0b 07/27/2017
>>>> [ 213.726998] RIP: 0010:__xfrm_policy_check+0xcb/0x690
>>>> [ 213.731962] Code: 80 3d 0a d8 f1 00 00 0f 84 c1 02 00 00 4c 8b 25
>>>> 2b af f4 00 e8 66 a6 6a ff 85 c0 74 0d 80 3d eb d7 f1 00 00 0f 84 d5
>>>> 02 00 00 <49> 8b 44 24 08 48 85 c0 74 0c 48 8d b5 78 ff ff ff 4c 89 ff
>>>> ff d0
>>>
>>> This looks like a bug that I've seen already. If it is what I think,
>>> then commit 2c205dd3981f ("netfilter: add struct nf_nat_hook and use
>>> it") introduced this bug.
>>>
>>> There was already a fix for this on the netdev list, but
>>> I don't know the current status of that patch:
>>>
>>> https://patchwork.ozlabs.org/patch/921387/
>>
>> Hi, I applied the patch and ran bpf/test_tunnel.sh and I I couldn't
>> see any crash.
>> However, the script never returned (I had to Ctrl+c to get back), any ideas ?
>> See log from the test below.
>>
>> Cheers,
>> Anders
>>
>> [0;92mPASS: xfrm tunnel[0m
>
> Hi Anders,
> I think it should return 0 if you reach the above line.
Yes it should but it didn't.
However, when I reran the test_tunnel.sh today with kernel next-20180613
I got back from from the script and the test passed "PASS: xfrm tunnel".
So I'm not sure what happened before. =/
> The console output looks pretty messy due to using 'tee'
> I will send a patch to make the output more readable.
Great.
Cheers,
Anders