vt: push the tty_lock down into the map handling
When we do this it becomes clear the lock we should be holding is the vc lock, and in fact many of our other helpers are properly invoked this way. We don't at this point guarantee not to race the keyboard code but the results of that appear harmless and that was true before we started as well. We now have no users of tty_lock in the console driver... Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:

committed by
Greg Kroah-Hartman

parent
10af77c193
commit
5d1a33fa55
@@ -70,7 +70,6 @@ int con_set_unimap(struct vc_data *vc, ushort ct, struct unipair __user *list);
|
||||
int con_get_unimap(struct vc_data *vc, ushort ct, ushort __user *uct, struct unipair __user *list);
|
||||
int con_set_default_unimap(struct vc_data *vc);
|
||||
void con_free_unimap(struct vc_data *vc);
|
||||
void con_protect_unimap(struct vc_data *vc, int rdonly);
|
||||
int con_copy_unimap(struct vc_data *dst_vc, struct vc_data *src_vc);
|
||||
|
||||
#define vc_translate(vc, c) ((vc)->vc_translate[(c) | \
|
||||
|
Reference in New Issue
Block a user