From: Julian Wollrath <jwollrath@web.de>
To: netdev@vger.kernel.org
Subject: Kernel v5.2-rc4 trace involving nf_conntrack
Date: Tue, 11 Jun 2019 11:32:51 +0200 [thread overview]
Message-ID: <20190611113251.2e3feffe@schienar> (raw)
Hi,
I got the following trace on v5.2-rc4 involving nf_conntrack:
[ 143.193245] general protection fault: 0000 [#1] SMP PTI
[ 143.193264] CPU: 3 PID: 201 Comm: kworker/3:2 Tainted: G W 5.2.0-rc4 #1
[ 143.193271] Hardware name: FUJITSU LIFEBOOK U747/FJNB2A5, BIOS Version 1.17 09/11/2017
[ 143.193292] Workqueue: events_power_efficient gc_worker [nf_conntrack]
[ 143.193316] RIP: 0010:nf_ct_helper_destroy+0x21/0x40 [nf_conntrack]
[ 143.193327] Code: 50 ff ff ff 0f 1f 44 00 00 48 8b 87 b8 00 00 00 48 85 c0 74 24 0f b6 50 10 84 d2 74 1d 4
4 0e <48> 8b 40 68 48 85 c0 74 05 e8 a1 b9 d9 e5 c3 c3 c3 66 66 2e 0f 1f
[ 143.193335] RSP: 0018:ffffaa9780e9bdc0 EFLAGS: 00010286
[ 143.193344] RAX: ff89bb1b62090000 RBX: ffffffffa66ae200 RCX: 0000000000000000
[ 143.193350] RDX: 00000000000000ff RSI: 0000000000000000 RDI: ffff89bb492b0000
[ 143.193356] RBP: 0000000000000000 R08: 0000000000000010 R09: 0000746e65696369
[ 143.193362] R10: 8080808080808080 R11: 0000000000000018 R12: 0000000000004900
[ 143.193367] R13: ffff89bb492b0000 R14: ffffffffc0471c54 R15: 0000000000000002
[ 143.193376] FS: 0000000000000000(0000) GS:ffff89bb5dd80000(0000) knlGS:0000000000000000
[ 143.193382] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 143.193388] CR2: 00007fc6558b2008 CR3: 00000001b9c0a003 CR4: 00000000003606e0
[ 143.193394] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 143.193400] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 143.193404] Call Trace:
[ 143.193425] nf_ct_delete_from_lists+0x1d/0x140 [nf_conntrack]
[ 143.193441] ? __switch_to_asm+0x40/0x70
[ 143.193451] ? __switch_to_asm+0x34/0x70
[ 143.193466] nf_ct_delete+0x68/0x160 [nf_conntrack]
[ 143.193477] ? __switch_to_asm+0x34/0x70
[ 143.193491] nf_ct_gc_expired+0x64/0x80 [nf_conntrack]
[ 143.193506] gc_worker+0x24e/0x2e0 [nf_conntrack]
[ 143.193525] process_one_work+0x1f5/0x3f0
[ 143.193539] ? process_one_work+0x3f0/0x3f0
[ 143.193551] worker_thread+0x28/0x3c0
[ 143.193564] ? process_one_work+0x3f0/0x3f0
[ 143.193574] kthread+0x111/0x130
[ 143.193586] ? kthread_create_worker_on_cpu+0x60/0x60
[ 143.193596] ret_from_fork+0x35/0x40
[ 143.193605] Modules linked in: kafs dns_resolver fcrypt pcbc rxrpc arc4 snd_hda_codec_hdmi iwlmvm snd_hda_
_generic btrtl btbcm mac80211 btintel bluetooth nft_counter iwlwifi uvcvideo videobuf2_vmalloc intel_rapl vid
l videobuf2_v4l2 intel_powerclamp nft_limit videodev coretemp i915 drbg snd_hda_intel videobuf2_common snd_us
t snd_usbmidi_lib snd_hda_core snd_hwdep ansi_cprng drm_kms_helper snd_pcm snd_rawmidi syscopyarea snd_timer
snd soundcore serio_raw cfg80211 sysimgblt ecdh_generic ecc fb_sys_fops rfkill crc16 drm idma64 wmi battery b
ag_ipv6 nf_defrag_ipv4 tpm_crb tpm fujitsu_laptop sparse_keymap video acpi_pad ac nf_tables_set nf_tables nfn
her af_alg hid_generic usbhid hid dm_crypt dm_mod sd_mod crct10dif_pclmul i2c_designware_platform i2c_designw
l
[ 143.193713] ghash_clmulni_intel e1000e psmouse sdhci_pci ptp cqhci pps_core sdhci i2c_i801 mmc_core ahci
scsi_mod usbcore intel_lpss_pci intel_lpss usb_common
[ 143.193753] ---[ end trace 473de765b5682889 ]---
[ 143.193772] RIP: 0010:nf_ct_helper_destroy+0x21/0x40 [nf_conntrack]
[ 143.193782] Code: 50 ff ff ff 0f 1f 44 00 00 48 8b 87 b8 00 00 00 48 85 c0 74 24 0f b6 50 10 84 d2 74 1d 48 01 d0 74 17 48 8b 00 48 85 c0 74 0e <48> 8b 40 68 48 85 c0 74 05 e8 a1 b9 d9 e5 c3 c3 c3 66 66 2e 0f 1f
[ 143.193789] RSP: 0018:ffffaa9780e9bdc0 EFLAGS: 00010286
[ 143.193796] RAX: ff89bb1b62090000 RBX: ffffffffa66ae200 RCX: 0000000000000000
[ 143.193801] RDX: 00000000000000ff RSI: 0000000000000000 RDI: ffff89bb492b0000
[ 143.193807] RBP: 0000000000000000 R08: 0000000000000010 R09: 0000746e65696369
[ 143.193812] R10: 8080808080808080 R11: 0000000000000018 R12: 0000000000004900
[ 143.193817] R13: ffff89bb492b0000 R14: ffffffffc0471c54 R15: 0000000000000002
[ 143.193825] FS: 0000000000000000(0000) GS:ffff89bb5dd80000(0000) knlGS:0000000000000000
[ 143.193831] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 143.193837] CR2: 00007fc6558b2008 CR3: 00000001b9c0a003 CR4: 00000000003606e0
[ 143.193842] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 143.193847] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Best regards,
Julian Wollrath
--
() ascii ribbon campaign - against html e-mail
/\ - against proprietary attachments
reply other threads:[~2019-06-11 9:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190611113251.2e3feffe@schienar \
--to=jwollrath@web.de \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.