linux-mm.kvack.org archive mirror
 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 20:28:50 +0500	[thread overview]
Message-ID: <1515252530.17396.16.camel@gmail.com> (raw)
In-Reply-To: <201801062352.EFF56799.HFFLOMOJOFSQtV@I-love.SAKURA.ne.jp>

On Sat, 2018-01-06 at 23:52 +0900, Tetsuo Handa wrote:
> 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).

Very strange because neither '\n' not 10 seconds helps to flush
buffers.
$ echo -e "test\n" > /dev/udp/127.0.0.1/6666
May be I used obsolete source? Could you check this?

> 
> > 
> > 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.


Too strange because this condition
https://github.com/kohsuke/udplogger/blob/master/udplogger.c#L82
do not allow open two file in one second.

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

How much your "ulimit -n" ?
My is 1024.
$ ulimit -n
1024

May be your ulimit much greater or you launch udplogger under root?

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

$ gcc --version
gcc (GCC) 7.2.1 20170915 (Red Hat 7.2.1-2)
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.

--
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 15:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  3:50 mikhail
2017-12-08  4:05 ` Darrick J. Wong
2017-12-08 10:18   ` Tetsuo Handa
2017-12-09 13:17     ` mikhail
2017-12-09 14:14       ` Tetsuo Handa
2017-12-10 21:49         ` mikhail
2017-12-11  0:14           ` Tetsuo Handa
2017-12-11  3:34             ` mikhail
2017-12-11  3:48               ` Tetsuo Handa
2018-01-06 14:17                 ` mikhail
2018-01-06 14:52                   ` Tetsuo Handa
2018-01-06 15:28                     ` mikhail [this message]
2018-01-06 15:48                       ` Tetsuo Handa
2018-01-06 17:24                         ` mikhail
2018-01-07  3:42                           ` Tetsuo Handa
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=1515252530.17396.16.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox