diff options
author | Jan Kara <jack@suse.cz> | 2010-09-21 11:49:01 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-03-21 12:45:41 -0700 |
commit | 44498d9d63480b416a23e67a57c51481c861f8a3 (patch) | |
tree | e244ad44c7890a54924f36d50107317fcb525f0c /drivers | |
parent | 060049e494a4f234002941aa2403d849ca8c883c (diff) |
char: Mark /dev/zero and /dev/kmem as not capable of writeback
commit 371d217ee1ff8b418b8f73fb2a34990f951ec2d4 upstream.
These devices don't do any writeback but their device inodes still can get
dirty so mark bdi appropriately so that bdi code does the right thing and files
inodes to lists of bdi carrying the device inodes.
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers')
-rw-r--r-- | drivers/char/mem.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/char/mem.c b/drivers/char/mem.c index 48788db4e28..bc46ea8e359 100644 --- a/drivers/char/mem.c +++ b/drivers/char/mem.c @@ -784,10 +784,11 @@ static const struct file_operations zero_fops = { /* * capabilities for /dev/zero * - permits private mappings, "copies" are taken of the source of zeros + * - no writeback happens */ static struct backing_dev_info zero_bdi = { .name = "char/mem", - .capabilities = BDI_CAP_MAP_COPY, + .capabilities = BDI_CAP_MAP_COPY | BDI_CAP_NO_ACCT_AND_WRITEBACK, }; static const struct file_operations full_fops = { |