summaryrefslogtreecommitdiff
path: root/crypto/crypto_user.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2012-12-03 10:53:25 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2012-12-03 10:53:25 -0800
commitd3594ea2b343fbbabaaebeb4ce4e1f29e88ab6b3 (patch)
tree206d28de8ea10397d2eb5dea0fb19dfee6da8077 /crypto/crypto_user.c
parent7e5530af11be68f3109672aed59243f82e1272f0 (diff)
parentbbec0270bdd887f96377065ee38b8848b5afa395 (diff)
Merge branch 'block-dev'
Merge 'block-dev' branch. I was going to just mark everything here for stable and leave it to the 3.8 merge window, but having decided on doing another -rc, I migth as well merge it now. This removes the bd_block_size_semaphore semaphore that was added in this release to fix a race condition between block size changes and block IO, and replaces it with atomicity guaratees in fs/buffer.c instead, along with simplifying fs/block-dev.c. This removes more lines than it adds, makes the code generally simpler, and avoids the latency/rt issues that the block size semaphore introduced for mount. I'm not happy with the timing, but it wouldn't be much better doing this during the merge window and then having some delayed back-port of it into stable. * block-dev: blkdev_max_block: make private to fs/buffer.c direct-io: don't read inode->i_blkbits multiple times blockdev: remove bd_block_size_semaphore again fs/buffer.c: make block-size be per-page and protected by the page lock
Diffstat (limited to 'crypto/crypto_user.c')
0 files changed, 0 insertions, 0 deletions