From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751417AbdJAREz (ORCPT <rfc822;w@1wt.eu>);
        Sun, 1 Oct 2017 13:04:55 -0400
Received: from mout.gmx.net ([212.227.15.15]:55300 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751093AbdJAREy (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 1 Oct 2017 13:04:54 -0400
Message-ID: <1506877383.5529.1.camel@gmx.de>
Subject: Re: How to verify linux-next
From: Mike Galbraith <efault@gmx.de>
To: Randy Dunlap <rdunlap@infradead.org>,
        Damian Tometzki <damian.tometzki@icloud.com>,
        Pintu Kumar <pintu.ping@gmail.com>, "Theodore Ts'o" <tytso@mit.edu>,
        Valdis Kletnieks <valdis.kletnieks@vt.edu>,
        linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org
Date: Sun, 01 Oct 2017 19:03:03 +0200
In-Reply-To: <649f4bab-608d-9422-f2c3-401038c036c3@infradead.org>
References: <CAOuPNLik8AiWiBXokFAVpbnFxdLz8T+2wZPWfWLn-F+piAHCSw@mail.gmail.com>
         <CAOuPNLgtf6cbU7JHn5-w00EyEz9k6cS5d+n7FfP1fVTYRKpQmw@mail.gmail.com>
         <CAOuPNLgFUgo0Cbbfu_96R3FHUL5VRnZq+-FMYJQ8XB8NLS_Djg@mail.gmail.com>
         <159555.1506688878@turing-police.cc.vt.edu>
         <1506690885.1771.6.camel@icloud.com>
         <CAOuPNLj_TXmULGXOEg0iMy_77u4OoLuU4Nx6xxRpOEk8prc9dQ@mail.gmail.com>
         <20170929215007.kpea2kan6hg7jzcw@thunk.org>
         <CAOuPNLhaApVJBB0Wk7xcF7QF5orT_U2qzccE_VakX9p28im8eg@mail.gmail.com>
         <20170930052530.rf7bcwe3o327sobe@thunk.org>
         <CAOuPNLj0v1GqCzs_twO8rLREBh0yXq22LbJrxri-eFmbjehEmg@mail.gmail.com>
         <1506876289.2536.2.camel@icloud.com>
         <649f4bab-608d-9422-f2c3-401038c036c3@infradead.org>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.20.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:p7SvgQZlChrcvfjFY7OiCcuTcGjFjp6g6/UZBLbo/nEbiTEFslz
 QPQWntR5cKnpkIwalD9S8WpSy9VfBZpsLncMuX6/aSyee2IxceHDwz1uc61WQQgry2hYKMY
 eceBWID38LVwfdV77JBuGaijQOu/6CEEwhIA6hCS0THALQsoke24TykGAMk5FZo/B0U1Y3q
 UfSCCEkVYy0V78UylrrWg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Pp3EI0qwsBg=:4F55MfQWZruT63QDBfG1aU
 7BiavaNfsR2iQ7yah1qkwHRq05lRFeHJlwB5ekmsTGflRtKOJlMCeSn+V7cuqoO9Dj37oC32B
 I5XYxqpq0Tw3ZjjSngzDHmuhwhWREToXV915iawBwNGEZceyuPOAwrKC+RObTrl5CZV8hyT8m
 SjhRD51xceCfltwA9tDbOPZVSSvcoeKmWFj0PgX33YUfohAgeuCTw8B7HoZxEUQGsanrdxacI
 f/6cGUunyglMI9PsTFWWVm/k3wRJm13wwnRsLz3Mhwxto0HI9ejzRNBckgN9bsAVvfqK4qkQq
 tx/0EpzcSwg1VBAlg3hRCd/2RKmBc0+1gTv6Ih7RcyJPGcaXVcqfOKUhZHwyceKpRGgmaGFCJ
 mJ/iiadkmjWEGImUxrrDNTDMEcOJnyBMaC+sDbQMcIVuuqnR/Mf+GnWSJNddAxehvu+IMgH9B
 MAW8CU/lKMDNkcPt628DGWyPfpX73W/DPzOgLso0ABsH2+r3qN+4j5vZmesveeANi8Od9f/KU
 AZPb7324ltHr0+th0rcDHO5xKsptEYxDt5NNzrbERD0dZo58GyK0tC7is7rT+RdjgVah6qQSz
 Kc3p3KVwckGWxWTzbl+M91R4Ev+vH2h489BYKHkU/6hALr71ZpSZLZ+f0s1XMuTYSQQ5JY+nD
 73Tkak/I51z9l1GrCfZHB/E5zH0OlyoXVqCGfgxNzSeSZkSrNrkRdU5Knz387ck3lQHD1gL66
 NkF6RSLpMPe4+xKHT63KU3tRwhg2nh1LxPL0QWmWETKe0ei6lfxag8f1VrX6rHIBwlTBc3O7N
 XZK8JCoZ8TX3XrYjC2lLOfYRuZt6pr2i49a7zW8U8Igy6rSjzU=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun, 2017-10-01 at 09:48 -0700, Randy Dunlap wrote:
> On 10/01/17 09:44, Damian Tometzki wrote:
> 
> > i resolved the issue with:
> > sudo /etc/init.d/apparmor stop
> 
> or boot with: apparmor=0

or systemctl mask apparmor