All of lore.kernel.org
 help / color / mirror / Atom feed
From: mikhail <mikhail.v.gavrilov@gmail.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: mhocko@kernel.org, darrick.wong@oracle.com,
	linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Google Chrome cause locks held in system (kernel 4.15 rc2)
Date: Sat, 06 Jan 2018 19:17:15 +0500	[thread overview]
Message-ID: <1515248235.17396.4.camel@gmail.com> (raw)
In-Reply-To: <201712110348.vBB3mSFZ068689@www262.sakura.ne.jp>

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/

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.

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

WARNING: multiple messages have this Message-ID (diff)
From: mikhail <mikhail.v.gavrilov@gmail.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: mhocko@kernel.org, darrick.wong@oracle.com,
	linux-xfs@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Google Chrome cause locks held in system (kernel 4.15 rc2)
Date: Sat, 06 Jan 2018 19:17:15 +0500	[thread overview]
Message-ID: <1515248235.17396.4.camel@gmail.com> (raw)
In-Reply-To: <201712110348.vBB3mSFZ068689@www262.sakura.ne.jp>

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/

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.

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

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2018-01-06 14:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  3:50 Google Chrome cause locks held in system (kernel 4.15 rc2) mikhail
2017-12-08  3:50 ` mikhail
2017-12-08  4:05 ` Darrick J. Wong
2017-12-08  4:05   ` Darrick J. Wong
2017-12-08 10:18   ` Tetsuo Handa
2017-12-08 10:18     ` Tetsuo Handa
2017-12-09 13:17     ` mikhail
2017-12-09 13:17       ` mikhail
2017-12-09 14:14       ` Tetsuo Handa
2017-12-09 14:14         ` Tetsuo Handa
2017-12-10 21:49         ` mikhail
2017-12-10 21:49           ` mikhail
2017-12-11  0:14           ` Tetsuo Handa
2017-12-11  0:14             ` Tetsuo Handa
2017-12-11  3:34             ` mikhail
2017-12-11  3:34               ` mikhail
2017-12-11  3:48               ` Tetsuo Handa
2017-12-11  3:48                 ` Tetsuo Handa
2018-01-06 14:17                 ` mikhail [this message]
2018-01-06 14:17                   ` mikhail
2018-01-06 14:52                   ` Tetsuo Handa
2018-01-06 14:52                     ` Tetsuo Handa
2018-01-06 15:28                     ` mikhail
2018-01-06 15:28                       ` mikhail
2018-01-06 15:48                       ` Tetsuo Handa
2018-01-06 15:48                         ` Tetsuo Handa
2018-01-06 17:24                         ` mikhail
2018-01-06 17:24                           ` mikhail
2018-01-07  3:42                           ` Tetsuo Handa
2018-01-07  3:42                             ` Tetsuo Handa
2017-12-09 12:31   ` mikhail
2017-12-09 12:31     ` mikhail
  -- strict thread matches above, loose matches on Subject: below --
2017-12-08  3:48 mikhail

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=1515248235.17396.4.camel@gmail.com \
    --to=mikhail.v.gavrilov@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    /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.