summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-s3c2440
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2010-08-07 18:25:34 +0200
committerJens Axboe <jaxboe@fusionio.com>2010-08-07 18:25:34 +0200
commit6e9624b8caec290d28b4c6d9ec75749df6372b87 (patch)
tree47225b544e1da82742795553dc4e8aa70c17afdc /arch/arm/mach-s3c2440
parentblock: push down BKL into .locked_ioctl (diff)
downloadlinux-6e9624b8caec290d28b4c6d9ec75749df6372b87.tar.xz
linux-6e9624b8caec290d28b4c6d9ec75749df6372b87.zip
block: push down BKL into .open and .release
The open and release block_device_operations are currently called with the BKL held. In order to change that, we must first make sure that all drivers that currently rely on this have no regressions. This blindly pushes the BKL into all .open and .release operations for all block drivers to prepare for the next step. The drivers can subsequently replace the BKL with their own locks or remove it completely when it can be shown that it is not needed. The functions blkdev_get and blkdev_put are the only remaining users of the big kernel lock in the block layer, besides a few uses in the ioctl code, none of which need to serialize with blkdev_{get,put}. Most of these two functions is also under the protection of bdev->bd_mutex, including the actual calls to ->open and ->release, and the common code does not access any global data structures that need the BKL. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Christoph Hellwig <hch@infradead.org> Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'arch/arm/mach-s3c2440')
0 files changed, 0 insertions, 0 deletions