From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=0.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_SBL,URIBL_SBL_A autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3FB71C3A59F for ; Mon, 26 Aug 2019 16:40:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 12E4C206BA for ; Mon, 26 Aug 2019 16:40:35 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="fP2Xk61P" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732901AbfHZQk3 (ORCPT ); Mon, 26 Aug 2019 12:40:29 -0400 Received: from mail-wm1-f67.google.com ([209.85.128.67]:40730 "EHLO mail-wm1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732900AbfHZQk3 (ORCPT ); Mon, 26 Aug 2019 12:40:29 -0400 Received: by mail-wm1-f67.google.com with SMTP id c5so148375wmb.5; Mon, 26 Aug 2019 09:40:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QjxgBXa3y+uuhZsdeO1qBTZUTIy7XmFfl96V9DIMo6Q=; b=fP2Xk61Pf9uROtag057QqLPki/+ga9LNABXUsoDIZwVgKzbaYY+Yv54/cDTBAKId+L Gsa9FVVOLgcFlieoK30m+kYMru8msmE8LoggM8vJq/vdFO5xSMSr2LvZhqfkrFHXjhov 6rD3Xh8wbBkjlyhtb6/yu5I7HY09bDnj1SpktDTI8oAOdA7J0NOLAlDbY2lLOwpdhVKk cgebex/jZ8OF4iLFyBI5qhK43EJK74aDyp2TI03EElLOgyt3ObsAka0s9GSEMRH+4nIE wzpWbuPNjYFtI1GG4jgryZIAosVXa3K6wI33LepQmdDRTSqGL6fvoKnf8pvI24SlblRD GsiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QjxgBXa3y+uuhZsdeO1qBTZUTIy7XmFfl96V9DIMo6Q=; b=M4eda8zIN+kaCcU6edWUZUSvD/2VlMTwfa/3KWOYvsE7JeBzkfWRIVrIf5xs1DI7Kh ZN/MS6cyQ2zG7yAeHrnTwnMrmdWp15fwi0+lAe1ZxTguasGUrsQqNTXCiQZPi1GCcla4 Up84J1/a10cMc1Ovq9a81ZV7rGyfmiE7hnQmZpQPa1Wr7eCsJu4TV7NTmLvSRDP2gJ88 HtLGRgYkAcjmi+YE524EEndPfekydRFodFxiAnwMQYSv4SGFUPc9D2Vk5RSnLC0jKpqI 3exkyUXeISXDkTnWrJJUPO7WhgkeB3/JE2k8tA7qFrf5CM3aMRZU6Sl4LqmfwE0GVAdW 8pzQ== X-Gm-Message-State: APjAAAXbzUr5fNMpQFiWbxyN7IAkWna+JJDhKYPu2qMNYHs6F2vouGcU 7T0ZrG0dkho/SvLvaYbWaelFfs5WSMT3YR0F0Cw= X-Google-Smtp-Source: APXvYqyR0ybZtJiikv+kwAVgdY7AWb/vcdMGH7sI0c/nWNAyYF6Ch2IHDX6ee2DH+0Mm7f0lXuO3Rk/bCGgW2RweGT4= X-Received: by 2002:a1c:e487:: with SMTP id b129mr23317012wmh.93.1566837626850; Mon, 26 Aug 2019 09:40:26 -0700 (PDT) MIME-Version: 1.0 References: <20190822205533.4877-1-david.abdurachmanov@sifive.com> <20190826145756.GB4664@cisco> In-Reply-To: <20190826145756.GB4664@cisco> From: David Abdurachmanov Date: Mon, 26 Aug 2019 09:39:50 -0700 Message-ID: Subject: Re: [PATCH v2] riscv: add support for SECCOMP and SECCOMP_FILTER To: Tycho Andersen Cc: Paul Walmsley , Palmer Dabbelt , Albert Ou , Oleg Nesterov , Kees Cook , Andy Lutomirski , Will Drewry , Shuah Khan , Alexei Starovoitov , Daniel Borkmann , Martin KaFai Lau , Song Liu , Yonghong Song , David Abdurachmanov , Thomas Gleixner , Allison Randal , Alexios Zavras , Anup Patel , Vincent Chen , Alan Kao , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org, me@carlosedp.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kselftest-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kselftest@vger.kernel.org On Mon, Aug 26, 2019 at 7:57 AM Tycho Andersen wrote: > > Hi, > > On Fri, Aug 23, 2019 at 05:30:53PM -0700, Paul Walmsley wrote: > > On Thu, 22 Aug 2019, David Abdurachmanov wrote: > > > > > There is one failing kernel selftest: global.user_notification_signal > > > > Also - could you follow up with the author of this failing test to see if > > we can get some more clarity about what might be going wrong here? It > > appears that the failing test was added in commit 6a21cc50f0c7f ("seccomp: > > add a return code to trap to userspace") by Tycho Andersen > > . > > Can you post an strace and a cat of /proc/$pid/stack for both tasks > where it gets stuck? I don't have any riscv hardware, and it "works > for me" on x86 and arm64 with 100 tries. I don't have the a build with SECCOMP for the board right now, so it will have to wait. I just finished a new kernel (almost rc6) for Fedora, but it will take time to assemble new repositories and a disk image. There is older disk image available (5.2.0-rc7 kernel with v2 SECCOMP) for QEMU or libvirt/QEMU: https://dl.fedoraproject.org/pub/alt/risc-v/disk-images/fedora/rawhide/20190703.n.0/Developer/ https://fedoraproject.org/wiki/Architectures/RISC-V/Installing#Boot_with_libvirt (If you are interesting trying it locally.) IIRC I attempted to connected with strace, but it quickly returns and fails properly. Simply put strace unblocks whatever is stuck. david