-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kernel BUG at fw/connection.h:529 #1910
Comments
krizhanovsky
changed the title
kernel BUG at /home/evgeny/workdir/tempesta/fw/connection.h:529!
kernel BUG at fw/connection.h:529!
Jun 22, 2023
krizhanovsky
changed the title
kernel BUG at fw/connection.h:529!
kernel BUG at fw/connection.h:529
Jun 22, 2023
EvgeniiMekhanik
added a commit
that referenced
this issue
Jul 10, 2023
We should put server connection reference counter before call it's destructor Closes #1910
EvgeniiMekhanik
added a commit
that referenced
this issue
Jul 12, 2023
We should put server connection reference counter before call it's destructor Closes #1910
EvgeniiMekhanik
added a commit
that referenced
this issue
Jul 13, 2023
We should put server connection reference counter before call it's destructor Closes #1910
EvgeniiMekhanik
added a commit
that referenced
this issue
Jul 14, 2023
We should put server connection reference counter before call it's destructor Closes #1910
EvgeniiMekhanik
added a commit
that referenced
this issue
Jul 14, 2023
We should put server connection reference counter before call it's destructor Closes #1910
EvgeniiMekhanik
added a commit
that referenced
this issue
Jul 24, 2023
We should put server connection reference counter before call it's destructor Closes #1910
EvgeniiMekhanik
added a commit
that referenced
this issue
Jul 24, 2023
We should put server connection reference counter before call it's destructor Closes #1910
EvgeniiMekhanik
added a commit
that referenced
this issue
Jul 24, 2023
Fix incorrect server connection reference conter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
kernel BUG at /home/evgeny/workdir/tempesta/fw/connection.h:529!
[ 187.398989] invalid opcode: 0000 [#1] SMP NOPTI
[ 187.399615] CPU: 0 PID: 20252 Comm: sysctl Tainted: G OE 5.10.35+ #233
[ 187.400344] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
[ 187.402588] RIP: 0010:tfw_sock_srv_del_conns+0x195/0x1c0 [tempesta_fw]
[ 187.404825] Code: 0f 0b 48 c7 c7 c0 92 d0 c0 e8 04 e2 67 ce 0f 0b 48 c7 c7 b0 92 d0 c0 e8 f6 e1 67 ce 0f 0b 48 c7 c7 a0 92 d0 c0 e8 e8 e1 67 ce <0f> 0b 48 c7 c7 90 92 d0 c0 e8 da e1 67 ce 0f 0b 48 c7 c7 80 92 d0
[ 187.409946] RSP: 0018:ffffbe6500eabc18 EFLAGS: 00010202
[ 187.411335] RAX: 0000000040000001 RBX: ffff9670dfa16d08 RCX: ffff9670dfa150d0
[ 187.412981] RDX: ffff9670a758cd10 RSI: 00000000fffffe01 RDI: ffffffffc0cbc1b7
[ 187.414265] RBP: ffffbe6500eabc48 R08: 0000000000000001 R09: 0000000000000000
[ 187.415341] R10: 0000000000000001 R11: 0000000000030600 R12: ffff9670dfa16cd8
[ 187.416278] R13: ffff9670a758cd20 R14: ffff9670a758cd10 R15: ffff9670dfa150a0
[ 187.417065] FS: 00007f5b77368740(0000) GS:ffff9671b7c00000(0000) knlGS:0000000000000000
[ 187.417869] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 187.418367] CR2: 00005646c7c2e6d8 CR3: 0000000163ff0004 CR4: 0000000000770ef0
[ 187.418935] PKRU: 55555554
[ 187.419150] Call Trace:
[ 187.419318] tfw_server_destroy+0x1f/0x90 [tempesta_fw]
[ 187.419650] __tfw_sg_del_srv+0xb5/0xc0 [tempesta_fw]
[ 187.419971] tfw_sg_release_all+0xd3/0x200 [tempesta_fw]
[ 187.420308] tfw_sock_srv_stop+0x158/0x1a0 [tempesta_fw]
[ 187.420645] tfw_mods_stop+0x38/0xc0 [tempesta_fw]
[ 187.420950] tfw_ctlfn_state_io+0x239/0x400 [tempesta_fw]
[ 187.421291] proc_sys_call_handler+0x12e/0x240
[ 187.421570] proc_sys_write+0x13/0x20
[ 187.421803] new_sync_write+0x114/0x1b0
[ 187.422046] vfs_write+0x1c0/0x270
[ 187.422265] ksys_write+0x67/0xe0
[ 187.422476] __x64_sys_write+0x19/0x20
[ 187.422714] do_syscall_64+0x38/0x90
[ 187.422942] entry_SYSCALL_64_after_hwframe+0x44/0xa9
while true
do
sudo ./run_tests.py ws/
done
5-10 minutes an we have crash in ws.test_ws_ping.RestartOnUpgrade.test
The text was updated successfully, but these errors were encountered: