mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul@paul-moore.com>,
	syzbot <syzbot+044fdf24e96093584232@syzkaller.appspotmail.com>
Cc: audit@vger.kernel.org, eparis@redhat.com, jmorris@namei.org,
	john.johansen@canonical.com, linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org, serge@hallyn.com,
	syzkaller-bugs@googlegroups.com,
	Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [syzbot] [audit?] general protection fault in smack_log_callback
Date: Thu, 19 Sep 2024 09:37:11 -0700	[thread overview]
Message-ID: <1a38172e-ef03-4a87-9200-cfbe20c3bb77@schaufler-ca.com> (raw)
In-Reply-To: <CAHC9VhRpDPTopxgOEbDt1d_XyDVNzaA7++6UojWXidbpBHjeVA@mail.gmail.com>

On 9/19/2024 9:05 AM, Paul Moore wrote:
> On Thu, Sep 19, 2024 at 9:23 AM syzbot
> <syzbot+044fdf24e96093584232@syzkaller.appspotmail.com> wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit:    bdf56c7580d2 Merge tag 'slab-for-6.12' of git://git.kernel..
>> git tree:       upstream
>> console output: https://syzkaller.appspot.com/x/log.txt?x=12584b00580000
>> kernel config:  https://syzkaller.appspot.com/x/.config?x=4540f5bcdd31e3de
>> dashboard link: https://syzkaller.appspot.com/bug?extid=044fdf24e96093584232
>> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=155cffc7980000
>> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16ad24a9980000
>>
>> Downloadable assets:
>> disk image: https://storage.googleapis.com/syzbot-assets/cec9f3c675f1/disk-bdf56c75.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/21e06ae5b159/vmlinux-bdf56c75.xz
>> kernel image: https://storage.googleapis.com/syzbot-assets/1e936c954b8b/bzImage-bdf56c75.xz
>>
>> The issue was bisected to:
>>
>> commit 5f8d28f6d7d568dbbc8c5bce94894474c07afd4f
>> Author: Casey Schaufler <casey@schaufler-ca.com>
>> Date:   Wed Jul 10 21:32:26 2024 +0000
>>
>>     lsm: infrastructure management of the key security blob
>>
>> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1124d69f980000
>> final oops:     https://syzkaller.appspot.com/x/report.txt?x=1324d69f980000
>> console output: https://syzkaller.appspot.com/x/log.txt?x=1524d69f980000
> I just posted a patch which I believe should fix the problem, but I'd
> like to get Casey's ACK on it before submitting upstream as it does
> touch Smack code; lore link below:

Thanks for jumping on this. Your build and test cycle is faster than mine.

>
> https://lore.kernel.org/linux-security-module/20240919155740.29539-2-paul@paul-moore.com
>
> .. in the meantime, I'm attaching the patch here so syzbot can verify
> that it solves the problem.
>
> #syz test
>

  reply	other threads:[~2024-09-19 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 13:23 syzbot
2024-09-19 16:05 ` Paul Moore
2024-09-19 16:37   ` Casey Schaufler [this message]
2024-09-19 19:37   ` syzbot

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=1a38172e-ef03-4a87-9200-cfbe20c3bb77@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=audit@vger.kernel.org \
    --cc=eparis@redhat.com \
    --cc=jmorris@namei.org \
    --cc=john.johansen@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.com \
    --cc=syzbot+044fdf24e96093584232@syzkaller.appspotmail.com \
    --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

all inboxes | Powered by JetHome®