diff options
author | Theodore Ts'o <tytso@mit.edu> | 2012-09-18 13:33:44 -0400 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2012-09-18 13:33:44 -0400 |
commit | b5e2368baeddf401bf3da9e364fc1c96676279cd (patch) | |
tree | d442a7cc61a579fd500a39fa478dac7427bc1226 /fs/ext4/namei.c | |
parent | 90b0a97323f42ead278bbccbdf0e123db2add400 (diff) | |
download | linux-stable-b5e2368baeddf401bf3da9e364fc1c96676279cd.tar.gz linux-stable-b5e2368baeddf401bf3da9e364fc1c96676279cd.tar.bz2 linux-stable-b5e2368baeddf401bf3da9e364fc1c96676279cd.zip |
ext4: re-enable -o discard functionality in no-journal mode
This is a revert of commit b56ff9d397ce, which removed the call to
ext4_issue_discard() to fix a BUG reported because
ext4_issue_discard() was being called from inside a block group
spinlock. As it turns out this bug had already been fixed by Lukas
Czerner in commit 53fdcf992d61 by the simple expedient of moving when
we call ext4_issue_discard() outside the spinlock.
So it should be safe to re-enable this functionality, which I tested
by putting an BUG_ON(in_atomic) just after the restored callsite to
ext4_issue_discard().
Addresses-Google-Bug: #6750518
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: Anatol Pomozov <anatol.pomozov@gmail.com>
Diffstat (limited to 'fs/ext4/namei.c')
0 files changed, 0 insertions, 0 deletions