Linus Torvalds 0eead9ab41 Don't dump task struct in a.out core-dumps ... akiphie points out that a.out core-dumps have that odd task struct dumping that was never used and was never really a good idea (it goes back into the mists of history, probably the original core-dumping code). Just remove it. Also do the access_ok() check on dump_write(). It probably doesn't matter (since normal filesystems all seem to do it anyway), but he points out that it's normally done by the VFS layer, so ... [ I suspect that we should possibly do "vfs_write()" instead of calling ->write directly. That also does the whole fsnotify and write statistics thing, which may or may not be a good idea. ] And just to be anal, do this all for the x86-64 32-bit a.out emulation code too, even though it's not enabled (and won't currently even compile) Reported-by: akiphie <akiphie@lavabit.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2010-10-14 10:57:40 -07:00
..
audit.c
ia32_aout.c	Don't dump task struct in a.out core-dumps	2010-10-14 10:57:40 -07:00
ia32_signal.c	x86: ia32_signal: introduce {get|set}_user_seg()	2009-02-22 17:54:47 +01:00
ia32entry.S	x86-64, compat: Retruncate rax after ia32 syscall entry tracing	2010-09-14 16:08:47 -07:00
ipc32.c
Makefile
sys_ia32.c	Mark arguments to certain syscalls as being const	2010-08-13 16:53:13 -07:00