fs: cleanup files_lock locking
PATCH 1/2 fs: cleanup files_lock locking
Al, would you consider merging these two patches please?
Thanks,
Nick
--
fs: cleanup files_lock locking
Lock tty_files with a new spinlock, tty_files_lock; provide helpers to manipulate the per-sb files list; unexport the files_lock spinlock.
--- drivers/char/pty.c | 6 +++++- drivers/char/tty_io.c | 26 ++++++++++++++++++-------- fs/file_table.c | 42 ++++++++++++++++++------------------------ fs/open.c | 4 ++-- include/linux/fs.h | 7 ++----- include/linux/tty.h | 1 + security/selinux/hooks.c | 4 ++-- 7 files changed, 48 insertions(+), 42 deletions(-)
security/selinux/hooks.c +2 -2
@@ -2219,7 +2219,7 @@ static inline void flush_unauthorized_fi tty =get_current_tty ();if (tty) { -file_list_lock (); +spin_lock (&tty_files_lock);if (!list_empty (&tty->tty_files)) {struct inode *inode;
@@ -2235,7 +2235,7 @@ static inline void flush_unauthorized_fi drop_tty =1 ; } } -file_list_unlock (); +spin_unlock (&tty_files_lock);tty_kref_put (tty); }/* Reset controlling tty. */
drivers/char/pty.c +5 -1
@@ -650,7 +650,11 @@ static int __ptmx_open(struct inode *inoset_bit (TTY_PTY_LOCK , &tty->flags);/* LOCK THE SLAVE */ filp->private_data = tty; -file_move (filp, &tty->tty_files); + +file_sb_list_del (filp);/* __dentry_open has put it on the sb list */ +spin_lock (&tty_files_lock); +list_add (&filp->f_u.fu_list, &tty->tty_files); +spin_unlock (&tty_files_lock); retval =devpts_pty_new (inode, tty->link);if (retval)
drivers/char/tty_io.c +18 -8
@@ -136,6 +136,9 @@ LIST_HEAD(tty_drivers); /* linked listDEFINE_MUTEX (tty_mutex);EXPORT_SYMBOL (tty_mutex); +/* Spinlock to protect the tty->tty_files list */ +DEFINE_SPINLOCK (tty_files_lock); +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 *); ssize_t redirected_tty_write(struct file *, const char __user *,
@@ -234,11 +237,11 @@ static int check_tty_count(struct tty_ststruct list_head *p;int count =0 ; -file_list_lock (); +spin_lock (&tty_files_lock);list_for_each (p, &tty->tty_files) { count++; } -file_list_unlock (); +spin_unlock (&tty_files_lock);if (tty->driver->type ==TTY_DRIVER_TYPE_PTY && tty->driver->subtype ==PTY_TYPE_SLAVE && tty->link && tty->link->count)
@@ -517,7 +520,7 @@ static void do_tty_hangup(struct work_stlock_kernel ();check_tty_count (tty,"do_tty_hangup" ); -file_list_lock (); +spin_lock (&tty_files_lock);/* This breaks for file handles being sent over AF_UNIX sockets ? */ list_for_each_entry (filp, &tty->tty_files, f_u.fu_list) {if (filp->f_op->write == redirected_tty_write)
@@ -528,7 +531,7 @@ static void do_tty_hangup(struct work_sttty_fasync (-1 , filp,0 );/* can't block */ filp->f_op = &hung_up_tty_fops; } -file_list_unlock (); +spin_unlock (&tty_files_lock);tty_ldisc_hangup (tty);
@@ -1419,9 +1422,9 @@ static void release_one_tty(struct work_tty_driver_kref_put (driver);module_put (driver->owner); -file_list_lock (); +spin_lock (&tty_files_lock);list_del_init (&tty->tty_files); -file_list_unlock (); +spin_unlock (&tty_files_lock);put_pid (tty->pgrp);put_pid (tty->session);
@@ -1666,7 +1669,10 @@ int tty_release(struct inode *inode, str* - do_tty_hangup no longer sees this file descriptor as * something that needs to be handled for hangups. */ -file_kill (filp); +spin_lock (&tty_files_lock); +BUG_ON (list_empty (&filp->f_u.fu_list)); +list_del_init (&filp->f_u.fu_list); +spin_unlock (&tty_files_lock); filp->private_data =NULL ;/*
@@ -1835,7 +1841,11 @@ got_driver: } filp->private_data = tty; -file_move (filp, &tty->tty_files); +BUG_ON (list_empty (&filp->f_u.fu_list)); +file_sb_list_del (filp);/* __dentry_open has put it on the sb list */ +spin_lock (&tty_files_lock); +list_add (&filp->f_u.fu_list, &tty->tty_files); +spin_unlock (&tty_files_lock);check_tty_count (tty,"tty_open" );if (tty->driver->type ==TTY_DRIVER_TYPE_PTY && tty->driver->subtype ==PTY_TYPE_MASTER )
fs/file_table.c +18 -24
104 lines not on this page · raw message
fs/open.c +2 -2
@@ -675,7 +675,7 @@ static struct file *__dentry_open(struct f->f_path.mnt = mnt; f->f_pos =0 ; f->f_op =fops_get (inode->i_fop); -file_move (f, &inode->i_sb->s_files); +file_sb_list_add (f, inode->i_sb); error =security_dentry_open (f, cred);if (error)
@@ -721,7 +721,7 @@ cleanup_all:mnt_drop_write (mnt); } } -file_kill (f); +file_sb_list_del (f); f->f_path.dentry =NULL ; f->f_path.mnt =NULL ; cleanup_file:
include/linux/fs.h +2 -5
@@ -949,9 +949,6 @@ struct file {unsigned long f_mnt_write_state;#endif }; -extern spinlock_t files_lock; -#define file_list_lock () spin_lock(&files_lock); -#define file_list_unlock () spin_unlock(&files_lock);#define get_file (x) atomic_long_inc(&(x)->f_count)#define fput_atomic (x) atomic_long_add_unless(&(x)->f_count, -1, 1)
@@ -2182,8 +2179,8 @@ static inline void insert_inode_hash(str__insert_inode_hash (inode, inode->i_ino); } -extern void file_move (struct file *f,struct list_head *list); -extern void file_kill (struct file *f); +extern void file_sb_list_add (struct file *f,struct super_block *sb); +extern void file_sb_list_del (struct file *f);#ifdef CONFIG_BLOCK struct bio ;extern void submit_bio (int ,struct bio *);
include/linux/tty.h +1 -0
@@ -467,6 +467,7 @@ extern struct tty_struct *tty_pair_get_textern struct tty_struct *tty_pair_get_pty (struct tty_struct *tty);extern struct mutex tty_mutex; +extern spinlock_t tty_files_lock;extern void tty_write_unlock (struct tty_struct *tty);extern int tty_write_lock (struct tty_struct *tty,int ndelay);
PATCH 2/2 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 name unlinked, 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". So add a new private list for ttys and leave tty files on the sb list so they are caught by this check. This makes tty nodes behave the same way as other device nodes.
The next step is to allocate a tty private structure at private_data and get rid of f_ttyonly_list, but the error handling is not trivial in the tty code. Hence this intermediate step.
[ Arguably on-disk device inode would not be referenced by driver's pseudo inode once it is open, but in practice it's not clear whether that will ever be worth implementing. ]
--- drivers/char/pty.c | 3 +-- drivers/char/tty_io.c | 9 +++------ fs/internal.h | 2 ++ include/linux/fs.h | 3 +-- security/selinux/hooks.c | 3 ++- 5 files changed, 9 insertions(+), 11 deletions(-)
include/linux/fs.h +1 -2
@@ -939,6 +939,7 @@ struct file {#endif /* needed for tty driver, and maybe others */ void *private_data; +struct list_head f_ttyonly_list;/* No new users! */ #ifdef CONFIG_EPOLL /* Used by fs/eventpoll.c to link all the hooks to this file */
@@ -2179,8 +2180,6 @@ static inline void insert_inode_hash(str__insert_inode_hash (inode, inode->i_ino); } -extern void file_sb_list_add (struct file *f,struct super_block *sb); -extern void file_sb_list_del (struct file *f);#ifdef CONFIG_BLOCK struct bio ;extern void submit_bio (int ,struct bio *);
drivers/char/pty.c +1 -2
@@ -651,9 +651,8 @@ static int __ptmx_open(struct inode *inoset_bit (TTY_PTY_LOCK , &tty->flags);/* LOCK THE SLAVE */ filp->private_data = tty; -file_sb_list_del (filp);/* __dentry_open has put it on the sb list */ spin_lock (&tty_files_lock); -list_add (&filp->f_u.fu_list, &tty->tty_files); +list_add (&filp->f_ttyonly_list, &tty->tty_files);spin_unlock (&tty_files_lock); retval =devpts_pty_new (inode, tty->link);
drivers/char/tty_io.c +3 -6
@@ -522,7 +522,7 @@ static void do_tty_hangup(struct work_stspin_lock (&tty_files_lock);/* This breaks for file handles being sent over AF_UNIX sockets ? */ -list_for_each_entry (filp, &tty->tty_files, f_u.fu_list) { +list_for_each_entry (filp, &tty->tty_files, f_ttyonly_list) {if (filp->f_op->write == redirected_tty_write) cons_filp = filp;if (filp->f_op->write != tty_write)
@@ -1670,8 +1670,7 @@ int tty_release(struct inode *inode, str* something that needs to be handled for hangups. */ spin_lock (&tty_files_lock); -BUG_ON (list_empty (&filp->f_u.fu_list)); -list_del_init (&filp->f_u.fu_list); +list_del (&filp->f_ttyonly_list);spin_unlock (&tty_files_lock); filp->private_data =NULL ;
@@ -1841,10 +1840,8 @@ got_driver: } filp->private_data = tty; -BUG_ON (list_empty (&filp->f_u.fu_list)); -file_sb_list_del (filp);/* __dentry_open has put it on the sb list */ spin_lock (&tty_files_lock); -list_add (&filp->f_u.fu_list, &tty->tty_files); +list_add (&filp->f_ttyonly_list, &tty->tty_files);spin_unlock (&tty_files_lock);check_tty_count (tty,"tty_open" ); if (tty->driver->type == TTY_DRIVER_TYPE_PTY &&
security/selinux/hooks.c +2 -1
@@ -2228,7 +2228,8 @@ static inline void flush_unauthorized_fithan using file_has_perm, as this particular open file may belong to another process and we are only interested in the inode-based check here. */ - file = list_first_entry(&tty->tty_files, struct file, f_u.fu_list); + file =list_first_entry (&tty->tty_files, + struct file, f_ttyonly_list); inode = file->f_path.dentry->d_inode;if (inode_has_perm (cred, inode,FILE__READ |FILE__WRITE ,NULL )) {
fs/internal.h +2 -0
@@ -80,6 +80,8 @@ extern void chroot_fs_refs(struct path */* * file_table.c */ +extern void file_sb_list_add (struct file *f,struct super_block *sb); +extern void file_sb_list_del (struct file *f);extern void mark_files_ro (struct super_block *);extern struct file *get_empty_filp (void );
Re: [patch 2/2] tty fix fu_list abuse
Quoted 12 lines · Nick Piggin
tty: fix
fu_listabusetty code abuses
fu_list, which causes a bug in remount,ro handling.If a tty device node is opened on a filesystem, then the name unlinked, the filesystem will be allowed to be remounted readonly. This is because
fs_may_remount_rodoes 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". So add a new private list for ttys and leave tty files on the sb list so they are caught by this check. This makes tty nodes behave the same way as other device nodes.
Quoted 3 lines
The next step is to allocate a tty private structure at
private_dataand get rid off_ttyonly_list, but the error handling is not trivial in the tty code. Hence this intermediate step.
Growing struct file by two pointers for the tty special case simply isn't acceptable.
Re: [patch 2/2] tty fix fu_list abuse
Quoted 13 lines · Christoph Hellwig
Quoted 12 lines · Nick Piggin
tty: fix
fu_listabusetty code abuses
fu_list, which causes a bug in remount,ro handling.If a tty device node is opened on a filesystem, then the name unlinked, the filesystem will be allowed to be remounted readonly. This is because
fs_may_remount_rodoes 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". So add a new private list for ttys and leave tty files on the sb list so they are caught by this check. This makes tty nodes behave the same way as other device nodes.
Quoted 6 lines
Quoted 3 lines
The next step is to allocate a tty private structure at
private_dataand get rid off_ttyonly_list, but the error handling is not trivial in the tty code. Hence this intermediate step.Growing struct file by two pointers for the tty special case simply isn't acceptable.
I agree, so it can be removed when tty gets its act together. But tty breaks the s_files list right now which is not acceptable either. So I think it is better to take the simple fix that can be easily applied. I liked your patch, but error handling was totally broken in it so that indicates it is going to require some maturing in the tty tree.