[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1205011800220.13575@chino.kir.corp.google.com>
Date: Tue, 1 May 2012 18:01:47 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Nick Piggin <npiggin@...il.com>
cc: Minchan Kim <minchan@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, kamezawa.hiroyu@...fujitsu.com,
kosaki.motohiro@...il.com, Neil Brown <neilb@...e.de>,
Artem Bityutskiy <dedekind1@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
Theodore Ts'o <tytso@....edu>,
Adrian Hunter <adrian.hunter@...el.com>,
Steven Whitehouse <swhiteho@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
James Morris <jmorris@...ei.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Sage Weil <sage@...dream.net>
Subject: Re: [RFC] vmalloc: add warning in __vmalloc
On Wed, 2 May 2012, Nick Piggin wrote:
> Because it needs to be an ongoing thing, which is caught as soon as the
> developer writes some code, rather than continually audited for and fixed
> up after the fact. There is not a good way to enforce this at compile time.
>
> The existing callers do need to be fixed too, of course.
>
I'm asking that existing callers be fixed up before such a warning is
introduced.
--
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