Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <3c63e34b-e54f-9b01-bad4-8fde8528a64d@linux.microsoft.com>
In-Reply-To: <3c63e34b-e54f-9b01-bad4-8fde8528a64d@linux.microsoft.com>
From:   Paul Moore <paul@paul-moore.com>
Date:   Sat, 3 Apr 2021 10:33:15 -0400
Message-ID: <CAHC9VhTD2iXw7CkxgwnOx1zNN_AqMV+x1Vy8FijdMQE1m4AOJA@mail.gmail.com>
Subject: Re: [BUG] Oops in sidtab_context_to_sid
To:     Vijay Balakrishna <vijayb@linux.microsoft.com>,
        Tyler Hicks <tyhicks@linux.microsoft.com>,
        Ondrej Mosnacek <omosnace@redhat.com>
Cc:     Stephen Smalley <stephen.smalley.work@gmail.com>,
        selinux@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Fri, Apr 2, 2021 at 6:35 PM Vijay Balakrishna
<vijayb@linux.microsoft.com> wrote:
>
> Seeing oops in 5.4.83 sidtab_context_to_sid().  I checked with Tyler (copied),  he said it might be
>
> https://lore.kernel.org/selinux/CAFqZXNu8s5edDbSZuSutetTsy58i08vPuP2h-n9=kT34HcPc4w@mail.gmail.com/
>
> Ondrej, can you confirm?  Unfortunately, we don't have a on demand repro.

I'm guessing this may be the problem that Tyler reported earlier and
which appeared to be fixed by the patch below:

https://lore.kernel.org/selinux/20210318215303.2578052-3-omosnace@redhat.com

... which was merged into Linus' tree during the v5.12-rcX development
phase, any chance you could try that patch to see if it resolves your
issue?  There are still some issues to be sorted out, but if you
aren't reloading policy it shouldn't be a concern.

Tyler, since both of you are at Microsoft, do you have a patched
kernel that Vijay could try?

-- 
paul moore
www.paul-moore.com