diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2015-02-23 03:21:31 -0500 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2015-04-11 22:24:31 -0400 |
| commit | a555ad450f973528825201a5fedbe46374f86644 (patch) | |
| tree | 693c68515fb05210c87c5dea011564f8a3b132ae /arch/hexagon/kernel/process.c | |
| parent | 9e7543e9398ddd9679fbc81748a3e62eff4ab105 (diff) | |
whack-a-mole: no need to set_fs(USER_DS) in {start,flush}_thread()
flush_old_exec() has already done that. Back on 2011 a bunch of
instances like that had been kicked out, but that hadn't taken
care of then-out-of-tree architectures, obviously, and they served
as reinfection vector...
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'arch/hexagon/kernel/process.c')
| -rw-r--r-- | arch/hexagon/kernel/process.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/arch/hexagon/kernel/process.c b/arch/hexagon/kernel/process.c index 0a0dd5c05b46..a9ebd471823a 100644 --- a/arch/hexagon/kernel/process.c +++ b/arch/hexagon/kernel/process.c @@ -37,8 +37,6 @@ */ void start_thread(struct pt_regs *regs, unsigned long pc, unsigned long sp) { - /* Set to run with user-mode data segmentation */ - set_fs(USER_DS); /* We want to zero all data-containing registers. Is this overkill? */ memset(regs, 0, sizeof(*regs)); /* We might want to also zero all Processor registers here */ |