From: Leo Stone <leocstone@gmail.com>
To: syzbot+35a21b6aade7af3c7b3a@syzkaller.appspotmail.com
Cc: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [f2fs?] WARNING in f2fs_delete_entry
Date: Mon, 25 Nov 2024 10:18:10 -0800 [thread overview]
Message-ID: <20241125181810.190792-1-leocstone@gmail.com> (raw)
In-Reply-To: <6740a00c.050a0220.363a1b.0144.GAE@google.com>
This is the same exact image as in:
https://syzkaller.appspot.com/bug?extid=b01a36acd7007e273a83
This is the diff of the reproducers:
diff --git a/repro_f2fs_86.c b/repro_f2fs_arm.c
index e9473a9..b96d52f 100644
--- a/repro_f2fs_86.c
+++ b/repro_f2fs_arm.c
@@ -1,4 +1,4 @@
-// https://syzkaller.appspot.com/bug?id=ce049cbd95a443ac6ed3f6f4bad09498d3692995
+// https://syzkaller.appspot.com/bug?id=64df843cec772943672cee2084811aa72fd41ff8
// autogenerated by syzkaller (https://github.com/google/syzkaller)
#define _GNU_SOURCE
@@ -24,7 +24,13 @@
#include <linux/loop.h>
#ifndef __NR_memfd_create
-#define __NR_memfd_create 319
+#define __NR_memfd_create 279
+#endif
+#ifndef __NR_mmap
+#define __NR_mmap 222
+#endif
+#ifndef __NR_unlinkat
+#define __NR_unlinkat 35
#endif
static unsigned long long procid;
#syz dup: WARNING in f2fs_unlink
next prev parent reply other threads:[~2024-11-25 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 15:15 [syzbot] [f2fs?] WARNING in f2fs_delete_entry syzbot
2024-11-24 1:37 ` [syzbot] " syzbot
2024-11-25 18:18 ` Leo Stone [this message]
[not found] <20241124013441.23975-1-leocstone@gmail.com>
2024-11-24 2:03 ` 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=20241125181810.190792-1-leocstone@gmail.com \
--to=leocstone@gmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+35a21b6aade7af3c7b3a@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