From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753088AbdFVQSo (ORCPT ); Thu, 22 Jun 2017 12:18:44 -0400 Received: from mail-wr0-f174.google.com ([209.85.128.174]:33398 "EHLO mail-wr0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752020AbdFVQSm (ORCPT ); Thu, 22 Jun 2017 12:18:42 -0400 MIME-Version: 1.0 From: Sumit Semwal Date: Thu, 22 Jun 2017 21:48:19 +0530 Message-ID: Subject: seccomp ptrace selftest failures with 4.4-stable [Was: Re: LTS testing with latest kselftests - some failures] To: Kees Cook , luto@amacapital.net Cc: Brian Norris , mcgrof@kernel.org, Greg Kroah-Hartman , LKML , stable@vger.kernel.org, linux-kselftest@vger.kernel.org, Shuah Khan Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Kees, Andy, On 15 June 2017 at 23:26, Sumit Semwal wrote: > 3. 'seccomp ptrace hole closure' patches got added in 4.7 [3] - > feature and test together. > - This one also seems like a security hole being closed, and the > 'feature' could be a candidate for stable backports, but Arnd tried > that, and it was quite non-trivial. So perhaps we'll need some help > from the subsystem developers here. Could you please help us sort this out? Our goal is to help Greg with testing stable kernels, and currently the seccomp tests fail due to missing feature (seccomp ptrace hole closure) getting tested via latest kselftest. If you feel the feature isn't a stable candidate, then could you please help make the test degrade gracefully in its absence? Greatly appreciated! Thanks and best regards, Sumit