From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: henry.snow@nielsen.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id d2c66032 for ; Thu, 10 May 2018 17:32:34 +0000 (UTC) Received: from mail-pl0-x22f.google.com (mail-pl0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id cf7afa16 for ; Thu, 10 May 2018 17:32:34 +0000 (UTC) Received: by mail-pl0-x22f.google.com with SMTP id e6-v6so1689381plt.11 for ; Thu, 10 May 2018 10:35:19 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Henry Snow Date: Thu, 10 May 2018 17:35:08 +0000 Message-ID: Subject: Re: wireguard-dkms and CentOS 7.5 To: "Jason A. Donenfeld" Content-Type: multipart/alternative; boundary="00000000000071225c056bdd71fd" Cc: "wireguard@lists.zx2c4.com" List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --00000000000071225c056bdd71fd Content-Type: text/plain; charset="UTF-8" Was able to pull a little more this time. This help? datasource: [ 29.570013] ------------[ cut here ]------------ [ 29.575937] kernel BUG at mm/slub.c:3601! [ 29.580741] invalid opcode: 0000 [#1] SMP [ 29.585663] Modules linked in: wireguard(OE) veth vxlan ip6_udp_tunnel udp_tunnel bridge sd [ 29.689129] CPU: 1 PID: 223 Comm: kworker/1:1 Tainted: G OE ------------ 3.101 [ 29.700019] Hardware name: Dell Inc. PowerEdge R640/0W23H8, BIOS 1.3.7 02/08/2018 [ 29.708399] Workqueue: wg-crypt-wg0 packet_rx_worker [wireguard] [ 29.715340] task: ffff920e8b608000 ti: ffff920e8b610000 task.ti: ffff920e8b610000 [ 29.723722] RIP: 0010:[] [] kfree+0x13c/0x140 [ 29.732222] RSP: 0018:ffff920e8b613ce8 EFLAGS: 00010246 [ 29.738429] RAX: 006fffff00000000 RBX: ffff920e76fbf000 RCX: 00000000fffbdd13 [ 29.746466] RDX: 006fffff00000000 RSI: 0000000000000206 RDI: ffff920e76fbf000 [ 29.754489] RBP: ffff920e8b613d00 R08: 0000000000000001 R09: b7c55a3205f72200 [ 29.762508] R10: 0000000000000000 R11: ffffeddddfdbefc0 R12: ffff920e76fbf6c0 [ 29.770525] R13: ffffffff8b5d60c5 R14: ffff920e80220000 R15: ffff920e7e7e2500 [ 29.778535] FS: 0000000000000000(0000) GS:ffff920e8be00000(0000) knlGS:0000000000000000 [ 29.787497] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 29.794125] CR2: 00007ffe415adee0 CR3: 0000000c0e1ea000 CR4: 00000000007607e0 [ 29.802143] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 29.810161] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 29.818152] PKRU: 00000000 [ 29.821713] Call Trace: [ 29.825002] [] skb_release_data+0xf5/0x140 [ 29.831595] [] skb_release_all+0x24/0x30 [ 29.838008] [] consume_skb+0x2c/0x90 [ 29.844073] [] packet_rx_worker+0x2d5/0x7f0 [wireguard] [ 29.851802] [] ? __schedule+0x41c/0xa20 [ 29.858139] [] process_one_work+0x17f/0x440 [ 29.864817] [] worker_thread+0x126/0x3c0 [ 29.871238] [] ? manage_workers.isra.24+0x2a0/0x2a0 [ 29.878612] [] kthread+0xd1/0xe0 [ 29.884338] [] ? insert_kthread_work+0x40/0x40 [ 29.891284] [] ret_from_fork_nospec_begin+0x7/0x21 [ 29.898578] [] ? insert_kthread_work+0x40/0x40 [ 29.905513] Code: 49 8b 03 31 f6 f6 c4 40 74 04 41 8b 73 68 4c 89 df e8 89 63 fa ff eb 84 [ 29.927746] RIP [] kfree+0x13c/0x140 [ 29.933888] RSP [ 29.938300] ---[ end trace 66811942e35f2cba ]--- # [ 29.948435] Kernel panic - not syncing: Fatal exception in interrupt On Thu, May 10, 2018 at 1:26 PM Jason A. Donenfeld wrote: > Yikes. I guess I need to examine my compat backport closely. Do you > have any more logging than that? Usually there's a backtrace. > -- Henry Snow | Director, Site Reliability Engineering eXelate, a Nielsen company E: henry.snow@nielsen.com | M: 347.366.2700 675 6th Ave, 3rd Floor, New York, NY 10010 --00000000000071225c056bdd71fd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Was able to pull a little more this time. This help?
<= br>
=C2=A0datasource:=C2=A0 =C2=A0 =C2=A0 [=C2=A0 =C2=A029.5= 70013] ------------[ cut here ]------------
[=C2=A0 =C2=A029.5759= 37] kernel BUG at mm/slub.c:3601!
[=C2=A0 =C2=A029.580741] invali= d opcode: 0000 [#1] SMP=C2=A0
[=C2=A0 =C2=A029.585663] Modules li= nked in: wireguard(OE) veth vxlan ip6_udp_tunnel udp_tunnel bridge sd
=
[=C2=A0 =C2=A029.689129] CPU: 1 PID: 223 Comm: kworker/1:1 Tainted: G= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0OE=C2=A0 ------------=C2=A0 =C2=A0= 3.101
[=C2=A0 =C2=A029.700019] Hardware name: Dell Inc. PowerEdge= R640/0W23H8, BIOS 1.3.7 02/08/2018
[=C2=A0 =C2=A029.708399] Work= queue: wg-crypt-wg0 packet_rx_worker [wireguard]
[=C2=A0 =C2=A029= .715340] task: ffff920e8b608000 ti: ffff920e8b610000 task.ti: ffff920e8b610= 000
[=C2=A0 =C2=A029.723722] RIP: 0010:[<ffffffff8b1f6c1c>]= =C2=A0 [<ffffffff8b1f6c1c>] kfree+0x13c/0x140
[=C2=A0 =C2= =A029.732222] RSP: 0018:ffff920e8b613ce8=C2=A0 EFLAGS: 00010246
[= =C2=A0 =C2=A029.738429] RAX: 006fffff00000000 RBX: ffff920e76fbf000 RCX: 00= 000000fffbdd13
[=C2=A0 =C2=A029.746466] RDX: 006fffff00000000 RSI= : 0000000000000206 RDI: ffff920e76fbf000
[=C2=A0 =C2=A029.754489]= RBP: ffff920e8b613d00 R08: 0000000000000001 R09: b7c55a3205f72200
[=C2=A0 =C2=A029.762508] R10: 0000000000000000 R11: ffffeddddfdbefc0 R12:= ffff920e76fbf6c0
[=C2=A0 =C2=A029.770525] R13: ffffffff8b5d60c5 = R14: ffff920e80220000 R15: ffff920e7e7e2500
[=C2=A0 =C2=A029.7785= 35] FS:=C2=A0 0000000000000000(0000) GS:ffff920e8be00000(0000) knlGS:000000= 0000000000
[=C2=A0 =C2=A029.787497] CS:=C2=A0 0010 DS: 0000 ES: 0= 000 CR0: 0000000080050033
[=C2=A0 =C2=A029.794125] CR2: 00007ffe4= 15adee0 CR3: 0000000c0e1ea000 CR4: 00000000007607e0
[=C2=A0 =C2= =A029.802143] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 000000000000= 0000
[=C2=A0 =C2=A029.810161] DR3: 0000000000000000 DR6: 00000000= fffe0ff0 DR7: 0000000000000400
[=C2=A0 =C2=A029.818152] PKRU: 000= 00000
[=C2=A0 =C2=A029.821713] Call Trace:
[=C2=A0 =C2= =A029.825002]=C2=A0 [<ffffffff8b5d60c5>] skb_release_data+0xf5/0x140<= /div>
[=C2=A0 =C2=A029.831595]=C2=A0 [<ffffffff8b5d6134>] skb_rel= ease_all+0x24/0x30
[=C2=A0 =C2=A029.838008]=C2=A0 [<ffffffff8b= 5d659c>] consume_skb+0x2c/0x90
[=C2=A0 =C2=A029.844073]=C2=A0 = [<ffffffffc088df35>] packet_rx_worker+0x2d5/0x7f0 [wireguard]
[=C2=A0 =C2=A029.851802]=C2=A0 [<ffffffff8b71291c>] ? __schedule+0= x41c/0xa20
[=C2=A0 =C2=A029.858139]=C2=A0 [<ffffffff8b0b2dff&g= t;] process_one_work+0x17f/0x440
[=C2=A0 =C2=A029.864817]=C2=A0 [= <ffffffff8b0b3ac6>] worker_thread+0x126/0x3c0
[=C2=A0 =C2= =A029.871238]=C2=A0 [<ffffffff8b0b39a0>] ? manage_workers.isra.24+0x2= a0/0x2a0
[=C2=A0 =C2=A029.878612]=C2=A0 [<ffffffff8b0bae31>= ] kthread+0xd1/0xe0
[=C2=A0 =C2=A029.884338]=C2=A0 [<ffffffff8= b0bad60>] ? insert_kthread_work+0x40/0x40
[=C2=A0 =C2=A029.891= 284]=C2=A0 [<ffffffff8b71f61d>] ret_from_fork_nospec_begin+0x7/0x21
[=C2=A0 =C2=A029.898578]=C2=A0 [<ffffffff8b0bad60>] ? insert= _kthread_work+0x40/0x40
[=C2=A0 =C2=A029.905513] Code: 49 8b 03 3= 1 f6 f6 c4 40 74 04 41 8b 73 68 4c 89 df e8 89 63 fa ff eb 84=C2=A0=C2=A0
[=C2=A0 =C2=A029.927746] RIP=C2=A0 [<ffffffff8b1f6c1c>] kfre= e+0x13c/0x140
[=C2=A0 =C2=A029.933888]=C2=A0 RSP <ffff920e8b61= 3ce8>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = [=C2=A0 =C2=A029.938300] ---[ end trace 66811942e35f2cba ]---
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 #
[=C2=A0 =C2=A029.948435] Kernel panic - no= t syncing: Fatal exception in interrupt

On Thu, May 10, 2018 at 1:26 P= M Jason A. Donenfeld <Jason@zx2c4.com= > wrote:
Yikes. I guess I ne= ed to examine my compat backport closely. Do you
have any more logging than that? Usually there's a backtrace.
--
Henry Snow | Director, Site R= eliability Engineering
eXelate, = a Nielsen company
E:=C2=A0= henry.snow@nielsen.com=C2=A0|=C2=A0M: 347.366.2700675 6= th Ave, 3rd Floor, New York, NY 10010=C2=A0
--00000000000071225c056bdd71fd--