[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d981504-3e32-eb70-4f93-7d897b8f9be4@suse.cz>
Date: Tue, 24 Oct 2017 17:19:41 +0200
From: Vlastimil Babka <vbabka@...e.cz>
To: James Bottomley <James.Bottomley@...senPartnership.com>,
Thorsten Leemhuis <regressions@...mhuis.info>,
John Johansen <john.johansen@...onical.com>,
Seth Arnold <seth.arnold@...onical.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: regression in 4.14-rc2 caused by apparmor: add base infastructure
for socket mediation
On 10/24/2017 01:03 PM, James Bottomley wrote:
> On Tue, 2017-10-24 at 08:39 +0200, Thorsten Leemhuis wrote:
>> Lo, your friendly regression tracker here!
>>
>> On 03.10.2017 09:17, John Johansen wrote:
>>>
>>> On 10/02/2017 11:48 PM, Vlastimil Babka wrote:
>>>>
>>>> On 10/03/2017 07:15 AM, James Bottomley wrote:
>>>> Hm, but if this was because opensuse kernel and apparmor rules
>>>> relied on an out-of-tree patch, then it's not an upstream
>>>> regression?
>>> While its true that previous opensuse kernels were relying on an
>>> out of tree patch for doing mediation in this area, the real issue
>>> is the configuration of the userspace on the system is setup to
>>> enforce new policy features advertised by the kernel. Regardless of
>>> whether policy has been updated to deal with it.
>>
>> Did anything came out of this discussion?
>
> Not really, no. I've got the patch reverted locally, so it's not
> causing *me* problems anymore.
openSUSE tumbleweed was fixed already and IIRC the maintainer also said
that Leap would be fixed as well, even though 4.14 is not an official
kernel. You could check whether the apparmor-profiles package was
updated yet on your version...
Powered by blists - more mailing lists