[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1474085296.32273.95.camel@perches.com>
Date: Fri, 16 Sep 2016 21:08:16 -0700
From: Joe Perches <joe@...ches.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Sam Varshavchik <mrsam@...rier-mta.com>,
Ingo Molnar <mingo@...nel.org>
Cc: Laura Abbott <labbott@...hat.com>, Brent <fix@...realm.com>,
Konstantin Khlebnikov <koct9i@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Christian Borntraeger <borntraeger@...ibm.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [REGRESSION] RLIMIT_DATA crashes named
On Fri, 2016-09-16 at 17:040700, Linus Torvalds wrote:
> On Fri, Sep 16, 2016 at 4:58 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> > Here's a totally untested patch. What do people say?
> Heh. It looks like "pr_xyz_once()" is used in places that haven't
> included "ratelimit.h", so this doesn't actually build for everything.
> But I guess as a concept patch it's not hard to understand, even if
> the implementation needs a bit of tweaking.
do_just_once just isn't a good name for a global
rate limited mechanism that does something very
different than the name.
Maybe allow_once_per_ratelimit or the like
There could be an equivalent do_once
https://lkml.org/lkml/2009/5/22/3
Powered by blists - more mailing lists