From: John Johansen <john.johansen@canonical.com>
To: Alexander Potapenko <glider@google.com>
Cc: apparmor@lists.ubuntu.com, jmorris@namei.org, john@apparmor.net,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
serge@hallyn.com, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [apparmor?] linux-next test error: WARNING in apparmor_unix_stream_connect
Date: Wed, 30 Jul 2025 03:17:52 -0700 [thread overview]
Message-ID: <2a6074ec-59ca-49af-87e8-d468cffc4a87@canonical.com> (raw)
In-Reply-To: <CAG_fn=WSae7yjaHh=_iUc7eFALHX1vLQFMw8ryfas4-ijgFTiQ@mail.gmail.com>
On 7/28/25 01:16, Alexander Potapenko wrote:
> On Mon, Jul 21, 2025 at 11:35 AM syzbot
> <syzbot+cd38ee04bcb3866b0c6d@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following issue on:
>
> John, do you have an idea what's going on?
> This is pretty likely to be related to your "apparmor: make sure unix
> socket labeling is correctly updated." patch.
yeah it is being caused by that patch. Specifically it introduces using
security_sk_alloc() to make sure the sk is given a default label which
makes this check now incorrect the fix is just to drop the check. I have
added the fix with the syzbot ref
prev parent reply other threads:[~2025-07-30 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 9:35 [syzbot] [apparmor?] linux-next test error: WARNING in apparmor_unix_stream_connect syzbot
2025-07-28 8:16 ` Alexander Potapenko
2025-07-30 10:17 ` John Johansen [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=2a6074ec-59ca-49af-87e8-d468cffc4a87@canonical.com \
--to=john.johansen@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=glider@google.com \
--cc=jmorris@namei.org \
--cc=john@apparmor.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=sfr@canb.auug.org.au \
--cc=syzkaller-bugs@googlegroups.com \
/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