diff options
| author | Jiri Slaby <jslaby@suse.cz> | 2012-03-05 14:51:56 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-03-08 11:38:51 -0800 |
| commit | 26b23209c0ea5503824df60b8f218fb04b80cad0 (patch) | |
| tree | 6225f9e7e4db8dc77023887e8e70539f8b185396 /arch | |
| parent | 91cedcde1e5feede6c1e4c2086ec4f3c84c56d4f (diff) | |
| download | linux-3.10-26b23209c0ea5503824df60b8f218fb04b80cad0.tar.gz linux-3.10-26b23209c0ea5503824df60b8f218fb04b80cad0.tar.bz2 linux-3.10-26b23209c0ea5503824df60b8f218fb04b80cad0.zip | |
TTY: tty_driver, document tty->ops->shutdown limitation
Note that tty->ops->shutdown is called from whatever context the user
drops the last tty reference from. E.g. if one takes a reference in
an ISR, tty close happens on other CPU and the final tty put is from
the ISR, tty->ops->shutdown will be called from that hard irq context.
We would have a problem in vt if we start using tty refcounting from
other contexts than user there. It is because vt's shutdown uses
mutexes. This is yet to be fixed.
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Reported-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions