linux-kernel - Re: BKL status?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 11 Sep 2010 22:08:05 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	John Kacur <jkacur@...hat.com>,
	Sam Ravnborg <sam@...nborg.org>,
	Trond Myklebust <Trond.Myklebust@...app.com>,
	"J. Bruce Fields" <bfields@...ldses.org>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	Jan Blunck <jblunck@...e.de>,
	Hans Verkuil <hverkuil@...all.nl>,
	linux-kernel@...r.kernel.org, David Miller <davem@...emloft.net>
Subject: Re: BKL status?

On Tuesday 07 September 2010 17:10:40 Arnd Bergmann wrote:
> 
> > - individual drivers
> 
> We have two categories here. There are a large number of trivial
> drivers where we can prove that the BKL can get replaced with a
> private mutex, as my 'trivial' branch in g.k.o:bkl.git does.
> 
> Then there are some modules that are actually hard to do, most
> of them obsolete. Judging purely by the number of number of
> lock_kernel() calls, which is somewhat misleading, the main
> offenders are:
> 
> drivers/{media,staging,usb/gadget,char/raw}
> fs/{autofs,coda,hpfs,isofs,ncpfs,nfs,smbfs,udf,ufs}
> net/{appletalk,ipx,irda,ax25}
> 
> Out of these, we definitely need to fix v4l, isofs and nfs
> to have a chance of disabling the BKL in a distro kernel.
> But first things first, once fs/lockd is done, we are
> at the point where all remaining BKL users are in modules.

I have now taken care of most of the trivial ones in my git
tree and rebased the series.

The only bits that are left are those I didn't want to
touch for some reason:

arch/sparc: DaveM to look into it
drivers/media/video: Frederic has a series
drivers/gpu/drm/{i810,i830}: actually hard, can become BROKEN_ON_SMP
fs/lockd: Trond and Bruce will take care, disabled for now
fs/*/: interdependencies with the vfs series, can wait for one more release
net/{appletalk,ipx,irda,ax25}: no idea how to do it, need someone to
    actually care.

Many of the file systems should be fairly easy to do for someone who
knows more about VFS than me. However: autofs, coda, hpfs, ncpfs, smbfs
and ufs may end up not surviving the BKL removal unharmed and likely
get removed or marked BROKEN_ON_SMP unless someone puts some serious
work into them. isofs and udf look similar, but I suppose someone
will do it after all. Frederic has managed to do it for Reiserfs, so
I'm sure we will find a way to fix these.

	Arnd
--
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/