From: syzbot <syzbot+78359d5fbb04318c35e9@syzkaller.appspotmail.com>
To: activprithvi@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_del_inode_from_orphan
Date: Sun, 22 Feb 2026 19:51:05 -0800 [thread overview]
Message-ID: <699bcea9.050a0220.340abe.0d36.GAE@google.com> (raw)
In-Reply-To: <20260223033802.13422-1-activprithvi@gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
fs/ocfs2/aops.c:2426:11: error: use of undeclared identifier 'ENOTSUP'
Tested on:
commit: c22e26bd Merge tag 'landlock-7.0-rc1' of git://git.ker..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=6428d17febdfb14e
dashboard link: https://syzkaller.appspot.com/bug?extid=78359d5fbb04318c35e9
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1332395a580000
next parent reply other threads:[~2026-02-23 3:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260223033802.13422-1-activprithvi@gmail.com>
2026-02-23 3:51 ` syzbot [this message]
[not found] <a7w3563ajutp2yexhvpwdntif75zuyxn76yezxs7sa5r4fgbzg@ro7v6isoyp4e>
2026-03-02 5:53 ` [syzbot] [ocfs2?] possible deadlock in ocfs2_del_inode_from_orphan syzbot
[not found] <dvzyokzoiuibgprc7aoz5myhf4ml7w44swrwclqnpxwybckjdl@kvmw645tetpv>
2026-02-24 7:00 ` syzbot
[not found] <oh26fpojbfgcs5gljzjz4vaqlqloz7wqnhlmdmlqzwnrvk7uyr@cxa3ek5uiy6t>
2026-02-24 5:46 ` syzbot
[not found] <20260223035943.22844-1-activprithvi@gmail.com>
2026-02-23 4:56 ` syzbot
2026-01-06 11:30 Syzbot test for ocfs2: Fix " Prithvi Tambewagh
2026-01-06 11:59 ` [syzbot] [ocfs2?] possible " syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-10-03 2:18 syzbot
2024-12-19 8:16 ` 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=699bcea9.050a0220.340abe.0d36.GAE@google.com \
--to=syzbot+78359d5fbb04318c35e9@syzkaller.appspotmail.com \
--cc=activprithvi@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox