From: syzbot <syzbot+25317a459958aec47bfa@syzkaller.appspotmail.com>
To: brauner@kernel.org
Cc: brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] general protection fault in pidfs_free_pid
Date: Tue, 24 Jun 2025 01:45:35 -0700 [thread overview]
Message-ID: <685a65af.050a0220.2303ee.0008.GAE@google.com> (raw)
In-Reply-To: <20250624-serienweise-bezeugen-0f2a5ecd5d76@brauner>
> On Mon, Jun 23, 2025 at 11:27:26AM -0700, syzbot wrote:
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 5d4809e25903 Add linux-next specific files for 20250620
>> git tree: linux-next
>> console+strace: https://syzkaller.appspot.com/x/log.txt?x=150ef30c580000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=58afc4b78b52b7e3
>> dashboard link: https://syzkaller.appspot.com/bug?extid=25317a459958aec47bfa
>> compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a5330c580000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12c9f6bc580000
>>
>> Downloadable assets:
>> disk image: https://storage.googleapis.com/syzbot-assets/16492bf6b788/disk-5d4809e2.raw.xz
>> vmlinux: https://storage.googleapis.com/syzbot-assets/7be284ded1de/vmlinux-5d4809e2.xz
>> kernel image: https://storage.googleapis.com/syzbot-assets/467d717f0d9c/bzImage-5d4809e2.xz
>>
>> The issue was bisected to:
>>
>> commit fb0b3e2b2d7f213cb4fde623706f9ed6d748a373
>> Author: Christian Brauner <brauner@kernel.org>
>> Date: Wed Jun 18 20:53:46 2025 +0000
>>
>> pidfs: support xattrs on pidfds
>>
>> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15a1b370580000
>> final oops: https://syzkaller.appspot.com/x/report.txt?x=17a1b370580000
>> console output: https://syzkaller.appspot.com/x/log.txt?x=13a1b370580000
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+25317a459958aec47bfa@syzkaller.appspotmail.com
>> Fixes: fb0b3e2b2d7f ("pidfs: support xattrs on pidfds")
>
> #syz test:
>
> #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs-6.17.pidfs
Command #1:
want either no args or 2 args (repo, branch), got 4
next prev parent reply other threads:[~2025-06-24 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 18:27 [syzbot] [fs?] general protection fault in pidfs_free_pid syzbot
2025-06-24 0:55 ` Hillf Danton
2025-06-24 2:23 ` syzbot
2025-06-24 8:44 ` Christian Brauner
2025-06-24 8:45 ` Christian Brauner
2025-06-24 8:45 ` syzbot [this message]
2025-06-24 9:23 ` Christian Brauner
2025-06-24 10:39 ` syzbot
2025-06-24 10:52 ` 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=685a65af.050a0220.2303ee.0008.GAE@google.com \
--to=syzbot+25317a459958aec47bfa@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.