[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANq1E4QW0u-e=_aUYs_nCmSmMBZaNcB4AFHUuBeVWkuT76xYdA@mail.gmail.com>
Date: Thu, 16 Apr 2015 17:01:31 +0200
From: David Herrmann <dh.herrmann@...il.com>
To: Andy Lutomirski <luto@...capital.net>
Cc: Tom Gundersen <teg@...m.no>, Havoc Pennington <hp@...ox.com>,
Rik van Riel <riel@...hat.com>,
One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Kosina <jkosina@...e.cz>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Daniel Mack <daniel@...que.org>,
Djalal Harouni <tixxdz@...ndz.org>
Subject: Re: [GIT PULL] kdbus for 4.1-rc1
Hi
On Thu, Apr 16, 2015 at 4:34 PM, Andy Lutomirski <luto@...capital.net> wrote:
> Whose memcg does the pool use?
The pool-owner's (i.e., the receiver's).
> If it's the receiver's, and if the
> receiver can configure a memcg, then it seems that even a single
> receiver could probably cause the sender to block for an unlimited
> amount of time.
How? Which of those calls can block? I don't see how that can happen.
Thanks
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists