From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: John Johansen <john.johansen@canonical.com>,
Matthew Wilcox <willy@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Al Viro <viro@zeniv.linux.org.uk>,
James Morris <jmorris@namei.org>,
LSM List <linux-security-module@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-fsdevel@vger.kernel.org, Linux-MM <linux-mm@kvack.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>
Subject: Re: Linux 5.18-rc4
Date: Wed, 13 Jul 2022 16:37:32 +0700 [thread overview]
Message-ID: <c5336d2f-bb63-1799-f4c0-effc11048998@gnuweeb.org> (raw)
In-Reply-To: <cd2a4ea4-52d2-cf95-7769-859b0a35b564@canonical.com>
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
prev parent reply other threads:[~2022-07-13 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=whmtHMzjaVUF9bS+7vE_rrRctcCTvsAeB8fuLYcyYLN-g@mail.gmail.com>
2022-04-27 17:59 ` Linux 5.18-rc4 Ammar Faizi
2022-04-27 18:31 ` Linus Torvalds
[not found] ` <87r1414y5v.fsf@email.froward.int.ebiederm.org>
2022-06-06 18:28 ` Linus Torvalds
2022-06-06 19:19 ` John Johansen
2022-06-06 19:47 ` Linus Torvalds
2022-06-06 20:23 ` Matthew Wilcox
2022-06-06 21:00 ` John Johansen
2022-06-13 22:48 ` Matthew Wilcox
2022-06-21 20:27 ` John Johansen
2022-07-13 9:37 ` Ammar Faizi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c5336d2f-bb63-1799-f4c0-effc11048998@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=ebiederm@xmission.com \
--cc=gwml@vger.gnuweeb.org \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).