[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091011090313.1b8f0eb1@infradead.org>
Date: Sun, 11 Oct 2009 09:03:13 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: John Kacur <jkacur@...hat.com>, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Christoph Hellwig <hch@...radead.org>,
Jonathan Corbet <corbet@....net>,
Andrew Morton <akpm@...ux-foundation.org>,
Vincent Sanders <vince@...tec.co.uk>,
linux-scsi@...r.kernel.org
Subject: Re: [PATCH RFC] [PATCH] drivers/scsi/ch.c: Remove BKL in ch_open
On Sun, 11 Oct 2009 16:54:08 +0100
Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > > I'm not so sure. In fact there are some quite umm interesting
> > > questions about this code, and some of them are shared with other
> > > modules too.
> > >
> > > Consider the following sequence
> > >
> > > CPU1 CPU2
> > > register_chrdev
> > > ok
> > > open device
> > > takes lock
> >
> >
> > but open does not take the BKL, so the BKL is not protecting you at
> > all against this..
>
> But module load/unload does
it does?
looking at the code.... so far failing to find where.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
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