Re: Google Chrome cause locks held in system (kernel 4.15 rc2)

Tetsuo Handa
2018-01-06T14:53:02Z

mikhail wrote:
> On Mon, 2017-12-11 at 12:48 +0900, Tetsuo Handa wrote:
> > mikhail wrote:
> > > > > netconsole works only within local network? destination ip may
> > > > > be from
> > > > > another network?
> > > >
> > > > netconsole can work with another network.
> > > >
> > > > (step 1) Verify that UDP packets are reachable. You can test with
> > > >
> > > > # echo test > /dev/udp/213.136.82.171/6666
> > > >
> > > > if you are using bash.
> > >
> > > After this on remote machine was created folder with name of router
> > > external ip address.
> > > Inside this folder was places one file with name of current day.
> > > This
> > > file has size 0 of bytes and not contain "test" message inside.
> > > That is how it should be?
> >
> > The message should be written to the log file. If not written, UDP
> > packets
> > are dropped somewhere. You need to solve this problem first.
>
> I found root cause this problem. Here culprit udplogger, because it not
> flush buffers when terminated by ctrl-c.
>
> Here my pull request with fix this problem:
> https://github.com/kohsuke/udplogger/pull/1/

Thank you. But excuse me?
Something unexpected must be happening in your environment.

udplogger will flush buffers upon '\n' or timeout (default is 10 seconds) or
too long line (default is 65536 bytes).

>
> Also i fixed two segfault:
>
> 1) When send two messages in one second from different hosts or ports.
> For reproduce just run
> "echo test > /dev/udp/127.0.0.1/6666 && echo test >
> /dev/udp/127.0.0.1/6666"
> in console.

I can't observe such problem.
udplogger is ready to concurrently receive from multiple sources.

2018-01-06 23:30:08 127.0.0.1:33637 test
2018-01-06 23:30:08 127.0.0.1:47459 test
2018-01-06 23:32:52 127.0.0.1:36343 test
2018-01-06 23:32:52 127.0.0.1:49087 test
2018-01-06 23:32:53 127.0.0.1:43124 test
2018-01-06 23:32:53 127.0.0.1:40711 test
2018-01-06 23:32:53 127.0.0.1:48455 test
2018-01-06 23:32:53 127.0.0.1:60887 test
2018-01-06 23:32:53 127.0.0.1:49617 test
2018-01-06 23:32:53 127.0.0.1:56967 test
2018-01-06 23:32:54 127.0.0.1:44289 test
2018-01-06 23:32:54 127.0.0.1:52134 test
2018-01-06 23:32:54 127.0.0.1:57924 test
2018-01-06 23:32:54 127.0.0.1:54044 test
2018-01-06 23:32:54 127.0.0.1:42350 test
2018-01-06 23:32:54 127.0.0.1:56750 test
2018-01-06 23:32:54 127.0.0.1:33790 test
2018-01-06 23:32:54 127.0.0.1:55627 test
2018-01-06 23:32:55 127.0.0.1:46477 test
2018-01-06 23:32:55 127.0.0.1:34978 test
2018-01-06 23:32:55 127.0.0.1:41563 test
2018-01-06 23:32:55 127.0.0.1:34146 test

>
> 2) When exced limit of open files.
> Just run "echo test > /dev/udp/127.0.0.1/6666" more than 1024 times.
>

I can't observe such problem.
udplogger switches to a new file upon acrossing 00:00:00 of the local time.
Simply repeating 1024 times can't reach max open files limit.

Are you using special environment? What is the shell? What is the compiler/version?