[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1284648549.23787.26.camel@gandalf.stny.rr.com>
Date: Thu, 16 Sep 2010 10:49:09 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Arnd Bergmann <arnd@...db.de>, Jens Axboe <jaxboe@...ionio.com>
Cc: codalist@...a.cs.cmu.edu, autofs@...ux.kernel.org,
linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
Christoph Hellwig <hch@...radead.org>,
Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>,
Trond Myklebust <Trond.Myklebust@...app.com>,
Petr Vandrovec <vandrove@...cvut.cz>,
Anders Larsen <al@...rsen.net>, Jan Kara <jack@...e.cz>,
Evgeniy Dushistov <dushistov@...l.ru>,
Ingo Molnar <mingo@...e.hu>, netdev@...r.kernel.org,
Samuel Ortiz <samuel@...tiz.org>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Andrew Hendry <andrew.hendry@...il.com>
Subject: Re: Remaining BKL users, what to do
On Thu, 2010-09-16 at 16:32 +0200, Arnd Bergmann wrote:
> The big kernel lock is gone from almost all code in linux-next, this is
> the status of what I think will happen to the remaining users:
> kernel/trace/blktrace.c:
> Should be easy. Ingo? Steven?
>
Jens,
Git blame shows this to be your code (copied from block/blktrace.c from
years past).
Is the lock_kernel() needed here? (although Arnd did add it in 62c2a7d9)
-- Steve
--
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