From: syzbot <syzbot+2208f82282740c1c8915@syzkaller.appspotmail.com>
To: amir73il@gmail.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [overlayfs?] general protection fault in ovl_encode_real_fh
Date: Mon, 02 Oct 2023 21:56:33 -0700 [thread overview]
Message-ID: <000000000000fb84850606c8b688@google.com> (raw)
In-Reply-To: <00000000000056dad80606c447e0@google.com>
syzbot has bisected this issue to:
commit 16aac5ad1fa94894b798dd522c5c3a6a0628d7f0
Author: Amir Goldstein <amir73il@gmail.com>
Date: Sun Apr 23 16:02:04 2023 +0000
ovl: support encoding non-decodable file handles
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11972062680000
start commit: 8a749fd1a872 Linux 6.6-rc4
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13972062680000
console output: https://syzkaller.appspot.com/x/log.txt?x=15972062680000
kernel config: https://syzkaller.appspot.com/x/.config?x=57da1ac039c4c78a
dashboard link: https://syzkaller.appspot.com/bug?extid=2208f82282740c1c8915
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14877eb2680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13b701f6680000
Reported-by: syzbot+2208f82282740c1c8915@syzkaller.appspotmail.com
Fixes: 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-10-03 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 23:39 [syzbot] [overlayfs?] general protection fault in ovl_encode_real_fh syzbot
2023-10-03 4:56 ` syzbot [this message]
2023-10-03 7:45 ` Amir Goldstein
2023-10-03 8:06 ` 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=000000000000fb84850606c8b688@google.com \
--to=syzbot+2208f82282740c1c8915@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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.