From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,NO_DNS_FOR_FROM, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from [192.168.88.254] (unknown [125.163.212.174]) by gnuweeb.org (Postfix) with ESMTPSA id A329F7E257; Wed, 13 Jul 2022 09:37:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1657705068; bh=57SLDvvXl7rAug93QDj0lqPFPcMCMvcdhau9G4XvILU=; h=Date:To:Cc:References:From:Subject:In-Reply-To:From; b=IIgI5xu30CTTbc0kQQGgSjypt0Hk5DiHNiL/CQqUKg2f1xwjVTQJvrayg3lEvY1Ky pLGGFNJx+DrsdLyTmBh7iqFipkB7+XXjMfZRkcI0rjy7bXEpYt8/3IlQYPigzcdeMj /M/Gnrk8M/3ytApnaizbieBLjX1mA/WsB8cYdUZgoivbx8x4TKNGq5sziF14bkWpZC pWPmXO0sBDZIoRDfhNU+xzFIJF90xQzZ0NsNnqPbDZM+ZYpjboO9mf9oktmoV3mwYq lS2wQ7Zr+MICXCtX0p1Iv2R+zZXHR44HmyUKIl0Se5Kwk0xKrQqKY8h4sSYLMUFAJC h4CHGGibu/s3g== Message-ID: Date: Wed, 13 Jul 2022 16:37:32 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Content-Language: en-US To: John Johansen , Matthew Wilcox Cc: Linus Torvalds , "Eric W. Biederman" , Ammar Faizi , Al Viro , James Morris , LSM List , Linux Kernel Mailing List , Kees Cook , linux-fsdevel@vger.kernel.org, Linux-MM , GNU/Weeb Mailing List References: <226cee6a-6ca1-b603-db08-8500cd8f77b7@gnuweeb.org> <87r1414y5v.fsf@email.froward.int.ebiederm.org> <266e648a-c537-66bc-455b-37105567c942@canonical.com> From: Ammar Faizi Subject: Re: Linux 5.18-rc4 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: 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