From: syzbot <syzbot+94891a5155abdf6821b7@syzkaller.appspotmail.com>
To: aivazian.tigran@gmail.com, amir73il@gmail.com,
andrew.kanner@gmail.com, kovalev@altlinux.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-unionfs@vger.kernel.org, miklos@szeredi.hu,
stable@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] BUG: unable to handle kernel NULL pointer dereference in __lookup_slow (3)
Date: Wed, 08 Jan 2025 12:42:04 -0800 [thread overview]
Message-ID: <677ee31c.050a0220.25a300.01a2.GAE@google.com> (raw)
In-Reply-To: <0000000000003d5bc30617238b6d@google.com>
syzbot suspects this issue was fixed by commit:
commit c8b359dddb418c60df1a69beea01d1b3322bfe83
Author: Vasiliy Kovalev <kovalev@altlinux.org>
Date: Tue Nov 19 15:58:17 2024 +0000
ovl: Filter invalid inodes with missing lookup function
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14ef4dc4580000
start commit: 20371ba12063 Merge tag 'drm-fixes-2024-08-30' of https://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d806687521800cad
dashboard link: https://syzkaller.appspot.com/bug?extid=94891a5155abdf6821b7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1673fcb7980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15223467980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ovl: Filter invalid inodes with missing lookup function
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-01-08 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 8:01 [syzbot] [overlayfs?] BUG: unable to handle kernel NULL pointer dereference in __lookup_slow (3) syzbot
2024-09-03 22:39 ` [syzbot] retest overlayfs-next syzbot
2024-09-29 0:45 ` [syzbot] retest bfs fix, please syzbot
2025-01-08 20:42 ` syzbot [this message]
2025-01-09 11:33 ` [syzbot] [overlayfs?] BUG: unable to handle kernel NULL pointer dereference in __lookup_slow (3) Miklos Szeredi
2025-01-09 13:13 ` Miklos Szeredi
2025-01-09 13:13 ` syzbot
[not found] <66d79038.170a0220.22e970.97fd@mx.google.com>
2024-09-04 7:04 ` syzbot
[not found] <66f8a340.170a0220.2c5856.ac87@mx.google.com>
2024-09-29 1:32 ` 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=677ee31c.050a0220.25a300.01a2.GAE@google.com \
--to=syzbot+94891a5155abdf6821b7@syzkaller.appspotmail.com \
--cc=aivazian.tigran@gmail.com \
--cc=amir73il@gmail.com \
--cc=andrew.kanner@gmail.com \
--cc=kovalev@altlinux.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stable@vger.kernel.org \
--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 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.