redonkable/remarkable-linux
redonkable/remarkable-linux
1
0
Fork 0
Code Releases Activity

coredump: call do_unlinkat directly instead of sys_unlink

Browse source 
And stop messing with the address limit.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
This commit is contained in:
Christoph Hellwig 2017-11-04 13:44:46 +03:00 committed by Al Viro
parent da2f1362c8
commit 96271654f5
1 changed files with 1 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
fs/coredump.c
View file

@ -679,16 +679,11 @@ void do_coredump(const siginfo_t *siginfo)
* privs and don't want to unlink another user's coredump. * privs and don't want to unlink another user's coredump.
*/ */
if (!need_suid_safe) { if (!need_suid_safe) {
mm_segment_t old_fs;
old_fs = get_fs();
set_fs(KERNEL_DS);
/* /*
* If it doesn't exist, that's fine. If there's some * If it doesn't exist, that's fine. If there's some
* other problem, we'll catch it at the filp_open(). * other problem, we'll catch it at the filp_open().
*/ */
(void) sys_unlink((const char __user *)cn.corename); do_unlinkat(AT_FDCWD, getname_kernel(cn.corename));
set_fs(old_fs);
} }
/* /*