From: David Howells <dhowells@redhat.com>
To: syzbot <syzbot+c0dc46208750f063d0e0@syzkaller.appspotmail.com>
Cc: dhowells@redhat.com, Dominique Martinet <asmadeus@codewreck.org>,
jlayton@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netfs@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfs?] kernel BUG in folio_unlock (3)
Date: Wed, 26 Feb 2025 08:41:53 +0000 [thread overview]
Message-ID: <2453211.1740559313@warthog.procyon.org.uk> (raw)
In-Reply-To: <67b75198.050a0220.14d86d.02e2.GAE@google.com>
syzbot <syzbot+c0dc46208750f063d0e0@syzkaller.appspotmail.com> wrote:
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141b4ba4580000
I'm not sure how this would even work.
memcpy((void*)0x4000000001c0, "syz\000", 4);
memcpy((void*)0x400000000480, "./file0\000", 8);
memcpy((void*)0x4000000004c0, "9p\000", 3);
memcpy((void*)0x400000000c00,
"\x56\xc7\x8e\x3c\x73\x3d\x76\x69\x72\x74\x69\x6f\x2c\x6e\x6f\x65\x78"
"\x74\x65\x6e\x64\x2c\x61\x63\x63\x81\x73\x73\x3d\x61\x6e\x79\x2c\x63"
"\x61\x63\x68\x65\x3d\x66\x73\x63\x61\x63\x68\x65\x2c\x76\x65\x72\x73"
"\x69\x6f\x6e\x3d\x39\x70\x32\x30\x30\x30\x2e\x75",
63);
syscall(__NR_mount, /*src=*/0x4000000001c0ul, /*dst=*/0x400000000480ul,
/*type=*/0x4000000004c0ul, /*flags=*/0ul, /*opts=*/0x400000000c00ul);
The options string is rubbish:
[pid 8084] mount("syz", "./file0", "9p", 0, "V\307\216<s=virtio,noextend,acc\201ss=any,cache=fscache,version=9p2000.u") = -1 EINVAL (Invalid argument)
David
next prev parent reply other threads:[~2025-02-26 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 16:00 syzbot
2025-02-20 16:15 ` Matthew Wilcox
2025-02-20 22:05 ` Dominique Martinet
2025-02-21 23:35 ` Hillf Danton
2025-02-21 23:58 ` syzbot
2025-02-26 8:41 ` David Howells [this message]
2025-05-31 23:20 ` syzbot
2025-06-01 0:26 ` Matthew Wilcox
2025-06-11 14:08 ` Aleksandr Nogikh
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=2453211.1740559313@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=asmadeus@codewreck.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=syzbot+c0dc46208750f063d0e0@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
all inboxes | Powered by JetHome®