From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] UNIX: Do not loop forever at unix_autobind().
Date: Sat, 04 Sep 2010 10:24:07 +0200 [thread overview]
Message-ID: <1283588647.3402.12.camel@edumazet-laptop> (raw)
In-Reply-To: <201009040740.o847eB4f040772@www262.sakura.ne.jp>
Le samedi 04 septembre 2010 à 16:40 +0900, Tetsuo Handa a écrit :
> Eric Dumazet wrote:
> > Sorry, this wont work very well if you have many processes using
> > autobind(). Some of them will loop many time before hitting
> > "stop_ordernum".
>
> I see. Then, we should use local counter rather than global counter for yield()
> checking in case there are multiple threads hitting this loop.
> ----------------------------------------
> From 57a49c7b5a39de58d4538b85c60c758be3d2ce4f Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Sat, 4 Sep 2010 16:23:46 +0900
> Subject: [PATCH] UNIX: Do not loop forever at unix_autobind().
>
> We assumed that unix_autobind() never fails if kzalloc() succeeded.
> But unix_autobind() allows only 1048576 names. If /proc/sys/fs/file-max is
> larger than 1048576 (e.g. systems with more than 10GB of RAM), a local user can
> consume all names using fork()/socket()/bind().
>
> If all names are in use, those who call bind() with addr_len == sizeof(short)
> or connect()/sendmsg() with setsockopt(SO_PASSCRED) will continue
>
> while (1)
> yield();
>
> loop at unix_autobind() till a name becomes available.
> This patch adds a loop counter in order to give up after 1048576 attempts and
> use the loop counter in order to count yield() interval more reliably when
> there are many threads hitting this loop.
>
> Note that currently a local user can consume 2GB of kernel memory if the user
> is allowed to create and autobind 1048576 UNIX domain sockets. We should
> consider adding some restriction for autobind operation.
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> ---
> net/unix/af_unix.c | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
> index 4414a18..eedfe50 100644
> --- a/net/unix/af_unix.c
> +++ b/net/unix/af_unix.c
> @@ -692,6 +692,7 @@ static int unix_autobind(struct socket *sock)
> static u32 ordernum = 1;
> struct unix_address *addr;
> int err;
> + unsigned int retries = 0;
>
> mutex_lock(&u->readlock);
>
> @@ -717,8 +718,14 @@ retry:
> if (__unix_find_socket_byname(net, addr->name, addr->len, sock->type,
> addr->hash)) {
> spin_unlock(&unix_table_lock);
> + /* Give up if all names seems to be in use. */
> + if (retries++ == 0xFFFFF) {
> + err = -ENOMEM;
> + kfree(addr);
> + goto out;
> + }
> /* Sanity yield. It is unusual case, but yet... */
> - if (!(ordernum&0xFF))
> + if (!(retries & 0xFF))
> yield();
> goto retry;
> }
Quite frankly, given __unix_find_socket_byname() can take quite a long
time with one million entries in table, we should just remove
if (whatever)
yield();
and use a more friendly :
cond_resched();
next prev parent reply other threads:[~2010-09-04 8:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 12:01 About unix_autobind() Tetsuo Handa
2010-08-21 12:34 ` Changli Gao
2010-08-30 13:27 ` [PATCH] UNIX: Do not loop forever at unix_autobind() Tetsuo Handa
2010-09-01 19:47 ` Eric Dumazet
2010-09-04 6:58 ` Tetsuo Handa
2010-09-04 7:11 ` Eric Dumazet
2010-09-04 7:40 ` Tetsuo Handa
2010-09-04 8:24 ` Eric Dumazet [this message]
2010-09-04 9:31 ` Tetsuo Handa
2010-09-04 10:55 ` Eric Dumazet
2010-09-04 11:34 ` Tetsuo Handa
2010-09-07 1:45 ` David Miller
2010-09-04 11:52 ` Michał Mirosław
2010-09-01 21:33 ` How can OOM killer detect process consuming much kernel memory? Tetsuo Handa
2010-09-01 22:25 ` David Rientjes
2010-09-03 6:32 ` KOSAKI Motohiro
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=1283588647.3402.12.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.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