[GitHub] trafficserver issue #1401: Segfault in write_to_net_io with 7.1.x

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/issues/1401 epoll_wait triggered EVENTIO_ERROR after accept(do_blocking_accept) will cause coredump, because we do not call any do_io_xx. In 6.x.x we do not handle EVENTIO_ERROR event，it may cause vc

[GitHub] trafficserver issue #1401: Segfault in write_to_net_io with 7.1.x

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/issues/1401 epoll_wait trigger EVENTIO_ERROR(in read or write) would case segfault, because we do not set any state in vc(by calling do_io_xxx). we just recevie sockets and register in epoll_wait

[GitHub] trafficserver issue #1130: TS-4991 jtest should handle Range request

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/pull/1130 TS-4991 jtest should handle Range request Jtest will support random range by "--range_model 1" args. And it uses the dran48 to generate 2 numbers as the range boundary.

[GitHub] trafficserver pull request #1229: TS-5061 TS use ats_malloc instead of mallo...

GitHub user scw00 opened a pull request: https://github.com/apache/trafficserver/pull/1229 TS-5061 TS use ats_malloc instead of malloc in log module It should be abort immediately while malloc failed . So why do not use ats_malloc instead of malloc? You can merge this pull request

[GitHub] trafficserver pull request #1130: TS-4991 jtest should handle Range request

GitHub user scw00 opened a pull request: https://github.com/apache/trafficserver/pull/1130 TS-4991 jtest should handle Range request Jtest would support random range. You can merge this pull request into a Git repository by running: $ git pull https://github.com/scw00

[GitHub] trafficserver pull request #1180: TS-4991 jtest should handle Range request

GitHub user scw00 opened a pull request: https://github.com/apache/trafficserver/pull/1180 TS-4991 jtest should handle Range request TS-4991 jtest should handle Range request Jtest will support random range by "--range_model 1" args. And it uses the dran48 to

[GitHub] trafficserver pull request #1130: TS-4991 jtest should handle Range request

Github user scw00 closed the pull request at: https://github.com/apache/trafficserver/pull/1130 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] trafficserver issue #1229: TS-5061 TS use ats_malloc instead of malloc in lo...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/pull/1229 Here is another one , Sorry! https://github.com/apache/trafficserver/pull/1249 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] trafficserver pull request #1249: TS-5061 TS use ats_malloc instead of mallo...

GitHub user scw00 opened a pull request: https://github.com/apache/trafficserver/pull/1249 TS-5061 TS use ats_malloc instead of malloc in log module It should be abort immediately while malloc failed . So why do not use ats_malloc to instead of malloc? You can merge this pull

[GitHub] trafficserver issue #1229: TS-5061 TS use ats_malloc instead of malloc in lo...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/pull/1229 ok --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so

[GitHub] trafficserver pull request #1628: Assertion in state_read_server_response_he...

GitHub user scw00 opened a pull request: https://github.com/apache/trafficserver/pull/1628 Assertion in state_read_server_response_header (v7.1.0) In my opinion, the EPOLLERR always with read.enabled or write.enabled(otherwise, there is no sm could handle this event, we just

[GitHub] trafficserver issue #1531: Assertion in state_read_server_response_header (v...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/issues/1531 There are reasons for this creash: 1、ATS try to connect the origin server, but receive RST package. So ATS try again until retry_times == 0. It will clean the server_entry (mark the VC

[GitHub] trafficserver pull request #1629: Assertion in state_read_server_response_he...

GitHub user scw00 opened a pull request: https://github.com/apache/trafficserver/pull/1629 Assertion in state_read_server_response_header (v7.1.0) In my opinion, the EPOLLERR always with read.enabled or write.enabled(otherwise, there is no sm could handle this event, we just

[GitHub] trafficserver issue #1630: ATS Lua could support shared dictionary just like...

GitHub user scw00 opened an issue: https://github.com/apache/trafficserver/issues/1630 ATS Lua could support shared dictionary just like nginx To replace nginx, ATS Lua could support shared dictionary just like nginx. --- If your project is set up for it, you can reply

[GitHub] trafficserver pull request #1628: Assertion in state_read_server_response_he...

Github user scw00 closed the pull request at: https://github.com/apache/trafficserver/pull/1628 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] trafficserver issue #1625: HttpSM::state_cache_open_write crash

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/issues/1625 version? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so

[GitHub] trafficserver issue #1559: Do not callback one SM EVENT_ERROR twice.

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/pull/1559 @oknet I it work well on my test env, and jtest can not re-product any more ! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well

[GitHub] trafficserver issue #1544: AddressSanitizer failed to deallocate

GitHub user scw00 opened an issue: https://github.com/apache/trafficserver/issues/1544 AddressSanitizer failed to deallocate ``` ==22977== ERROR: AddressSanitizer failed to deallocate 0x23000 (143360) bytes at address 0x7fff680d ==22977== AddressSanitizer CHECK failed

[GitHub] trafficserver issue #1532: ATS 7.1 release running out of memory

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/issues/1532 We have meet the same situation in our product env, and we try to modified max_map_count, the kernel variable, and it work well. In Short, it may too much map nnon in process

[GitHub] trafficserver issue #1522: Ignore read and write errors if vio has been clea...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/pull/1522 ``` (gdb) p *server_entry->read_vio $3 = {_cont = 0x607000476100, nbytes = 9223372036854775807, ndone = 0, op = 1, buffer = {name = 0x0, mbuf = 0x6024000cebc0, entry =

[GitHub] trafficserver issue #1522: Ignore read and write errors if vio has been clea...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/pull/1522 Actually, there is still a problem in my test after these patch by jtest. ``` #0 0x72be9c37 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1

[GitHub] trafficserver issue #1531: Assertion in state_read_server_response_header (v...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/issues/1531 I think, it never call handler with read.enabled = 0(or write.enabled). It means the handler don not want this type of event .It may never handle this event and just assert! [https

[GitHub] trafficserver issue #1522: Ignore read and write errors if vio has been clea...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/pull/1522 I think, it #never calls handler with read.enabled = 0(or write.enabled). It means the handler don not want this type of event .It may never handle this event and just assert! #1531

[GitHub] trafficserver issue #1522: Ignore read and write errors if vio has been clea...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/pull/1522 I believe all of these issue have the same reason. the reproduct is easy. Run jtest and press Control + C, repeat until you see this assert. I think, if we merge this pr, that means

[GitHub] trafficserver issue #1531: Assertion in state_read_server_response_header (v...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/issues/1531 Based on #1522 we need to ensure that all the handler should handle read error event and write error event at same time. I'll track it ! --- If your project is set up for it, you

[GitHub] trafficserver issue #1544: AddressSanitizer failed to deallocate

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/issues/1544 7.1.0 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so

[GitHub] trafficserver issue #1522: Ignore read and write errors if vio has been clea...

Github user scw00 commented on the issue: https://github.com/apache/trafficserver/pull/1522 Agree!! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so