[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c5336d2f-bb63-1799-f4c0-effc11048998@gnuweeb.org>
Date: Wed, 13 Jul 2022 16:37:32 +0700
From: Ammar Faizi <ammarfaizi2@...weeb.org>
To: John Johansen <john.johansen@...onical.com>,
Matthew Wilcox <willy@...radead.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Ammar Faizi <ammarfaizi2@...weeb.org>,
Al Viro <viro@...iv.linux.org.uk>,
James Morris <jmorris@...ei.org>,
LSM List <linux-security-module@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kees Cook <keescook@...omium.org>,
linux-fsdevel@...r.kernel.org, Linux-MM <linux-mm@...ck.org>,
GNU/Weeb Mailing List <gwml@...r.gnuweeb.org>
Subject: Re: Linux 5.18-rc4
On 6/22/22 3:27 AM, John Johansen wrote:
> 99cc45e48678 apparmor: Use an IDR to allocate apparmor secids
>
> but I would like some other peoples opinions on doing that, because we
> don't understand why we are getting the current lock splat, and without
> understanding it is a fix by avoiding the issue rather than being sure
> the actual issue is fixed.
Update from me:
I can't reproduce the splat in 5.19.0-rc4. Not sure if it's already
fixed though, since it happened randomly and I didn't realize what
action provoked the splat. I am running Ubuntu 22.04 for my daily
desktop activity.
I'll keep my lockdep on and will send you update if it's still
triggering.
--
Ammar Faizi
Powered by blists - more mailing lists