[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180409202642.GD17347@saruman>
Date: Mon, 9 Apr 2018 21:26:43 +0100
From: James Hogan <jhogan@...nel.org>
To: Sasha Levin <Alexander.Levin@...rosoft.com>
Cc: "stable@...r.kernel.org" <stable@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
David Daney <david.daney@...ium.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Matt Redfearn <matt.redfearn@...tec.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-mips@...ux-mips.org" <linux-mips@...ux-mips.org>,
Ralf Baechle <ralf@...ux-mips.org>
Subject: Re: [PATCH AUTOSEL for 4.9 160/293] MIPS: Give __secure_computing()
access to syscall arguments.
On Mon, Apr 09, 2018 at 12:24:58AM +0000, Sasha Levin wrote:
> From: David Daney <david.daney@...ium.com>
>
> [ Upstream commit 669c4092225f0ed5df12ebee654581b558a5e3ed ]
>
> KProbes of __seccomp_filter() are not very useful without access to
> the syscall arguments.
>
> Do what x86 does, and populate a struct seccomp_data to be passed to
> __secure_computing(). This allows samples/bpf/tracex5 to extract a
> sensible trace.
This broke o32 indirect syscalls, and was fixed by commit 3d729deaf287
("MIPS: seccomp: Fix indirect syscall args").
Cheers
James
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists