aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/fs/jbd2/commit.c
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2010-07-27 11:56:07 -0400
committerTheodore Ts'o <tytso@mit.edu>2010-07-27 11:56:07 -0400
commit62d2b5f2dcd3707b070efb16bbfdf6947c38c194 (patch)
tree4e721db0ab4893f6d619d20d10c1a635da079700 /fs/jbd2/commit.c
parentext4: Fix potential memory leak in ext4_fill_super (diff)
downloadwireguard-linux-62d2b5f2dcd3707b070efb16bbfdf6947c38c194.tar.xz
wireguard-linux-62d2b5f2dcd3707b070efb16bbfdf6947c38c194.zip
ext4: Always journal quota file modifications
When journaled quota options are not specified, we do writes to quota files just in data=ordered mode. This actually causes warnings from JBD2 about dirty journaled buffer because ext4_getblk unconditionally treats a block allocated by it as metadata. Since quota actually is filesystem metadata, the easiest way to get rid of the warning is to always treat quota writes as metadata... Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'fs/jbd2/commit.c')
0 files changed, 0 insertions, 0 deletions