diff options
author | Meng Xu <mengxu.gatech@gmail.com> | 2017-10-04 10:38:37 -0400 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-10-20 14:06:45 +0200 |
commit | 8ffb82094be8ade4f5e60996edcc8afbbcb4f1f4 (patch) | |
tree | 195660244223deea7a400ef67051e2079c98abf9 /fs/f2fs/file.c | |
parent | dd076cffb8cd675a8973fc9b6cea0c04be6f0111 (diff) | |
download | linux-stable-8ffb82094be8ade4f5e60996edcc8afbbcb4f1f4.tar.gz linux-stable-8ffb82094be8ade4f5e60996edcc8afbbcb4f1f4.tar.bz2 linux-stable-8ffb82094be8ade4f5e60996edcc8afbbcb4f1f4.zip |
tty: vt: remove multi-fetch, derive font.height from font.data
In con_font_set(), when we need to guess font height (for
compat reasons?), the current approach uses multiple userspace
fetches, i.e., get_user(tmp, &charmap[32*i+h-1]), to derive
the height. This has two drawbacks:
1. performance: accessing userspace memory is less efficient than
directly de-reference the byte
2. security: a more critical problem is that the height derived
might not match with the actual font.data. This is because a user
thread might race condition to change the memory of op->data after
the op->height guessing but before the second fetch: font.data =
memdup_user(op->data, size). Leaving font.height = 32 while the
actual height is 1 or vice-versa.
This patch tries to resolve both issues by re-locating the height
guessing part after the font.data is fetched in. In this way, the
userspace data is fetched in one shot and we directly dereference
the font.data in kernel space to probe for the height.
Signed-off-by: Meng Xu <mengxu.gatech@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/f2fs/file.c')
0 files changed, 0 insertions, 0 deletions