| commit | c9efe51165fa0aff57be54e3cb0201ac87f68980 | |
| author | Al Viro <viro@zeniv.linux.org.uk> | |
| Sun, 2 Feb 2014 12:05:05 +0000 (2 07:05 -0500) | ||
| committer | Al Viro <viro@zeniv.linux.org.uk> | |
| Sun, 9 Feb 2014 20:21:16 +0000 (9 15:21 -0500) | ||
| tree | 2c956f57a8c176d0df62a16adc33a2d31b78a929 | treesnapshot (tar.gz zip) |
| parent | d311d79de305f1ada47cadd672e6ed1b28a949eb | commitdiff |
fix a kmap leak in virtio_console
While we are at it, don't do kmap() under kmap_atomic(), *especially*
for a page we'd allocated with GFP_KERNEL. It's spelled "page_address",
and had that been more than that, we'd have a real trouble - kmap_high()
can block, and doing that while holding kmap_atomic() is a Bad Idea(tm).
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
While we are at it, don't do kmap() under kmap_atomic(), *especially*
for a page we'd allocated with GFP_KERNEL. It's spelled "page_address",
and had that been more than that, we'd have a real trouble - kmap_high()
can block, and doing that while holding kmap_atomic() is a Bad Idea(tm).
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
| drivers/char/virtio_console.c | diffblobblamehistory |