Bug#751417: linux-image-3.2.0-4-5kc-malta: no SIGKILL after prctl(PR_SET_SECCOMP, 1, ...) on MIPS
- To: Ben Hutchings <ben@decadent.org.uk>
- Cc: stable <stable@vger.kernel.org>, linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>, 751417@bugs.debian.org, team@security.debian.org, Plamen Alexandrov <plamen@aomeda.com>, Markos Chandras <markos.chandras@imgtec.com>
- Subject: Bug#751417: linux-image-3.2.0-4-5kc-malta: no SIGKILL after prctl(PR_SET_SECCOMP, 1, ...) on MIPS
- From: Greg KH <greg@kroah.com>
- Date: Thu, 12 Jun 2014 14:03:23 -0700
- Message-id: <[🔎] 20140612210323.GA30046@kroah.com>
- Reply-to: Greg KH <greg@kroah.com>, 751417@bugs.debian.org
- In-reply-to: <[🔎] 1402604501.31756.50.camel@deadeye.wl.decadent.org.uk>
- References: <20140612161903.32229.20589.reportbug@debian-mips.""> <[🔎] 1402601767.31756.38.camel@deadeye.wl.decadent.org.uk> <[🔎] 1402604501.31756.50.camel@deadeye.wl.decadent.org.uk>
On Thu, Jun 12, 2014 at 09:21:41PM +0100, Ben Hutchings wrote:
> On Thu, 2014-06-12 at 20:36 +0100, Ben Hutchings wrote:
> > Control: tag -1 security upstream patch moreinfo
> > Control: severity -1 grave
> > Control: found -1 3.14.5-1
>
> Aurelien Jarno pointed out this appears to be fixed upstream in 3.15:
>
> commit 137f7df8cead00688524c82360930845396b8a21
> Author: Markos Chandras <markos.chandras@imgtec.com>
> Date: Wed Jan 22 14:40:00 2014 +0000
>
> MIPS: asm: thread_info: Add _TIF_SECCOMP flag
>
> It looks like this can be cherry-picked cleanly onto stable branches for
> 3.13 and 3.14. For 3.11 and 3.12, it will need trivial adjustment.
>
> For branches older than 3.11, this needs to be cherry-picked first:
>
> commit e7f3b48af7be9f8007a224663a5b91340626fed5
> Author: Ralf Baechle <ralf@linux-mips.org>
> Date: Wed May 29 01:02:18 2013 +0200
>
> MIPS: Cleanup flags in syscall flags handlers.
It also needs parts of 1d7bf993e0731b4ac790667c196b2a2d787f95c3 (MIPS:
ftrace: Add support for syscall tracepoints.) to apply properly to stuff
older than 3.11. But, I'm not so sure that is good to apply as that is
a whole new feature.
So I think I'll just do this "by hand" to get it to work properly...
thanks,
greg k-h
Reply to: