diff options
| author |   Mikulas Patocka <mpatocka@redhat.com> | 2014-10-16 14:45:20 -0400 |
|---|---|---|
| committer |   Mike Snitzer <snitzer@redhat.com> | 2014-10-17 01:40:23 -0400 |
| commit | 9d28eb12447ee08bb5d1e8bb3195cf20e1ecd1c0 (patch) | |
| tree | 24ece98c42840d5b51a1a1f5d520f6a41dd60c0c /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | dm stripe: fix potential for leak in stripe_ctr error path (diff) | |
| download | linux-dev-9d28eb12447ee08bb5d1e8bb3195cf20e1ecd1c0.tar.xz linux-dev-9d28eb12447ee08bb5d1e8bb3195cf20e1ecd1c0.zip | |
dm bufio: change __GFP_IO to __GFP_FS in shrinker callbacks
The shrinker uses gfp flags to indicate what kind of operation can the
driver wait for. If __GFP_IO flag is present, the driver can wait for
block I/O operations, if __GFP_FS flag is present, the driver can wait on
operations involving the filesystem.
dm-bufio tested for __GFP_IO. However, dm-bufio can run on a loop block
device that makes calls into the filesystem. If __GFP_IO is present and
__GFP_FS isn't, dm-bufio could still block on filesystem operations if it
runs on a loop block device.
The change from __GFP_IO to __GFP_FS supposedly fixes one observed (though
unreproducible) deadlock involving dm-bufio and loop device.
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Cc: stable@vger.kernel.org
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions