2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* Copyright (C) 1991, 1992 Linus Torvalds
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 'tty_io.c' gives an orthogonal feeling to tty's, be they consoles
|
|
|
|
* or rs-channels. It also implements echoing, cooked mode etc.
|
|
|
|
*
|
|
|
|
* Kill-line thanks to John T Kohl, who also corrected VMIN = VTIME = 0.
|
|
|
|
*
|
|
|
|
* Modified by Theodore Ts'o, 9/14/92, to dynamically allocate the
|
|
|
|
* tty_struct and tty_queue structures. Previously there was an array
|
|
|
|
* of 256 tty_struct's which was statically allocated, and the
|
|
|
|
* tty_queue structures were allocated at boot time. Both are now
|
|
|
|
* dynamically allocated only when the tty is open.
|
|
|
|
*
|
|
|
|
* Also restructured routines so that there is more of a separation
|
|
|
|
* between the high-level tty routines (tty_io.c and tty_ioctl.c) and
|
|
|
|
* the low-level tty routines (serial.c, pty.c, console.c). This
|
2008-02-08 05:18:47 -07:00
|
|
|
* makes for cleaner and more compact code. -TYT, 9/17/92
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
|
|
|
* Modified by Fred N. van Kempen, 01/29/93, to add line disciplines
|
|
|
|
* which can be dynamically activated and de-activated by the line
|
|
|
|
* discipline handling modules (like SLIP).
|
|
|
|
*
|
|
|
|
* NOTE: pay no attention to the line discipline code (yet); its
|
|
|
|
* interface is still subject to change in this version...
|
|
|
|
* -- TYT, 1/31/92
|
|
|
|
*
|
|
|
|
* Added functionality to the OPOST tty handling. No delays, but all
|
|
|
|
* other bits should be there.
|
|
|
|
* -- Nick Holloway <alfie@dcs.warwick.ac.uk>, 27th May 1993.
|
|
|
|
*
|
|
|
|
* Rewrote canonical mode and added more termios flags.
|
|
|
|
* -- julian@uhunix.uhcc.hawaii.edu (J. Cowley), 13Jan94
|
|
|
|
*
|
|
|
|
* Reorganized FASYNC support so mouse code can share it.
|
|
|
|
* -- ctm@ardi.com, 9Sep95
|
|
|
|
*
|
|
|
|
* New TIOCLINUX variants added.
|
|
|
|
* -- mj@k332.feld.cvut.cz, 19-Nov-95
|
2008-02-08 05:18:47 -07:00
|
|
|
*
|
2005-04-16 16:20:36 -06:00
|
|
|
* Restrict vt switching via ioctl()
|
|
|
|
* -- grif@cs.ucr.edu, 5-Dec-95
|
|
|
|
*
|
|
|
|
* Move console and virtual terminal code to more appropriate files,
|
|
|
|
* implement CONFIG_VT and generalize console device interface.
|
|
|
|
* -- Marko Kohtala <Marko.Kohtala@hut.fi>, March 97
|
|
|
|
*
|
2008-10-13 03:41:42 -06:00
|
|
|
* Rewrote tty_init_dev and tty_release_dev to eliminate races.
|
2005-04-16 16:20:36 -06:00
|
|
|
* -- Bill Hawes <whawes@star.net>, June 97
|
|
|
|
*
|
|
|
|
* Added devfs support.
|
|
|
|
* -- C. Scott Ananian <cananian@alumni.princeton.edu>, 13-Jan-1998
|
|
|
|
*
|
|
|
|
* Added support for a Unix98-style ptmx device.
|
|
|
|
* -- C. Scott Ananian <cananian@alumni.princeton.edu>, 14-Jan-1998
|
|
|
|
*
|
|
|
|
* Reduced memory usage for older ARM systems
|
|
|
|
* -- Russell King <rmk@arm.linux.org.uk>
|
|
|
|
*
|
|
|
|
* Move do_SAK() into process context. Less stack use in devfs functions.
|
2008-02-08 05:18:47 -07:00
|
|
|
* alloc_tty_struct() always uses kmalloc()
|
|
|
|
* -- Andrew Morton <andrewm@uow.edu.eu> 17Mar01
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/major.h>
|
|
|
|
#include <linux/errno.h>
|
|
|
|
#include <linux/signal.h>
|
|
|
|
#include <linux/fcntl.h>
|
|
|
|
#include <linux/sched.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/tty.h>
|
|
|
|
#include <linux/tty_driver.h>
|
|
|
|
#include <linux/tty_flip.h>
|
|
|
|
#include <linux/devpts_fs.h>
|
|
|
|
#include <linux/file.h>
|
2008-04-24 05:44:08 -06:00
|
|
|
#include <linux/fdtable.h>
|
2005-04-16 16:20:36 -06:00
|
|
|
#include <linux/console.h>
|
|
|
|
#include <linux/timer.h>
|
|
|
|
#include <linux/ctype.h>
|
|
|
|
#include <linux/kd.h>
|
|
|
|
#include <linux/mm.h>
|
|
|
|
#include <linux/string.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/poll.h>
|
|
|
|
#include <linux/proc_fs.h>
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/device.h>
|
|
|
|
#include <linux/wait.h>
|
|
|
|
#include <linux/bitops.h>
|
2005-06-25 15:58:42 -06:00
|
|
|
#include <linux/delay.h>
|
2008-07-16 14:53:12 -06:00
|
|
|
#include <linux/seq_file.h>
|
2010-09-16 11:21:24 -06:00
|
|
|
#include <linux/serial.h>
|
2011-06-16 06:07:22 -06:00
|
|
|
#include <linux/ratelimit.h>
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-07-16 14:53:12 -06:00
|
|
|
#include <linux/uaccess.h>
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
#include <linux/kbd_kern.h>
|
|
|
|
#include <linux/vt_kern.h>
|
|
|
|
#include <linux/selection.h>
|
|
|
|
|
|
|
|
#include <linux/kmod.h>
|
2007-10-19 00:40:14 -06:00
|
|
|
#include <linux/nsproxy.h>
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
#undef TTY_DEBUG_HANGUP
|
2015-07-12 20:49:09 -06:00
|
|
|
#ifdef TTY_DEBUG_HANGUP
|
|
|
|
# define tty_debug_hangup(tty, f, args...) tty_debug(tty, f, ##args)
|
|
|
|
#else
|
|
|
|
# define tty_debug_hangup(tty, f, args...) do { } while (0)
|
|
|
|
#endif
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
#define TTY_PARANOIA_CHECK 1
|
|
|
|
#define CHECK_TTY_COUNT 1
|
|
|
|
|
2006-12-08 03:38:44 -07:00
|
|
|
struct ktermios tty_std_termios = { /* for the benefit of tty drivers */
|
2005-04-16 16:20:36 -06:00
|
|
|
.c_iflag = ICRNL | IXON,
|
|
|
|
.c_oflag = OPOST | ONLCR,
|
|
|
|
.c_cflag = B38400 | CS8 | CREAD | HUPCL,
|
|
|
|
.c_lflag = ISIG | ICANON | ECHO | ECHOE | ECHOK |
|
|
|
|
ECHOCTL | ECHOKE | IEXTEN,
|
2006-12-08 03:38:44 -07:00
|
|
|
.c_cc = INIT_C_CC,
|
|
|
|
.c_ispeed = 38400,
|
2016-01-10 23:41:07 -07:00
|
|
|
.c_ospeed = 38400,
|
|
|
|
/* .c_line = N_TTY, */
|
2005-04-16 16:20:36 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(tty_std_termios);
|
|
|
|
|
|
|
|
/* This list gets poked at by procfs and various bits of boot up code. This
|
|
|
|
could do with some rationalisation such as pulling the tty proc function
|
|
|
|
into this file */
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
LIST_HEAD(tty_drivers); /* linked list of tty drivers */
|
|
|
|
|
2016-01-09 22:35:18 -07:00
|
|
|
/* Mutex to protect creating and releasing a tty */
|
2006-03-23 04:00:31 -07:00
|
|
|
DEFINE_MUTEX(tty_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
static ssize_t tty_read(struct file *, char __user *, size_t, loff_t *);
|
|
|
|
static ssize_t tty_write(struct file *, const char __user *, size_t, loff_t *);
|
2008-02-08 05:18:47 -07:00
|
|
|
ssize_t redirected_tty_write(struct file *, const char __user *,
|
|
|
|
size_t, loff_t *);
|
2005-04-16 16:20:36 -06:00
|
|
|
static unsigned int tty_poll(struct file *, poll_table *);
|
|
|
|
static int tty_open(struct inode *, struct file *);
|
2008-04-30 01:53:29 -06:00
|
|
|
long tty_ioctl(struct file *file, unsigned int cmd, unsigned long arg);
|
2007-05-10 23:22:50 -06:00
|
|
|
#ifdef CONFIG_COMPAT
|
2008-02-08 05:18:47 -07:00
|
|
|
static long tty_compat_ioctl(struct file *file, unsigned int cmd,
|
2007-05-10 23:22:50 -06:00
|
|
|
unsigned long arg);
|
|
|
|
#else
|
|
|
|
#define tty_compat_ioctl NULL
|
|
|
|
#endif
|
2010-06-01 14:53:01 -06:00
|
|
|
static int __tty_fasync(int fd, struct file *filp, int on);
|
2008-02-08 05:18:47 -07:00
|
|
|
static int tty_fasync(int fd, struct file *filp, int on);
|
2007-02-10 02:46:46 -07:00
|
|
|
static void release_tty(struct tty_struct *tty, int idx);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* free_tty_struct - free a disused tty
|
|
|
|
* @tty: tty struct to free
|
|
|
|
*
|
|
|
|
* Free the write buffers, tty queue and tty memory itself.
|
|
|
|
*
|
|
|
|
* Locking: none. Must be called after tty is definitely unused
|
|
|
|
*/
|
|
|
|
|
2016-01-09 22:13:48 -07:00
|
|
|
static void free_tty_struct(struct tty_struct *tty)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2016-01-09 22:13:46 -07:00
|
|
|
tty_ldisc_deinit(tty);
|
2014-11-21 05:42:29 -07:00
|
|
|
put_device(tty->dev);
|
2005-04-16 16:20:36 -06:00
|
|
|
kfree(tty->write_buf);
|
2012-08-08 09:30:13 -06:00
|
|
|
tty->magic = 0xDEADDEAD;
|
2005-04-16 16:20:36 -06:00
|
|
|
kfree(tty);
|
|
|
|
}
|
|
|
|
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
static inline struct tty_struct *file_tty(struct file *file)
|
|
|
|
{
|
|
|
|
return ((struct tty_file_private *)file->private_data)->tty;
|
|
|
|
}
|
|
|
|
|
2011-10-12 03:32:43 -06:00
|
|
|
int tty_alloc_file(struct file *file)
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
{
|
|
|
|
struct tty_file_private *priv;
|
|
|
|
|
2010-08-23 22:48:34 -06:00
|
|
|
priv = kmalloc(sizeof(*priv), GFP_KERNEL);
|
|
|
|
if (!priv)
|
|
|
|
return -ENOMEM;
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
|
2011-10-12 03:32:43 -06:00
|
|
|
file->private_data = priv;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Associate a new file with the tty structure */
|
|
|
|
void tty_add_file(struct tty_struct *tty, struct file *file)
|
|
|
|
{
|
|
|
|
struct tty_file_private *priv = file->private_data;
|
|
|
|
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
priv->tty = tty;
|
|
|
|
priv->file = file;
|
|
|
|
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_lock(&tty->files_lock);
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
list_add(&priv->list, &tty->tty_files);
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_unlock(&tty->files_lock);
|
2011-10-12 03:32:43 -06:00
|
|
|
}
|
2010-08-23 22:48:34 -06:00
|
|
|
|
2011-10-12 03:32:43 -06:00
|
|
|
/**
|
|
|
|
* tty_free_file - free file->private_data
|
|
|
|
*
|
|
|
|
* This shall be used only for fail path handling when tty_add_file was not
|
|
|
|
* called yet.
|
|
|
|
*/
|
|
|
|
void tty_free_file(struct file *file)
|
|
|
|
{
|
|
|
|
struct tty_file_private *priv = file->private_data;
|
|
|
|
|
|
|
|
file->private_data = NULL;
|
|
|
|
kfree(priv);
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Delete file from its tty */
|
2012-11-18 22:27:47 -07:00
|
|
|
static void tty_del_file(struct file *file)
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
{
|
|
|
|
struct tty_file_private *priv = file->private_data;
|
2016-01-09 22:35:23 -07:00
|
|
|
struct tty_struct *tty = priv->tty;
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_lock(&tty->files_lock);
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
list_del(&priv->list);
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_unlock(&tty->files_lock);
|
2011-10-12 03:32:43 -06:00
|
|
|
tty_free_file(file);
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
#define TTY_NUMBER(tty) ((tty)->index + (tty)->driver->name_base)
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tty_name - return tty naming
|
|
|
|
* @tty: tty structure
|
|
|
|
*
|
|
|
|
* Convert a tty structure into a name. The name reflects the kernel
|
|
|
|
* naming policy and if udev is in use may not reflect user space
|
|
|
|
*
|
|
|
|
* Locking: none
|
|
|
|
*/
|
|
|
|
|
2015-03-31 07:55:59 -06:00
|
|
|
const char *tty_name(const struct tty_struct *tty)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
if (!tty) /* Hmm. NULL pointer. That's fun. */
|
2015-03-31 07:55:58 -06:00
|
|
|
return "NULL tty";
|
|
|
|
return tty->name;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(tty_name);
|
|
|
|
|
2015-11-08 11:01:12 -07:00
|
|
|
const char *tty_driver_name(const struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
if (!tty || !tty->driver)
|
|
|
|
return "";
|
|
|
|
return tty->driver->name;
|
|
|
|
}
|
|
|
|
|
2015-11-08 11:01:09 -07:00
|
|
|
static int tty_paranoia_check(struct tty_struct *tty, struct inode *inode,
|
2005-04-16 16:20:36 -06:00
|
|
|
const char *routine)
|
|
|
|
{
|
|
|
|
#ifdef TTY_PARANOIA_CHECK
|
|
|
|
if (!tty) {
|
2015-11-08 11:01:18 -07:00
|
|
|
pr_warn("(%d:%d): %s: NULL tty\n",
|
2005-04-16 16:20:36 -06:00
|
|
|
imajor(inode), iminor(inode), routine);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
if (tty->magic != TTY_MAGIC) {
|
2015-11-08 11:01:18 -07:00
|
|
|
pr_warn("(%d:%d): %s: bad magic number\n",
|
2005-04-16 16:20:36 -06:00
|
|
|
imajor(inode), iminor(inode), routine);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2014-11-05 10:12:55 -07:00
|
|
|
/* Caller must hold tty_lock */
|
2005-04-16 16:20:36 -06:00
|
|
|
static int check_tty_count(struct tty_struct *tty, const char *routine)
|
|
|
|
{
|
|
|
|
#ifdef CHECK_TTY_COUNT
|
|
|
|
struct list_head *p;
|
|
|
|
int count = 0;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_lock(&tty->files_lock);
|
2005-04-16 16:20:36 -06:00
|
|
|
list_for_each(p, &tty->tty_files) {
|
|
|
|
count++;
|
|
|
|
}
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_unlock(&tty->files_lock);
|
2005-04-16 16:20:36 -06:00
|
|
|
if (tty->driver->type == TTY_DRIVER_TYPE_PTY &&
|
|
|
|
tty->driver->subtype == PTY_TYPE_SLAVE &&
|
|
|
|
tty->link && tty->link->count)
|
|
|
|
count++;
|
|
|
|
if (tty->count != count) {
|
2015-11-08 11:01:13 -07:00
|
|
|
tty_warn(tty, "%s: tty->count(%d) != #fd's(%d)\n",
|
|
|
|
routine, tty->count, count);
|
2005-04-16 16:20:36 -06:00
|
|
|
return count;
|
2006-12-08 03:36:04 -07:00
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
#endif
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* get_tty_driver - find device of a tty
|
|
|
|
* @dev_t: device identifier
|
|
|
|
* @index: returns the index of the tty
|
|
|
|
*
|
|
|
|
* This routine returns a tty driver structure, given a device number
|
|
|
|
* and also passes back the index number.
|
|
|
|
*
|
|
|
|
* Locking: caller must hold tty_mutex
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2006-08-27 02:24:01 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static struct tty_driver *get_tty_driver(dev_t device, int *index)
|
|
|
|
{
|
|
|
|
struct tty_driver *p;
|
|
|
|
|
|
|
|
list_for_each_entry(p, &tty_drivers, tty_drivers) {
|
|
|
|
dev_t base = MKDEV(p->major, p->minor_start);
|
|
|
|
if (device < base || device >= base + p->num)
|
|
|
|
continue;
|
|
|
|
*index = device - base;
|
2008-10-13 03:42:09 -06:00
|
|
|
return tty_driver_kref_get(p);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
2008-04-17 12:05:37 -06:00
|
|
|
#ifdef CONFIG_CONSOLE_POLL
|
|
|
|
|
|
|
|
/**
|
|
|
|
* tty_find_polling_driver - find device of a polled tty
|
|
|
|
* @name: name string to match
|
|
|
|
* @line: pointer to resulting tty line nr
|
|
|
|
*
|
|
|
|
* This routine returns a tty driver structure, given a name
|
|
|
|
* and the condition that the tty driver is capable of polled
|
|
|
|
* operation.
|
|
|
|
*/
|
|
|
|
struct tty_driver *tty_find_polling_driver(char *name, int *line)
|
|
|
|
{
|
|
|
|
struct tty_driver *p, *res = NULL;
|
|
|
|
int tty_line = 0;
|
2008-09-26 09:36:42 -06:00
|
|
|
int len;
|
2009-06-11 05:46:41 -06:00
|
|
|
char *str, *stp;
|
2008-04-17 12:05:37 -06:00
|
|
|
|
2008-09-26 09:36:42 -06:00
|
|
|
for (str = name; *str; str++)
|
|
|
|
if ((*str >= '0' && *str <= '9') || *str == ',')
|
|
|
|
break;
|
|
|
|
if (!*str)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
len = str - name;
|
|
|
|
tty_line = simple_strtoul(str, &str, 10);
|
|
|
|
|
2008-04-17 12:05:37 -06:00
|
|
|
mutex_lock(&tty_mutex);
|
|
|
|
/* Search through the tty devices to look for a match */
|
|
|
|
list_for_each_entry(p, &tty_drivers, tty_drivers) {
|
2008-09-26 09:36:42 -06:00
|
|
|
if (strncmp(name, p->name, len) != 0)
|
|
|
|
continue;
|
2009-06-11 05:46:41 -06:00
|
|
|
stp = str;
|
|
|
|
if (*stp == ',')
|
|
|
|
stp++;
|
|
|
|
if (*stp == '\0')
|
|
|
|
stp = NULL;
|
2008-04-17 12:05:37 -06:00
|
|
|
|
2010-09-02 08:06:16 -06:00
|
|
|
if (tty_line >= 0 && tty_line < p->num && p->ops &&
|
2009-06-11 05:46:41 -06:00
|
|
|
p->ops->poll_init && !p->ops->poll_init(p, tty_line, stp)) {
|
2008-10-13 03:42:09 -06:00
|
|
|
res = tty_driver_kref_get(p);
|
2008-04-17 12:05:37 -06:00
|
|
|
*line = tty_line;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
mutex_unlock(&tty_mutex);
|
|
|
|
|
|
|
|
return res;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(tty_find_polling_driver);
|
|
|
|
#endif
|
|
|
|
|
2016-01-09 22:35:21 -07:00
|
|
|
static int is_ignored(int sig)
|
|
|
|
{
|
|
|
|
return (sigismember(¤t->blocked, sig) ||
|
|
|
|
current->sighand->action[sig-1].sa.sa_handler == SIG_IGN);
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tty_check_change - check for POSIX terminal changes
|
|
|
|
* @tty: tty to check
|
|
|
|
*
|
|
|
|
* If we try to write to, or set the state of, a terminal and we're
|
|
|
|
* not in the foreground, send a SIGTTOU. If the signal is blocked or
|
|
|
|
* ignored, go ahead and perform the operation. (POSIX 7.2)
|
|
|
|
*
|
2008-04-30 01:53:59 -06:00
|
|
|
* Locking: ctrl_lock
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2006-08-27 02:24:01 -06:00
|
|
|
|
2015-10-10 18:28:42 -06:00
|
|
|
int __tty_check_change(struct tty_struct *tty, int sig)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2008-04-30 01:53:30 -06:00
|
|
|
unsigned long flags;
|
2015-10-10 18:28:42 -06:00
|
|
|
struct pid *pgrp, *tty_pgrp;
|
2008-04-30 01:53:30 -06:00
|
|
|
int ret = 0;
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
if (current->signal->tty != tty)
|
|
|
|
return 0;
|
2008-04-30 01:53:30 -06:00
|
|
|
|
2015-07-12 16:51:52 -06:00
|
|
|
rcu_read_lock();
|
|
|
|
pgrp = task_pgrp(current);
|
|
|
|
|
2008-04-30 01:53:30 -06:00
|
|
|
spin_lock_irqsave(&tty->ctrl_lock, flags);
|
2015-10-10 18:28:42 -06:00
|
|
|
tty_pgrp = tty->pgrp;
|
2008-05-14 17:05:58 -06:00
|
|
|
spin_unlock_irqrestore(&tty->ctrl_lock, flags);
|
2015-07-12 16:51:52 -06:00
|
|
|
|
2015-10-10 18:28:42 -06:00
|
|
|
if (tty_pgrp && pgrp != tty->pgrp) {
|
|
|
|
if (is_ignored(sig)) {
|
|
|
|
if (sig == SIGTTIN)
|
|
|
|
ret = -EIO;
|
|
|
|
} else if (is_current_pgrp_orphaned())
|
|
|
|
ret = -EIO;
|
|
|
|
else {
|
|
|
|
kill_pgrp(pgrp, sig, 1);
|
|
|
|
set_thread_flag(TIF_SIGPENDING);
|
|
|
|
ret = -ERESTARTSYS;
|
|
|
|
}
|
2008-04-30 01:53:30 -06:00
|
|
|
}
|
2015-07-12 16:51:52 -06:00
|
|
|
rcu_read_unlock();
|
2015-10-10 18:28:42 -06:00
|
|
|
|
2015-11-08 11:01:13 -07:00
|
|
|
if (!tty_pgrp)
|
|
|
|
tty_warn(tty, "sig=%d, tty->pgrp == NULL!\n", sig);
|
2015-10-10 18:28:42 -06:00
|
|
|
|
2008-04-30 01:53:30 -06:00
|
|
|
return ret;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2015-10-10 18:28:42 -06:00
|
|
|
int tty_check_change(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
return __tty_check_change(tty, SIGTTOU);
|
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
EXPORT_SYMBOL(tty_check_change);
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
static ssize_t hung_up_tty_read(struct file *file, char __user *buf,
|
2005-04-16 16:20:36 -06:00
|
|
|
size_t count, loff_t *ppos)
|
|
|
|
{
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
static ssize_t hung_up_tty_write(struct file *file, const char __user *buf,
|
2005-04-16 16:20:36 -06:00
|
|
|
size_t count, loff_t *ppos)
|
|
|
|
{
|
|
|
|
return -EIO;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* No kernel lock held - none needed ;) */
|
2008-02-08 05:18:47 -07:00
|
|
|
static unsigned int hung_up_tty_poll(struct file *filp, poll_table *wait)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
return POLLIN | POLLOUT | POLLERR | POLLHUP | POLLRDNORM | POLLWRNORM;
|
|
|
|
}
|
|
|
|
|
2008-04-30 01:53:29 -06:00
|
|
|
static long hung_up_tty_ioctl(struct file *file, unsigned int cmd,
|
|
|
|
unsigned long arg)
|
2007-06-16 11:15:55 -06:00
|
|
|
{
|
|
|
|
return cmd == TIOCSPGRP ? -ENOTTY : -EIO;
|
|
|
|
}
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
static long hung_up_tty_compat_ioctl(struct file *file,
|
2007-06-16 11:15:55 -06:00
|
|
|
unsigned int cmd, unsigned long arg)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
return cmd == TIOCSPGRP ? -ENOTTY : -EIO;
|
|
|
|
}
|
|
|
|
|
2016-01-09 22:45:10 -07:00
|
|
|
static int hung_up_tty_fasync(int fd, struct file *file, int on)
|
|
|
|
{
|
|
|
|
return -ENOTTY;
|
|
|
|
}
|
|
|
|
|
2006-07-03 01:24:21 -06:00
|
|
|
static const struct file_operations tty_fops = {
|
2005-04-16 16:20:36 -06:00
|
|
|
.llseek = no_llseek,
|
|
|
|
.read = tty_read,
|
|
|
|
.write = tty_write,
|
|
|
|
.poll = tty_poll,
|
2008-04-30 01:53:29 -06:00
|
|
|
.unlocked_ioctl = tty_ioctl,
|
2007-05-10 23:22:50 -06:00
|
|
|
.compat_ioctl = tty_compat_ioctl,
|
2005-04-16 16:20:36 -06:00
|
|
|
.open = tty_open,
|
|
|
|
.release = tty_release,
|
|
|
|
.fasync = tty_fasync,
|
|
|
|
};
|
|
|
|
|
2006-07-03 01:24:21 -06:00
|
|
|
static const struct file_operations console_fops = {
|
2005-04-16 16:20:36 -06:00
|
|
|
.llseek = no_llseek,
|
|
|
|
.read = tty_read,
|
|
|
|
.write = redirected_tty_write,
|
|
|
|
.poll = tty_poll,
|
2008-04-30 01:53:29 -06:00
|
|
|
.unlocked_ioctl = tty_ioctl,
|
2007-05-10 23:22:50 -06:00
|
|
|
.compat_ioctl = tty_compat_ioctl,
|
2005-04-16 16:20:36 -06:00
|
|
|
.open = tty_open,
|
|
|
|
.release = tty_release,
|
|
|
|
.fasync = tty_fasync,
|
|
|
|
};
|
|
|
|
|
2006-07-03 01:24:21 -06:00
|
|
|
static const struct file_operations hung_up_tty_fops = {
|
2005-04-16 16:20:36 -06:00
|
|
|
.llseek = no_llseek,
|
|
|
|
.read = hung_up_tty_read,
|
|
|
|
.write = hung_up_tty_write,
|
|
|
|
.poll = hung_up_tty_poll,
|
2008-04-30 01:53:29 -06:00
|
|
|
.unlocked_ioctl = hung_up_tty_ioctl,
|
2007-06-16 11:15:55 -06:00
|
|
|
.compat_ioctl = hung_up_tty_compat_ioctl,
|
2005-04-16 16:20:36 -06:00
|
|
|
.release = tty_release,
|
2016-01-09 22:45:10 -07:00
|
|
|
.fasync = hung_up_tty_fasync,
|
2005-04-16 16:20:36 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
static DEFINE_SPINLOCK(redirect_lock);
|
|
|
|
static struct file *redirect;
|
|
|
|
|
2014-10-16 12:59:42 -06:00
|
|
|
|
|
|
|
void proc_clear_tty(struct task_struct *p)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
struct tty_struct *tty;
|
|
|
|
spin_lock_irqsave(&p->sighand->siglock, flags);
|
|
|
|
tty = p->signal->tty;
|
|
|
|
p->signal->tty = NULL;
|
|
|
|
spin_unlock_irqrestore(&p->sighand->siglock, flags);
|
|
|
|
tty_kref_put(tty);
|
|
|
|
}
|
|
|
|
|
2014-10-16 12:59:47 -06:00
|
|
|
/**
|
|
|
|
* proc_set_tty - set the controlling terminal
|
|
|
|
*
|
|
|
|
* Only callable by the session leader and only if it does not already have
|
|
|
|
* a controlling terminal.
|
|
|
|
*
|
2014-10-16 12:59:49 -06:00
|
|
|
* Caller must hold: tty_lock()
|
|
|
|
* a readlock on tasklist_lock
|
2014-10-16 12:59:47 -06:00
|
|
|
* sighand lock
|
|
|
|
*/
|
2014-10-16 12:59:43 -06:00
|
|
|
static void __proc_set_tty(struct tty_struct *tty)
|
2014-10-16 12:59:42 -06:00
|
|
|
{
|
2014-10-16 12:59:46 -06:00
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&tty->ctrl_lock, flags);
|
2014-10-16 12:59:50 -06:00
|
|
|
/*
|
|
|
|
* The session and fg pgrp references will be non-NULL if
|
|
|
|
* tiocsctty() is stealing the controlling tty
|
|
|
|
*/
|
2014-10-16 12:59:46 -06:00
|
|
|
put_pid(tty->session);
|
|
|
|
put_pid(tty->pgrp);
|
|
|
|
tty->pgrp = get_pid(task_pgrp(current));
|
|
|
|
spin_unlock_irqrestore(&tty->ctrl_lock, flags);
|
|
|
|
tty->session = get_pid(task_session(current));
|
|
|
|
if (current->signal->tty) {
|
2015-07-12 20:49:08 -06:00
|
|
|
tty_debug(tty, "current tty %s not NULL!!\n",
|
|
|
|
current->signal->tty->name);
|
2014-10-16 12:59:46 -06:00
|
|
|
tty_kref_put(current->signal->tty);
|
2014-10-16 12:59:42 -06:00
|
|
|
}
|
2014-10-16 12:59:43 -06:00
|
|
|
put_pid(current->signal->tty_old_pgrp);
|
|
|
|
current->signal->tty = tty_kref_get(tty);
|
|
|
|
current->signal->tty_old_pgrp = NULL;
|
2014-10-16 12:59:42 -06:00
|
|
|
}
|
|
|
|
|
2014-10-16 12:59:43 -06:00
|
|
|
static void proc_set_tty(struct tty_struct *tty)
|
2014-10-16 12:59:42 -06:00
|
|
|
{
|
2014-10-16 12:59:43 -06:00
|
|
|
spin_lock_irq(¤t->sighand->siglock);
|
|
|
|
__proc_set_tty(tty);
|
|
|
|
spin_unlock_irq(¤t->sighand->siglock);
|
2014-10-16 12:59:42 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
struct tty_struct *get_current_tty(void)
|
|
|
|
{
|
|
|
|
struct tty_struct *tty;
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(¤t->sighand->siglock, flags);
|
|
|
|
tty = tty_kref_get(current->signal->tty);
|
|
|
|
spin_unlock_irqrestore(¤t->sighand->siglock, flags);
|
|
|
|
return tty;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(get_current_tty);
|
|
|
|
|
|
|
|
static void session_clear_tty(struct pid *session)
|
|
|
|
{
|
|
|
|
struct task_struct *p;
|
|
|
|
do_each_pid_task(session, PIDTYPE_SID, p) {
|
|
|
|
proc_clear_tty(p);
|
|
|
|
} while_each_pid_task(session, PIDTYPE_SID, p);
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/**
|
|
|
|
* tty_wakeup - request more data
|
|
|
|
* @tty: terminal
|
|
|
|
*
|
|
|
|
* Internal and external helper for wakeups of tty. This function
|
|
|
|
* informs the line discipline if present that the driver is ready
|
|
|
|
* to receive more output data.
|
|
|
|
*/
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
void tty_wakeup(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
struct tty_ldisc *ld;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
if (test_bit(TTY_DO_WRITE_WAKEUP, &tty->flags)) {
|
|
|
|
ld = tty_ldisc_ref(tty);
|
2008-02-08 05:18:47 -07:00
|
|
|
if (ld) {
|
2008-07-16 14:53:12 -06:00
|
|
|
if (ld->ops->write_wakeup)
|
|
|
|
ld->ops->write_wakeup(tty);
|
2005-04-16 16:20:36 -06:00
|
|
|
tty_ldisc_deref(ld);
|
|
|
|
}
|
|
|
|
}
|
2009-03-31 16:24:24 -06:00
|
|
|
wake_up_interruptible_poll(&tty->write_wait, POLLOUT);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL_GPL(tty_wakeup);
|
|
|
|
|
2013-03-06 05:20:53 -07:00
|
|
|
/**
|
|
|
|
* tty_signal_session_leader - sends SIGHUP to session leader
|
2013-03-06 05:20:56 -07:00
|
|
|
* @tty controlling tty
|
|
|
|
* @exit_session if non-zero, signal all foreground group processes
|
2013-03-06 05:20:53 -07:00
|
|
|
*
|
2013-03-06 05:20:56 -07:00
|
|
|
* Send SIGHUP and SIGCONT to the session leader and its process group.
|
|
|
|
* Optionally, signal all processes in the foreground process group.
|
2013-03-06 05:20:53 -07:00
|
|
|
*
|
|
|
|
* Returns the number of processes in the session with this tty
|
|
|
|
* as their controlling terminal. This value is used to drop
|
|
|
|
* tty references for those processes.
|
|
|
|
*/
|
2013-03-06 05:20:56 -07:00
|
|
|
static int tty_signal_session_leader(struct tty_struct *tty, int exit_session)
|
2013-03-06 05:20:53 -07:00
|
|
|
{
|
|
|
|
struct task_struct *p;
|
|
|
|
int refs = 0;
|
2013-03-06 05:20:56 -07:00
|
|
|
struct pid *tty_pgrp = NULL;
|
2013-03-06 05:20:53 -07:00
|
|
|
|
|
|
|
read_lock(&tasklist_lock);
|
|
|
|
if (tty->session) {
|
|
|
|
do_each_pid_task(tty->session, PIDTYPE_SID, p) {
|
|
|
|
spin_lock_irq(&p->sighand->siglock);
|
|
|
|
if (p->signal->tty == tty) {
|
|
|
|
p->signal->tty = NULL;
|
|
|
|
/* We defer the dereferences outside fo
|
|
|
|
the tasklist lock */
|
|
|
|
refs++;
|
|
|
|
}
|
|
|
|
if (!p->signal->leader) {
|
|
|
|
spin_unlock_irq(&p->sighand->siglock);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
__group_send_sig_info(SIGHUP, SEND_SIG_PRIV, p);
|
|
|
|
__group_send_sig_info(SIGCONT, SEND_SIG_PRIV, p);
|
|
|
|
put_pid(p->signal->tty_old_pgrp); /* A noop */
|
2013-03-06 05:20:55 -07:00
|
|
|
spin_lock(&tty->ctrl_lock);
|
2013-03-06 05:20:56 -07:00
|
|
|
tty_pgrp = get_pid(tty->pgrp);
|
2013-03-06 05:20:53 -07:00
|
|
|
if (tty->pgrp)
|
|
|
|
p->signal->tty_old_pgrp = get_pid(tty->pgrp);
|
2013-03-06 05:20:55 -07:00
|
|
|
spin_unlock(&tty->ctrl_lock);
|
2013-03-06 05:20:53 -07:00
|
|
|
spin_unlock_irq(&p->sighand->siglock);
|
|
|
|
} while_each_pid_task(tty->session, PIDTYPE_SID, p);
|
|
|
|
}
|
|
|
|
read_unlock(&tasklist_lock);
|
|
|
|
|
2013-03-06 05:20:56 -07:00
|
|
|
if (tty_pgrp) {
|
|
|
|
if (exit_session)
|
|
|
|
kill_pgrp(tty_pgrp, SIGHUP, exit_session);
|
|
|
|
put_pid(tty_pgrp);
|
|
|
|
}
|
|
|
|
|
2013-03-06 05:20:53 -07:00
|
|
|
return refs;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2010-06-18 06:58:07 -06:00
|
|
|
* __tty_hangup - actual handler for hangup events
|
2006-11-22 07:55:48 -07:00
|
|
|
* @work: tty device
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
2012-12-26 21:43:41 -07:00
|
|
|
* This can be called by a "kworker" kernel thread. That is process
|
2006-08-27 02:24:01 -06:00
|
|
|
* synchronous but doesn't hold any locks, so we need to make sure we
|
|
|
|
* have the appropriate locks for what we're doing.
|
|
|
|
*
|
|
|
|
* The hangup event clears any pending redirections onto the hung up
|
|
|
|
* device. It ensures future writes will error and it does the needed
|
|
|
|
* line discipline hangup and signal delivery. The tty object itself
|
|
|
|
* remains intact.
|
|
|
|
*
|
|
|
|
* Locking:
|
2010-06-01 14:53:01 -06:00
|
|
|
* BTM
|
2006-12-08 03:36:04 -07:00
|
|
|
* redirect lock for undoing redirection
|
|
|
|
* file list lock for manipulating list of ttys
|
2013-06-15 05:04:46 -06:00
|
|
|
* tty_ldiscs_lock from called functions
|
2013-06-15 07:14:23 -06:00
|
|
|
* termios_rwsem resetting termios data
|
2006-12-08 03:36:04 -07:00
|
|
|
* tasklist_lock to walk task list for hangup event
|
|
|
|
* ->siglock to protect ->signal/->sighand
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2013-03-06 05:20:56 -07:00
|
|
|
static void __tty_hangup(struct tty_struct *tty, int exit_session)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2008-02-08 05:18:47 -07:00
|
|
|
struct file *cons_filp = NULL;
|
2005-04-16 16:20:36 -06:00
|
|
|
struct file *filp, *f = NULL;
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
struct tty_file_private *priv;
|
2005-04-16 16:20:36 -06:00
|
|
|
int closecount = 0, n;
|
2013-03-06 05:20:53 -07:00
|
|
|
int refs;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
if (!tty)
|
|
|
|
return;
|
|
|
|
|
|
|
|
|
|
|
|
spin_lock(&redirect_lock);
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
if (redirect && file_tty(redirect) == tty) {
|
2005-04-16 16:20:36 -06:00
|
|
|
f = redirect;
|
|
|
|
redirect = NULL;
|
|
|
|
}
|
|
|
|
spin_unlock(&redirect_lock);
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_lock(tty);
|
2010-06-18 06:58:07 -06:00
|
|
|
|
tty: Only hangup once
Instrumented testing shows a tty can be hungup multiple times [1].
Although concurrent hangups are properly serialized, multiple
hangups for the same tty should be prevented.
If tty has already been HUPPED, abort hangup. Note it is not
necessary to cleanup file *redirect on subsequent hangups,
as only TIOCCONS can set that value and ioctls are disabled
after hangup.
[1]
Test performed by simulating a concurrent async hangup via
tty_hangup() with a sync hangup via tty_vhangup(), while
__tty_hangup() was instrumented with:
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index 26bb78c..fe8b061 100644
--- a/drivers/tty/tty_io.c
+++ b/drivers/tty/tty_io.c
@@ -629,6 +629,8 @@ static void __tty_hangup(struct tty_struct *tty, int exit_session)
tty_lock(tty);
+ WARN_ON(test_bit(TTY_HUPPED, &tty->flags));
+
/* some functions below drop BTM, so we need this bit */
set_bit(TTY_HUPPING, &tty->flags);
Test result:
WARNING: at /home/peter/src/kernels/mainline/drivers/tty/tty_io.c:632 __tty_hangup+0x459/0x460()
Modules linked in: ip6table_filter ip6_tables ebtable_nat <...snip...>
CPU: 6 PID: 1197 Comm: kworker/6:2 Not tainted 3.10.0-0+rfcomm-xeon #0+rfcomm
Hardware name: Dell Inc. Precision WorkStation T5400 /0RW203, BIOS A11 04/30/2012
Workqueue: events do_tty_hangup
0000000000000009 ffff8802b16d7d18 ffffffff816b553e ffff8802b16d7d58
ffffffff810407e0 ffff880254f95c00 ffff880254f95c00 ffff8802bfd92b00
ffff8802bfd96b00 ffff880254f95e40 0000000000000180 ffff8802b16d7d68
Call Trace:
[<ffffffff816b553e>] dump_stack+0x19/0x1b
[<ffffffff810407e0>] warn_slowpath_common+0x70/0xa0
[<ffffffff8104082a>] warn_slowpath_null+0x1a/0x20
[<ffffffff813fb279>] __tty_hangup+0x459/0x460
[<ffffffff8107409c>] ? finish_task_switch+0xbc/0xe0
[<ffffffff813fb297>] do_tty_hangup+0x17/0x20
[<ffffffff8105fd6f>] process_one_work+0x16f/0x450
[<ffffffff8106007c>] process_scheduled_works+0x2c/0x40
[<ffffffff8106060a>] worker_thread+0x26a/0x380
[<ffffffff810603a0>] ? rescuer_thread+0x310/0x310
[<ffffffff810698a0>] kthread+0xc0/0xd0
[<ffffffff816b0000>] ? destroy_compound_page+0x65/0x92
[<ffffffff810697e0>] ? kthread_create_on_node+0x130/0x130
[<ffffffff816c495c>] ret_from_fork+0x7c/0xb0
[<ffffffff810697e0>] ? kthread_create_on_node+0x130/0x130
---[ end trace 98d9f01536cf411e ]---
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-07-31 12:05:45 -06:00
|
|
|
if (test_bit(TTY_HUPPED, &tty->flags)) {
|
|
|
|
tty_unlock(tty);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2010-06-01 14:53:01 -06:00
|
|
|
/* inuse_filps is protected by the single tty lock,
|
|
|
|
this really needs to change if we want to flush the
|
|
|
|
workqueue with the lock held */
|
2010-06-18 06:58:07 -06:00
|
|
|
check_tty_count(tty, "tty_hangup");
|
2009-11-30 06:18:51 -07:00
|
|
|
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_lock(&tty->files_lock);
|
2005-04-16 16:20:36 -06:00
|
|
|
/* This breaks for file handles being sent over AF_UNIX sockets ? */
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
list_for_each_entry(priv, &tty->tty_files, list) {
|
|
|
|
filp = priv->file;
|
2005-04-16 16:20:36 -06:00
|
|
|
if (filp->f_op->write == redirected_tty_write)
|
|
|
|
cons_filp = filp;
|
|
|
|
if (filp->f_op->write != tty_write)
|
|
|
|
continue;
|
|
|
|
closecount++;
|
2010-06-01 14:53:01 -06:00
|
|
|
__tty_fasync(-1, filp, 0); /* can't block */
|
2005-04-16 16:20:36 -06:00
|
|
|
filp->f_op = &hung_up_tty_fops;
|
|
|
|
}
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_unlock(&tty->files_lock);
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2013-03-06 05:20:57 -07:00
|
|
|
refs = tty_signal_session_leader(tty, exit_session);
|
|
|
|
/* Account for the p->signal references we killed */
|
|
|
|
while (refs--)
|
|
|
|
tty_kref_put(tty);
|
|
|
|
|
tty: Destroy ldisc instance on hangup
Currently, when the tty is hungup, the ldisc is re-instanced; ie., the
current instance is destroyed and a new instance is created. The purpose
of this design was to guarantee a valid, open ldisc for the lifetime of
the tty.
However, now that tty buffers are owned by and have lifetime equivalent
to the tty_port (since v3.10), any data received immediately after the
ldisc is re-instanced may cause continued driver i/o operations
concurrently with the driver's hangup() operation. For drivers that
shutdown h/w on hangup, this is unexpected and usually bad. For example,
the serial core may free the xmit buffer page concurrently with an
in-progress write() operation (triggered by echo).
With the existing stable and robust ldisc reference handling, the
cleaned-up tty_reopen(), the straggling unsafe ldisc use cleaned up, and
the preparation to properly handle a NULL tty->ldisc, the ldisc instance
can be destroyed and only re-instanced when the tty is re-opened.
If the tty was opened as /dev/console or /dev/tty0, the original behavior
of re-instancing the ldisc is retained (the 'reinit' parameter to
tty_ldisc_hangup() is true). This is required since those file descriptors
are never hungup.
This patch has neglible impact on userspace; the tty file_operations ptr
is changed to point to the hungup file operations _before_ the ldisc
instance is destroyed, so only racing file operations might now retrieve
a NULL ldisc reference (which is simply handled as if the hungup file
operation had been called instead -- see "tty: Prepare for destroying
line discipline on hangup").
This resolves a long-standing FIXME and several crash reports.
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2016-01-10 23:41:06 -07:00
|
|
|
tty_ldisc_hangup(tty, cons_filp != NULL);
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2013-03-06 05:20:54 -07:00
|
|
|
spin_lock_irq(&tty->ctrl_lock);
|
2009-06-11 05:50:12 -06:00
|
|
|
clear_bit(TTY_THROTTLED, &tty->flags);
|
|
|
|
clear_bit(TTY_DO_WRITE_WAKEUP, &tty->flags);
|
2007-03-18 12:45:44 -06:00
|
|
|
put_pid(tty->session);
|
|
|
|
put_pid(tty->pgrp);
|
2007-02-12 01:53:00 -07:00
|
|
|
tty->session = NULL;
|
|
|
|
tty->pgrp = NULL;
|
2005-04-16 16:20:36 -06:00
|
|
|
tty->ctrl_status = 0;
|
2013-03-06 05:20:54 -07:00
|
|
|
spin_unlock_irq(&tty->ctrl_lock);
|
2008-10-13 03:37:26 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
2008-02-08 05:18:47 -07:00
|
|
|
* If one of the devices matches a console pointer, we
|
|
|
|
* cannot just call hangup() because that will cause
|
|
|
|
* tty->count and state->count to go out of sync.
|
|
|
|
* So we just call close() the right number of times.
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
|
|
|
if (cons_filp) {
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->close)
|
2005-04-16 16:20:36 -06:00
|
|
|
for (n = 0; n < closecount; n++)
|
2008-04-30 01:54:13 -06:00
|
|
|
tty->ops->close(tty, cons_filp);
|
|
|
|
} else if (tty->ops->hangup)
|
2014-06-16 07:17:08 -06:00
|
|
|
tty->ops->hangup(tty);
|
2008-02-08 05:18:47 -07:00
|
|
|
/*
|
tty: Destroy ldisc instance on hangup
Currently, when the tty is hungup, the ldisc is re-instanced; ie., the
current instance is destroyed and a new instance is created. The purpose
of this design was to guarantee a valid, open ldisc for the lifetime of
the tty.
However, now that tty buffers are owned by and have lifetime equivalent
to the tty_port (since v3.10), any data received immediately after the
ldisc is re-instanced may cause continued driver i/o operations
concurrently with the driver's hangup() operation. For drivers that
shutdown h/w on hangup, this is unexpected and usually bad. For example,
the serial core may free the xmit buffer page concurrently with an
in-progress write() operation (triggered by echo).
With the existing stable and robust ldisc reference handling, the
cleaned-up tty_reopen(), the straggling unsafe ldisc use cleaned up, and
the preparation to properly handle a NULL tty->ldisc, the ldisc instance
can be destroyed and only re-instanced when the tty is re-opened.
If the tty was opened as /dev/console or /dev/tty0, the original behavior
of re-instancing the ldisc is retained (the 'reinit' parameter to
tty_ldisc_hangup() is true). This is required since those file descriptors
are never hungup.
This patch has neglible impact on userspace; the tty file_operations ptr
is changed to point to the hungup file operations _before_ the ldisc
instance is destroyed, so only racing file operations might now retrieve
a NULL ldisc reference (which is simply handled as if the hungup file
operation had been called instead -- see "tty: Prepare for destroying
line discipline on hangup").
This resolves a long-standing FIXME and several crash reports.
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2016-01-10 23:41:06 -07:00
|
|
|
* We don't want to have driver/ldisc interactions beyond the ones
|
|
|
|
* we did here. The driver layer expects no calls after ->hangup()
|
|
|
|
* from the ldisc side, which is now guaranteed.
|
2008-02-08 05:18:47 -07:00
|
|
|
*/
|
2005-04-16 16:20:36 -06:00
|
|
|
set_bit(TTY_HUPPED, &tty->flags);
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_unlock(tty);
|
2010-06-18 06:58:07 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
if (f)
|
|
|
|
fput(f);
|
|
|
|
}
|
|
|
|
|
2010-06-01 14:53:08 -06:00
|
|
|
static void do_tty_hangup(struct work_struct *work)
|
|
|
|
{
|
|
|
|
struct tty_struct *tty =
|
|
|
|
container_of(work, struct tty_struct, hangup_work);
|
|
|
|
|
2013-03-06 05:20:56 -07:00
|
|
|
__tty_hangup(tty, 0);
|
2010-06-01 14:53:08 -06:00
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tty_hangup - trigger a hangup event
|
|
|
|
* @tty: tty to hangup
|
|
|
|
*
|
|
|
|
* A carrier loss (virtual or otherwise) has occurred on this like
|
|
|
|
* schedule a hangup sequence to run after this event.
|
|
|
|
*/
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
void tty_hangup(struct tty_struct *tty)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2015-11-08 11:01:19 -07:00
|
|
|
tty_debug_hangup(tty, "hangup\n");
|
2005-04-16 16:20:36 -06:00
|
|
|
schedule_work(&tty->hangup_work);
|
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(tty_hangup);
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tty_vhangup - process vhangup
|
|
|
|
* @tty: tty to hangup
|
|
|
|
*
|
|
|
|
* The user has asked via system call for the terminal to be hung up.
|
|
|
|
* We do this synchronously so that when the syscall returns the process
|
2007-10-19 15:10:43 -06:00
|
|
|
* is complete. That guarantee is necessary for security reasons.
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
void tty_vhangup(struct tty_struct *tty)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2015-11-08 11:01:19 -07:00
|
|
|
tty_debug_hangup(tty, "vhangup\n");
|
2013-03-06 05:20:56 -07:00
|
|
|
__tty_hangup(tty, 0);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
EXPORT_SYMBOL(tty_vhangup);
|
|
|
|
|
2010-06-18 06:58:07 -06:00
|
|
|
|
2008-10-13 03:40:30 -06:00
|
|
|
/**
|
|
|
|
* tty_vhangup_self - process vhangup for own ctty
|
|
|
|
*
|
|
|
|
* Perform a vhangup on the current controlling tty
|
|
|
|
*/
|
|
|
|
|
|
|
|
void tty_vhangup_self(void)
|
|
|
|
{
|
|
|
|
struct tty_struct *tty;
|
|
|
|
|
|
|
|
tty = get_current_tty();
|
|
|
|
if (tty) {
|
|
|
|
tty_vhangup(tty);
|
|
|
|
tty_kref_put(tty);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-03-06 05:20:56 -07:00
|
|
|
/**
|
|
|
|
* tty_vhangup_session - hangup session leader exit
|
|
|
|
* @tty: tty to hangup
|
|
|
|
*
|
|
|
|
* The session leader is exiting and hanging up its controlling terminal.
|
|
|
|
* Every process in the foreground process group is signalled SIGHUP.
|
|
|
|
*
|
|
|
|
* We do this synchronously so that when the syscall returns the process
|
|
|
|
* is complete. That guarantee is necessary for security reasons.
|
|
|
|
*/
|
|
|
|
|
2013-03-19 18:42:04 -06:00
|
|
|
static void tty_vhangup_session(struct tty_struct *tty)
|
2013-03-06 05:20:56 -07:00
|
|
|
{
|
2015-11-08 11:01:19 -07:00
|
|
|
tty_debug_hangup(tty, "session hangup\n");
|
2013-03-06 05:20:56 -07:00
|
|
|
__tty_hangup(tty, 1);
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tty_hung_up_p - was tty hung up
|
|
|
|
* @filp: file pointer of tty
|
|
|
|
*
|
|
|
|
* Return true if the tty has been subject to a vhangup or a carrier
|
|
|
|
* loss
|
|
|
|
*/
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
int tty_hung_up_p(struct file *filp)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
return (filp->f_op == &hung_up_tty_fops);
|
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(tty_hung_up_p);
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* disassociate_ctty - disconnect controlling tty
|
|
|
|
* @on_exit: true if exiting so need to "hang up" the session
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
2006-08-27 02:24:01 -06:00
|
|
|
* This function is typically called only by the session leader, when
|
|
|
|
* it wants to disassociate itself from its controlling tty.
|
|
|
|
*
|
|
|
|
* It performs the following functions:
|
2005-04-16 16:20:36 -06:00
|
|
|
* (1) Sends a SIGHUP and SIGCONT to the foreground process group
|
|
|
|
* (2) Clears the tty from being controlling the session
|
|
|
|
* (3) Clears the controlling tty for all processes in the
|
|
|
|
* session group.
|
|
|
|
*
|
2006-08-27 02:24:01 -06:00
|
|
|
* The argument on_exit is set to 1 if called when a process is
|
|
|
|
* exiting; it is 0 if called by the ioctl TIOCNOTTY.
|
|
|
|
*
|
2006-12-08 03:36:04 -07:00
|
|
|
* Locking:
|
2010-06-01 14:53:01 -06:00
|
|
|
* BTM is taken for hysterical raisins, and held when
|
|
|
|
* called from no_tty().
|
2006-12-08 03:36:04 -07:00
|
|
|
* tty_mutex is taken to protect tty
|
|
|
|
* ->siglock is taken to protect ->signal/->sighand
|
|
|
|
* tasklist_lock is taken to walk process list for sessions
|
|
|
|
* ->siglock is taken to protect ->signal/->sighand
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2006-08-27 02:24:01 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
void disassociate_ctty(int on_exit)
|
|
|
|
{
|
|
|
|
struct tty_struct *tty;
|
|
|
|
|
2009-11-30 06:18:45 -07:00
|
|
|
if (!current->signal->leader)
|
|
|
|
return;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2006-12-08 03:36:04 -07:00
|
|
|
tty = get_current_tty();
|
2005-04-16 16:20:36 -06:00
|
|
|
if (tty) {
|
2013-03-06 05:20:56 -07:00
|
|
|
if (on_exit && tty->driver->type != TTY_DRIVER_TYPE_PTY) {
|
|
|
|
tty_vhangup_session(tty);
|
|
|
|
} else {
|
|
|
|
struct pid *tty_pgrp = tty_get_pgrp(tty);
|
|
|
|
if (tty_pgrp) {
|
|
|
|
kill_pgrp(tty_pgrp, SIGHUP, on_exit);
|
2013-09-15 09:50:26 -06:00
|
|
|
if (!on_exit)
|
|
|
|
kill_pgrp(tty_pgrp, SIGCONT, on_exit);
|
2013-03-06 05:20:56 -07:00
|
|
|
put_pid(tty_pgrp);
|
|
|
|
}
|
2011-11-09 13:33:18 -07:00
|
|
|
}
|
2013-03-06 05:20:56 -07:00
|
|
|
tty_kref_put(tty);
|
|
|
|
|
2007-02-12 01:52:52 -07:00
|
|
|
} else if (on_exit) {
|
2007-02-12 01:53:00 -07:00
|
|
|
struct pid *old_pgrp;
|
2007-02-12 01:52:52 -07:00
|
|
|
spin_lock_irq(¤t->sighand->siglock);
|
|
|
|
old_pgrp = current->signal->tty_old_pgrp;
|
2007-02-12 01:53:00 -07:00
|
|
|
current->signal->tty_old_pgrp = NULL;
|
2007-02-12 01:52:52 -07:00
|
|
|
spin_unlock_irq(¤t->sighand->siglock);
|
2006-12-08 03:36:04 -07:00
|
|
|
if (old_pgrp) {
|
2007-02-12 01:53:00 -07:00
|
|
|
kill_pgrp(old_pgrp, SIGHUP, on_exit);
|
|
|
|
kill_pgrp(old_pgrp, SIGCONT, on_exit);
|
|
|
|
put_pid(old_pgrp);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2006-12-08 03:36:04 -07:00
|
|
|
spin_lock_irq(¤t->sighand->siglock);
|
2007-05-08 01:26:53 -06:00
|
|
|
put_pid(current->signal->tty_old_pgrp);
|
2007-02-20 14:58:05 -07:00
|
|
|
current->signal->tty_old_pgrp = NULL;
|
2006-12-08 03:36:04 -07:00
|
|
|
|
2014-04-14 21:52:51 -06:00
|
|
|
tty = tty_kref_get(current->signal->tty);
|
2006-12-08 03:36:04 -07:00
|
|
|
if (tty) {
|
2008-04-30 01:53:30 -06:00
|
|
|
unsigned long flags;
|
|
|
|
spin_lock_irqsave(&tty->ctrl_lock, flags);
|
2007-02-12 01:53:00 -07:00
|
|
|
put_pid(tty->session);
|
|
|
|
put_pid(tty->pgrp);
|
|
|
|
tty->session = NULL;
|
|
|
|
tty->pgrp = NULL;
|
2008-04-30 01:53:30 -06:00
|
|
|
spin_unlock_irqrestore(&tty->ctrl_lock, flags);
|
2008-10-13 03:39:13 -06:00
|
|
|
tty_kref_put(tty);
|
2015-07-12 20:49:09 -06:00
|
|
|
} else
|
|
|
|
tty_debug_hangup(tty, "no current tty\n");
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2014-04-14 21:52:51 -06:00
|
|
|
spin_unlock_irq(¤t->sighand->siglock);
|
2005-04-16 16:20:36 -06:00
|
|
|
/* Now clear signal->tty under the lock */
|
|
|
|
read_lock(&tasklist_lock);
|
2007-02-12 01:53:00 -07:00
|
|
|
session_clear_tty(task_session(current));
|
2005-04-16 16:20:36 -06:00
|
|
|
read_unlock(&tasklist_lock);
|
|
|
|
}
|
|
|
|
|
2007-05-08 01:26:56 -06:00
|
|
|
/**
|
|
|
|
*
|
|
|
|
* no_tty - Ensure the current process does not have a controlling tty
|
|
|
|
*/
|
|
|
|
void no_tty(void)
|
|
|
|
{
|
2012-05-03 15:21:53 -06:00
|
|
|
/* FIXME: Review locking here. The tty_lock never covered any race
|
|
|
|
between a new association and proc_clear_tty but possible we need
|
|
|
|
to protect against this anyway */
|
2007-05-08 01:26:56 -06:00
|
|
|
struct task_struct *tsk = current;
|
2009-11-30 06:18:45 -07:00
|
|
|
disassociate_ctty(0);
|
2007-05-08 01:26:56 -06:00
|
|
|
proc_clear_tty(tsk);
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
|
|
|
|
/**
|
2007-05-08 23:14:03 -06:00
|
|
|
* stop_tty - propagate flow control
|
2006-08-27 02:24:01 -06:00
|
|
|
* @tty: tty to stop
|
|
|
|
*
|
2014-09-10 13:06:32 -06:00
|
|
|
* Perform flow control to the driver. May be called
|
2006-08-27 02:24:01 -06:00
|
|
|
* on an already stopped device and will not re-call the driver
|
|
|
|
* method.
|
|
|
|
*
|
|
|
|
* This functionality is used by both the line disciplines for
|
|
|
|
* halting incoming flow and by the driver. It may therefore be
|
|
|
|
* called from any context, may be under the tty atomic_write_lock
|
|
|
|
* but not always.
|
|
|
|
*
|
|
|
|
* Locking:
|
2014-09-10 13:06:31 -06:00
|
|
|
* flow_lock
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2014-09-10 13:06:31 -06:00
|
|
|
void __stop_tty(struct tty_struct *tty)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2014-09-10 13:06:31 -06:00
|
|
|
if (tty->stopped)
|
2005-04-16 16:20:36 -06:00
|
|
|
return;
|
|
|
|
tty->stopped = 1;
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->stop)
|
2014-11-05 10:26:25 -07:00
|
|
|
tty->ops->stop(tty);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2014-09-10 13:06:31 -06:00
|
|
|
void stop_tty(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&tty->flow_lock, flags);
|
|
|
|
__stop_tty(tty);
|
|
|
|
spin_unlock_irqrestore(&tty->flow_lock, flags);
|
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
EXPORT_SYMBOL(stop_tty);
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2007-05-08 23:14:03 -06:00
|
|
|
* start_tty - propagate flow control
|
2006-08-27 02:24:01 -06:00
|
|
|
* @tty: tty to start
|
|
|
|
*
|
2014-09-10 13:06:32 -06:00
|
|
|
* Start a tty that has been stopped if at all possible. If this
|
|
|
|
* tty was previous stopped and is now being started, the driver
|
|
|
|
* start method is invoked and the line discipline woken.
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
|
|
|
* Locking:
|
2014-09-10 13:06:31 -06:00
|
|
|
* flow_lock
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2014-09-10 13:06:31 -06:00
|
|
|
void __start_tty(struct tty_struct *tty)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2014-09-10 13:06:31 -06:00
|
|
|
if (!tty->stopped || tty->flow_stopped)
|
2005-04-16 16:20:36 -06:00
|
|
|
return;
|
|
|
|
tty->stopped = 0;
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->start)
|
2014-11-05 10:26:25 -07:00
|
|
|
tty->ops->start(tty);
|
2005-04-16 16:20:36 -06:00
|
|
|
tty_wakeup(tty);
|
|
|
|
}
|
|
|
|
|
2014-09-10 13:06:31 -06:00
|
|
|
void start_tty(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&tty->flow_lock, flags);
|
|
|
|
__start_tty(tty);
|
|
|
|
spin_unlock_irqrestore(&tty->flow_lock, flags);
|
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
EXPORT_SYMBOL(start_tty);
|
|
|
|
|
2013-04-26 05:48:53 -06:00
|
|
|
static void tty_update_time(struct timespec *time)
|
|
|
|
{
|
tty: fix up atime/mtime mess, take four
This problem was taken care of three times already in
* b0de59b5733d18b0d1974a060860a8b5c1b36a2e (TTY: do not update
atime/mtime on read/write),
* 37b7f3c76595e23257f61bd80b223de8658617ee (TTY: fix atime/mtime
regression), and
* b0b885657b6c8ef63a46bc9299b2a7715d19acde (tty: fix up atime/mtime
mess, take three)
But it still misses one point. As John Paul correctly points out, we
do not care about setting date. If somebody ever changes wall
time backwards (by mistake for example), tty timestamps are never
updated until the original wall time passes.
So check the absolute difference of times and if it large than "8
seconds or so", always update the time. That means we will update
immediatelly when changing time. Ergo, CAP_SYS_TIME can foul the
check, but it was always that way.
Thanks John for serving me this so nicely debugged.
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
Reported-by: John Paul Perry <john_paul.perry@alcatel-lucent.com>
Cc: <stable@vger.kernel.org> # all, as b0b885657 was backported
Acked-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2015-02-27 10:40:31 -07:00
|
|
|
unsigned long sec = get_seconds();
|
2015-03-26 16:10:27 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* We only care if the two values differ in anything other than the
|
|
|
|
* lower three bits (i.e every 8 seconds). If so, then we can update
|
|
|
|
* the time of the tty device, otherwise it could be construded as a
|
|
|
|
* security leak to let userspace know the exact timing of the tty.
|
|
|
|
*/
|
|
|
|
if ((sec ^ time->tv_sec) & ~7)
|
2013-04-26 05:48:53 -06:00
|
|
|
time->tv_sec = sec;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tty_read - read method for tty device files
|
|
|
|
* @file: pointer to tty file
|
|
|
|
* @buf: user buffer
|
|
|
|
* @count: size of user buffer
|
|
|
|
* @ppos: unused
|
|
|
|
*
|
|
|
|
* Perform the read system call function on this terminal device. Checks
|
|
|
|
* for hung up devices before calling the line discipline method.
|
|
|
|
*
|
|
|
|
* Locking:
|
2008-04-30 01:53:30 -06:00
|
|
|
* Locks the line discipline internally while needed. Multiple
|
|
|
|
* read calls may be outstanding in parallel.
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
static ssize_t tty_read(struct file *file, char __user *buf, size_t count,
|
2005-04-16 16:20:36 -06:00
|
|
|
loff_t *ppos)
|
|
|
|
{
|
|
|
|
int i;
|
2013-04-26 05:48:53 -06:00
|
|
|
struct inode *inode = file_inode(file);
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
struct tty_struct *tty = file_tty(file);
|
2005-04-16 16:20:36 -06:00
|
|
|
struct tty_ldisc *ld;
|
|
|
|
|
2013-04-26 05:48:53 -06:00
|
|
|
if (tty_paranoia_check(tty, inode, "tty_read"))
|
2005-04-16 16:20:36 -06:00
|
|
|
return -EIO;
|
|
|
|
if (!tty || (test_bit(TTY_IO_ERROR, &tty->flags)))
|
|
|
|
return -EIO;
|
|
|
|
|
|
|
|
/* We want to wait for the line discipline to sort out in this
|
|
|
|
situation */
|
|
|
|
ld = tty_ldisc_ref_wait(tty);
|
2016-01-10 23:41:01 -07:00
|
|
|
if (!ld)
|
|
|
|
return hung_up_tty_read(file, buf, count, ppos);
|
2008-07-16 14:53:12 -06:00
|
|
|
if (ld->ops->read)
|
2014-11-05 10:26:25 -07:00
|
|
|
i = ld->ops->read(tty, file, buf, count);
|
2005-04-16 16:20:36 -06:00
|
|
|
else
|
|
|
|
i = -EIO;
|
|
|
|
tty_ldisc_deref(ld);
|
2013-02-15 07:25:05 -07:00
|
|
|
|
2013-04-26 05:48:53 -06:00
|
|
|
if (i > 0)
|
|
|
|
tty_update_time(&inode->i_atime);
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
return i;
|
|
|
|
}
|
|
|
|
|
2014-09-10 13:06:34 -06:00
|
|
|
static void tty_write_unlock(struct tty_struct *tty)
|
2007-07-16 00:39:43 -06:00
|
|
|
{
|
|
|
|
mutex_unlock(&tty->atomic_write_lock);
|
2009-03-31 16:24:24 -06:00
|
|
|
wake_up_interruptible_poll(&tty->write_wait, POLLOUT);
|
2007-07-16 00:39:43 -06:00
|
|
|
}
|
|
|
|
|
2014-09-10 13:06:34 -06:00
|
|
|
static int tty_write_lock(struct tty_struct *tty, int ndelay)
|
2007-07-16 00:39:43 -06:00
|
|
|
{
|
|
|
|
if (!mutex_trylock(&tty->atomic_write_lock)) {
|
|
|
|
if (ndelay)
|
|
|
|
return -EAGAIN;
|
|
|
|
if (mutex_lock_interruptible(&tty->atomic_write_lock))
|
|
|
|
return -ERESTARTSYS;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* Split writes up in sane blocksizes to avoid
|
|
|
|
* denial-of-service type attacks
|
|
|
|
*/
|
|
|
|
static inline ssize_t do_tty_write(
|
|
|
|
ssize_t (*write)(struct tty_struct *, struct file *, const unsigned char *, size_t),
|
|
|
|
struct tty_struct *tty,
|
|
|
|
struct file *file,
|
|
|
|
const char __user *buf,
|
|
|
|
size_t count)
|
|
|
|
{
|
2007-07-16 00:39:43 -06:00
|
|
|
ssize_t ret, written = 0;
|
2005-04-16 16:20:36 -06:00
|
|
|
unsigned int chunk;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2007-07-16 00:39:43 -06:00
|
|
|
ret = tty_write_lock(tty, file->f_flags & O_NDELAY);
|
|
|
|
if (ret < 0)
|
|
|
|
return ret;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* We chunk up writes into a temporary buffer. This
|
|
|
|
* simplifies low-level drivers immensely, since they
|
|
|
|
* don't have locking issues and user mode accesses.
|
|
|
|
*
|
|
|
|
* But if TTY_NO_WRITE_SPLIT is set, we should use a
|
|
|
|
* big chunk-size..
|
|
|
|
*
|
|
|
|
* The default chunk-size is 2kB, because the NTTY
|
|
|
|
* layer has problems with bigger chunks. It will
|
|
|
|
* claim to be able to handle more characters than
|
|
|
|
* it actually does.
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
|
|
|
* FIXME: This can probably go away now except that 64K chunks
|
|
|
|
* are too likely to fail unless switched to vmalloc...
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
|
|
|
chunk = 2048;
|
|
|
|
if (test_bit(TTY_NO_WRITE_SPLIT, &tty->flags))
|
|
|
|
chunk = 65536;
|
|
|
|
if (count < chunk)
|
|
|
|
chunk = count;
|
|
|
|
|
2006-03-23 04:00:31 -07:00
|
|
|
/* write_buf/write_cnt is protected by the atomic_write_lock mutex */
|
2005-04-16 16:20:36 -06:00
|
|
|
if (tty->write_cnt < chunk) {
|
2008-10-13 03:45:36 -06:00
|
|
|
unsigned char *buf_chunk;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
if (chunk < 1024)
|
|
|
|
chunk = 1024;
|
|
|
|
|
2008-10-13 03:45:36 -06:00
|
|
|
buf_chunk = kmalloc(chunk, GFP_KERNEL);
|
|
|
|
if (!buf_chunk) {
|
2007-07-16 00:39:43 -06:00
|
|
|
ret = -ENOMEM;
|
|
|
|
goto out;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
kfree(tty->write_buf);
|
|
|
|
tty->write_cnt = chunk;
|
2008-10-13 03:45:36 -06:00
|
|
|
tty->write_buf = buf_chunk;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Do the write .. */
|
|
|
|
for (;;) {
|
|
|
|
size_t size = count;
|
|
|
|
if (size > chunk)
|
|
|
|
size = chunk;
|
|
|
|
ret = -EFAULT;
|
|
|
|
if (copy_from_user(tty->write_buf, buf, size))
|
|
|
|
break;
|
|
|
|
ret = write(tty, file, tty->write_buf, size);
|
|
|
|
if (ret <= 0)
|
|
|
|
break;
|
|
|
|
written += ret;
|
|
|
|
buf += ret;
|
|
|
|
count -= ret;
|
|
|
|
if (!count)
|
|
|
|
break;
|
|
|
|
ret = -ERESTARTSYS;
|
|
|
|
if (signal_pending(current))
|
|
|
|
break;
|
|
|
|
cond_resched();
|
|
|
|
}
|
2013-04-26 05:48:53 -06:00
|
|
|
if (written) {
|
|
|
|
tty_update_time(&file_inode(file)->i_mtime);
|
2005-04-16 16:20:36 -06:00
|
|
|
ret = written;
|
2013-04-26 05:48:53 -06:00
|
|
|
}
|
2007-07-16 00:39:43 -06:00
|
|
|
out:
|
|
|
|
tty_write_unlock(tty);
|
2005-04-16 16:20:36 -06:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2008-10-13 03:39:23 -06:00
|
|
|
/**
|
|
|
|
* tty_write_message - write a message to a certain tty, not just the console.
|
|
|
|
* @tty: the destination tty_struct
|
|
|
|
* @msg: the message to write
|
|
|
|
*
|
|
|
|
* This is used for messages that need to be redirected to a specific tty.
|
|
|
|
* We don't put it into the syslog queue right now maybe in the future if
|
|
|
|
* really needed.
|
|
|
|
*
|
2010-06-01 14:53:01 -06:00
|
|
|
* We must still hold the BTM and test the CLOSING flag for the moment.
|
2008-10-13 03:39:23 -06:00
|
|
|
*/
|
|
|
|
|
|
|
|
void tty_write_message(struct tty_struct *tty, char *msg)
|
|
|
|
{
|
|
|
|
if (tty) {
|
|
|
|
mutex_lock(&tty->atomic_write_lock);
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_lock(tty);
|
2015-10-10 18:28:44 -06:00
|
|
|
if (tty->ops->write && tty->count > 0)
|
2008-10-13 03:39:23 -06:00
|
|
|
tty->ops->write(tty, msg, strlen(msg));
|
2015-10-10 18:28:44 -06:00
|
|
|
tty_unlock(tty);
|
2008-10-13 03:39:23 -06:00
|
|
|
tty_write_unlock(tty);
|
|
|
|
}
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tty_write - write method for tty device file
|
|
|
|
* @file: tty file pointer
|
|
|
|
* @buf: user data to write
|
|
|
|
* @count: bytes to write
|
|
|
|
* @ppos: unused
|
|
|
|
*
|
|
|
|
* Write data to a tty device via the line discipline.
|
|
|
|
*
|
|
|
|
* Locking:
|
|
|
|
* Locks the line discipline as required
|
|
|
|
* Writes to the tty driver are serialized by the atomic_write_lock
|
|
|
|
* and are then processed in chunks to the device. The line discipline
|
2009-01-02 06:40:53 -07:00
|
|
|
* write method will not be invoked in parallel for each device.
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
static ssize_t tty_write(struct file *file, const char __user *buf,
|
|
|
|
size_t count, loff_t *ppos)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
struct tty_struct *tty = file_tty(file);
|
|
|
|
struct tty_ldisc *ld;
|
2005-04-16 16:20:36 -06:00
|
|
|
ssize_t ret;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2013-02-27 14:59:05 -07:00
|
|
|
if (tty_paranoia_check(tty, file_inode(file), "tty_write"))
|
2005-04-16 16:20:36 -06:00
|
|
|
return -EIO;
|
2008-04-30 01:54:13 -06:00
|
|
|
if (!tty || !tty->ops->write ||
|
2008-02-08 05:18:47 -07:00
|
|
|
(test_bit(TTY_IO_ERROR, &tty->flags)))
|
|
|
|
return -EIO;
|
2008-04-30 01:54:13 -06:00
|
|
|
/* Short term debug to catch buggy drivers */
|
|
|
|
if (tty->ops->write_room == NULL)
|
2015-11-08 11:01:13 -07:00
|
|
|
tty_err(tty, "missing write_room method\n");
|
2008-02-08 05:18:47 -07:00
|
|
|
ld = tty_ldisc_ref_wait(tty);
|
2016-01-10 23:41:01 -07:00
|
|
|
if (!ld)
|
|
|
|
return hung_up_tty_write(file, buf, count, ppos);
|
2008-07-16 14:53:12 -06:00
|
|
|
if (!ld->ops->write)
|
2005-04-16 16:20:36 -06:00
|
|
|
ret = -EIO;
|
|
|
|
else
|
2008-07-16 14:53:12 -06:00
|
|
|
ret = do_tty_write(ld->ops->write, tty, file, buf, count);
|
2005-04-16 16:20:36 -06:00
|
|
|
tty_ldisc_deref(ld);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
ssize_t redirected_tty_write(struct file *file, const char __user *buf,
|
|
|
|
size_t count, loff_t *ppos)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
struct file *p = NULL;
|
|
|
|
|
|
|
|
spin_lock(&redirect_lock);
|
2012-08-27 12:48:26 -06:00
|
|
|
if (redirect)
|
|
|
|
p = get_file(redirect);
|
2005-04-16 16:20:36 -06:00
|
|
|
spin_unlock(&redirect_lock);
|
|
|
|
|
|
|
|
if (p) {
|
|
|
|
ssize_t res;
|
|
|
|
res = vfs_write(p, buf, count, &p->f_pos);
|
|
|
|
fput(p);
|
|
|
|
return res;
|
|
|
|
}
|
|
|
|
return tty_write(file, buf, count, ppos);
|
|
|
|
}
|
|
|
|
|
2014-09-10 13:06:34 -06:00
|
|
|
/**
|
|
|
|
* tty_send_xchar - send priority character
|
|
|
|
*
|
|
|
|
* Send a high priority character to the tty even if stopped
|
|
|
|
*
|
|
|
|
* Locking: none for xchar method, write ordering for write method.
|
|
|
|
*/
|
|
|
|
|
|
|
|
int tty_send_xchar(struct tty_struct *tty, char ch)
|
|
|
|
{
|
|
|
|
int was_stopped = tty->stopped;
|
|
|
|
|
|
|
|
if (tty->ops->send_xchar) {
|
2015-11-11 06:03:54 -07:00
|
|
|
down_read(&tty->termios_rwsem);
|
2014-09-10 13:06:34 -06:00
|
|
|
tty->ops->send_xchar(tty, ch);
|
2015-11-11 06:03:54 -07:00
|
|
|
up_read(&tty->termios_rwsem);
|
2014-09-10 13:06:34 -06:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (tty_write_lock(tty, 0) < 0)
|
|
|
|
return -ERESTARTSYS;
|
|
|
|
|
2015-11-11 06:03:54 -07:00
|
|
|
down_read(&tty->termios_rwsem);
|
2014-09-10 13:06:34 -06:00
|
|
|
if (was_stopped)
|
|
|
|
start_tty(tty);
|
|
|
|
tty->ops->write(tty, &ch, 1);
|
|
|
|
if (was_stopped)
|
|
|
|
stop_tty(tty);
|
2015-11-11 06:03:54 -07:00
|
|
|
up_read(&tty->termios_rwsem);
|
2014-09-10 13:06:34 -06:00
|
|
|
tty_write_unlock(tty);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static char ptychar[] = "pqrstuvwxyzabcde";
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* pty_line_name - generate name for a pty
|
|
|
|
* @driver: the tty driver in use
|
|
|
|
* @index: the minor number
|
|
|
|
* @p: output buffer of at least 6 bytes
|
|
|
|
*
|
|
|
|
* Generate a name from a driver reference and write it to the output
|
|
|
|
* buffer.
|
|
|
|
*
|
|
|
|
* Locking: None
|
|
|
|
*/
|
|
|
|
static void pty_line_name(struct tty_driver *driver, int index, char *p)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
int i = index + driver->name_base;
|
|
|
|
/* ->name is initialized to "ttyp", but "tty" is expected */
|
|
|
|
sprintf(p, "%s%c%x",
|
2008-02-08 05:18:47 -07:00
|
|
|
driver->subtype == PTY_TYPE_SLAVE ? "tty" : driver->name,
|
|
|
|
ptychar[i >> 4 & 0xf], i & 0xf);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2008-10-13 03:42:19 -06:00
|
|
|
* tty_line_name - generate name for a tty
|
2006-08-27 02:24:01 -06:00
|
|
|
* @driver: the tty driver in use
|
|
|
|
* @index: the minor number
|
|
|
|
* @p: output buffer of at least 7 bytes
|
|
|
|
*
|
|
|
|
* Generate a name from a driver reference and write it to the output
|
2014-02-22 15:31:04 -07:00
|
|
|
* buffer.
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
|
|
|
* Locking: None
|
|
|
|
*/
|
2014-02-27 04:30:51 -07:00
|
|
|
static ssize_t tty_line_name(struct tty_driver *driver, int index, char *p)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2012-08-08 14:26:43 -06:00
|
|
|
if (driver->flags & TTY_DRIVER_UNNUMBERED_NODE)
|
2014-02-27 04:30:51 -07:00
|
|
|
return sprintf(p, "%s", driver->name);
|
2012-08-08 14:26:43 -06:00
|
|
|
else
|
2014-02-27 04:30:51 -07:00
|
|
|
return sprintf(p, "%s%d", driver->name,
|
|
|
|
index + driver->name_base);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2008-10-13 03:42:00 -06:00
|
|
|
/**
|
|
|
|
* tty_driver_lookup_tty() - find an existing tty, if any
|
|
|
|
* @driver: the driver for the tty
|
|
|
|
* @idx: the minor number
|
2008-10-13 03:41:51 -06:00
|
|
|
*
|
2014-11-05 10:12:51 -07:00
|
|
|
* Return the tty, if found. If not found, return NULL or ERR_PTR() if the
|
|
|
|
* driver lookup() method returns an error.
|
2008-10-13 03:41:51 -06:00
|
|
|
*
|
2014-11-05 10:12:51 -07:00
|
|
|
* Locking: tty_mutex must be held. If the tty is found, bump the tty kref.
|
2008-10-13 03:41:51 -06:00
|
|
|
*/
|
2009-01-02 06:43:04 -07:00
|
|
|
static struct tty_struct *tty_driver_lookup_tty(struct tty_driver *driver,
|
2008-10-13 03:42:59 -06:00
|
|
|
struct inode *inode, int idx)
|
2008-10-13 03:41:51 -06:00
|
|
|
{
|
2014-11-05 10:12:51 -07:00
|
|
|
struct tty_struct *tty;
|
|
|
|
|
2008-10-13 03:42:00 -06:00
|
|
|
if (driver->ops->lookup)
|
2014-11-05 10:12:51 -07:00
|
|
|
tty = driver->ops->lookup(driver, inode, idx);
|
|
|
|
else
|
|
|
|
tty = driver->ttys[idx];
|
2008-10-13 03:41:51 -06:00
|
|
|
|
2014-11-05 10:12:51 -07:00
|
|
|
if (!IS_ERR(tty))
|
|
|
|
tty_kref_get(tty);
|
|
|
|
return tty;
|
2008-10-13 03:41:51 -06:00
|
|
|
}
|
|
|
|
|
2008-10-13 03:42:39 -06:00
|
|
|
/**
|
|
|
|
* tty_init_termios - helper for termios setup
|
|
|
|
* @tty: the tty to set up
|
|
|
|
*
|
|
|
|
* Initialise the termios structures for this tty. Thus runs under
|
|
|
|
* the tty_mutex currently so we can be relaxed about ordering.
|
|
|
|
*/
|
|
|
|
|
2016-01-09 22:13:48 -07:00
|
|
|
void tty_init_termios(struct tty_struct *tty)
|
2008-10-13 03:42:39 -06:00
|
|
|
{
|
2008-10-13 03:44:08 -06:00
|
|
|
struct ktermios *tp;
|
2008-10-13 03:42:39 -06:00
|
|
|
int idx = tty->index;
|
|
|
|
|
2012-07-17 10:06:57 -06:00
|
|
|
if (tty->driver->flags & TTY_DRIVER_RESET_TERMIOS)
|
|
|
|
tty->termios = tty->driver->init_termios;
|
|
|
|
else {
|
|
|
|
/* Check for lazy saved data */
|
|
|
|
tp = tty->driver->termios[idx];
|
2016-01-10 23:40:57 -07:00
|
|
|
if (tp != NULL) {
|
2012-07-17 10:06:57 -06:00
|
|
|
tty->termios = *tp;
|
2016-01-10 23:40:57 -07:00
|
|
|
tty->termios.c_line = tty->driver->init_termios.c_line;
|
|
|
|
} else
|
2012-07-17 10:06:57 -06:00
|
|
|
tty->termios = tty->driver->init_termios;
|
2008-10-13 03:42:39 -06:00
|
|
|
}
|
|
|
|
/* Compatibility until drivers always set this */
|
2012-07-14 08:31:47 -06:00
|
|
|
tty->termios.c_ispeed = tty_termios_input_baud_rate(&tty->termios);
|
|
|
|
tty->termios.c_ospeed = tty_termios_baud_rate(&tty->termios);
|
2008-10-13 03:42:39 -06:00
|
|
|
}
|
2009-09-19 14:13:33 -06:00
|
|
|
EXPORT_SYMBOL_GPL(tty_init_termios);
|
2008-10-13 03:42:39 -06:00
|
|
|
|
2012-01-30 13:14:28 -07:00
|
|
|
int tty_standard_install(struct tty_driver *driver, struct tty_struct *tty)
|
|
|
|
{
|
2016-01-09 22:13:48 -07:00
|
|
|
tty_init_termios(tty);
|
2012-01-30 13:14:28 -07:00
|
|
|
tty_driver_kref_get(driver);
|
|
|
|
tty->count++;
|
|
|
|
driver->ttys[tty->index] = tty;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(tty_standard_install);
|
|
|
|
|
2008-10-13 03:42:00 -06:00
|
|
|
/**
|
2008-10-13 03:42:19 -06:00
|
|
|
* tty_driver_install_tty() - install a tty entry in the driver
|
|
|
|
* @driver: the driver for the tty
|
|
|
|
* @tty: the tty
|
|
|
|
*
|
|
|
|
* Install a tty object into the driver tables. The tty->index field
|
2008-10-13 03:42:39 -06:00
|
|
|
* will be set by the time this is called. This method is responsible
|
|
|
|
* for ensuring any need additional structures are allocated and
|
|
|
|
* configured.
|
2008-10-13 03:42:19 -06:00
|
|
|
*
|
|
|
|
* Locking: tty_mutex for now
|
|
|
|
*/
|
|
|
|
static int tty_driver_install_tty(struct tty_driver *driver,
|
|
|
|
struct tty_struct *tty)
|
|
|
|
{
|
2012-01-30 13:14:28 -07:00
|
|
|
return driver->ops->install ? driver->ops->install(driver, tty) :
|
|
|
|
tty_standard_install(driver, tty);
|
2008-10-13 03:42:19 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* tty_driver_remove_tty() - remove a tty from the driver tables
|
|
|
|
* @driver: the driver for the tty
|
|
|
|
* @idx: the minor number
|
|
|
|
*
|
|
|
|
* Remvoe a tty object from the driver tables. The tty->index field
|
|
|
|
* will be set by the time this is called.
|
|
|
|
*
|
|
|
|
* Locking: tty_mutex for now
|
|
|
|
*/
|
2016-01-09 22:13:49 -07:00
|
|
|
static void tty_driver_remove_tty(struct tty_driver *driver, struct tty_struct *tty)
|
2008-10-13 03:42:19 -06:00
|
|
|
{
|
|
|
|
if (driver->ops->remove)
|
|
|
|
driver->ops->remove(driver, tty);
|
|
|
|
else
|
|
|
|
driver->ttys[tty->index] = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* tty_reopen() - fast re-open of an open tty
|
|
|
|
* @tty - the tty to open
|
2008-10-13 03:41:51 -06:00
|
|
|
*
|
2008-10-13 03:42:00 -06:00
|
|
|
* Return 0 on success, -errno on error.
|
2014-11-05 10:12:47 -07:00
|
|
|
* Re-opens on master ptys are not allowed and return -EIO.
|
2008-10-13 03:41:51 -06:00
|
|
|
*
|
2014-11-05 10:12:47 -07:00
|
|
|
* Locking: Caller must hold tty_lock
|
2008-10-13 03:41:51 -06:00
|
|
|
*/
|
2008-10-13 03:42:00 -06:00
|
|
|
static int tty_reopen(struct tty_struct *tty)
|
2008-10-13 03:41:51 -06:00
|
|
|
{
|
|
|
|
struct tty_driver *driver = tty->driver;
|
|
|
|
|
|
|
|
if (driver->type == TTY_DRIVER_TYPE_PTY &&
|
2014-11-05 10:12:47 -07:00
|
|
|
driver->subtype == PTY_TYPE_MASTER)
|
|
|
|
return -EIO;
|
2008-10-13 03:41:51 -06:00
|
|
|
|
2016-01-09 22:13:45 -07:00
|
|
|
if (!tty->count)
|
|
|
|
return -EAGAIN;
|
|
|
|
|
2014-12-30 08:39:25 -07:00
|
|
|
if (test_bit(TTY_EXCLUSIVE, &tty->flags) && !capable(CAP_SYS_ADMIN))
|
|
|
|
return -EBUSY;
|
|
|
|
|
2008-10-13 03:41:51 -06:00
|
|
|
tty->count++;
|
|
|
|
|
tty: Destroy ldisc instance on hangup
Currently, when the tty is hungup, the ldisc is re-instanced; ie., the
current instance is destroyed and a new instance is created. The purpose
of this design was to guarantee a valid, open ldisc for the lifetime of
the tty.
However, now that tty buffers are owned by and have lifetime equivalent
to the tty_port (since v3.10), any data received immediately after the
ldisc is re-instanced may cause continued driver i/o operations
concurrently with the driver's hangup() operation. For drivers that
shutdown h/w on hangup, this is unexpected and usually bad. For example,
the serial core may free the xmit buffer page concurrently with an
in-progress write() operation (triggered by echo).
With the existing stable and robust ldisc reference handling, the
cleaned-up tty_reopen(), the straggling unsafe ldisc use cleaned up, and
the preparation to properly handle a NULL tty->ldisc, the ldisc instance
can be destroyed and only re-instanced when the tty is re-opened.
If the tty was opened as /dev/console or /dev/tty0, the original behavior
of re-instancing the ldisc is retained (the 'reinit' parameter to
tty_ldisc_hangup() is true). This is required since those file descriptors
are never hungup.
This patch has neglible impact on userspace; the tty file_operations ptr
is changed to point to the hungup file operations _before_ the ldisc
instance is destroyed, so only racing file operations might now retrieve
a NULL ldisc reference (which is simply handled as if the hungup file
operation had been called instead -- see "tty: Prepare for destroying
line discipline on hangup").
This resolves a long-standing FIXME and several crash reports.
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2016-01-10 23:41:06 -07:00
|
|
|
if (!tty->ldisc)
|
|
|
|
return tty_ldisc_reinit(tty, tty->termios.c_line);
|
2008-10-13 03:41:51 -06:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2008-10-13 03:41:42 -06:00
|
|
|
* tty_init_dev - initialise a tty device
|
2006-08-27 02:24:01 -06:00
|
|
|
* @driver: tty driver we are opening a device on
|
|
|
|
* @idx: device index
|
2008-10-13 03:41:03 -06:00
|
|
|
* @ret_tty: returned tty structure
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
|
|
|
* Prepare a tty device. This may not be a "new" clean device but
|
|
|
|
* could also be an active device. The pty drivers require special
|
|
|
|
* handling because of this.
|
|
|
|
*
|
|
|
|
* Locking:
|
|
|
|
* The function is called under the tty_mutex, which
|
|
|
|
* protects us from the tty struct or driver itself going away.
|
|
|
|
*
|
|
|
|
* On exit the tty device has the line discipline attached and
|
|
|
|
* a reference count of 1. If a pair was created for pty/tty use
|
|
|
|
* and the other was a pty master then it too has a reference count of 1.
|
|
|
|
*
|
2005-04-16 16:20:36 -06:00
|
|
|
* WSH 06/09/97: Rewritten to remove races and properly clean up after a
|
2006-03-23 04:00:31 -07:00
|
|
|
* failed open. The new code protects the open with a mutex, so it's
|
|
|
|
* really quite straightforward. The mutex locking can probably be
|
2005-04-16 16:20:36 -06:00
|
|
|
* relaxed for the (most common) case of reopening a tty.
|
|
|
|
*/
|
2006-08-27 02:24:01 -06:00
|
|
|
|
2012-01-05 02:04:21 -07:00
|
|
|
struct tty_struct *tty_init_dev(struct tty_driver *driver, int idx)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2008-10-13 03:42:39 -06:00
|
|
|
struct tty_struct *tty;
|
2008-10-13 03:42:29 -06:00
|
|
|
int retval;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* First time open is complex, especially for PTY devices.
|
|
|
|
* This code guarantees that either everything succeeds and the
|
|
|
|
* TTY is ready for operation, or else the table slots are vacated
|
2008-02-08 05:18:47 -07:00
|
|
|
* and the allocated memory released. (Except that the termios
|
2005-04-16 16:20:36 -06:00
|
|
|
* and locked termios may be retained.)
|
|
|
|
*/
|
|
|
|
|
2008-10-13 03:42:29 -06:00
|
|
|
if (!try_module_get(driver->owner))
|
|
|
|
return ERR_PTR(-ENODEV);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2014-07-10 13:01:22 -06:00
|
|
|
tty = alloc_tty_struct(driver, idx);
|
2011-03-23 03:48:32 -06:00
|
|
|
if (!tty) {
|
|
|
|
retval = -ENOMEM;
|
|
|
|
goto err_module_put;
|
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_lock(tty);
|
2008-10-13 03:42:29 -06:00
|
|
|
retval = tty_driver_install_tty(driver, tty);
|
2011-03-23 03:48:32 -06:00
|
|
|
if (retval < 0)
|
2016-01-09 22:13:46 -07:00
|
|
|
goto err_free_tty;
|
2008-10-13 03:42:19 -06:00
|
|
|
|
2012-06-04 05:35:36 -06:00
|
|
|
if (!tty->port)
|
|
|
|
tty->port = driver->ports[idx];
|
|
|
|
|
2012-08-17 06:27:52 -06:00
|
|
|
WARN_RATELIMIT(!tty->port,
|
|
|
|
"%s: %s driver does not set tty->port. This will crash the kernel later. Fix the driver!\n",
|
|
|
|
__func__, tty->driver->name);
|
|
|
|
|
2012-10-18 14:26:46 -06:00
|
|
|
tty->port->itty = tty;
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
/*
|
2005-04-16 16:20:36 -06:00
|
|
|
* Structures all installed ... call the ldisc open routines.
|
2007-02-10 02:46:46 -07:00
|
|
|
* If we fail here just call release_tty to clean up. No need
|
|
|
|
* to decrement the use counts, as release_tty doesn't care.
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2008-10-13 03:42:39 -06:00
|
|
|
retval = tty_ldisc_setup(tty, tty->link);
|
2008-07-22 04:16:55 -06:00
|
|
|
if (retval)
|
2011-03-23 03:48:32 -06:00
|
|
|
goto err_release_tty;
|
2012-08-08 09:30:13 -06:00
|
|
|
/* Return the tty locked so that it cannot vanish under the caller */
|
2008-10-13 03:42:29 -06:00
|
|
|
return tty;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2016-01-09 22:13:46 -07:00
|
|
|
err_free_tty:
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_unlock(tty);
|
2011-03-23 03:48:32 -06:00
|
|
|
free_tty_struct(tty);
|
|
|
|
err_module_put:
|
2005-04-16 16:20:36 -06:00
|
|
|
module_put(driver->owner);
|
2011-03-23 03:48:32 -06:00
|
|
|
return ERR_PTR(retval);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2007-02-10 02:46:46 -07:00
|
|
|
/* call the tty release_tty routine to clean out this slot */
|
2011-03-23 03:48:32 -06:00
|
|
|
err_release_tty:
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_unlock(tty);
|
2015-11-08 11:01:13 -07:00
|
|
|
tty_info_ratelimited(tty, "ldisc open failed (%d), clearing slot %d\n",
|
|
|
|
retval, idx);
|
2007-02-10 02:46:46 -07:00
|
|
|
release_tty(tty, idx);
|
2008-10-13 03:42:29 -06:00
|
|
|
return ERR_PTR(retval);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2016-01-09 22:13:48 -07:00
|
|
|
static void tty_free_termios(struct tty_struct *tty)
|
2008-10-13 03:41:30 -06:00
|
|
|
{
|
|
|
|
struct ktermios *tp;
|
|
|
|
int idx = tty->index;
|
2012-07-17 10:06:57 -06:00
|
|
|
|
|
|
|
/* If the port is going to reset then it has no termios to save */
|
|
|
|
if (tty->driver->flags & TTY_DRIVER_RESET_TERMIOS)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* Stash the termios data */
|
|
|
|
tp = tty->driver->termios[idx];
|
|
|
|
if (tp == NULL) {
|
|
|
|
tp = kmalloc(sizeof(struct ktermios), GFP_KERNEL);
|
2015-11-08 11:01:11 -07:00
|
|
|
if (tp == NULL)
|
2012-07-17 10:06:57 -06:00
|
|
|
return;
|
2012-07-24 05:51:52 -06:00
|
|
|
tty->driver->termios[idx] = tp;
|
2008-10-13 03:41:30 -06:00
|
|
|
}
|
2012-07-17 10:06:57 -06:00
|
|
|
*tp = tty->termios;
|
2008-10-13 03:41:30 -06:00
|
|
|
}
|
|
|
|
|
2013-03-11 14:44:35 -06:00
|
|
|
/**
|
2014-11-05 10:12:57 -07:00
|
|
|
* tty_flush_works - flush all works of a tty/pty pair
|
|
|
|
* @tty: tty device to flush works for (or either end of a pty pair)
|
2013-03-11 14:44:35 -06:00
|
|
|
*
|
2014-11-05 10:12:57 -07:00
|
|
|
* Sync flush all works belonging to @tty (and the 'other' tty).
|
2013-03-11 14:44:35 -06:00
|
|
|
*/
|
|
|
|
static void tty_flush_works(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
flush_work(&tty->SAK_work);
|
|
|
|
flush_work(&tty->hangup_work);
|
2014-11-05 10:12:57 -07:00
|
|
|
if (tty->link) {
|
|
|
|
flush_work(&tty->link->SAK_work);
|
|
|
|
flush_work(&tty->link->hangup_work);
|
|
|
|
}
|
2013-03-11 14:44:35 -06:00
|
|
|
}
|
2008-10-13 03:41:30 -06:00
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2007-02-10 02:46:46 -07:00
|
|
|
* release_one_tty - release tty structure memory
|
2008-10-13 03:37:26 -06:00
|
|
|
* @kref: kref of tty we are obliterating
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
|
|
|
* Releases memory associated with a tty structure, and clears out the
|
|
|
|
* driver table slots. This function is called when a device is no longer
|
|
|
|
* in use. It also gets called when setup of a device fails.
|
|
|
|
*
|
|
|
|
* Locking:
|
|
|
|
* takes the file list lock internally when working on the list
|
|
|
|
* of ttys that the driver keeps.
|
2009-09-19 14:13:22 -06:00
|
|
|
*
|
|
|
|
* This method gets called from a work queue so that the driver private
|
2009-09-27 10:00:42 -06:00
|
|
|
* cleanup ops can sleep (needed for USB at least)
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2009-09-19 14:13:22 -06:00
|
|
|
static void release_one_tty(struct work_struct *work)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2009-09-19 14:13:22 -06:00
|
|
|
struct tty_struct *tty =
|
|
|
|
container_of(work, struct tty_struct, hangup_work);
|
2008-10-13 03:37:36 -06:00
|
|
|
struct tty_driver *driver = tty->driver;
|
2014-08-07 14:26:15 -06:00
|
|
|
struct module *owner = driver->owner;
|
2007-02-10 02:46:46 -07:00
|
|
|
|
2009-09-27 10:00:42 -06:00
|
|
|
if (tty->ops->cleanup)
|
|
|
|
tty->ops->cleanup(tty);
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
tty->magic = 0;
|
2008-10-13 03:42:09 -06:00
|
|
|
tty_driver_kref_put(driver);
|
2014-08-07 14:26:15 -06:00
|
|
|
module_put(owner);
|
2007-02-10 02:46:46 -07:00
|
|
|
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_lock(&tty->files_lock);
|
2005-04-16 16:20:36 -06:00
|
|
|
list_del_init(&tty->tty_files);
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_unlock(&tty->files_lock);
|
2007-02-10 02:46:46 -07:00
|
|
|
|
2010-04-02 10:05:12 -06:00
|
|
|
put_pid(tty->pgrp);
|
|
|
|
put_pid(tty->session);
|
2005-04-16 16:20:36 -06:00
|
|
|
free_tty_struct(tty);
|
|
|
|
}
|
|
|
|
|
2009-09-19 14:13:22 -06:00
|
|
|
static void queue_release_one_tty(struct kref *kref)
|
|
|
|
{
|
|
|
|
struct tty_struct *tty = container_of(kref, struct tty_struct, kref);
|
2009-09-27 10:00:42 -06:00
|
|
|
|
2009-09-19 14:13:22 -06:00
|
|
|
/* The hangup queue is now free so we can reuse it rather than
|
|
|
|
waste a chunk of memory for each port */
|
|
|
|
INIT_WORK(&tty->hangup_work, release_one_tty);
|
|
|
|
schedule_work(&tty->hangup_work);
|
|
|
|
}
|
|
|
|
|
2008-10-13 03:37:26 -06:00
|
|
|
/**
|
|
|
|
* tty_kref_put - release a tty kref
|
|
|
|
* @tty: tty device
|
|
|
|
*
|
|
|
|
* Release a reference to a tty device and if need be let the kref
|
|
|
|
* layer destruct the object for us
|
|
|
|
*/
|
|
|
|
|
|
|
|
void tty_kref_put(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
if (tty)
|
2009-09-19 14:13:22 -06:00
|
|
|
kref_put(&tty->kref, queue_release_one_tty);
|
2008-10-13 03:37:26 -06:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(tty_kref_put);
|
|
|
|
|
2007-02-10 02:46:46 -07:00
|
|
|
/**
|
|
|
|
* release_tty - release tty structure memory
|
|
|
|
*
|
|
|
|
* Release both @tty and a possible linked partner (think pty pair),
|
|
|
|
* and decrement the refcount of the backing module.
|
|
|
|
*
|
|
|
|
* Locking:
|
2012-07-27 11:02:54 -06:00
|
|
|
* tty_mutex
|
2007-02-10 02:46:46 -07:00
|
|
|
* takes the file list lock internally when working on the list
|
|
|
|
* of ttys that the driver keeps.
|
2008-10-13 03:37:26 -06:00
|
|
|
*
|
2007-02-10 02:46:46 -07:00
|
|
|
*/
|
|
|
|
static void release_tty(struct tty_struct *tty, int idx)
|
|
|
|
{
|
2008-10-13 03:37:26 -06:00
|
|
|
/* This should always be true but check for the moment */
|
|
|
|
WARN_ON(tty->index != idx);
|
2012-07-27 11:02:54 -06:00
|
|
|
WARN_ON(!mutex_is_locked(&tty_mutex));
|
2012-07-17 10:06:57 -06:00
|
|
|
if (tty->ops->shutdown)
|
|
|
|
tty->ops->shutdown(tty);
|
|
|
|
tty_free_termios(tty);
|
|
|
|
tty_driver_remove_tty(tty->driver, tty);
|
2012-10-18 14:26:46 -06:00
|
|
|
tty->port->itty = NULL;
|
2013-06-15 07:01:00 -06:00
|
|
|
if (tty->link)
|
|
|
|
tty->link->port->itty = NULL;
|
2015-10-17 14:36:23 -06:00
|
|
|
tty_buffer_cancel_work(tty->port);
|
2012-07-17 10:06:57 -06:00
|
|
|
|
2014-11-21 05:42:29 -07:00
|
|
|
tty_kref_put(tty->link);
|
2008-10-13 03:37:26 -06:00
|
|
|
tty_kref_put(tty);
|
2007-02-10 02:46:46 -07:00
|
|
|
}
|
|
|
|
|
2011-11-11 02:47:23 -07:00
|
|
|
/**
|
|
|
|
* tty_release_checks - check a tty before real release
|
|
|
|
* @tty: tty to check
|
|
|
|
* @o_tty: link of @tty (if any)
|
|
|
|
* @idx: index of the tty
|
|
|
|
*
|
|
|
|
* Performs some paranoid checking before true release of the @tty.
|
|
|
|
* This is a no-op unless TTY_PARANOIA_CHECK is defined.
|
|
|
|
*/
|
2014-11-05 10:12:59 -07:00
|
|
|
static int tty_release_checks(struct tty_struct *tty, int idx)
|
2011-11-11 02:47:23 -07:00
|
|
|
{
|
|
|
|
#ifdef TTY_PARANOIA_CHECK
|
|
|
|
if (idx < 0 || idx >= tty->driver->num) {
|
2015-07-12 20:49:08 -06:00
|
|
|
tty_debug(tty, "bad idx %d\n", idx);
|
2011-11-11 02:47:23 -07:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* not much to check for devpts */
|
|
|
|
if (tty->driver->flags & TTY_DRIVER_DEVPTS_MEM)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (tty != tty->driver->ttys[idx]) {
|
2015-07-12 20:49:08 -06:00
|
|
|
tty_debug(tty, "bad driver table[%d] = %p\n",
|
|
|
|
idx, tty->driver->ttys[idx]);
|
2011-11-11 02:47:23 -07:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
if (tty->driver->other) {
|
2014-11-05 10:12:59 -07:00
|
|
|
struct tty_struct *o_tty = tty->link;
|
|
|
|
|
2011-11-11 02:47:23 -07:00
|
|
|
if (o_tty != tty->driver->other->ttys[idx]) {
|
2015-07-12 20:49:08 -06:00
|
|
|
tty_debug(tty, "bad other table[%d] = %p\n",
|
|
|
|
idx, tty->driver->other->ttys[idx]);
|
2011-11-11 02:47:23 -07:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
if (o_tty->link != tty) {
|
2015-07-12 20:49:08 -06:00
|
|
|
tty_debug(tty, "bad link = %p\n", o_tty->link);
|
2011-11-11 02:47:23 -07:00
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2009-11-30 06:18:29 -07:00
|
|
|
/**
|
|
|
|
* tty_release - vfs callback for close
|
|
|
|
* @inode: inode of tty
|
|
|
|
* @filp: file pointer for handle to tty
|
|
|
|
*
|
|
|
|
* Called the last time each file handle is closed that references
|
|
|
|
* this tty. There may however be several such references.
|
|
|
|
*
|
|
|
|
* Locking:
|
|
|
|
* Takes bkl. See tty_release_dev
|
|
|
|
*
|
2005-04-16 16:20:36 -06:00
|
|
|
* Even releasing the tty structures is a tricky business.. We have
|
|
|
|
* to be very careful that the structures are all released at the
|
|
|
|
* same time, as interrupts might otherwise get the wrong pointers.
|
|
|
|
*
|
|
|
|
* WSH 09/09/97: rewritten to avoid some nasty race conditions that could
|
|
|
|
* lead to double frees or releasing memory still in use.
|
|
|
|
*/
|
2009-11-30 06:18:29 -07:00
|
|
|
|
|
|
|
int tty_release(struct inode *inode, struct file *filp)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
struct tty_struct *tty = file_tty(filp);
|
2014-11-05 10:13:00 -07:00
|
|
|
struct tty_struct *o_tty = NULL;
|
|
|
|
int do_sleep, final;
|
2005-04-16 16:20:36 -06:00
|
|
|
int idx;
|
2014-10-16 11:51:30 -06:00
|
|
|
long timeout = 0;
|
2014-10-16 11:54:36 -06:00
|
|
|
int once = 1;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2011-11-09 13:33:24 -07:00
|
|
|
if (tty_paranoia_check(tty, inode, __func__))
|
2009-11-30 06:18:29 -07:00
|
|
|
return 0;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_lock(tty);
|
2011-11-09 13:33:24 -07:00
|
|
|
check_tty_count(tty, __func__);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2010-06-01 14:53:01 -06:00
|
|
|
__tty_fasync(-1, filp, 0);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
idx = tty->index;
|
2014-11-05 10:13:00 -07:00
|
|
|
if (tty->driver->type == TTY_DRIVER_TYPE_PTY &&
|
|
|
|
tty->driver->subtype == PTY_TYPE_MASTER)
|
|
|
|
o_tty = tty->link;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2014-11-05 10:12:59 -07:00
|
|
|
if (tty_release_checks(tty, idx)) {
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_unlock(tty);
|
2009-11-30 06:18:29 -07:00
|
|
|
return 0;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2015-11-08 11:01:19 -07:00
|
|
|
tty_debug_hangup(tty, "releasing (count=%d)\n", tty->count);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->close)
|
|
|
|
tty->ops->close(tty, filp);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2014-11-05 10:13:01 -07:00
|
|
|
/* If tty is pty master, lock the slave pty (stable lock order) */
|
|
|
|
tty_lock_slave(o_tty);
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* Sanity check: if tty->count is going to zero, there shouldn't be
|
|
|
|
* any waiters on tty->read_wait or tty->write_wait. We test the
|
|
|
|
* wait queues and kick everyone out _before_ actually starting to
|
|
|
|
* close. This ensures that we won't block while releasing the tty
|
|
|
|
* structure.
|
|
|
|
*
|
|
|
|
* The test for the o_tty closing is necessary, since the master and
|
|
|
|
* slave sides may close in any order. If the slave side closes out
|
|
|
|
* first, its count will be one, since the master side holds an open.
|
2014-11-05 10:12:56 -07:00
|
|
|
* Thus this test wouldn't be triggered at the time the slave closed,
|
2005-04-16 16:20:36 -06:00
|
|
|
* so we do it now.
|
|
|
|
*/
|
|
|
|
while (1) {
|
|
|
|
do_sleep = 0;
|
|
|
|
|
2014-11-05 10:12:56 -07:00
|
|
|
if (tty->count <= 1) {
|
2005-04-16 16:20:36 -06:00
|
|
|
if (waitqueue_active(&tty->read_wait)) {
|
2009-03-31 16:24:24 -06:00
|
|
|
wake_up_poll(&tty->read_wait, POLLIN);
|
2005-04-16 16:20:36 -06:00
|
|
|
do_sleep++;
|
|
|
|
}
|
|
|
|
if (waitqueue_active(&tty->write_wait)) {
|
2009-03-31 16:24:24 -06:00
|
|
|
wake_up_poll(&tty->write_wait, POLLOUT);
|
2005-04-16 16:20:36 -06:00
|
|
|
do_sleep++;
|
|
|
|
}
|
|
|
|
}
|
2014-11-05 10:13:00 -07:00
|
|
|
if (o_tty && o_tty->count <= 1) {
|
2005-04-16 16:20:36 -06:00
|
|
|
if (waitqueue_active(&o_tty->read_wait)) {
|
2009-03-31 16:24:24 -06:00
|
|
|
wake_up_poll(&o_tty->read_wait, POLLIN);
|
2005-04-16 16:20:36 -06:00
|
|
|
do_sleep++;
|
|
|
|
}
|
|
|
|
if (waitqueue_active(&o_tty->write_wait)) {
|
2009-03-31 16:24:24 -06:00
|
|
|
wake_up_poll(&o_tty->write_wait, POLLOUT);
|
2005-04-16 16:20:36 -06:00
|
|
|
do_sleep++;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (!do_sleep)
|
|
|
|
break;
|
|
|
|
|
2014-10-16 11:54:36 -06:00
|
|
|
if (once) {
|
|
|
|
once = 0;
|
2015-11-08 11:01:13 -07:00
|
|
|
tty_warn(tty, "read/write wait queue active!\n");
|
2014-10-16 11:54:36 -06:00
|
|
|
}
|
2014-10-16 11:51:30 -06:00
|
|
|
schedule_timeout_killable(timeout);
|
|
|
|
if (timeout < 120 * HZ)
|
|
|
|
timeout = 2 * timeout + 1;
|
|
|
|
else
|
|
|
|
timeout = MAX_SCHEDULE_TIMEOUT;
|
2008-02-08 05:18:47 -07:00
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2014-11-05 10:13:00 -07:00
|
|
|
if (o_tty) {
|
2005-04-16 16:20:36 -06:00
|
|
|
if (--o_tty->count < 0) {
|
2015-11-08 11:01:13 -07:00
|
|
|
tty_warn(tty, "bad slave count (%d)\n", o_tty->count);
|
2005-04-16 16:20:36 -06:00
|
|
|
o_tty->count = 0;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (--tty->count < 0) {
|
2015-11-08 11:01:13 -07:00
|
|
|
tty_warn(tty, "bad tty->count (%d)\n", tty->count);
|
2005-04-16 16:20:36 -06:00
|
|
|
tty->count = 0;
|
|
|
|
}
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* We've decremented tty->count, so we need to remove this file
|
|
|
|
* descriptor off the tty->tty_files list; this serves two
|
|
|
|
* purposes:
|
|
|
|
* - check_tty_count sees the correct number of file descriptors
|
|
|
|
* associated with this tty.
|
|
|
|
* - do_tty_hangup no longer sees this file descriptor as
|
|
|
|
* something that needs to be handled for hangups.
|
|
|
|
*/
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
tty_del_file(filp);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Perform some housekeeping before deciding whether to return.
|
|
|
|
*
|
|
|
|
* If _either_ side is closing, make sure there aren't any
|
|
|
|
* processes that still think tty or o_tty is their controlling
|
|
|
|
* tty.
|
|
|
|
*/
|
2014-11-05 10:12:56 -07:00
|
|
|
if (!tty->count) {
|
2005-04-16 16:20:36 -06:00
|
|
|
read_lock(&tasklist_lock);
|
2006-12-08 03:36:04 -07:00
|
|
|
session_clear_tty(tty->session);
|
2014-11-05 10:13:00 -07:00
|
|
|
if (o_tty)
|
2006-12-08 03:36:04 -07:00
|
|
|
session_clear_tty(o_tty->session);
|
2005-04-16 16:20:36 -06:00
|
|
|
read_unlock(&tasklist_lock);
|
|
|
|
}
|
|
|
|
|
2014-11-05 10:12:56 -07:00
|
|
|
/* check whether both sides are closing ... */
|
2014-11-05 10:13:00 -07:00
|
|
|
final = !tty->count && !(o_tty && o_tty->count);
|
2014-11-05 10:12:56 -07:00
|
|
|
|
2014-11-05 10:13:01 -07:00
|
|
|
tty_unlock_slave(o_tty);
|
|
|
|
tty_unlock(tty);
|
|
|
|
|
2014-11-05 10:12:52 -07:00
|
|
|
/* At this point, the tty->count == 0 should ensure a dead tty
|
2012-07-27 11:02:54 -06:00
|
|
|
cannot be re-opened by a racing opener */
|
2006-02-14 14:53:00 -07:00
|
|
|
|
2014-11-05 10:12:56 -07:00
|
|
|
if (!final)
|
2009-11-30 06:18:29 -07:00
|
|
|
return 0;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2015-07-12 20:49:09 -06:00
|
|
|
tty_debug_hangup(tty, "final close\n");
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
2008-07-22 04:16:55 -06:00
|
|
|
* Ask the line discipline code to release its structures
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2014-11-05 10:12:58 -07:00
|
|
|
tty_ldisc_release(tty);
|
2013-03-11 14:44:35 -06:00
|
|
|
|
|
|
|
/* Wait for pending work before tty destruction commmences */
|
|
|
|
tty_flush_works(tty);
|
|
|
|
|
2015-11-08 11:01:19 -07:00
|
|
|
tty_debug_hangup(tty, "freeing structure\n");
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
2007-02-10 02:46:46 -07:00
|
|
|
* The release_tty function takes care of the details of clearing
|
2012-08-08 09:30:13 -06:00
|
|
|
* the slots and preserving the termios structure. The tty_unlock_pair
|
|
|
|
* should be safe as we keep a kref while the tty is locked (so the
|
|
|
|
* unlock never unlocks a freed tty).
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2012-07-27 11:02:54 -06:00
|
|
|
mutex_lock(&tty_mutex);
|
2007-02-10 02:46:46 -07:00
|
|
|
release_tty(tty, idx);
|
2012-07-27 11:02:54 -06:00
|
|
|
mutex_unlock(&tty_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2009-11-30 06:18:29 -07:00
|
|
|
return 0;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2011-11-09 13:33:19 -07:00
|
|
|
/**
|
tty: Re-open /dev/tty without tty_mutex
Opening /dev/tty (ie., the controlling tty for the current task)
is always a re-open of the underlying tty. Because holding the
tty_lock is sufficient for safely re-opening a tty, and because
having a tty kref is sufficient for safely acquiring the tty_lock [1],
tty_open_current_tty() does not require holding tty_mutex.
Repurpose tty_open_current_tty() to perform the re-open itself and
refactor tty_open().
[1] Analysis of safely re-opening the current tty w/o tty_mutex
get_current_tty() gets a tty kref from the already kref'ed tty value of
current->signal->tty while holding the sighand lock for the current
task. This guarantees that the tty pointer returned from
get_current_tty() points to a tty which remains referenceable
while holding the kref.
Although release_tty() may run concurrently, and thus the driver
reference may be removed, release_one_tty() cannot have run, and
won't while holding the tty kref.
This, in turn, guarantees the tty_lock() can safely be acquired
(since tty->magic and tty->legacy_mutex are still a valid dereferences).
The tty_lock() also gets a tty kref to prevent the tty_unlock() from
dereferencing a released tty. Thus, the kref returned from
get_current_tty() can be released.
Lastly, the first operation of tty_reopen() is to check the tty count.
If non-zero, this ensures release_tty() is not running concurrently,
and the driver references have not been removed.
Reviewed-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-11-05 10:12:50 -07:00
|
|
|
* tty_open_current_tty - get locked tty of current task
|
2011-11-09 13:33:19 -07:00
|
|
|
* @device: device number
|
|
|
|
* @filp: file pointer to tty
|
tty: Re-open /dev/tty without tty_mutex
Opening /dev/tty (ie., the controlling tty for the current task)
is always a re-open of the underlying tty. Because holding the
tty_lock is sufficient for safely re-opening a tty, and because
having a tty kref is sufficient for safely acquiring the tty_lock [1],
tty_open_current_tty() does not require holding tty_mutex.
Repurpose tty_open_current_tty() to perform the re-open itself and
refactor tty_open().
[1] Analysis of safely re-opening the current tty w/o tty_mutex
get_current_tty() gets a tty kref from the already kref'ed tty value of
current->signal->tty while holding the sighand lock for the current
task. This guarantees that the tty pointer returned from
get_current_tty() points to a tty which remains referenceable
while holding the kref.
Although release_tty() may run concurrently, and thus the driver
reference may be removed, release_one_tty() cannot have run, and
won't while holding the tty kref.
This, in turn, guarantees the tty_lock() can safely be acquired
(since tty->magic and tty->legacy_mutex are still a valid dereferences).
The tty_lock() also gets a tty kref to prevent the tty_unlock() from
dereferencing a released tty. Thus, the kref returned from
get_current_tty() can be released.
Lastly, the first operation of tty_reopen() is to check the tty count.
If non-zero, this ensures release_tty() is not running concurrently,
and the driver references have not been removed.
Reviewed-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-11-05 10:12:50 -07:00
|
|
|
* @return: locked tty of the current task iff @device is /dev/tty
|
|
|
|
*
|
|
|
|
* Performs a re-open of the current task's controlling tty.
|
2011-11-09 13:33:19 -07:00
|
|
|
*
|
|
|
|
* We cannot return driver and index like for the other nodes because
|
|
|
|
* devpts will not work then. It expects inodes to be from devpts FS.
|
|
|
|
*/
|
|
|
|
static struct tty_struct *tty_open_current_tty(dev_t device, struct file *filp)
|
|
|
|
{
|
|
|
|
struct tty_struct *tty;
|
tty: Re-open /dev/tty without tty_mutex
Opening /dev/tty (ie., the controlling tty for the current task)
is always a re-open of the underlying tty. Because holding the
tty_lock is sufficient for safely re-opening a tty, and because
having a tty kref is sufficient for safely acquiring the tty_lock [1],
tty_open_current_tty() does not require holding tty_mutex.
Repurpose tty_open_current_tty() to perform the re-open itself and
refactor tty_open().
[1] Analysis of safely re-opening the current tty w/o tty_mutex
get_current_tty() gets a tty kref from the already kref'ed tty value of
current->signal->tty while holding the sighand lock for the current
task. This guarantees that the tty pointer returned from
get_current_tty() points to a tty which remains referenceable
while holding the kref.
Although release_tty() may run concurrently, and thus the driver
reference may be removed, release_one_tty() cannot have run, and
won't while holding the tty kref.
This, in turn, guarantees the tty_lock() can safely be acquired
(since tty->magic and tty->legacy_mutex are still a valid dereferences).
The tty_lock() also gets a tty kref to prevent the tty_unlock() from
dereferencing a released tty. Thus, the kref returned from
get_current_tty() can be released.
Lastly, the first operation of tty_reopen() is to check the tty count.
If non-zero, this ensures release_tty() is not running concurrently,
and the driver references have not been removed.
Reviewed-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-11-05 10:12:50 -07:00
|
|
|
int retval;
|
2011-11-09 13:33:19 -07:00
|
|
|
|
|
|
|
if (device != MKDEV(TTYAUX_MAJOR, 0))
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
tty = get_current_tty();
|
|
|
|
if (!tty)
|
|
|
|
return ERR_PTR(-ENXIO);
|
|
|
|
|
|
|
|
filp->f_flags |= O_NONBLOCK; /* Don't let /dev/tty block */
|
|
|
|
/* noctty = 1; */
|
tty: Re-open /dev/tty without tty_mutex
Opening /dev/tty (ie., the controlling tty for the current task)
is always a re-open of the underlying tty. Because holding the
tty_lock is sufficient for safely re-opening a tty, and because
having a tty kref is sufficient for safely acquiring the tty_lock [1],
tty_open_current_tty() does not require holding tty_mutex.
Repurpose tty_open_current_tty() to perform the re-open itself and
refactor tty_open().
[1] Analysis of safely re-opening the current tty w/o tty_mutex
get_current_tty() gets a tty kref from the already kref'ed tty value of
current->signal->tty while holding the sighand lock for the current
task. This guarantees that the tty pointer returned from
get_current_tty() points to a tty which remains referenceable
while holding the kref.
Although release_tty() may run concurrently, and thus the driver
reference may be removed, release_one_tty() cannot have run, and
won't while holding the tty kref.
This, in turn, guarantees the tty_lock() can safely be acquired
(since tty->magic and tty->legacy_mutex are still a valid dereferences).
The tty_lock() also gets a tty kref to prevent the tty_unlock() from
dereferencing a released tty. Thus, the kref returned from
get_current_tty() can be released.
Lastly, the first operation of tty_reopen() is to check the tty count.
If non-zero, this ensures release_tty() is not running concurrently,
and the driver references have not been removed.
Reviewed-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-11-05 10:12:50 -07:00
|
|
|
tty_lock(tty);
|
|
|
|
tty_kref_put(tty); /* safe to drop the kref now */
|
|
|
|
|
|
|
|
retval = tty_reopen(tty);
|
|
|
|
if (retval < 0) {
|
|
|
|
tty_unlock(tty);
|
|
|
|
tty = ERR_PTR(retval);
|
|
|
|
}
|
2011-11-09 13:33:19 -07:00
|
|
|
return tty;
|
|
|
|
}
|
|
|
|
|
2011-11-09 13:33:20 -07:00
|
|
|
/**
|
|
|
|
* tty_lookup_driver - lookup a tty driver for a given device file
|
|
|
|
* @device: device number
|
|
|
|
* @filp: file pointer to tty
|
|
|
|
* @noctty: set if the device should not become a controlling tty
|
|
|
|
* @index: index for the device in the @return driver
|
|
|
|
* @return: driver for this inode (with increased refcount)
|
|
|
|
*
|
|
|
|
* If @return is not erroneous, the caller is responsible to decrement the
|
|
|
|
* refcount by tty_driver_kref_put.
|
|
|
|
*
|
|
|
|
* Locking: tty_mutex protects get_tty_driver
|
|
|
|
*/
|
|
|
|
static struct tty_driver *tty_lookup_driver(dev_t device, struct file *filp,
|
2016-01-09 22:13:52 -07:00
|
|
|
int *index)
|
2011-11-09 13:33:20 -07:00
|
|
|
{
|
|
|
|
struct tty_driver *driver;
|
|
|
|
|
2011-11-09 13:33:22 -07:00
|
|
|
switch (device) {
|
2011-11-09 13:33:20 -07:00
|
|
|
#ifdef CONFIG_VT
|
2011-11-09 13:33:22 -07:00
|
|
|
case MKDEV(TTY_MAJOR, 0): {
|
2011-11-09 13:33:20 -07:00
|
|
|
extern struct tty_driver *console_driver;
|
|
|
|
driver = tty_driver_kref_get(console_driver);
|
|
|
|
*index = fg_console;
|
2011-11-09 13:33:22 -07:00
|
|
|
break;
|
2011-11-09 13:33:20 -07:00
|
|
|
}
|
|
|
|
#endif
|
2011-11-09 13:33:22 -07:00
|
|
|
case MKDEV(TTYAUX_MAJOR, 1): {
|
2011-11-09 13:33:20 -07:00
|
|
|
struct tty_driver *console_driver = console_device(index);
|
|
|
|
if (console_driver) {
|
|
|
|
driver = tty_driver_kref_get(console_driver);
|
|
|
|
if (driver) {
|
|
|
|
/* Don't let /dev/console block */
|
|
|
|
filp->f_flags |= O_NONBLOCK;
|
2011-11-09 13:33:22 -07:00
|
|
|
break;
|
2011-11-09 13:33:20 -07:00
|
|
|
}
|
|
|
|
}
|
|
|
|
return ERR_PTR(-ENODEV);
|
|
|
|
}
|
2011-11-09 13:33:22 -07:00
|
|
|
default:
|
|
|
|
driver = get_tty_driver(device, index);
|
|
|
|
if (!driver)
|
|
|
|
return ERR_PTR(-ENODEV);
|
|
|
|
break;
|
|
|
|
}
|
2011-11-09 13:33:20 -07:00
|
|
|
return driver;
|
|
|
|
}
|
|
|
|
|
2016-01-09 22:13:53 -07:00
|
|
|
/**
|
|
|
|
* tty_open_by_driver - open a tty device
|
|
|
|
* @device: dev_t of device to open
|
|
|
|
* @inode: inode of device file
|
|
|
|
* @filp: file pointer to tty
|
|
|
|
*
|
|
|
|
* Performs the driver lookup, checks for a reopen, or otherwise
|
|
|
|
* performs the first-time tty initialization.
|
|
|
|
*
|
|
|
|
* Returns the locked initialized or re-opened &tty_struct
|
|
|
|
*
|
|
|
|
* Claims the global tty_mutex to serialize:
|
|
|
|
* - concurrent first-time tty initialization
|
|
|
|
* - concurrent tty driver removal w/ lookup
|
|
|
|
* - concurrent tty removal from driver table
|
|
|
|
*/
|
|
|
|
static struct tty_struct *tty_open_by_driver(dev_t device, struct inode *inode,
|
|
|
|
struct file *filp)
|
|
|
|
{
|
|
|
|
struct tty_struct *tty;
|
|
|
|
struct tty_driver *driver = NULL;
|
|
|
|
int index = -1;
|
|
|
|
int retval;
|
|
|
|
|
|
|
|
mutex_lock(&tty_mutex);
|
|
|
|
driver = tty_lookup_driver(device, filp, &index);
|
|
|
|
if (IS_ERR(driver)) {
|
|
|
|
mutex_unlock(&tty_mutex);
|
|
|
|
return ERR_CAST(driver);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* check whether we're reopening an existing tty */
|
|
|
|
tty = tty_driver_lookup_tty(driver, inode, index);
|
|
|
|
if (IS_ERR(tty)) {
|
|
|
|
mutex_unlock(&tty_mutex);
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (tty) {
|
|
|
|
mutex_unlock(&tty_mutex);
|
|
|
|
retval = tty_lock_interruptible(tty);
|
2016-03-31 18:47:07 -06:00
|
|
|
tty_kref_put(tty); /* drop kref from tty_driver_lookup_tty() */
|
2016-01-09 22:13:53 -07:00
|
|
|
if (retval) {
|
|
|
|
if (retval == -EINTR)
|
|
|
|
retval = -ERESTARTSYS;
|
|
|
|
tty = ERR_PTR(retval);
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
retval = tty_reopen(tty);
|
|
|
|
if (retval < 0) {
|
|
|
|
tty_unlock(tty);
|
|
|
|
tty = ERR_PTR(retval);
|
|
|
|
}
|
|
|
|
} else { /* Returns with the tty_lock held for now */
|
|
|
|
tty = tty_init_dev(driver, index);
|
|
|
|
mutex_unlock(&tty_mutex);
|
|
|
|
}
|
|
|
|
out:
|
|
|
|
tty_driver_kref_put(driver);
|
|
|
|
return tty;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2009-11-30 06:18:29 -07:00
|
|
|
* tty_open - open a tty device
|
2006-08-27 02:24:01 -06:00
|
|
|
* @inode: inode of device file
|
|
|
|
* @filp: file pointer to tty
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
2006-08-27 02:24:01 -06:00
|
|
|
* tty_open and tty_release keep up the tty count that contains the
|
|
|
|
* number of opens done on a tty. We cannot use the inode-count, as
|
|
|
|
* different inodes might point to the same tty.
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
2006-08-27 02:24:01 -06:00
|
|
|
* Open-counting is needed for pty masters, as well as for keeping
|
|
|
|
* track of serial lines: DTR is dropped when the last close happens.
|
|
|
|
* (This is not done solely through tty->count, now. - Ted 1/27/92)
|
|
|
|
*
|
|
|
|
* The termios state of a pty is reset on first open so that
|
|
|
|
* settings don't persist across reuse.
|
|
|
|
*
|
2011-11-09 13:33:20 -07:00
|
|
|
* Locking: tty_mutex protects tty, tty_lookup_driver and tty_init_dev.
|
2006-12-08 03:36:04 -07:00
|
|
|
* tty->count should protect the rest.
|
|
|
|
* ->siglock protects ->signal/->sighand
|
2012-08-08 09:30:13 -06:00
|
|
|
*
|
|
|
|
* Note: the tty_unlock/lock cases without a ref are only safe due to
|
|
|
|
* tty_mutex
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2006-08-27 02:24:01 -06:00
|
|
|
|
2009-11-30 06:18:29 -07:00
|
|
|
static int tty_open(struct inode *inode, struct file *filp)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2011-11-09 13:33:19 -07:00
|
|
|
struct tty_struct *tty;
|
2005-04-16 16:20:36 -06:00
|
|
|
int noctty, retval;
|
|
|
|
dev_t device = inode->i_rdev;
|
2009-04-02 17:56:36 -06:00
|
|
|
unsigned saved_flags = filp->f_flags;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
nonseekable_open(inode, filp);
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
retry_open:
|
2011-10-12 03:32:43 -06:00
|
|
|
retval = tty_alloc_file(filp);
|
|
|
|
if (retval)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
2011-11-09 13:33:19 -07:00
|
|
|
tty = tty_open_current_tty(device, filp);
|
2016-01-09 22:13:53 -07:00
|
|
|
if (!tty)
|
|
|
|
tty = tty_open_by_driver(device, inode, filp);
|
tty: Re-open /dev/tty without tty_mutex
Opening /dev/tty (ie., the controlling tty for the current task)
is always a re-open of the underlying tty. Because holding the
tty_lock is sufficient for safely re-opening a tty, and because
having a tty kref is sufficient for safely acquiring the tty_lock [1],
tty_open_current_tty() does not require holding tty_mutex.
Repurpose tty_open_current_tty() to perform the re-open itself and
refactor tty_open().
[1] Analysis of safely re-opening the current tty w/o tty_mutex
get_current_tty() gets a tty kref from the already kref'ed tty value of
current->signal->tty while holding the sighand lock for the current
task. This guarantees that the tty pointer returned from
get_current_tty() points to a tty which remains referenceable
while holding the kref.
Although release_tty() may run concurrently, and thus the driver
reference may be removed, release_one_tty() cannot have run, and
won't while holding the tty kref.
This, in turn, guarantees the tty_lock() can safely be acquired
(since tty->magic and tty->legacy_mutex are still a valid dereferences).
The tty_lock() also gets a tty kref to prevent the tty_unlock() from
dereferencing a released tty. Thus, the kref returned from
get_current_tty() can be released.
Lastly, the first operation of tty_reopen() is to check the tty count.
If non-zero, this ensures release_tty() is not running concurrently,
and the driver references have not been removed.
Reviewed-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2014-11-05 10:12:50 -07:00
|
|
|
|
2009-11-30 06:18:29 -07:00
|
|
|
if (IS_ERR(tty)) {
|
2016-01-09 22:13:53 -07:00
|
|
|
tty_free_file(filp);
|
2011-11-09 13:33:21 -07:00
|
|
|
retval = PTR_ERR(tty);
|
2016-01-09 22:13:45 -07:00
|
|
|
if (retval != -EAGAIN || signal_pending(current))
|
2016-01-09 22:13:53 -07:00
|
|
|
return retval;
|
2016-01-09 22:13:45 -07:00
|
|
|
schedule();
|
|
|
|
goto retry_open;
|
2009-11-30 06:18:29 -07:00
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2011-10-12 03:32:43 -06:00
|
|
|
tty_add_file(tty, filp);
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
|
2011-11-09 13:33:24 -07:00
|
|
|
check_tty_count(tty, __func__);
|
2015-11-08 11:01:19 -07:00
|
|
|
tty_debug_hangup(tty, "opening (count=%d)\n", tty->count);
|
2015-07-12 20:49:09 -06:00
|
|
|
|
2011-03-31 12:35:31 -06:00
|
|
|
if (tty->ops->open)
|
|
|
|
retval = tty->ops->open(tty, filp);
|
|
|
|
else
|
|
|
|
retval = -ENODEV;
|
2005-04-16 16:20:36 -06:00
|
|
|
filp->f_flags = saved_flags;
|
|
|
|
|
|
|
|
if (retval) {
|
2015-11-08 11:01:19 -07:00
|
|
|
tty_debug_hangup(tty, "open error %d, releasing\n", retval);
|
2015-07-12 20:49:09 -06:00
|
|
|
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_unlock(tty); /* need to call tty_release without BTM */
|
2009-11-30 06:18:29 -07:00
|
|
|
tty_release(inode, filp);
|
2010-06-01 14:53:02 -06:00
|
|
|
if (retval != -ERESTARTSYS)
|
2005-04-16 16:20:36 -06:00
|
|
|
return retval;
|
2010-06-01 14:53:02 -06:00
|
|
|
|
|
|
|
if (signal_pending(current))
|
2005-04-16 16:20:36 -06:00
|
|
|
return retval;
|
2010-06-01 14:53:02 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
schedule();
|
|
|
|
/*
|
|
|
|
* Need to reset f_op in case a hangup happened.
|
|
|
|
*/
|
2014-11-05 10:26:24 -07:00
|
|
|
if (tty_hung_up_p(filp))
|
2005-04-16 16:20:36 -06:00
|
|
|
filp->f_op = &tty_fops;
|
|
|
|
goto retry_open;
|
|
|
|
}
|
2013-11-19 06:46:27 -07:00
|
|
|
clear_bit(TTY_HUPPED, &tty->flags);
|
2009-11-30 06:18:29 -07:00
|
|
|
|
2006-12-08 03:36:04 -07:00
|
|
|
|
2014-10-16 12:59:47 -06:00
|
|
|
read_lock(&tasklist_lock);
|
2006-12-08 03:36:04 -07:00
|
|
|
spin_lock_irq(¤t->sighand->siglock);
|
2016-01-09 22:13:52 -07:00
|
|
|
noctty = (filp->f_flags & O_NOCTTY) ||
|
2016-03-31 18:05:30 -06:00
|
|
|
(IS_ENABLED(CONFIG_VT) && device == MKDEV(TTY_MAJOR, 0)) ||
|
2016-01-09 22:13:52 -07:00
|
|
|
device == MKDEV(TTYAUX_MAJOR, 1) ||
|
|
|
|
(tty->driver->type == TTY_DRIVER_TYPE_PTY &&
|
|
|
|
tty->driver->subtype == PTY_TYPE_MASTER);
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
if (!noctty &&
|
|
|
|
current->signal->leader &&
|
|
|
|
!current->signal->tty &&
|
2015-10-04 11:29:12 -06:00
|
|
|
tty->session == NULL) {
|
|
|
|
/*
|
|
|
|
* Don't let a process that only has write access to the tty
|
|
|
|
* obtain the privileges associated with having a tty as
|
|
|
|
* controlling terminal (being able to reopen it with full
|
|
|
|
* access through /dev/tty, being able to perform pushback).
|
|
|
|
* Many distributions set the group of all ttys to "tty" and
|
|
|
|
* grant write-only access to all terminals for setgid tty
|
|
|
|
* binaries, which should not imply full privileges on all ttys.
|
|
|
|
*
|
|
|
|
* This could theoretically break old code that performs open()
|
|
|
|
* on a write-only file descriptor. In that case, it might be
|
|
|
|
* necessary to also permit this if
|
|
|
|
* inode_permission(inode, MAY_READ) == 0.
|
|
|
|
*/
|
|
|
|
if (filp->f_mode & FMODE_READ)
|
|
|
|
__proc_set_tty(tty);
|
|
|
|
}
|
2006-12-08 03:36:04 -07:00
|
|
|
spin_unlock_irq(¤t->sighand->siglock);
|
2014-10-16 12:59:47 -06:00
|
|
|
read_unlock(&tasklist_lock);
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_unlock(tty);
|
2005-04-16 16:20:36 -06:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2008-05-16 09:10:50 -06:00
|
|
|
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tty_poll - check tty status
|
|
|
|
* @filp: file being polled
|
|
|
|
* @wait: poll wait structures to update
|
|
|
|
*
|
|
|
|
* Call the line discipline polling method to obtain the poll
|
|
|
|
* status of the device.
|
|
|
|
*
|
|
|
|
* Locking: locks called line discipline but ldisc poll method
|
|
|
|
* may be re-entered freely by other callers.
|
|
|
|
*/
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
static unsigned int tty_poll(struct file *filp, poll_table *wait)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
struct tty_struct *tty = file_tty(filp);
|
2005-04-16 16:20:36 -06:00
|
|
|
struct tty_ldisc *ld;
|
|
|
|
int ret = 0;
|
|
|
|
|
2013-02-27 14:59:05 -07:00
|
|
|
if (tty_paranoia_check(tty, file_inode(filp), "tty_poll"))
|
2005-04-16 16:20:36 -06:00
|
|
|
return 0;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
ld = tty_ldisc_ref_wait(tty);
|
2016-01-10 23:41:01 -07:00
|
|
|
if (!ld)
|
|
|
|
return hung_up_tty_poll(filp, wait);
|
2008-07-16 14:53:12 -06:00
|
|
|
if (ld->ops->poll)
|
2014-11-05 10:26:25 -07:00
|
|
|
ret = ld->ops->poll(tty, filp, wait);
|
2005-04-16 16:20:36 -06:00
|
|
|
tty_ldisc_deref(ld);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2010-06-01 14:53:01 -06:00
|
|
|
static int __tty_fasync(int fd, struct file *filp, int on)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
struct tty_struct *tty = file_tty(filp);
|
2008-04-30 01:53:30 -06:00
|
|
|
unsigned long flags;
|
2008-06-19 16:04:53 -06:00
|
|
|
int retval = 0;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2013-02-27 14:59:05 -07:00
|
|
|
if (tty_paranoia_check(tty, file_inode(filp), "tty_fasync"))
|
2008-06-19 16:04:53 -06:00
|
|
|
goto out;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
retval = fasync_helper(fd, filp, on, &tty->fasync);
|
|
|
|
if (retval <= 0)
|
2008-06-19 16:04:53 -06:00
|
|
|
goto out;
|
2013-06-15 05:28:28 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
if (on) {
|
2007-02-12 01:53:00 -07:00
|
|
|
enum pid_type type;
|
|
|
|
struct pid *pid;
|
2013-06-15 05:28:28 -06:00
|
|
|
|
2008-04-30 01:53:30 -06:00
|
|
|
spin_lock_irqsave(&tty->ctrl_lock, flags);
|
2007-02-12 01:53:00 -07:00
|
|
|
if (tty->pgrp) {
|
|
|
|
pid = tty->pgrp;
|
|
|
|
type = PIDTYPE_PGID;
|
|
|
|
} else {
|
|
|
|
pid = task_pid(current);
|
|
|
|
type = PIDTYPE_PID;
|
|
|
|
}
|
2010-02-07 11:11:23 -07:00
|
|
|
get_pid(pid);
|
2009-12-17 08:07:19 -07:00
|
|
|
spin_unlock_irqrestore(&tty->ctrl_lock, flags);
|
2014-08-22 09:27:32 -06:00
|
|
|
__f_setown(filp, pid, type, 0);
|
2010-02-07 11:11:23 -07:00
|
|
|
put_pid(pid);
|
2014-08-22 09:27:32 -06:00
|
|
|
retval = 0;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2008-06-19 16:04:53 -06:00
|
|
|
out:
|
2010-06-01 14:53:01 -06:00
|
|
|
return retval;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int tty_fasync(int fd, struct file *filp, int on)
|
|
|
|
{
|
2012-08-08 09:30:13 -06:00
|
|
|
struct tty_struct *tty = file_tty(filp);
|
2016-01-09 22:45:11 -07:00
|
|
|
int retval = -ENOTTY;
|
2012-08-08 09:30:13 -06:00
|
|
|
|
|
|
|
tty_lock(tty);
|
2016-01-09 22:45:11 -07:00
|
|
|
if (!tty_hung_up_p(filp))
|
|
|
|
retval = __tty_fasync(fd, filp, on);
|
2012-08-08 09:30:13 -06:00
|
|
|
tty_unlock(tty);
|
|
|
|
|
2008-06-19 16:04:53 -06:00
|
|
|
return retval;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tiocsti - fake input character
|
|
|
|
* @tty: tty to fake input into
|
|
|
|
* @p: pointer to character
|
|
|
|
*
|
2007-10-19 15:10:43 -06:00
|
|
|
* Fake input to a tty device. Does the necessary locking and
|
2006-08-27 02:24:01 -06:00
|
|
|
* input management.
|
|
|
|
*
|
|
|
|
* FIXME: does not honour flow control ??
|
|
|
|
*
|
|
|
|
* Locking:
|
2013-06-15 05:04:46 -06:00
|
|
|
* Called functions take tty_ldiscs_lock
|
2006-08-27 02:24:01 -06:00
|
|
|
* current->signal->tty check is safe without locks
|
2006-09-29 03:00:58 -06:00
|
|
|
*
|
|
|
|
* FIXME: may race normal receive processing
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static int tiocsti(struct tty_struct *tty, char __user *p)
|
|
|
|
{
|
|
|
|
char ch, mbz = 0;
|
|
|
|
struct tty_ldisc *ld;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
if ((current->signal->tty != tty) && !capable(CAP_SYS_ADMIN))
|
|
|
|
return -EPERM;
|
|
|
|
if (get_user(ch, p))
|
|
|
|
return -EFAULT;
|
2008-12-09 02:23:33 -07:00
|
|
|
tty_audit_tiocsti(tty, ch);
|
2005-04-16 16:20:36 -06:00
|
|
|
ld = tty_ldisc_ref_wait(tty);
|
2016-01-10 23:41:01 -07:00
|
|
|
if (!ld)
|
|
|
|
return -EIO;
|
2008-07-16 14:53:12 -06:00
|
|
|
ld->ops->receive_buf(tty, &ch, &mbz, 1);
|
2005-04-16 16:20:36 -06:00
|
|
|
tty_ldisc_deref(ld);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tiocgwinsz - implement window query ioctl
|
|
|
|
* @tty; tty
|
|
|
|
* @arg: user buffer for result
|
|
|
|
*
|
2006-09-29 03:00:40 -06:00
|
|
|
* Copies the kernel idea of the window size into the user buffer.
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
tty: Fix lock order in tty_do_resize()
Commits 6a1c0680cf3ba94356ecd58833e1540c93472a57 and
9356b535fcb71db494fc434acceb79f56d15bda2, respectively
'tty: Convert termios_mutex to termios_rwsem' and
'n_tty: Access termios values safely'
introduced a circular lock dependency with console_lock and
termios_rwsem.
The lockdep report [1] shows that n_tty_write() will attempt
to claim console_lock while holding the termios_rwsem, whereas
tty_do_resize() may already hold the console_lock while
claiming the termios_rwsem.
Since n_tty_write() and tty_do_resize() do not contend
over the same data -- the tty->winsize structure -- correct
the lock dependency by introducing a new lock which
specifically serializes access to tty->winsize only.
[1] Lockdep report
======================================================
[ INFO: possible circular locking dependency detected ]
3.10.0-0+tip-xeon+lockdep #0+tip Not tainted
-------------------------------------------------------
modprobe/277 is trying to acquire lock:
(&tty->termios_rwsem){++++..}, at: [<ffffffff81452656>] tty_do_resize+0x36/0xe0
but task is already holding lock:
((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 ((fb_notifier_list).rwsem){.+.+.+}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b797>] down_read+0x47/0x5c
[<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #1 (console_lock){+.+.+.}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff810430a7>] console_lock+0x77/0x80
[<ffffffff8146b2a1>] con_flush_chars+0x31/0x50
[<ffffffff8145780c>] n_tty_write+0x1ec/0x4d0
[<ffffffff814541b9>] tty_write+0x159/0x2e0
[<ffffffff814543f5>] redirected_tty_write+0xb5/0xc0
[<ffffffff811ab9d5>] vfs_write+0xc5/0x1f0
[<ffffffff811abec5>] SyS_write+0x55/0xa0
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #0 (&tty->termios_rwsem){++++..}:
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Chain exists of:
&tty->termios_rwsem --> console_lock --> (fb_notifier_list).rwsem
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock((fb_notifier_list).rwsem);
lock(console_lock);
lock((fb_notifier_list).rwsem);
lock(&tty->termios_rwsem);
*** DEADLOCK ***
7 locks held by modprobe/277:
#0: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b5b>] __driver_attach+0x5b/0xb0
#1: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b69>] __driver_attach+0x69/0xb0
#2: (drm_global_mutex){+.+.+.}, at: [<ffffffffa008a6dd>] drm_get_pci_dev+0xbd/0x2a0 [drm]
#3: (registration_lock){+.+.+.}, at: [<ffffffff813d93f5>] register_framebuffer+0x25/0x320
#4: (&fb_info->lock){+.+.+.}, at: [<ffffffff813d8116>] lock_fb_info+0x26/0x60
#5: (console_lock){+.+.+.}, at: [<ffffffff813d95a4>] register_framebuffer+0x1d4/0x320
#6: ((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
stack backtrace:
CPU: 0 PID: 277 Comm: modprobe Not tainted 3.10.0-0+tip-xeon+lockdep #0+tip
Hardware name: Dell Inc. Precision WorkStation T5400 /0RW203, BIOS A11 04/30/2012
ffffffff8213e5e0 ffff8802aa2fb298 ffffffff81755f19 ffff8802aa2fb2e8
ffffffff8174f506 ffff8802aa2fa000 ffff8802aa2fb378 ffff8802aa2ea8e8
ffff8802aa2ea910 ffff8802aa2ea8e8 0000000000000006 0000000000000007
Call Trace:
[<ffffffff81755f19>] dump_stack+0x19/0x1b
[<ffffffff8174f506>] print_circular_bug+0x1fb/0x20c
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b775e>] ? mark_held_locks+0xae/0x120
[<ffffffff810b78d5>] ? trace_hardirqs_on_caller+0x105/0x1d0
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffff8173cbcb>] ? kmemleak_alloc+0x5b/0xc0
[<ffffffff81198874>] ? kmem_cache_alloc_trace+0x104/0x290
[<ffffffffa01035e1>] ? drm_fb_helper_single_add_all_connectors+0x81/0xf0 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff8175f162>] ? _raw_spin_unlock_irqrestore+0x42/0x80
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff81497b00>] ? driver_probe_device+0x3a0/0x3a0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff81399a50>] ? ddebug_proc_open+0xb0/0xb0
[<ffffffff813855ae>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-07-24 14:43:51 -06:00
|
|
|
* Locking: tty->winsize_mutex is taken to ensure the winsize data
|
2006-09-29 03:00:40 -06:00
|
|
|
* is consistent.
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2008-02-08 05:18:47 -07:00
|
|
|
static int tiocgwinsz(struct tty_struct *tty, struct winsize __user *arg)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2006-09-29 03:00:40 -06:00
|
|
|
int err;
|
|
|
|
|
tty: Fix lock order in tty_do_resize()
Commits 6a1c0680cf3ba94356ecd58833e1540c93472a57 and
9356b535fcb71db494fc434acceb79f56d15bda2, respectively
'tty: Convert termios_mutex to termios_rwsem' and
'n_tty: Access termios values safely'
introduced a circular lock dependency with console_lock and
termios_rwsem.
The lockdep report [1] shows that n_tty_write() will attempt
to claim console_lock while holding the termios_rwsem, whereas
tty_do_resize() may already hold the console_lock while
claiming the termios_rwsem.
Since n_tty_write() and tty_do_resize() do not contend
over the same data -- the tty->winsize structure -- correct
the lock dependency by introducing a new lock which
specifically serializes access to tty->winsize only.
[1] Lockdep report
======================================================
[ INFO: possible circular locking dependency detected ]
3.10.0-0+tip-xeon+lockdep #0+tip Not tainted
-------------------------------------------------------
modprobe/277 is trying to acquire lock:
(&tty->termios_rwsem){++++..}, at: [<ffffffff81452656>] tty_do_resize+0x36/0xe0
but task is already holding lock:
((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 ((fb_notifier_list).rwsem){.+.+.+}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b797>] down_read+0x47/0x5c
[<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #1 (console_lock){+.+.+.}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff810430a7>] console_lock+0x77/0x80
[<ffffffff8146b2a1>] con_flush_chars+0x31/0x50
[<ffffffff8145780c>] n_tty_write+0x1ec/0x4d0
[<ffffffff814541b9>] tty_write+0x159/0x2e0
[<ffffffff814543f5>] redirected_tty_write+0xb5/0xc0
[<ffffffff811ab9d5>] vfs_write+0xc5/0x1f0
[<ffffffff811abec5>] SyS_write+0x55/0xa0
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #0 (&tty->termios_rwsem){++++..}:
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Chain exists of:
&tty->termios_rwsem --> console_lock --> (fb_notifier_list).rwsem
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock((fb_notifier_list).rwsem);
lock(console_lock);
lock((fb_notifier_list).rwsem);
lock(&tty->termios_rwsem);
*** DEADLOCK ***
7 locks held by modprobe/277:
#0: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b5b>] __driver_attach+0x5b/0xb0
#1: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b69>] __driver_attach+0x69/0xb0
#2: (drm_global_mutex){+.+.+.}, at: [<ffffffffa008a6dd>] drm_get_pci_dev+0xbd/0x2a0 [drm]
#3: (registration_lock){+.+.+.}, at: [<ffffffff813d93f5>] register_framebuffer+0x25/0x320
#4: (&fb_info->lock){+.+.+.}, at: [<ffffffff813d8116>] lock_fb_info+0x26/0x60
#5: (console_lock){+.+.+.}, at: [<ffffffff813d95a4>] register_framebuffer+0x1d4/0x320
#6: ((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
stack backtrace:
CPU: 0 PID: 277 Comm: modprobe Not tainted 3.10.0-0+tip-xeon+lockdep #0+tip
Hardware name: Dell Inc. Precision WorkStation T5400 /0RW203, BIOS A11 04/30/2012
ffffffff8213e5e0 ffff8802aa2fb298 ffffffff81755f19 ffff8802aa2fb2e8
ffffffff8174f506 ffff8802aa2fa000 ffff8802aa2fb378 ffff8802aa2ea8e8
ffff8802aa2ea910 ffff8802aa2ea8e8 0000000000000006 0000000000000007
Call Trace:
[<ffffffff81755f19>] dump_stack+0x19/0x1b
[<ffffffff8174f506>] print_circular_bug+0x1fb/0x20c
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b775e>] ? mark_held_locks+0xae/0x120
[<ffffffff810b78d5>] ? trace_hardirqs_on_caller+0x105/0x1d0
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffff8173cbcb>] ? kmemleak_alloc+0x5b/0xc0
[<ffffffff81198874>] ? kmem_cache_alloc_trace+0x104/0x290
[<ffffffffa01035e1>] ? drm_fb_helper_single_add_all_connectors+0x81/0xf0 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff8175f162>] ? _raw_spin_unlock_irqrestore+0x42/0x80
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff81497b00>] ? driver_probe_device+0x3a0/0x3a0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff81399a50>] ? ddebug_proc_open+0xb0/0xb0
[<ffffffff813855ae>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-07-24 14:43:51 -06:00
|
|
|
mutex_lock(&tty->winsize_mutex);
|
2006-09-29 03:00:40 -06:00
|
|
|
err = copy_to_user(arg, &tty->winsize, sizeof(*arg));
|
tty: Fix lock order in tty_do_resize()
Commits 6a1c0680cf3ba94356ecd58833e1540c93472a57 and
9356b535fcb71db494fc434acceb79f56d15bda2, respectively
'tty: Convert termios_mutex to termios_rwsem' and
'n_tty: Access termios values safely'
introduced a circular lock dependency with console_lock and
termios_rwsem.
The lockdep report [1] shows that n_tty_write() will attempt
to claim console_lock while holding the termios_rwsem, whereas
tty_do_resize() may already hold the console_lock while
claiming the termios_rwsem.
Since n_tty_write() and tty_do_resize() do not contend
over the same data -- the tty->winsize structure -- correct
the lock dependency by introducing a new lock which
specifically serializes access to tty->winsize only.
[1] Lockdep report
======================================================
[ INFO: possible circular locking dependency detected ]
3.10.0-0+tip-xeon+lockdep #0+tip Not tainted
-------------------------------------------------------
modprobe/277 is trying to acquire lock:
(&tty->termios_rwsem){++++..}, at: [<ffffffff81452656>] tty_do_resize+0x36/0xe0
but task is already holding lock:
((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 ((fb_notifier_list).rwsem){.+.+.+}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b797>] down_read+0x47/0x5c
[<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #1 (console_lock){+.+.+.}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff810430a7>] console_lock+0x77/0x80
[<ffffffff8146b2a1>] con_flush_chars+0x31/0x50
[<ffffffff8145780c>] n_tty_write+0x1ec/0x4d0
[<ffffffff814541b9>] tty_write+0x159/0x2e0
[<ffffffff814543f5>] redirected_tty_write+0xb5/0xc0
[<ffffffff811ab9d5>] vfs_write+0xc5/0x1f0
[<ffffffff811abec5>] SyS_write+0x55/0xa0
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #0 (&tty->termios_rwsem){++++..}:
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Chain exists of:
&tty->termios_rwsem --> console_lock --> (fb_notifier_list).rwsem
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock((fb_notifier_list).rwsem);
lock(console_lock);
lock((fb_notifier_list).rwsem);
lock(&tty->termios_rwsem);
*** DEADLOCK ***
7 locks held by modprobe/277:
#0: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b5b>] __driver_attach+0x5b/0xb0
#1: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b69>] __driver_attach+0x69/0xb0
#2: (drm_global_mutex){+.+.+.}, at: [<ffffffffa008a6dd>] drm_get_pci_dev+0xbd/0x2a0 [drm]
#3: (registration_lock){+.+.+.}, at: [<ffffffff813d93f5>] register_framebuffer+0x25/0x320
#4: (&fb_info->lock){+.+.+.}, at: [<ffffffff813d8116>] lock_fb_info+0x26/0x60
#5: (console_lock){+.+.+.}, at: [<ffffffff813d95a4>] register_framebuffer+0x1d4/0x320
#6: ((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
stack backtrace:
CPU: 0 PID: 277 Comm: modprobe Not tainted 3.10.0-0+tip-xeon+lockdep #0+tip
Hardware name: Dell Inc. Precision WorkStation T5400 /0RW203, BIOS A11 04/30/2012
ffffffff8213e5e0 ffff8802aa2fb298 ffffffff81755f19 ffff8802aa2fb2e8
ffffffff8174f506 ffff8802aa2fa000 ffff8802aa2fb378 ffff8802aa2ea8e8
ffff8802aa2ea910 ffff8802aa2ea8e8 0000000000000006 0000000000000007
Call Trace:
[<ffffffff81755f19>] dump_stack+0x19/0x1b
[<ffffffff8174f506>] print_circular_bug+0x1fb/0x20c
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b775e>] ? mark_held_locks+0xae/0x120
[<ffffffff810b78d5>] ? trace_hardirqs_on_caller+0x105/0x1d0
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffff8173cbcb>] ? kmemleak_alloc+0x5b/0xc0
[<ffffffff81198874>] ? kmem_cache_alloc_trace+0x104/0x290
[<ffffffffa01035e1>] ? drm_fb_helper_single_add_all_connectors+0x81/0xf0 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff8175f162>] ? _raw_spin_unlock_irqrestore+0x42/0x80
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff81497b00>] ? driver_probe_device+0x3a0/0x3a0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff81399a50>] ? ddebug_proc_open+0xb0/0xb0
[<ffffffff813855ae>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-07-24 14:43:51 -06:00
|
|
|
mutex_unlock(&tty->winsize_mutex);
|
2006-09-29 03:00:40 -06:00
|
|
|
|
|
|
|
return err ? -EFAULT: 0;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2008-08-15 03:39:38 -06:00
|
|
|
* tty_do_resize - resize event
|
|
|
|
* @tty: tty being resized
|
|
|
|
* @rows: rows (character)
|
|
|
|
* @cols: cols (character)
|
|
|
|
*
|
tree-wide: Assorted spelling fixes
In particular, several occurances of funny versions of 'success',
'unknown', 'therefore', 'acknowledge', 'argument', 'achieve', 'address',
'beginning', 'desirable', 'separate' and 'necessary' are fixed.
Signed-off-by: Daniel Mack <daniel@caiaq.de>
Cc: Joe Perches <joe@perches.com>
Cc: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
2010-02-02 17:01:28 -07:00
|
|
|
* Update the termios variables and send the necessary signals to
|
2008-08-15 03:39:38 -06:00
|
|
|
* peform a terminal resize correctly
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2009-01-02 06:43:17 -07:00
|
|
|
int tty_do_resize(struct tty_struct *tty, struct winsize *ws)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2009-01-02 06:43:17 -07:00
|
|
|
struct pid *pgrp;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2009-01-02 06:43:17 -07:00
|
|
|
/* Lock the tty */
|
tty: Fix lock order in tty_do_resize()
Commits 6a1c0680cf3ba94356ecd58833e1540c93472a57 and
9356b535fcb71db494fc434acceb79f56d15bda2, respectively
'tty: Convert termios_mutex to termios_rwsem' and
'n_tty: Access termios values safely'
introduced a circular lock dependency with console_lock and
termios_rwsem.
The lockdep report [1] shows that n_tty_write() will attempt
to claim console_lock while holding the termios_rwsem, whereas
tty_do_resize() may already hold the console_lock while
claiming the termios_rwsem.
Since n_tty_write() and tty_do_resize() do not contend
over the same data -- the tty->winsize structure -- correct
the lock dependency by introducing a new lock which
specifically serializes access to tty->winsize only.
[1] Lockdep report
======================================================
[ INFO: possible circular locking dependency detected ]
3.10.0-0+tip-xeon+lockdep #0+tip Not tainted
-------------------------------------------------------
modprobe/277 is trying to acquire lock:
(&tty->termios_rwsem){++++..}, at: [<ffffffff81452656>] tty_do_resize+0x36/0xe0
but task is already holding lock:
((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 ((fb_notifier_list).rwsem){.+.+.+}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b797>] down_read+0x47/0x5c
[<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #1 (console_lock){+.+.+.}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff810430a7>] console_lock+0x77/0x80
[<ffffffff8146b2a1>] con_flush_chars+0x31/0x50
[<ffffffff8145780c>] n_tty_write+0x1ec/0x4d0
[<ffffffff814541b9>] tty_write+0x159/0x2e0
[<ffffffff814543f5>] redirected_tty_write+0xb5/0xc0
[<ffffffff811ab9d5>] vfs_write+0xc5/0x1f0
[<ffffffff811abec5>] SyS_write+0x55/0xa0
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #0 (&tty->termios_rwsem){++++..}:
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Chain exists of:
&tty->termios_rwsem --> console_lock --> (fb_notifier_list).rwsem
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock((fb_notifier_list).rwsem);
lock(console_lock);
lock((fb_notifier_list).rwsem);
lock(&tty->termios_rwsem);
*** DEADLOCK ***
7 locks held by modprobe/277:
#0: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b5b>] __driver_attach+0x5b/0xb0
#1: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b69>] __driver_attach+0x69/0xb0
#2: (drm_global_mutex){+.+.+.}, at: [<ffffffffa008a6dd>] drm_get_pci_dev+0xbd/0x2a0 [drm]
#3: (registration_lock){+.+.+.}, at: [<ffffffff813d93f5>] register_framebuffer+0x25/0x320
#4: (&fb_info->lock){+.+.+.}, at: [<ffffffff813d8116>] lock_fb_info+0x26/0x60
#5: (console_lock){+.+.+.}, at: [<ffffffff813d95a4>] register_framebuffer+0x1d4/0x320
#6: ((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
stack backtrace:
CPU: 0 PID: 277 Comm: modprobe Not tainted 3.10.0-0+tip-xeon+lockdep #0+tip
Hardware name: Dell Inc. Precision WorkStation T5400 /0RW203, BIOS A11 04/30/2012
ffffffff8213e5e0 ffff8802aa2fb298 ffffffff81755f19 ffff8802aa2fb2e8
ffffffff8174f506 ffff8802aa2fa000 ffff8802aa2fb378 ffff8802aa2ea8e8
ffff8802aa2ea910 ffff8802aa2ea8e8 0000000000000006 0000000000000007
Call Trace:
[<ffffffff81755f19>] dump_stack+0x19/0x1b
[<ffffffff8174f506>] print_circular_bug+0x1fb/0x20c
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b775e>] ? mark_held_locks+0xae/0x120
[<ffffffff810b78d5>] ? trace_hardirqs_on_caller+0x105/0x1d0
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffff8173cbcb>] ? kmemleak_alloc+0x5b/0xc0
[<ffffffff81198874>] ? kmem_cache_alloc_trace+0x104/0x290
[<ffffffffa01035e1>] ? drm_fb_helper_single_add_all_connectors+0x81/0xf0 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff8175f162>] ? _raw_spin_unlock_irqrestore+0x42/0x80
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff81497b00>] ? driver_probe_device+0x3a0/0x3a0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff81399a50>] ? ddebug_proc_open+0xb0/0xb0
[<ffffffff813855ae>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-07-24 14:43:51 -06:00
|
|
|
mutex_lock(&tty->winsize_mutex);
|
2009-01-02 06:43:17 -07:00
|
|
|
if (!memcmp(ws, &tty->winsize, sizeof(*ws)))
|
2006-09-29 03:00:03 -06:00
|
|
|
goto done;
|
2008-04-30 01:53:30 -06:00
|
|
|
|
2014-10-16 12:59:45 -06:00
|
|
|
/* Signal the foreground process group */
|
|
|
|
pgrp = tty_get_pgrp(tty);
|
2008-04-30 01:53:30 -06:00
|
|
|
if (pgrp)
|
|
|
|
kill_pgrp(pgrp, SIGWINCH, 1);
|
|
|
|
put_pid(pgrp);
|
|
|
|
|
2008-08-15 03:39:38 -06:00
|
|
|
tty->winsize = *ws;
|
2006-09-29 03:00:03 -06:00
|
|
|
done:
|
tty: Fix lock order in tty_do_resize()
Commits 6a1c0680cf3ba94356ecd58833e1540c93472a57 and
9356b535fcb71db494fc434acceb79f56d15bda2, respectively
'tty: Convert termios_mutex to termios_rwsem' and
'n_tty: Access termios values safely'
introduced a circular lock dependency with console_lock and
termios_rwsem.
The lockdep report [1] shows that n_tty_write() will attempt
to claim console_lock while holding the termios_rwsem, whereas
tty_do_resize() may already hold the console_lock while
claiming the termios_rwsem.
Since n_tty_write() and tty_do_resize() do not contend
over the same data -- the tty->winsize structure -- correct
the lock dependency by introducing a new lock which
specifically serializes access to tty->winsize only.
[1] Lockdep report
======================================================
[ INFO: possible circular locking dependency detected ]
3.10.0-0+tip-xeon+lockdep #0+tip Not tainted
-------------------------------------------------------
modprobe/277 is trying to acquire lock:
(&tty->termios_rwsem){++++..}, at: [<ffffffff81452656>] tty_do_resize+0x36/0xe0
but task is already holding lock:
((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 ((fb_notifier_list).rwsem){.+.+.+}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b797>] down_read+0x47/0x5c
[<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #1 (console_lock){+.+.+.}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff810430a7>] console_lock+0x77/0x80
[<ffffffff8146b2a1>] con_flush_chars+0x31/0x50
[<ffffffff8145780c>] n_tty_write+0x1ec/0x4d0
[<ffffffff814541b9>] tty_write+0x159/0x2e0
[<ffffffff814543f5>] redirected_tty_write+0xb5/0xc0
[<ffffffff811ab9d5>] vfs_write+0xc5/0x1f0
[<ffffffff811abec5>] SyS_write+0x55/0xa0
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #0 (&tty->termios_rwsem){++++..}:
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Chain exists of:
&tty->termios_rwsem --> console_lock --> (fb_notifier_list).rwsem
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock((fb_notifier_list).rwsem);
lock(console_lock);
lock((fb_notifier_list).rwsem);
lock(&tty->termios_rwsem);
*** DEADLOCK ***
7 locks held by modprobe/277:
#0: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b5b>] __driver_attach+0x5b/0xb0
#1: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b69>] __driver_attach+0x69/0xb0
#2: (drm_global_mutex){+.+.+.}, at: [<ffffffffa008a6dd>] drm_get_pci_dev+0xbd/0x2a0 [drm]
#3: (registration_lock){+.+.+.}, at: [<ffffffff813d93f5>] register_framebuffer+0x25/0x320
#4: (&fb_info->lock){+.+.+.}, at: [<ffffffff813d8116>] lock_fb_info+0x26/0x60
#5: (console_lock){+.+.+.}, at: [<ffffffff813d95a4>] register_framebuffer+0x1d4/0x320
#6: ((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
stack backtrace:
CPU: 0 PID: 277 Comm: modprobe Not tainted 3.10.0-0+tip-xeon+lockdep #0+tip
Hardware name: Dell Inc. Precision WorkStation T5400 /0RW203, BIOS A11 04/30/2012
ffffffff8213e5e0 ffff8802aa2fb298 ffffffff81755f19 ffff8802aa2fb2e8
ffffffff8174f506 ffff8802aa2fa000 ffff8802aa2fb378 ffff8802aa2ea8e8
ffff8802aa2ea910 ffff8802aa2ea8e8 0000000000000006 0000000000000007
Call Trace:
[<ffffffff81755f19>] dump_stack+0x19/0x1b
[<ffffffff8174f506>] print_circular_bug+0x1fb/0x20c
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b775e>] ? mark_held_locks+0xae/0x120
[<ffffffff810b78d5>] ? trace_hardirqs_on_caller+0x105/0x1d0
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffff8173cbcb>] ? kmemleak_alloc+0x5b/0xc0
[<ffffffff81198874>] ? kmem_cache_alloc_trace+0x104/0x290
[<ffffffffa01035e1>] ? drm_fb_helper_single_add_all_connectors+0x81/0xf0 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff8175f162>] ? _raw_spin_unlock_irqrestore+0x42/0x80
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff81497b00>] ? driver_probe_device+0x3a0/0x3a0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff81399a50>] ? ddebug_proc_open+0xb0/0xb0
[<ffffffff813855ae>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-07-24 14:43:51 -06:00
|
|
|
mutex_unlock(&tty->winsize_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
return 0;
|
|
|
|
}
|
2013-01-04 06:55:13 -07:00
|
|
|
EXPORT_SYMBOL(tty_do_resize);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-08-15 03:39:38 -06:00
|
|
|
/**
|
|
|
|
* tiocswinsz - implement window size set ioctl
|
2009-01-02 06:43:17 -07:00
|
|
|
* @tty; tty side of tty
|
2008-08-15 03:39:38 -06:00
|
|
|
* @arg: user buffer for result
|
|
|
|
*
|
|
|
|
* Copies the user idea of the window size to the kernel. Traditionally
|
|
|
|
* this is just advisory information but for the Linux console it
|
|
|
|
* actually has driver level meaning and triggers a VC resize.
|
|
|
|
*
|
|
|
|
* Locking:
|
2011-03-30 19:57:33 -06:00
|
|
|
* Driver dependent. The default do_resize method takes the
|
2008-08-15 03:39:38 -06:00
|
|
|
* tty termios mutex and ctrl_lock. The console takes its own lock
|
|
|
|
* then calls into the default method.
|
|
|
|
*/
|
|
|
|
|
2009-01-02 06:43:17 -07:00
|
|
|
static int tiocswinsz(struct tty_struct *tty, struct winsize __user *arg)
|
2008-08-15 03:39:38 -06:00
|
|
|
{
|
|
|
|
struct winsize tmp_ws;
|
|
|
|
if (copy_from_user(&tmp_ws, arg, sizeof(*arg)))
|
|
|
|
return -EFAULT;
|
|
|
|
|
|
|
|
if (tty->ops->resize)
|
2009-01-02 06:43:17 -07:00
|
|
|
return tty->ops->resize(tty, &tmp_ws);
|
2008-08-15 03:39:38 -06:00
|
|
|
else
|
2009-01-02 06:43:17 -07:00
|
|
|
return tty_do_resize(tty, &tmp_ws);
|
2008-08-15 03:39:38 -06:00
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tioccons - allow admin to move logical console
|
|
|
|
* @file: the file to become console
|
|
|
|
*
|
2011-03-30 19:57:33 -06:00
|
|
|
* Allow the administrator to move the redirected console device
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
|
|
|
* Locking: uses redirect_lock to guard the redirect information
|
|
|
|
*/
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static int tioccons(struct file *file)
|
|
|
|
{
|
|
|
|
if (!capable(CAP_SYS_ADMIN))
|
|
|
|
return -EPERM;
|
|
|
|
if (file->f_op->write == redirected_tty_write) {
|
|
|
|
struct file *f;
|
|
|
|
spin_lock(&redirect_lock);
|
|
|
|
f = redirect;
|
|
|
|
redirect = NULL;
|
|
|
|
spin_unlock(&redirect_lock);
|
|
|
|
if (f)
|
|
|
|
fput(f);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
spin_lock(&redirect_lock);
|
|
|
|
if (redirect) {
|
|
|
|
spin_unlock(&redirect_lock);
|
|
|
|
return -EBUSY;
|
|
|
|
}
|
2012-08-27 12:48:26 -06:00
|
|
|
redirect = get_file(file);
|
2005-04-16 16:20:36 -06:00
|
|
|
spin_unlock(&redirect_lock);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* fionbio - non blocking ioctl
|
|
|
|
* @file: file to set blocking value
|
|
|
|
* @p: user parameter
|
|
|
|
*
|
|
|
|
* Historical tty interfaces had a blocking control ioctl before
|
|
|
|
* the generic functionality existed. This piece of history is preserved
|
|
|
|
* in the expected tty API of posix OS's.
|
|
|
|
*
|
2009-09-19 14:13:19 -06:00
|
|
|
* Locking: none, the open file handle ensures it won't go away.
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
static int fionbio(struct file *file, int __user *p)
|
|
|
|
{
|
|
|
|
int nonblock;
|
|
|
|
|
|
|
|
if (get_user(nonblock, p))
|
|
|
|
return -EFAULT;
|
|
|
|
|
2009-02-06 15:25:24 -07:00
|
|
|
spin_lock(&file->f_lock);
|
2005-04-16 16:20:36 -06:00
|
|
|
if (nonblock)
|
|
|
|
file->f_flags |= O_NONBLOCK;
|
|
|
|
else
|
|
|
|
file->f_flags &= ~O_NONBLOCK;
|
2009-02-06 15:25:24 -07:00
|
|
|
spin_unlock(&file->f_lock);
|
2005-04-16 16:20:36 -06:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tiocsctty - set controlling tty
|
|
|
|
* @tty: tty structure
|
|
|
|
* @arg: user argument
|
|
|
|
*
|
|
|
|
* This ioctl is used to manage job control. It permits a session
|
|
|
|
* leader to set this tty as the controlling tty for the session.
|
|
|
|
*
|
|
|
|
* Locking:
|
2014-10-16 12:59:49 -06:00
|
|
|
* Takes tty_lock() to serialize proc_set_tty() for this tty
|
2006-12-08 03:36:04 -07:00
|
|
|
* Takes tasklist_lock internally to walk sessions
|
|
|
|
* Takes ->siglock() when updating signal->tty
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2015-10-04 11:29:12 -06:00
|
|
|
static int tiocsctty(struct tty_struct *tty, struct file *file, int arg)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2006-12-08 03:36:04 -07:00
|
|
|
int ret = 0;
|
|
|
|
|
2014-10-16 12:59:49 -06:00
|
|
|
tty_lock(tty);
|
2014-10-16 12:59:47 -06:00
|
|
|
read_lock(&tasklist_lock);
|
|
|
|
|
|
|
|
if (current->signal->leader && (task_session(current) == tty->session))
|
|
|
|
goto unlock;
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* The process must be a session leader and
|
|
|
|
* not have a controlling tty already.
|
|
|
|
*/
|
2006-12-08 03:36:04 -07:00
|
|
|
if (!current->signal->leader || current->signal->tty) {
|
|
|
|
ret = -EPERM;
|
|
|
|
goto unlock;
|
|
|
|
}
|
|
|
|
|
2007-02-12 01:53:00 -07:00
|
|
|
if (tty->session) {
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* This tty is already the controlling
|
|
|
|
* tty for another session group!
|
|
|
|
*/
|
2008-02-08 05:18:47 -07:00
|
|
|
if (arg == 1 && capable(CAP_SYS_ADMIN)) {
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* Steal it away
|
|
|
|
*/
|
2006-12-08 03:36:04 -07:00
|
|
|
session_clear_tty(tty->session);
|
|
|
|
} else {
|
|
|
|
ret = -EPERM;
|
|
|
|
goto unlock;
|
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2015-10-04 11:29:12 -06:00
|
|
|
|
|
|
|
/* See the comment in tty_open(). */
|
|
|
|
if ((file->f_mode & FMODE_READ) == 0 && !capable(CAP_SYS_ADMIN)) {
|
|
|
|
ret = -EPERM;
|
|
|
|
goto unlock;
|
|
|
|
}
|
|
|
|
|
2014-10-16 12:59:43 -06:00
|
|
|
proc_set_tty(tty);
|
2006-12-08 03:36:04 -07:00
|
|
|
unlock:
|
2014-10-16 12:59:47 -06:00
|
|
|
read_unlock(&tasklist_lock);
|
2014-10-16 12:59:49 -06:00
|
|
|
tty_unlock(tty);
|
2006-12-08 03:36:04 -07:00
|
|
|
return ret;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2008-04-30 01:53:31 -06:00
|
|
|
/**
|
|
|
|
* tty_get_pgrp - return a ref counted pgrp pid
|
|
|
|
* @tty: tty to read
|
|
|
|
*
|
|
|
|
* Returns a refcounted instance of the pid struct for the process
|
|
|
|
* group controlling the tty.
|
|
|
|
*/
|
|
|
|
|
|
|
|
struct pid *tty_get_pgrp(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
unsigned long flags;
|
|
|
|
struct pid *pgrp;
|
|
|
|
|
|
|
|
spin_lock_irqsave(&tty->ctrl_lock, flags);
|
|
|
|
pgrp = get_pid(tty->pgrp);
|
|
|
|
spin_unlock_irqrestore(&tty->ctrl_lock, flags);
|
|
|
|
|
|
|
|
return pgrp;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(tty_get_pgrp);
|
|
|
|
|
2014-10-16 12:59:48 -06:00
|
|
|
/*
|
|
|
|
* This checks not only the pgrp, but falls back on the pid if no
|
|
|
|
* satisfactory pgrp is found. I dunno - gdb doesn't work correctly
|
|
|
|
* without this...
|
|
|
|
*
|
|
|
|
* The caller must hold rcu lock or the tasklist lock.
|
|
|
|
*/
|
|
|
|
static struct pid *session_of_pgrp(struct pid *pgrp)
|
|
|
|
{
|
|
|
|
struct task_struct *p;
|
|
|
|
struct pid *sid = NULL;
|
|
|
|
|
|
|
|
p = pid_task(pgrp, PIDTYPE_PGID);
|
|
|
|
if (p == NULL)
|
|
|
|
p = pid_task(pgrp, PIDTYPE_PID);
|
|
|
|
if (p != NULL)
|
|
|
|
sid = task_session(p);
|
|
|
|
|
|
|
|
return sid;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tiocgpgrp - get process group
|
|
|
|
* @tty: tty passed by user
|
2011-03-30 19:57:33 -06:00
|
|
|
* @real_tty: tty side of the tty passed by the user if a pty else the tty
|
2006-08-27 02:24:01 -06:00
|
|
|
* @p: returned pid
|
|
|
|
*
|
|
|
|
* Obtain the process group of the tty. If there is no process group
|
|
|
|
* return an error.
|
|
|
|
*
|
2006-12-08 03:36:04 -07:00
|
|
|
* Locking: none. Reference to current->signal->tty is safe.
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static int tiocgpgrp(struct tty_struct *tty, struct tty_struct *real_tty, pid_t __user *p)
|
|
|
|
{
|
2008-04-30 01:53:31 -06:00
|
|
|
struct pid *pid;
|
|
|
|
int ret;
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* (tty == real_tty) is a cheap way of
|
|
|
|
* testing if the tty is NOT a master pty.
|
|
|
|
*/
|
|
|
|
if (tty == real_tty && current->signal->tty != real_tty)
|
|
|
|
return -ENOTTY;
|
2008-04-30 01:53:31 -06:00
|
|
|
pid = tty_get_pgrp(real_tty);
|
|
|
|
ret = put_user(pid_vnr(pid), p);
|
|
|
|
put_pid(pid);
|
|
|
|
return ret;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tiocspgrp - attempt to set process group
|
|
|
|
* @tty: tty passed by user
|
|
|
|
* @real_tty: tty side device matching tty passed by user
|
|
|
|
* @p: pid pointer
|
|
|
|
*
|
|
|
|
* Set the process group of the tty to the session passed. Only
|
|
|
|
* permitted where the tty session is our session.
|
|
|
|
*
|
2008-04-30 01:53:30 -06:00
|
|
|
* Locking: RCU, ctrl lock
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static int tiocspgrp(struct tty_struct *tty, struct tty_struct *real_tty, pid_t __user *p)
|
|
|
|
{
|
2007-02-12 01:52:56 -07:00
|
|
|
struct pid *pgrp;
|
|
|
|
pid_t pgrp_nr;
|
2005-04-16 16:20:36 -06:00
|
|
|
int retval = tty_check_change(real_tty);
|
|
|
|
|
|
|
|
if (retval == -EIO)
|
|
|
|
return -ENOTTY;
|
|
|
|
if (retval)
|
|
|
|
return retval;
|
|
|
|
if (!current->signal->tty ||
|
|
|
|
(current->signal->tty != real_tty) ||
|
2007-02-12 01:53:00 -07:00
|
|
|
(real_tty->session != task_session(current)))
|
2005-04-16 16:20:36 -06:00
|
|
|
return -ENOTTY;
|
2007-02-12 01:52:56 -07:00
|
|
|
if (get_user(pgrp_nr, p))
|
2005-04-16 16:20:36 -06:00
|
|
|
return -EFAULT;
|
2007-02-12 01:52:56 -07:00
|
|
|
if (pgrp_nr < 0)
|
2005-04-16 16:20:36 -06:00
|
|
|
return -EINVAL;
|
2007-02-12 01:52:56 -07:00
|
|
|
rcu_read_lock();
|
2007-10-19 00:40:14 -06:00
|
|
|
pgrp = find_vpid(pgrp_nr);
|
2007-02-12 01:52:56 -07:00
|
|
|
retval = -ESRCH;
|
|
|
|
if (!pgrp)
|
|
|
|
goto out_unlock;
|
|
|
|
retval = -EPERM;
|
|
|
|
if (session_of_pgrp(pgrp) != task_session(current))
|
|
|
|
goto out_unlock;
|
|
|
|
retval = 0;
|
2015-10-10 18:28:43 -06:00
|
|
|
spin_lock_irq(&tty->ctrl_lock);
|
2007-02-12 01:53:00 -07:00
|
|
|
put_pid(real_tty->pgrp);
|
|
|
|
real_tty->pgrp = get_pid(pgrp);
|
2015-10-10 18:28:43 -06:00
|
|
|
spin_unlock_irq(&tty->ctrl_lock);
|
2007-02-12 01:52:56 -07:00
|
|
|
out_unlock:
|
|
|
|
rcu_read_unlock();
|
|
|
|
return retval;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tiocgsid - get session id
|
|
|
|
* @tty: tty passed by user
|
2011-03-30 19:57:33 -06:00
|
|
|
* @real_tty: tty side of the tty passed by the user if a pty else the tty
|
2006-08-27 02:24:01 -06:00
|
|
|
* @p: pointer to returned session id
|
|
|
|
*
|
|
|
|
* Obtain the session id of the tty. If there is no session
|
|
|
|
* return an error.
|
|
|
|
*
|
2006-12-08 03:36:04 -07:00
|
|
|
* Locking: none. Reference to current->signal->tty is safe.
|
2006-08-27 02:24:01 -06:00
|
|
|
*/
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static int tiocgsid(struct tty_struct *tty, struct tty_struct *real_tty, pid_t __user *p)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* (tty == real_tty) is a cheap way of
|
|
|
|
* testing if the tty is NOT a master pty.
|
|
|
|
*/
|
|
|
|
if (tty == real_tty && current->signal->tty != real_tty)
|
|
|
|
return -ENOTTY;
|
2007-02-12 01:53:00 -07:00
|
|
|
if (!real_tty->session)
|
2005-04-16 16:20:36 -06:00
|
|
|
return -ENOTTY;
|
2007-10-19 00:40:14 -06:00
|
|
|
return put_user(pid_vnr(real_tty->session), p);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* tiocsetd - set line discipline
|
|
|
|
* @tty: tty device
|
|
|
|
* @p: pointer to user data
|
|
|
|
*
|
|
|
|
* Set the line discipline according to user request.
|
|
|
|
*
|
|
|
|
* Locking: see tty_set_ldisc, this function is just a helper
|
|
|
|
*/
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static int tiocsetd(struct tty_struct *tty, int __user *p)
|
|
|
|
{
|
2016-01-10 23:41:04 -07:00
|
|
|
int disc;
|
2008-04-30 01:53:29 -06:00
|
|
|
int ret;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2016-01-10 23:41:04 -07:00
|
|
|
if (get_user(disc, p))
|
2005-04-16 16:20:36 -06:00
|
|
|
return -EFAULT;
|
2008-04-30 01:53:29 -06:00
|
|
|
|
2016-01-10 23:41:04 -07:00
|
|
|
ret = tty_set_ldisc(tty, disc);
|
2008-04-30 01:53:29 -06:00
|
|
|
|
|
|
|
return ret;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2016-01-10 23:40:55 -07:00
|
|
|
/**
|
|
|
|
* tiocgetd - get line discipline
|
|
|
|
* @tty: tty device
|
|
|
|
* @p: pointer to user data
|
|
|
|
*
|
|
|
|
* Retrieves the line discipline id directly from the ldisc.
|
|
|
|
*
|
|
|
|
* Locking: waits for ldisc reference (in case the line discipline
|
|
|
|
* is changing or the tty is being hungup)
|
|
|
|
*/
|
|
|
|
|
|
|
|
static int tiocgetd(struct tty_struct *tty, int __user *p)
|
|
|
|
{
|
|
|
|
struct tty_ldisc *ld;
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
ld = tty_ldisc_ref_wait(tty);
|
2016-01-10 23:41:01 -07:00
|
|
|
if (!ld)
|
|
|
|
return -EIO;
|
2016-01-10 23:40:55 -07:00
|
|
|
ret = put_user(ld->ops->num, p);
|
|
|
|
tty_ldisc_deref(ld);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
|
|
|
* send_break - performed time break
|
|
|
|
* @tty: device to break on
|
|
|
|
* @duration: timeout in mS
|
|
|
|
*
|
|
|
|
* Perform a timed break on hardware that lacks its own driver level
|
|
|
|
* timed break functionality.
|
|
|
|
*
|
|
|
|
* Locking:
|
2006-09-29 03:00:58 -06:00
|
|
|
* atomic_write_lock serializes
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
2005-06-25 15:58:42 -06:00
|
|
|
static int send_break(struct tty_struct *tty, unsigned int duration)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2008-07-22 04:18:03 -06:00
|
|
|
int retval;
|
|
|
|
|
|
|
|
if (tty->ops->break_ctl == NULL)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (tty->driver->flags & TTY_DRIVER_HARDWARE_BREAK)
|
|
|
|
retval = tty->ops->break_ctl(tty, duration);
|
|
|
|
else {
|
|
|
|
/* Do the work ourselves */
|
|
|
|
if (tty_write_lock(tty, 0) < 0)
|
|
|
|
return -EINTR;
|
|
|
|
retval = tty->ops->break_ctl(tty, -1);
|
|
|
|
if (retval)
|
|
|
|
goto out;
|
|
|
|
if (!signal_pending(current))
|
|
|
|
msleep_interruptible(duration);
|
|
|
|
retval = tty->ops->break_ctl(tty, 0);
|
|
|
|
out:
|
|
|
|
tty_write_unlock(tty);
|
|
|
|
if (signal_pending(current))
|
|
|
|
retval = -EINTR;
|
|
|
|
}
|
|
|
|
return retval;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2008-04-30 01:54:13 -06:00
|
|
|
* tty_tiocmget - get modem status
|
2006-08-27 02:24:01 -06:00
|
|
|
* @tty: tty device
|
|
|
|
* @file: user file pointer
|
|
|
|
* @p: pointer to result
|
|
|
|
*
|
|
|
|
* Obtain the modem status bits from the tty driver if the feature
|
|
|
|
* is supported. Return -EINVAL if it is not available.
|
|
|
|
*
|
|
|
|
* Locking: none (up to the driver)
|
|
|
|
*/
|
|
|
|
|
2011-02-14 09:26:14 -07:00
|
|
|
static int tty_tiocmget(struct tty_struct *tty, int __user *p)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
int retval = -EINVAL;
|
|
|
|
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->tiocmget) {
|
2011-02-14 09:26:14 -07:00
|
|
|
retval = tty->ops->tiocmget(tty);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
if (retval >= 0)
|
|
|
|
retval = put_user(retval, p);
|
|
|
|
}
|
|
|
|
return retval;
|
|
|
|
}
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2008-04-30 01:54:13 -06:00
|
|
|
* tty_tiocmset - set modem status
|
2006-08-27 02:24:01 -06:00
|
|
|
* @tty: tty device
|
|
|
|
* @cmd: command - clear bits, set bits or set all
|
|
|
|
* @p: pointer to desired bits
|
|
|
|
*
|
|
|
|
* Set the modem status bits from the tty driver if the feature
|
|
|
|
* is supported. Return -EINVAL if it is not available.
|
|
|
|
*
|
|
|
|
* Locking: none (up to the driver)
|
|
|
|
*/
|
|
|
|
|
2011-02-14 09:26:50 -07:00
|
|
|
static int tty_tiocmset(struct tty_struct *tty, unsigned int cmd,
|
2005-04-16 16:20:36 -06:00
|
|
|
unsigned __user *p)
|
|
|
|
{
|
2008-07-16 14:56:54 -06:00
|
|
|
int retval;
|
|
|
|
unsigned int set, clear, val;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-07-16 14:56:54 -06:00
|
|
|
if (tty->ops->tiocmset == NULL)
|
|
|
|
return -EINVAL;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-07-16 14:56:54 -06:00
|
|
|
retval = get_user(val, p);
|
|
|
|
if (retval)
|
|
|
|
return retval;
|
|
|
|
set = clear = 0;
|
|
|
|
switch (cmd) {
|
|
|
|
case TIOCMBIS:
|
|
|
|
set = val;
|
|
|
|
break;
|
|
|
|
case TIOCMBIC:
|
|
|
|
clear = val;
|
|
|
|
break;
|
|
|
|
case TIOCMSET:
|
|
|
|
set = val;
|
|
|
|
clear = ~val;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
set &= TIOCM_DTR|TIOCM_RTS|TIOCM_OUT1|TIOCM_OUT2|TIOCM_LOOP;
|
|
|
|
clear &= TIOCM_DTR|TIOCM_RTS|TIOCM_OUT1|TIOCM_OUT2|TIOCM_LOOP;
|
2011-02-14 09:26:50 -07:00
|
|
|
return tty->ops->tiocmset(tty, set, clear);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2010-09-16 11:21:24 -06:00
|
|
|
static int tty_tiocgicount(struct tty_struct *tty, void __user *arg)
|
|
|
|
{
|
|
|
|
int retval = -EINVAL;
|
|
|
|
struct serial_icounter_struct icount;
|
|
|
|
memset(&icount, 0, sizeof(icount));
|
|
|
|
if (tty->ops->get_icount)
|
|
|
|
retval = tty->ops->get_icount(tty, &icount);
|
|
|
|
if (retval != 0)
|
|
|
|
return retval;
|
|
|
|
if (copy_to_user(arg, &icount, sizeof(icount)))
|
|
|
|
return -EFAULT;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2014-11-06 08:56:33 -07:00
|
|
|
static void tty_warn_deprecated_flags(struct serial_struct __user *ss)
|
|
|
|
{
|
|
|
|
static DEFINE_RATELIMIT_STATE(depr_flags,
|
|
|
|
DEFAULT_RATELIMIT_INTERVAL,
|
|
|
|
DEFAULT_RATELIMIT_BURST);
|
|
|
|
char comm[TASK_COMM_LEN];
|
|
|
|
int flags;
|
|
|
|
|
|
|
|
if (get_user(flags, &ss->flags))
|
|
|
|
return;
|
|
|
|
|
|
|
|
flags &= ASYNC_DEPRECATED;
|
|
|
|
|
|
|
|
if (flags && __ratelimit(&depr_flags))
|
|
|
|
pr_warning("%s: '%s' is using deprecated serial flags (with no effect): %.8x\n",
|
|
|
|
__func__, get_task_comm(comm, current), flags);
|
|
|
|
}
|
|
|
|
|
2014-10-16 12:59:41 -06:00
|
|
|
/*
|
|
|
|
* if pty, return the slave side (real_tty)
|
|
|
|
* otherwise, return self
|
|
|
|
*/
|
|
|
|
static struct tty_struct *tty_pair_get_tty(struct tty_struct *tty)
|
2009-06-11 05:48:02 -06:00
|
|
|
{
|
|
|
|
if (tty->driver->type == TTY_DRIVER_TYPE_PTY &&
|
|
|
|
tty->driver->subtype == PTY_TYPE_MASTER)
|
|
|
|
tty = tty->link;
|
|
|
|
return tty;
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* Split this up, as gcc can choke on it otherwise..
|
|
|
|
*/
|
2008-04-30 01:53:29 -06:00
|
|
|
long tty_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
struct tty_struct *tty = file_tty(file);
|
|
|
|
struct tty_struct *real_tty;
|
2005-04-16 16:20:36 -06:00
|
|
|
void __user *p = (void __user *)arg;
|
|
|
|
int retval;
|
|
|
|
struct tty_ldisc *ld;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2013-02-27 14:59:05 -07:00
|
|
|
if (tty_paranoia_check(tty, file_inode(file), "tty_ioctl"))
|
2005-04-16 16:20:36 -06:00
|
|
|
return -EINVAL;
|
|
|
|
|
2009-06-11 05:48:02 -06:00
|
|
|
real_tty = tty_pair_get_tty(tty);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Factor out some common prep work
|
|
|
|
*/
|
|
|
|
switch (cmd) {
|
|
|
|
case TIOCSETD:
|
|
|
|
case TIOCSBRK:
|
|
|
|
case TIOCCBRK:
|
|
|
|
case TCSBRK:
|
2008-02-08 05:18:47 -07:00
|
|
|
case TCSBRKP:
|
2005-04-16 16:20:36 -06:00
|
|
|
retval = tty_check_change(tty);
|
|
|
|
if (retval)
|
|
|
|
return retval;
|
|
|
|
if (cmd != TIOCCBRK) {
|
|
|
|
tty_wait_until_sent(tty, 0);
|
|
|
|
if (signal_pending(current))
|
|
|
|
return -EINTR;
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2008-07-22 04:18:03 -06:00
|
|
|
/*
|
|
|
|
* Now do the stuff.
|
|
|
|
*/
|
2005-04-16 16:20:36 -06:00
|
|
|
switch (cmd) {
|
2008-02-08 05:18:47 -07:00
|
|
|
case TIOCSTI:
|
|
|
|
return tiocsti(tty, p);
|
|
|
|
case TIOCGWINSZ:
|
2008-10-13 03:38:46 -06:00
|
|
|
return tiocgwinsz(real_tty, p);
|
2008-02-08 05:18:47 -07:00
|
|
|
case TIOCSWINSZ:
|
2009-01-02 06:43:17 -07:00
|
|
|
return tiocswinsz(real_tty, p);
|
2008-02-08 05:18:47 -07:00
|
|
|
case TIOCCONS:
|
|
|
|
return real_tty != tty ? -EINVAL : tioccons(file);
|
|
|
|
case FIONBIO:
|
|
|
|
return fionbio(file, p);
|
|
|
|
case TIOCEXCL:
|
|
|
|
set_bit(TTY_EXCLUSIVE, &tty->flags);
|
|
|
|
return 0;
|
|
|
|
case TIOCNXCL:
|
|
|
|
clear_bit(TTY_EXCLUSIVE, &tty->flags);
|
|
|
|
return 0;
|
2012-10-24 13:43:22 -06:00
|
|
|
case TIOCGEXCL:
|
|
|
|
{
|
|
|
|
int excl = test_bit(TTY_EXCLUSIVE, &tty->flags);
|
|
|
|
return put_user(excl, (int __user *)p);
|
|
|
|
}
|
2008-02-08 05:18:47 -07:00
|
|
|
case TIOCNOTTY:
|
|
|
|
if (current->signal->tty != tty)
|
|
|
|
return -ENOTTY;
|
|
|
|
no_tty();
|
|
|
|
return 0;
|
|
|
|
case TIOCSCTTY:
|
2015-11-08 07:06:05 -07:00
|
|
|
return tiocsctty(real_tty, file, arg);
|
2008-02-08 05:18:47 -07:00
|
|
|
case TIOCGPGRP:
|
|
|
|
return tiocgpgrp(tty, real_tty, p);
|
|
|
|
case TIOCSPGRP:
|
|
|
|
return tiocspgrp(tty, real_tty, p);
|
|
|
|
case TIOCGSID:
|
|
|
|
return tiocgsid(tty, real_tty, p);
|
|
|
|
case TIOCGETD:
|
2016-01-10 23:40:55 -07:00
|
|
|
return tiocgetd(tty, p);
|
2008-02-08 05:18:47 -07:00
|
|
|
case TIOCSETD:
|
|
|
|
return tiocsetd(tty, p);
|
2011-02-17 10:39:28 -07:00
|
|
|
case TIOCVHANGUP:
|
|
|
|
if (!capable(CAP_SYS_ADMIN))
|
|
|
|
return -EPERM;
|
|
|
|
tty_vhangup(tty);
|
|
|
|
return 0;
|
2010-12-03 04:48:23 -07:00
|
|
|
case TIOCGDEV:
|
|
|
|
{
|
|
|
|
unsigned int ret = new_encode_dev(tty_devnum(real_tty));
|
|
|
|
return put_user(ret, (unsigned int __user *)p);
|
|
|
|
}
|
2008-02-08 05:18:47 -07:00
|
|
|
/*
|
|
|
|
* Break handling
|
|
|
|
*/
|
|
|
|
case TIOCSBRK: /* Turn break on, unconditionally */
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->break_ctl)
|
2008-07-22 04:18:03 -06:00
|
|
|
return tty->ops->break_ctl(tty, -1);
|
2008-02-08 05:18:47 -07:00
|
|
|
return 0;
|
|
|
|
case TIOCCBRK: /* Turn break off, unconditionally */
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->break_ctl)
|
2008-07-22 04:18:03 -06:00
|
|
|
return tty->ops->break_ctl(tty, 0);
|
2008-02-08 05:18:47 -07:00
|
|
|
return 0;
|
|
|
|
case TCSBRK: /* SVID version: non-zero arg --> no break */
|
|
|
|
/* non-zero arg means wait for all output data
|
|
|
|
* to be sent (performed above) but don't send break.
|
|
|
|
* This is used by the tcdrain() termios function.
|
|
|
|
*/
|
|
|
|
if (!arg)
|
|
|
|
return send_break(tty, 250);
|
|
|
|
return 0;
|
|
|
|
case TCSBRKP: /* support for POSIX tcsendbreak() */
|
|
|
|
return send_break(tty, arg ? arg*100 : 250);
|
|
|
|
|
|
|
|
case TIOCMGET:
|
2011-02-14 09:26:14 -07:00
|
|
|
return tty_tiocmget(tty, p);
|
2008-02-08 05:18:47 -07:00
|
|
|
case TIOCMSET:
|
|
|
|
case TIOCMBIC:
|
|
|
|
case TIOCMBIS:
|
2011-02-14 09:26:50 -07:00
|
|
|
return tty_tiocmset(tty, cmd, p);
|
2010-09-16 11:21:24 -06:00
|
|
|
case TIOCGICOUNT:
|
|
|
|
retval = tty_tiocgicount(tty, p);
|
|
|
|
/* For the moment allow fall through to the old method */
|
|
|
|
if (retval != -EINVAL)
|
|
|
|
return retval;
|
|
|
|
break;
|
2008-02-08 05:18:47 -07:00
|
|
|
case TCFLSH:
|
|
|
|
switch (arg) {
|
|
|
|
case TCIFLUSH:
|
|
|
|
case TCIOFLUSH:
|
|
|
|
/* flush tty buffer and allow ldisc to process ioctl */
|
2014-11-05 10:13:09 -07:00
|
|
|
tty_buffer_flush(tty, NULL);
|
2007-05-12 11:36:55 -06:00
|
|
|
break;
|
2008-02-08 05:18:47 -07:00
|
|
|
}
|
|
|
|
break;
|
2014-11-06 08:56:33 -07:00
|
|
|
case TIOCSSERIAL:
|
|
|
|
tty_warn_deprecated_flags(p);
|
|
|
|
break;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->ioctl) {
|
2014-11-05 10:26:25 -07:00
|
|
|
retval = tty->ops->ioctl(tty, cmd, arg);
|
2005-04-16 16:20:36 -06:00
|
|
|
if (retval != -ENOIOCTLCMD)
|
|
|
|
return retval;
|
|
|
|
}
|
|
|
|
ld = tty_ldisc_ref_wait(tty);
|
2016-01-10 23:41:01 -07:00
|
|
|
if (!ld)
|
|
|
|
return hung_up_tty_ioctl(file, cmd, arg);
|
2005-04-16 16:20:36 -06:00
|
|
|
retval = -EINVAL;
|
2008-07-16 14:53:12 -06:00
|
|
|
if (ld->ops->ioctl) {
|
|
|
|
retval = ld->ops->ioctl(tty, file, cmd, arg);
|
2005-04-16 16:20:36 -06:00
|
|
|
if (retval == -ENOIOCTLCMD)
|
2012-08-27 01:23:12 -06:00
|
|
|
retval = -ENOTTY;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
tty_ldisc_deref(ld);
|
|
|
|
return retval;
|
|
|
|
}
|
|
|
|
|
2007-05-10 23:22:50 -06:00
|
|
|
#ifdef CONFIG_COMPAT
|
2008-02-08 05:18:47 -07:00
|
|
|
static long tty_compat_ioctl(struct file *file, unsigned int cmd,
|
2007-05-10 23:22:50 -06:00
|
|
|
unsigned long arg)
|
|
|
|
{
|
tty: fix fu_list abuse
tty: fix fu_list abuse
tty code abuses fu_list, which causes a bug in remount,ro handling.
If a tty device node is opened on a filesystem, then the last link to the inode
removed, the filesystem will be allowed to be remounted readonly. This is
because fs_may_remount_ro does not find the 0 link tty inode on the file sb
list (because the tty code incorrectly removed it to use for its own purpose).
This can result in a filesystem with errors after it is marked "clean".
Taking idea from Christoph's initial patch, allocate a tty private struct
at file->private_data and put our required list fields in there, linking
file and tty. This makes tty nodes behave the same way as other device nodes
and avoid meddling with the vfs, and avoids this bug.
The error handling is not trivial in the tty code, so for this bugfix, I take
the simple approach of using __GFP_NOFAIL and don't worry about memory errors.
This is not a problem because our allocator doesn't fail small allocs as a rule
anyway. So proper error handling is left as an exercise for tty hackers.
[ Arguably filesystem's device inode would ideally be divorced from the
driver's pseudo inode when it is opened, but in practice it's not clear whether
that will ever be worth implementing. ]
Cc: linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2010-08-17 12:37:36 -06:00
|
|
|
struct tty_struct *tty = file_tty(file);
|
2007-05-10 23:22:50 -06:00
|
|
|
struct tty_ldisc *ld;
|
|
|
|
int retval = -ENOIOCTLCMD;
|
|
|
|
|
2013-02-27 14:59:05 -07:00
|
|
|
if (tty_paranoia_check(tty, file_inode(file), "tty_ioctl"))
|
2007-05-10 23:22:50 -06:00
|
|
|
return -EINVAL;
|
|
|
|
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->compat_ioctl) {
|
2014-11-05 10:26:25 -07:00
|
|
|
retval = tty->ops->compat_ioctl(tty, cmd, arg);
|
2007-05-10 23:22:50 -06:00
|
|
|
if (retval != -ENOIOCTLCMD)
|
|
|
|
return retval;
|
|
|
|
}
|
|
|
|
|
|
|
|
ld = tty_ldisc_ref_wait(tty);
|
2016-01-10 23:41:01 -07:00
|
|
|
if (!ld)
|
|
|
|
return hung_up_tty_compat_ioctl(file, cmd, arg);
|
2008-07-16 14:53:12 -06:00
|
|
|
if (ld->ops->compat_ioctl)
|
|
|
|
retval = ld->ops->compat_ioctl(tty, file, cmd, arg);
|
2011-10-05 15:13:13 -06:00
|
|
|
else
|
|
|
|
retval = n_tty_compat_ioctl_helper(tty, file, cmd, arg);
|
2007-05-10 23:22:50 -06:00
|
|
|
tty_ldisc_deref(ld);
|
|
|
|
|
|
|
|
return retval;
|
|
|
|
}
|
|
|
|
#endif
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2012-08-21 20:32:06 -06:00
|
|
|
static int this_tty(const void *t, struct file *file, unsigned fd)
|
|
|
|
{
|
|
|
|
if (likely(file->f_op->read != tty_read))
|
|
|
|
return 0;
|
|
|
|
return file_tty(file) != t ? 0 : fd + 1;
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* This implements the "Secure Attention Key" --- the idea is to
|
|
|
|
* prevent trojan horses by killing all processes associated with this
|
|
|
|
* tty when the user hits the "Secure Attention Key". Required for
|
|
|
|
* super-paranoid applications --- see the Orange Book for more details.
|
2008-02-08 05:18:47 -07:00
|
|
|
*
|
2005-04-16 16:20:36 -06:00
|
|
|
* This code could be nicer; ideally it should send a HUP, wait a few
|
|
|
|
* seconds, then send a INT, and then a KILL signal. But you then
|
|
|
|
* have to coordinate with the init process, since all processes associated
|
|
|
|
* with the current tty must be dead before the new getty is allowed
|
|
|
|
* to spawn.
|
|
|
|
*
|
|
|
|
* Now, if it would be correct ;-/ The current code has a nasty hole -
|
|
|
|
* it doesn't catch files in flight. We may send the descriptor to ourselves
|
|
|
|
* via AF_UNIX socket, close it and later fetch from socket. FIXME.
|
|
|
|
*
|
|
|
|
* Nasty bug: do_SAK is being called in interrupt context. This can
|
|
|
|
* deadlock. We punt it up to process context. AKPM - 16Mar2001
|
|
|
|
*/
|
2007-02-10 02:44:34 -07:00
|
|
|
void __do_SAK(struct tty_struct *tty)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
#ifdef TTY_SOFT_SAK
|
|
|
|
tty_hangup(tty);
|
|
|
|
#else
|
2006-03-28 17:11:02 -07:00
|
|
|
struct task_struct *g, *p;
|
2007-02-12 01:53:00 -07:00
|
|
|
struct pid *session;
|
2005-04-16 16:20:36 -06:00
|
|
|
int i;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
if (!tty)
|
|
|
|
return;
|
2006-12-08 03:36:04 -07:00
|
|
|
session = tty->session;
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2006-12-13 01:35:09 -07:00
|
|
|
tty_ldisc_flush(tty);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-04-30 01:54:13 -06:00
|
|
|
tty_driver_flush_buffer(tty);
|
2008-02-08 05:18:47 -07:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
read_lock(&tasklist_lock);
|
2006-03-28 17:11:02 -07:00
|
|
|
/* Kill the entire session */
|
2007-02-12 01:53:00 -07:00
|
|
|
do_each_pid_task(session, PIDTYPE_SID, p) {
|
2015-11-08 11:01:14 -07:00
|
|
|
tty_notice(tty, "SAK: killed process %d (%s): by session\n",
|
|
|
|
task_pid_nr(p), p->comm);
|
2006-03-28 17:11:02 -07:00
|
|
|
send_sig(SIGKILL, p, 1);
|
2007-02-12 01:53:00 -07:00
|
|
|
} while_each_pid_task(session, PIDTYPE_SID, p);
|
2015-11-08 11:01:14 -07:00
|
|
|
|
|
|
|
/* Now kill any processes that happen to have the tty open */
|
2006-03-28 17:11:02 -07:00
|
|
|
do_each_thread(g, p) {
|
|
|
|
if (p->signal->tty == tty) {
|
2015-11-08 11:01:14 -07:00
|
|
|
tty_notice(tty, "SAK: killed process %d (%s): by controlling tty\n",
|
|
|
|
task_pid_nr(p), p->comm);
|
2005-04-16 16:20:36 -06:00
|
|
|
send_sig(SIGKILL, p, 1);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
task_lock(p);
|
2012-08-21 20:32:06 -06:00
|
|
|
i = iterate_fd(p->files, 0, this_tty, tty);
|
|
|
|
if (i != 0) {
|
2015-11-08 11:01:14 -07:00
|
|
|
tty_notice(tty, "SAK: killed process %d (%s): by fd#%d\n",
|
|
|
|
task_pid_nr(p), p->comm, i - 1);
|
2012-08-21 20:32:06 -06:00
|
|
|
force_sig(SIGKILL, p);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
task_unlock(p);
|
2006-03-28 17:11:02 -07:00
|
|
|
} while_each_thread(g, p);
|
2005-04-16 16:20:36 -06:00
|
|
|
read_unlock(&tasklist_lock);
|
|
|
|
#endif
|
|
|
|
}
|
|
|
|
|
2007-02-10 02:44:34 -07:00
|
|
|
static void do_SAK_work(struct work_struct *work)
|
|
|
|
{
|
|
|
|
struct tty_struct *tty =
|
|
|
|
container_of(work, struct tty_struct, SAK_work);
|
|
|
|
__do_SAK(tty);
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* The tq handling here is a little racy - tty->SAK_work may already be queued.
|
|
|
|
* Fortunately we don't need to worry, because if ->SAK_work is already queued,
|
|
|
|
* the values which we write to it will be identical to the values which it
|
|
|
|
* already has. --akpm
|
|
|
|
*/
|
|
|
|
void do_SAK(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
if (!tty)
|
|
|
|
return;
|
|
|
|
schedule_work(&tty->SAK_work);
|
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL(do_SAK);
|
|
|
|
|
2013-02-06 16:59:18 -07:00
|
|
|
static int dev_match_devt(struct device *dev, const void *data)
|
2010-08-09 08:22:49 -06:00
|
|
|
{
|
2013-02-06 16:59:18 -07:00
|
|
|
const dev_t *devt = data;
|
2010-08-09 08:22:49 -06:00
|
|
|
return dev->devt == *devt;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Must put_device() after it's unused! */
|
|
|
|
static struct device *tty_get_device(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
dev_t devt = tty_devnum(tty);
|
|
|
|
return class_find_device(tty_class, NULL, &devt, dev_match_devt);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2006-08-27 02:24:01 -06:00
|
|
|
/**
|
2014-07-10 13:01:22 -06:00
|
|
|
* alloc_tty_struct
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
2014-07-10 13:01:22 -06:00
|
|
|
* This subroutine allocates and initializes a tty structure.
|
2006-08-27 02:24:01 -06:00
|
|
|
*
|
2014-07-10 13:01:22 -06:00
|
|
|
* Locking: none - tty in question is not exposed at this point
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2006-08-27 02:24:01 -06:00
|
|
|
|
2014-07-10 13:01:22 -06:00
|
|
|
struct tty_struct *alloc_tty_struct(struct tty_driver *driver, int idx)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2014-07-10 13:01:22 -06:00
|
|
|
struct tty_struct *tty;
|
|
|
|
|
|
|
|
tty = kzalloc(sizeof(*tty), GFP_KERNEL);
|
|
|
|
if (!tty)
|
|
|
|
return NULL;
|
|
|
|
|
2008-10-13 03:37:26 -06:00
|
|
|
kref_init(&tty->kref);
|
2005-04-16 16:20:36 -06:00
|
|
|
tty->magic = TTY_MAGIC;
|
2008-07-22 04:16:55 -06:00
|
|
|
tty_ldisc_init(tty);
|
2007-02-12 01:53:00 -07:00
|
|
|
tty->session = NULL;
|
|
|
|
tty->pgrp = NULL;
|
2012-08-08 09:30:13 -06:00
|
|
|
mutex_init(&tty->legacy_mutex);
|
2013-06-15 07:14:31 -06:00
|
|
|
mutex_init(&tty->throttle_mutex);
|
2013-06-15 07:14:23 -06:00
|
|
|
init_rwsem(&tty->termios_rwsem);
|
tty: Fix lock order in tty_do_resize()
Commits 6a1c0680cf3ba94356ecd58833e1540c93472a57 and
9356b535fcb71db494fc434acceb79f56d15bda2, respectively
'tty: Convert termios_mutex to termios_rwsem' and
'n_tty: Access termios values safely'
introduced a circular lock dependency with console_lock and
termios_rwsem.
The lockdep report [1] shows that n_tty_write() will attempt
to claim console_lock while holding the termios_rwsem, whereas
tty_do_resize() may already hold the console_lock while
claiming the termios_rwsem.
Since n_tty_write() and tty_do_resize() do not contend
over the same data -- the tty->winsize structure -- correct
the lock dependency by introducing a new lock which
specifically serializes access to tty->winsize only.
[1] Lockdep report
======================================================
[ INFO: possible circular locking dependency detected ]
3.10.0-0+tip-xeon+lockdep #0+tip Not tainted
-------------------------------------------------------
modprobe/277 is trying to acquire lock:
(&tty->termios_rwsem){++++..}, at: [<ffffffff81452656>] tty_do_resize+0x36/0xe0
but task is already holding lock:
((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 ((fb_notifier_list).rwsem){.+.+.+}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b797>] down_read+0x47/0x5c
[<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #1 (console_lock){+.+.+.}:
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff810430a7>] console_lock+0x77/0x80
[<ffffffff8146b2a1>] con_flush_chars+0x31/0x50
[<ffffffff8145780c>] n_tty_write+0x1ec/0x4d0
[<ffffffff814541b9>] tty_write+0x159/0x2e0
[<ffffffff814543f5>] redirected_tty_write+0xb5/0xc0
[<ffffffff811ab9d5>] vfs_write+0xc5/0x1f0
[<ffffffff811abec5>] SyS_write+0x55/0xa0
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
-> #0 (&tty->termios_rwsem){++++..}:
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
other info that might help us debug this:
Chain exists of:
&tty->termios_rwsem --> console_lock --> (fb_notifier_list).rwsem
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock((fb_notifier_list).rwsem);
lock(console_lock);
lock((fb_notifier_list).rwsem);
lock(&tty->termios_rwsem);
*** DEADLOCK ***
7 locks held by modprobe/277:
#0: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b5b>] __driver_attach+0x5b/0xb0
#1: (&__lockdep_no_validate__){......}, at: [<ffffffff81497b69>] __driver_attach+0x69/0xb0
#2: (drm_global_mutex){+.+.+.}, at: [<ffffffffa008a6dd>] drm_get_pci_dev+0xbd/0x2a0 [drm]
#3: (registration_lock){+.+.+.}, at: [<ffffffff813d93f5>] register_framebuffer+0x25/0x320
#4: (&fb_info->lock){+.+.+.}, at: [<ffffffff813d8116>] lock_fb_info+0x26/0x60
#5: (console_lock){+.+.+.}, at: [<ffffffff813d95a4>] register_framebuffer+0x1d4/0x320
#6: ((fb_notifier_list).rwsem){.+.+.+}, at: [<ffffffff8107aac6>] __blocking_notifier_call_chain+0x56/0xc0
stack backtrace:
CPU: 0 PID: 277 Comm: modprobe Not tainted 3.10.0-0+tip-xeon+lockdep #0+tip
Hardware name: Dell Inc. Precision WorkStation T5400 /0RW203, BIOS A11 04/30/2012
ffffffff8213e5e0 ffff8802aa2fb298 ffffffff81755f19 ffff8802aa2fb2e8
ffffffff8174f506 ffff8802aa2fa000 ffff8802aa2fb378 ffff8802aa2ea8e8
ffff8802aa2ea910 ffff8802aa2ea8e8 0000000000000006 0000000000000007
Call Trace:
[<ffffffff81755f19>] dump_stack+0x19/0x1b
[<ffffffff8174f506>] print_circular_bug+0x1fb/0x20c
[<ffffffff810b65c3>] __lock_acquire+0x1c43/0x1d30
[<ffffffff810b775e>] ? mark_held_locks+0xae/0x120
[<ffffffff810b78d5>] ? trace_hardirqs_on_caller+0x105/0x1d0
[<ffffffff810b6d62>] lock_acquire+0x92/0x1f0
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff8175b724>] down_write+0x44/0x70
[<ffffffff81452656>] ? tty_do_resize+0x36/0xe0
[<ffffffff81452656>] tty_do_resize+0x36/0xe0
[<ffffffff8146c841>] vc_do_resize+0x3e1/0x4c0
[<ffffffff8146c99f>] vc_resize+0x1f/0x30
[<ffffffff813e4535>] fbcon_init+0x385/0x5a0
[<ffffffff8146a4bc>] visual_init+0xbc/0x120
[<ffffffff8146cd13>] do_bind_con_driver+0x163/0x320
[<ffffffff8146cfa1>] do_take_over_console+0x61/0x70
[<ffffffff813e2b93>] do_fbcon_takeover+0x63/0xc0
[<ffffffff813e67a5>] fbcon_event_notify+0x715/0x820
[<ffffffff81762f9d>] notifier_call_chain+0x5d/0x110
[<ffffffff8107aadc>] __blocking_notifier_call_chain+0x6c/0xc0
[<ffffffff8107ab46>] blocking_notifier_call_chain+0x16/0x20
[<ffffffff813d7c0b>] fb_notifier_call_chain+0x1b/0x20
[<ffffffff813d95b2>] register_framebuffer+0x1e2/0x320
[<ffffffffa01043e1>] drm_fb_helper_initial_config+0x371/0x540 [drm_kms_helper]
[<ffffffff8173cbcb>] ? kmemleak_alloc+0x5b/0xc0
[<ffffffff81198874>] ? kmem_cache_alloc_trace+0x104/0x290
[<ffffffffa01035e1>] ? drm_fb_helper_single_add_all_connectors+0x81/0xf0 [drm_kms_helper]
[<ffffffffa01bcb05>] nouveau_fbcon_init+0x105/0x140 [nouveau]
[<ffffffffa01ad0af>] nouveau_drm_load+0x43f/0x610 [nouveau]
[<ffffffffa008a79e>] drm_get_pci_dev+0x17e/0x2a0 [drm]
[<ffffffffa01ad4da>] nouveau_drm_probe+0x25a/0x2a0 [nouveau]
[<ffffffff8175f162>] ? _raw_spin_unlock_irqrestore+0x42/0x80
[<ffffffff813b13db>] local_pci_probe+0x4b/0x80
[<ffffffff813b1701>] pci_device_probe+0x111/0x120
[<ffffffff814977eb>] driver_probe_device+0x8b/0x3a0
[<ffffffff81497bab>] __driver_attach+0xab/0xb0
[<ffffffff81497b00>] ? driver_probe_device+0x3a0/0x3a0
[<ffffffff814956ad>] bus_for_each_dev+0x5d/0xa0
[<ffffffff814971fe>] driver_attach+0x1e/0x20
[<ffffffff81496cc1>] bus_add_driver+0x111/0x290
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff814982b7>] driver_register+0x77/0x170
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffff813b0454>] __pci_register_driver+0x64/0x70
[<ffffffffa008a9da>] drm_pci_init+0x11a/0x130 [drm]
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a000>] ? 0xffffffffa0229fff
[<ffffffffa022a04d>] nouveau_drm_init+0x4d/0x1000 [nouveau]
[<ffffffff810002ea>] do_one_initcall+0xea/0x1a0
[<ffffffff810c54cb>] load_module+0x123b/0x1bf0
[<ffffffff81399a50>] ? ddebug_proc_open+0xb0/0xb0
[<ffffffff813855ae>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[<ffffffff810c5f57>] SyS_init_module+0xd7/0x120
[<ffffffff817677c2>] system_call_fastpath+0x16/0x1b
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2013-07-24 14:43:51 -06:00
|
|
|
mutex_init(&tty->winsize_mutex);
|
2013-06-15 05:04:48 -06:00
|
|
|
init_ldsem(&tty->ldisc_sem);
|
2005-04-16 16:20:36 -06:00
|
|
|
init_waitqueue_head(&tty->write_wait);
|
|
|
|
init_waitqueue_head(&tty->read_wait);
|
2006-11-22 07:55:48 -07:00
|
|
|
INIT_WORK(&tty->hangup_work, do_tty_hangup);
|
2006-03-23 04:00:31 -07:00
|
|
|
mutex_init(&tty->atomic_write_lock);
|
2008-04-30 01:53:29 -06:00
|
|
|
spin_lock_init(&tty->ctrl_lock);
|
2014-09-10 13:06:31 -06:00
|
|
|
spin_lock_init(&tty->flow_lock);
|
2016-01-09 22:35:23 -07:00
|
|
|
spin_lock_init(&tty->files_lock);
|
2005-04-16 16:20:36 -06:00
|
|
|
INIT_LIST_HEAD(&tty->tty_files);
|
2007-02-13 14:38:58 -07:00
|
|
|
INIT_WORK(&tty->SAK_work, do_SAK_work);
|
2008-10-13 03:42:39 -06:00
|
|
|
|
|
|
|
tty->driver = driver;
|
|
|
|
tty->ops = driver->ops;
|
|
|
|
tty->index = idx;
|
|
|
|
tty_line_name(driver, idx, tty->name);
|
2010-08-09 08:22:49 -06:00
|
|
|
tty->dev = tty_get_device(tty);
|
2014-07-10 13:01:22 -06:00
|
|
|
|
|
|
|
return tty;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
2008-04-30 01:54:13 -06:00
|
|
|
/**
|
|
|
|
* tty_put_char - write one character to a tty
|
|
|
|
* @tty: tty
|
|
|
|
* @ch: character
|
|
|
|
*
|
|
|
|
* Write one byte to the tty using the provided put_char method
|
|
|
|
* if present. Returns the number of characters successfully output.
|
|
|
|
*
|
|
|
|
* Note: the specific put_char operation in the driver layer may go
|
|
|
|
* away soon. Don't call it directly, use this method
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2006-08-27 02:24:01 -06:00
|
|
|
|
2008-04-30 01:54:13 -06:00
|
|
|
int tty_put_char(struct tty_struct *tty, unsigned char ch)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2008-04-30 01:54:13 -06:00
|
|
|
if (tty->ops->put_char)
|
|
|
|
return tty->ops->put_char(tty, ch);
|
|
|
|
return tty->ops->write(tty, &ch, 1);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2008-04-30 01:54:13 -06:00
|
|
|
EXPORT_SYMBOL_GPL(tty_put_char);
|
|
|
|
|
2008-10-13 03:41:42 -06:00
|
|
|
struct class *tty_class;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2012-08-08 14:26:44 -06:00
|
|
|
static int tty_cdev_add(struct tty_driver *driver, dev_t dev,
|
|
|
|
unsigned int index, unsigned int count)
|
|
|
|
{
|
2015-09-07 07:08:37 -06:00
|
|
|
int err;
|
|
|
|
|
2012-08-08 14:26:44 -06:00
|
|
|
/* init here, since reused cdevs cause crashes */
|
2015-05-19 09:06:53 -06:00
|
|
|
driver->cdevs[index] = cdev_alloc();
|
|
|
|
if (!driver->cdevs[index])
|
|
|
|
return -ENOMEM;
|
2015-09-07 07:08:37 -06:00
|
|
|
driver->cdevs[index]->ops = &tty_fops;
|
2015-05-19 09:06:53 -06:00
|
|
|
driver->cdevs[index]->owner = driver->owner;
|
2015-09-07 07:08:37 -06:00
|
|
|
err = cdev_add(driver->cdevs[index], dev, count);
|
|
|
|
if (err)
|
|
|
|
kobject_put(&driver->cdevs[index]->kobj);
|
|
|
|
return err;
|
2012-08-08 14:26:44 -06:00
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/**
|
2006-08-27 02:24:01 -06:00
|
|
|
* tty_register_device - register a tty device
|
|
|
|
* @driver: the tty driver that describes the tty device
|
|
|
|
* @index: the index in the tty driver for this tty device
|
|
|
|
* @device: a struct device that is associated with this tty device.
|
|
|
|
* This field is optional, if there is no known struct device
|
|
|
|
* for this tty device it can be set to NULL safely.
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
2006-08-07 23:19:37 -06:00
|
|
|
* Returns a pointer to the struct device for this tty device
|
|
|
|
* (or ERR_PTR(-EFOO) on error).
|
2006-04-22 10:36:53 -06:00
|
|
|
*
|
2006-08-27 02:24:01 -06:00
|
|
|
* This call is required to be made to register an individual tty device
|
|
|
|
* if the tty driver's flags have the TTY_DRIVER_DYNAMIC_DEV bit set. If
|
|
|
|
* that bit is not set, this function should not be called by a tty
|
|
|
|
* driver.
|
|
|
|
*
|
|
|
|
* Locking: ??
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2006-08-27 02:24:01 -06:00
|
|
|
|
2006-08-07 23:19:37 -06:00
|
|
|
struct device *tty_register_device(struct tty_driver *driver, unsigned index,
|
|
|
|
struct device *device)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2012-09-05 19:17:18 -06:00
|
|
|
return tty_register_device_attr(driver, index, device, NULL, NULL);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(tty_register_device);
|
|
|
|
|
2012-09-06 15:17:47 -06:00
|
|
|
static void tty_device_create_release(struct device *dev)
|
|
|
|
{
|
2015-11-08 11:01:21 -07:00
|
|
|
dev_dbg(dev, "releasing...\n");
|
2012-09-06 15:17:47 -06:00
|
|
|
kfree(dev);
|
|
|
|
}
|
|
|
|
|
2012-09-05 19:17:18 -06:00
|
|
|
/**
|
|
|
|
* tty_register_device_attr - register a tty device
|
|
|
|
* @driver: the tty driver that describes the tty device
|
|
|
|
* @index: the index in the tty driver for this tty device
|
|
|
|
* @device: a struct device that is associated with this tty device.
|
|
|
|
* This field is optional, if there is no known struct device
|
|
|
|
* for this tty device it can be set to NULL safely.
|
|
|
|
* @drvdata: Driver data to be set to device.
|
|
|
|
* @attr_grp: Attribute group to be set on device.
|
|
|
|
*
|
|
|
|
* Returns a pointer to the struct device for this tty device
|
|
|
|
* (or ERR_PTR(-EFOO) on error).
|
|
|
|
*
|
|
|
|
* This call is required to be made to register an individual tty device
|
|
|
|
* if the tty driver's flags have the TTY_DRIVER_DYNAMIC_DEV bit set. If
|
|
|
|
* that bit is not set, this function should not be called by a tty
|
|
|
|
* driver.
|
|
|
|
*
|
|
|
|
* Locking: ??
|
|
|
|
*/
|
|
|
|
struct device *tty_register_device_attr(struct tty_driver *driver,
|
|
|
|
unsigned index, struct device *device,
|
|
|
|
void *drvdata,
|
|
|
|
const struct attribute_group **attr_grp)
|
|
|
|
{
|
2005-04-16 16:20:36 -06:00
|
|
|
char name[64];
|
2012-09-05 19:17:18 -06:00
|
|
|
dev_t devt = MKDEV(driver->major, driver->minor_start) + index;
|
|
|
|
struct device *dev = NULL;
|
|
|
|
int retval = -ENODEV;
|
2012-08-08 14:26:44 -06:00
|
|
|
bool cdev = false;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
if (index >= driver->num) {
|
2015-11-08 11:01:15 -07:00
|
|
|
pr_err("%s: Attempt to register invalid tty line number (%d)\n",
|
|
|
|
driver->name, index);
|
2006-04-22 10:36:53 -06:00
|
|
|
return ERR_PTR(-EINVAL);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
|
|
|
|
if (driver->type == TTY_DRIVER_TYPE_PTY)
|
|
|
|
pty_line_name(driver, index, name);
|
|
|
|
else
|
|
|
|
tty_line_name(driver, index, name);
|
2006-04-22 10:36:53 -06:00
|
|
|
|
2012-08-08 14:26:44 -06:00
|
|
|
if (!(driver->flags & TTY_DRIVER_DYNAMIC_ALLOC)) {
|
2012-09-05 19:17:18 -06:00
|
|
|
retval = tty_cdev_add(driver, devt, index, 1);
|
|
|
|
if (retval)
|
|
|
|
goto error;
|
2012-08-08 14:26:44 -06:00
|
|
|
cdev = true;
|
|
|
|
}
|
|
|
|
|
2012-09-05 19:17:18 -06:00
|
|
|
dev = kzalloc(sizeof(*dev), GFP_KERNEL);
|
|
|
|
if (!dev) {
|
|
|
|
retval = -ENOMEM;
|
|
|
|
goto error;
|
|
|
|
}
|
2012-08-08 14:26:44 -06:00
|
|
|
|
2012-09-05 19:17:18 -06:00
|
|
|
dev->devt = devt;
|
|
|
|
dev->class = tty_class;
|
|
|
|
dev->parent = device;
|
2012-09-06 15:17:47 -06:00
|
|
|
dev->release = tty_device_create_release;
|
2012-09-05 19:17:18 -06:00
|
|
|
dev_set_name(dev, "%s", name);
|
|
|
|
dev->groups = attr_grp;
|
|
|
|
dev_set_drvdata(dev, drvdata);
|
|
|
|
|
|
|
|
retval = device_register(dev);
|
|
|
|
if (retval)
|
|
|
|
goto error;
|
|
|
|
|
|
|
|
return dev;
|
|
|
|
|
|
|
|
error:
|
|
|
|
put_device(dev);
|
2015-05-19 09:06:53 -06:00
|
|
|
if (cdev) {
|
|
|
|
cdev_del(driver->cdevs[index]);
|
|
|
|
driver->cdevs[index] = NULL;
|
|
|
|
}
|
2012-09-05 19:17:18 -06:00
|
|
|
return ERR_PTR(retval);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2012-09-05 19:17:18 -06:00
|
|
|
EXPORT_SYMBOL_GPL(tty_register_device_attr);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
/**
|
2006-08-27 02:24:01 -06:00
|
|
|
* tty_unregister_device - unregister a tty device
|
|
|
|
* @driver: the tty driver that describes the tty device
|
|
|
|
* @index: the index in the tty driver for this tty device
|
2005-04-16 16:20:36 -06:00
|
|
|
*
|
2006-08-27 02:24:01 -06:00
|
|
|
* If a tty device is registered with a call to tty_register_device() then
|
|
|
|
* this function must be called when the tty device is gone.
|
|
|
|
*
|
|
|
|
* Locking: ??
|
2005-04-16 16:20:36 -06:00
|
|
|
*/
|
2006-08-27 02:24:01 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
void tty_unregister_device(struct tty_driver *driver, unsigned index)
|
|
|
|
{
|
2008-02-08 05:18:47 -07:00
|
|
|
device_destroy(tty_class,
|
|
|
|
MKDEV(driver->major, driver->minor_start) + index);
|
2015-05-19 09:06:53 -06:00
|
|
|
if (!(driver->flags & TTY_DRIVER_DYNAMIC_ALLOC)) {
|
|
|
|
cdev_del(driver->cdevs[index]);
|
|
|
|
driver->cdevs[index] = NULL;
|
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(tty_unregister_device);
|
|
|
|
|
2012-08-07 13:47:42 -06:00
|
|
|
/**
|
|
|
|
* __tty_alloc_driver -- allocate tty driver
|
|
|
|
* @lines: count of lines this driver can handle at most
|
|
|
|
* @owner: module which is repsonsible for this driver
|
|
|
|
* @flags: some of TTY_DRIVER_* flags, will be set in driver->flags
|
|
|
|
*
|
|
|
|
* This should not be called directly, some of the provided macros should be
|
|
|
|
* used instead. Use IS_ERR and friends on @retval.
|
|
|
|
*/
|
|
|
|
struct tty_driver *__tty_alloc_driver(unsigned int lines, struct module *owner,
|
|
|
|
unsigned long flags)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
struct tty_driver *driver;
|
2012-08-08 14:26:44 -06:00
|
|
|
unsigned int cdevs = 1;
|
2012-08-08 14:26:42 -06:00
|
|
|
int err;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2012-08-08 14:26:43 -06:00
|
|
|
if (!lines || (flags & TTY_DRIVER_UNNUMBERED_NODE && lines > 1))
|
2012-08-07 13:47:42 -06:00
|
|
|
return ERR_PTR(-EINVAL);
|
|
|
|
|
2007-07-16 00:40:14 -06:00
|
|
|
driver = kzalloc(sizeof(struct tty_driver), GFP_KERNEL);
|
2012-08-07 13:47:42 -06:00
|
|
|
if (!driver)
|
|
|
|
return ERR_PTR(-ENOMEM);
|
|
|
|
|
|
|
|
kref_init(&driver->kref);
|
|
|
|
driver->magic = TTY_DRIVER_MAGIC;
|
|
|
|
driver->num = lines;
|
|
|
|
driver->owner = owner;
|
|
|
|
driver->flags = flags;
|
2012-08-08 14:26:42 -06:00
|
|
|
|
|
|
|
if (!(flags & TTY_DRIVER_DEVPTS_MEM)) {
|
|
|
|
driver->ttys = kcalloc(lines, sizeof(*driver->ttys),
|
|
|
|
GFP_KERNEL);
|
|
|
|
driver->termios = kcalloc(lines, sizeof(*driver->termios),
|
|
|
|
GFP_KERNEL);
|
|
|
|
if (!driver->ttys || !driver->termios) {
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto err_free_all;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!(flags & TTY_DRIVER_DYNAMIC_ALLOC)) {
|
|
|
|
driver->ports = kcalloc(lines, sizeof(*driver->ports),
|
|
|
|
GFP_KERNEL);
|
|
|
|
if (!driver->ports) {
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto err_free_all;
|
|
|
|
}
|
2012-08-08 14:26:44 -06:00
|
|
|
cdevs = lines;
|
|
|
|
}
|
|
|
|
|
|
|
|
driver->cdevs = kcalloc(cdevs, sizeof(*driver->cdevs), GFP_KERNEL);
|
|
|
|
if (!driver->cdevs) {
|
|
|
|
err = -ENOMEM;
|
|
|
|
goto err_free_all;
|
2012-08-08 14:26:42 -06:00
|
|
|
}
|
2012-08-07 13:47:42 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
return driver;
|
2012-08-08 14:26:42 -06:00
|
|
|
err_free_all:
|
|
|
|
kfree(driver->ports);
|
|
|
|
kfree(driver->ttys);
|
|
|
|
kfree(driver->termios);
|
2015-05-19 09:06:53 -06:00
|
|
|
kfree(driver->cdevs);
|
2012-08-08 14:26:42 -06:00
|
|
|
kfree(driver);
|
|
|
|
return ERR_PTR(err);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2012-08-07 13:47:42 -06:00
|
|
|
EXPORT_SYMBOL(__tty_alloc_driver);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-10-13 03:42:09 -06:00
|
|
|
static void destruct_tty_driver(struct kref *kref)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2008-10-13 03:42:09 -06:00
|
|
|
struct tty_driver *driver = container_of(kref, struct tty_driver, kref);
|
|
|
|
int i;
|
|
|
|
struct ktermios *tp;
|
|
|
|
|
|
|
|
if (driver->flags & TTY_DRIVER_INSTALLED) {
|
|
|
|
/*
|
|
|
|
* Free the termios and termios_locked structures because
|
|
|
|
* we don't want to get memory leaks when modular tty
|
|
|
|
* drivers are removed from the kernel.
|
|
|
|
*/
|
|
|
|
for (i = 0; i < driver->num; i++) {
|
|
|
|
tp = driver->termios[i];
|
|
|
|
if (tp) {
|
|
|
|
driver->termios[i] = NULL;
|
|
|
|
kfree(tp);
|
|
|
|
}
|
|
|
|
if (!(driver->flags & TTY_DRIVER_DYNAMIC_DEV))
|
|
|
|
tty_unregister_device(driver, i);
|
|
|
|
}
|
|
|
|
proc_tty_unregister_driver(driver);
|
2012-08-08 14:26:44 -06:00
|
|
|
if (driver->flags & TTY_DRIVER_DYNAMIC_ALLOC)
|
2015-05-19 09:06:53 -06:00
|
|
|
cdev_del(driver->cdevs[0]);
|
2008-10-13 03:42:09 -06:00
|
|
|
}
|
2012-08-08 14:26:44 -06:00
|
|
|
kfree(driver->cdevs);
|
2012-06-04 05:35:36 -06:00
|
|
|
kfree(driver->ports);
|
2012-08-08 14:26:42 -06:00
|
|
|
kfree(driver->termios);
|
|
|
|
kfree(driver->ttys);
|
2005-04-16 16:20:36 -06:00
|
|
|
kfree(driver);
|
|
|
|
}
|
|
|
|
|
2008-10-13 03:42:09 -06:00
|
|
|
void tty_driver_kref_put(struct tty_driver *driver)
|
|
|
|
{
|
|
|
|
kref_put(&driver->kref, destruct_tty_driver);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(tty_driver_kref_put);
|
|
|
|
|
2006-10-02 03:17:18 -06:00
|
|
|
void tty_set_operations(struct tty_driver *driver,
|
|
|
|
const struct tty_operations *op)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
2008-04-30 01:54:13 -06:00
|
|
|
driver->ops = op;
|
|
|
|
};
|
2008-10-13 03:42:09 -06:00
|
|
|
EXPORT_SYMBOL(tty_set_operations);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-10-13 03:42:09 -06:00
|
|
|
void put_tty_driver(struct tty_driver *d)
|
|
|
|
{
|
|
|
|
tty_driver_kref_put(d);
|
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
EXPORT_SYMBOL(put_tty_driver);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Called by a tty driver to register itself.
|
|
|
|
*/
|
|
|
|
int tty_register_driver(struct tty_driver *driver)
|
|
|
|
{
|
|
|
|
int error;
|
2008-02-08 05:18:47 -07:00
|
|
|
int i;
|
2005-04-16 16:20:36 -06:00
|
|
|
dev_t dev;
|
2010-09-05 12:32:22 -06:00
|
|
|
struct device *d;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
if (!driver->major) {
|
2008-02-08 05:18:47 -07:00
|
|
|
error = alloc_chrdev_region(&dev, driver->minor_start,
|
|
|
|
driver->num, driver->name);
|
2005-04-16 16:20:36 -06:00
|
|
|
if (!error) {
|
|
|
|
driver->major = MAJOR(dev);
|
|
|
|
driver->minor_start = MINOR(dev);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
dev = MKDEV(driver->major, driver->minor_start);
|
2007-02-20 07:45:21 -07:00
|
|
|
error = register_chrdev_region(dev, driver->num, driver->name);
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
2012-06-04 05:35:35 -06:00
|
|
|
if (error < 0)
|
2012-08-08 14:26:42 -06:00
|
|
|
goto err;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2012-08-08 14:26:44 -06:00
|
|
|
if (driver->flags & TTY_DRIVER_DYNAMIC_ALLOC) {
|
|
|
|
error = tty_cdev_add(driver, dev, 0, driver->num);
|
|
|
|
if (error)
|
|
|
|
goto err_unreg_char;
|
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2007-05-08 01:27:12 -06:00
|
|
|
mutex_lock(&tty_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
list_add(&driver->tty_drivers, &tty_drivers);
|
2007-05-08 01:27:12 -06:00
|
|
|
mutex_unlock(&tty_mutex);
|
2008-02-08 05:18:47 -07:00
|
|
|
|
|
|
|
if (!(driver->flags & TTY_DRIVER_DYNAMIC_DEV)) {
|
2010-09-05 12:32:22 -06:00
|
|
|
for (i = 0; i < driver->num; i++) {
|
|
|
|
d = tty_register_device(driver, i, NULL);
|
|
|
|
if (IS_ERR(d)) {
|
|
|
|
error = PTR_ERR(d);
|
2012-08-08 14:26:42 -06:00
|
|
|
goto err_unreg_devs;
|
2010-09-05 12:32:22 -06:00
|
|
|
}
|
|
|
|
}
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
proc_tty_register_driver(driver);
|
2008-10-13 03:42:09 -06:00
|
|
|
driver->flags |= TTY_DRIVER_INSTALLED;
|
2005-04-16 16:20:36 -06:00
|
|
|
return 0;
|
2010-09-05 12:32:22 -06:00
|
|
|
|
2012-08-08 14:26:42 -06:00
|
|
|
err_unreg_devs:
|
2010-09-05 12:32:22 -06:00
|
|
|
for (i--; i >= 0; i--)
|
|
|
|
tty_unregister_device(driver, i);
|
|
|
|
|
|
|
|
mutex_lock(&tty_mutex);
|
|
|
|
list_del(&driver->tty_drivers);
|
|
|
|
mutex_unlock(&tty_mutex);
|
|
|
|
|
2012-06-04 05:35:35 -06:00
|
|
|
err_unreg_char:
|
2010-09-05 12:32:22 -06:00
|
|
|
unregister_chrdev_region(dev, driver->num);
|
2012-08-08 14:26:42 -06:00
|
|
|
err:
|
2010-09-05 12:32:22 -06:00
|
|
|
return error;
|
2005-04-16 16:20:36 -06:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(tty_register_driver);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Called by a tty driver to unregister itself.
|
|
|
|
*/
|
|
|
|
int tty_unregister_driver(struct tty_driver *driver)
|
|
|
|
{
|
2008-10-13 03:42:09 -06:00
|
|
|
#if 0
|
|
|
|
/* FIXME */
|
2005-04-16 16:20:36 -06:00
|
|
|
if (driver->refcount)
|
|
|
|
return -EBUSY;
|
2008-10-13 03:42:09 -06:00
|
|
|
#endif
|
2005-04-16 16:20:36 -06:00
|
|
|
unregister_chrdev_region(MKDEV(driver->major, driver->minor_start),
|
|
|
|
driver->num);
|
2007-05-08 01:27:12 -06:00
|
|
|
mutex_lock(&tty_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
list_del(&driver->tty_drivers);
|
2007-05-08 01:27:12 -06:00
|
|
|
mutex_unlock(&tty_mutex);
|
2005-04-16 16:20:36 -06:00
|
|
|
return 0;
|
|
|
|
}
|
2008-10-13 03:42:09 -06:00
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
EXPORT_SYMBOL(tty_unregister_driver);
|
|
|
|
|
2006-12-08 03:36:04 -07:00
|
|
|
dev_t tty_devnum(struct tty_struct *tty)
|
|
|
|
{
|
|
|
|
return MKDEV(tty->driver->major, tty->driver->minor_start) + tty->index;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL(tty_devnum);
|
2005-04-16 16:20:36 -06:00
|
|
|
|
2008-10-13 03:41:42 -06:00
|
|
|
void tty_default_fops(struct file_operations *fops)
|
|
|
|
{
|
|
|
|
*fops = tty_fops;
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* Initialize the console device. This is called *early*, so
|
|
|
|
* we can't necessarily depend on lots of kernel help here.
|
|
|
|
* Just do some early initializations, and do the complex setup
|
|
|
|
* later.
|
|
|
|
*/
|
|
|
|
void __init console_init(void)
|
|
|
|
{
|
|
|
|
initcall_t *call;
|
|
|
|
|
|
|
|
/* Setup the default TTY line discipline. */
|
2016-01-09 22:35:19 -07:00
|
|
|
n_tty_init();
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
/*
|
2008-02-08 05:18:47 -07:00
|
|
|
* set up the console device so that later boot sequences can
|
2005-04-16 16:20:36 -06:00
|
|
|
* inform about problems etc..
|
|
|
|
*/
|
|
|
|
call = __con_initcall_start;
|
|
|
|
while (call < __con_initcall_end) {
|
|
|
|
(*call)();
|
|
|
|
call++;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2011-07-23 18:24:48 -06:00
|
|
|
static char *tty_devnode(struct device *dev, umode_t *mode)
|
2009-09-18 15:01:12 -06:00
|
|
|
{
|
|
|
|
if (!mode)
|
|
|
|
return NULL;
|
|
|
|
if (dev->devt == MKDEV(TTYAUX_MAJOR, 0) ||
|
|
|
|
dev->devt == MKDEV(TTYAUX_MAJOR, 2))
|
|
|
|
*mode = 0666;
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
static int __init tty_class_init(void)
|
|
|
|
{
|
2005-03-15 15:23:15 -07:00
|
|
|
tty_class = class_create(THIS_MODULE, "tty");
|
2005-04-16 16:20:36 -06:00
|
|
|
if (IS_ERR(tty_class))
|
|
|
|
return PTR_ERR(tty_class);
|
2009-09-18 15:01:12 -06:00
|
|
|
tty_class->devnode = tty_devnode;
|
2005-04-16 16:20:36 -06:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
postcore_initcall(tty_class_init);
|
|
|
|
|
|
|
|
/* 3/2004 jmc: why do these devices exist? */
|
|
|
|
static struct cdev tty_cdev, console_cdev;
|
|
|
|
|
2010-12-01 10:51:05 -07:00
|
|
|
static ssize_t show_cons_active(struct device *dev,
|
|
|
|
struct device_attribute *attr, char *buf)
|
|
|
|
{
|
|
|
|
struct console *cs[16];
|
|
|
|
int i = 0;
|
|
|
|
struct console *c;
|
|
|
|
ssize_t count = 0;
|
|
|
|
|
2011-01-25 16:07:35 -07:00
|
|
|
console_lock();
|
2011-01-09 08:39:14 -07:00
|
|
|
for_each_console(c) {
|
2010-12-01 10:51:05 -07:00
|
|
|
if (!c->device)
|
|
|
|
continue;
|
|
|
|
if (!c->write)
|
|
|
|
continue;
|
|
|
|
if ((c->flags & CON_ENABLED) == 0)
|
|
|
|
continue;
|
|
|
|
cs[i++] = c;
|
|
|
|
if (i >= ARRAY_SIZE(cs))
|
|
|
|
break;
|
|
|
|
}
|
2014-02-27 04:30:51 -07:00
|
|
|
while (i--) {
|
|
|
|
int index = cs[i]->index;
|
|
|
|
struct tty_driver *drv = cs[i]->device(cs[i], &index);
|
|
|
|
|
|
|
|
/* don't resolve tty0 as some programs depend on it */
|
|
|
|
if (drv && (cs[i]->index > 0 || drv->major != TTY_MAJOR))
|
|
|
|
count += tty_line_name(drv, index, buf + count);
|
|
|
|
else
|
|
|
|
count += sprintf(buf + count, "%s%d",
|
|
|
|
cs[i]->name, cs[i]->index);
|
|
|
|
|
|
|
|
count += sprintf(buf + count, "%c", i ? ' ':'\n');
|
|
|
|
}
|
2011-01-25 16:07:35 -07:00
|
|
|
console_unlock();
|
2010-12-01 10:51:05 -07:00
|
|
|
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
static DEVICE_ATTR(active, S_IRUGO, show_cons_active, NULL);
|
|
|
|
|
2015-02-05 03:07:42 -07:00
|
|
|
static struct attribute *cons_dev_attrs[] = {
|
|
|
|
&dev_attr_active.attr,
|
|
|
|
NULL
|
|
|
|
};
|
|
|
|
|
|
|
|
ATTRIBUTE_GROUPS(cons_dev);
|
|
|
|
|
2010-12-01 10:51:05 -07:00
|
|
|
static struct device *consdev;
|
|
|
|
|
|
|
|
void console_sysfs_notify(void)
|
|
|
|
{
|
|
|
|
if (consdev)
|
|
|
|
sysfs_notify(&consdev->kobj, NULL, "active");
|
|
|
|
}
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
* Ok, now we can initialize the rest of the tty devices and can count
|
|
|
|
* on memory allocations, interrupts etc..
|
|
|
|
*/
|
2010-08-06 09:34:43 -06:00
|
|
|
int __init tty_init(void)
|
2005-04-16 16:20:36 -06:00
|
|
|
{
|
|
|
|
cdev_init(&tty_cdev, &tty_fops);
|
|
|
|
if (cdev_add(&tty_cdev, MKDEV(TTYAUX_MAJOR, 0), 1) ||
|
|
|
|
register_chrdev_region(MKDEV(TTYAUX_MAJOR, 0), 1, "/dev/tty") < 0)
|
|
|
|
panic("Couldn't register /dev/tty driver\n");
|
2010-12-01 10:51:05 -07:00
|
|
|
device_create(tty_class, NULL, MKDEV(TTYAUX_MAJOR, 0), NULL, "tty");
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
cdev_init(&console_cdev, &console_fops);
|
|
|
|
if (cdev_add(&console_cdev, MKDEV(TTYAUX_MAJOR, 1), 1) ||
|
|
|
|
register_chrdev_region(MKDEV(TTYAUX_MAJOR, 1), 1, "/dev/console") < 0)
|
|
|
|
panic("Couldn't register /dev/console driver\n");
|
2015-02-05 03:07:42 -07:00
|
|
|
consdev = device_create_with_groups(tty_class, NULL,
|
|
|
|
MKDEV(TTYAUX_MAJOR, 1), NULL,
|
|
|
|
cons_dev_groups, "console");
|
2010-12-01 10:51:05 -07:00
|
|
|
if (IS_ERR(consdev))
|
|
|
|
consdev = NULL;
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
#ifdef CONFIG_VT
|
2008-10-13 03:41:42 -06:00
|
|
|
vty_init(&console_fops);
|
2005-04-16 16:20:36 -06:00
|
|
|
#endif
|
|
|
|
return 0;
|
|
|
|
}
|
2010-08-06 09:34:43 -06:00
|
|
|
|