diff options
| author | Herton R. Krzesinski <herton@redhat.com> | 2016-01-14 17:56:58 -0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-02-06 23:45:46 -0800 |
| commit | 1f55c718c290616889c04946864a13ef30f64929 (patch) | |
| tree | d578b6dee5f2eb8ebe8f73ccba2b79a31252c52c /mm/percpu.c | |
| parent | 2831c89f42dcde440cfdccb9fee9f42d54bbc1ef (diff) | |
| download | linux-1f55c718c290616889c04946864a13ef30f64929.tar.bz2 | |
pty: make sure super_block is still valid in final /dev/tty close
Considering current pty code and multiple devpts instances, it's possible
to umount a devpts file system while a program still has /dev/tty opened
pointing to a previosuly closed pty pair in that instance. In the case all
ptmx and pts/N files are closed, umount can be done. If the program closes
/dev/tty after umount is done, devpts_kill_index will use now an invalid
super_block, which was already destroyed in the umount operation after
running ->kill_sb. This is another "use after free" type of issue, but now
related to the allocated super_block instance.
To avoid the problem (warning at ida_remove and potential crashes) for
this specific case, I added two functions in devpts which grabs additional
references to the super_block, which pty code now uses so it makes sure
the super block structure is still valid until pty shutdown is done.
I also moved the additional inode references to the same functions, which
also covered similar case with inode being freed before /dev/tty final
close/shutdown.
Signed-off-by: Herton R. Krzesinski <herton@redhat.com>
Cc: stable@vger.kernel.org # 2.6.29+
Reviewed-by: Peter Hurley <peter@hurleysoftware.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm/percpu.c')
0 files changed, 0 insertions, 0 deletions