From: Richard Weinberger <richard@nod.at>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Cengiz Can <cengiz.can@canonical.com>,
Attila Szasz <szasza.contact@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Salvatore Bonaccorso <carnil@debian.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
lvc-patches@linuxtesting.org, dutyrok@altlinux.org,
syzbot+5f3a973ed3dfb85a6683@syzkaller.appspotmail.com,
stable <stable@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key
Date: Tue, 8 Apr 2025 17:58:20 +0200 (CEST) [thread overview]
Message-ID: <168561308.256760721.1744127900601.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20250408145053.GJ6266@frogsfrogsfrogs>
----- Ursprüngliche Mail -----
> Von: "Darrick J. Wong" <djwong@kernel.org>
>> IMHO guestmount and other userspace filesystem implementations should
>> be the default
>> for such mounts.
>
> Agree. I don't know if they (udisks upstream) have any good way to
> detect that a userspace filesystem driver is available for a given
> filesystem. Individual fuse drivers don't seem to have a naming
> convention (fusefat, fuse2fs) though at least on Debian some of them
> seem to end up as /sbin/mount.fuse.$FSTYPE.
>
> guestmount seems to boot the running kernel in qemu and use that? So I
> guess it's hard for guestmount itself even to tell you what formats it
> supports? I'm probably just ignorant on that issue.
Yes, libguestfs runs a Linux kernel inside. It support qemu, UserModeLinux
and IIRC it had even a PoC for LKL (Linux Kernel Library).
That said, the performance is not optimal but I'm sure with reasonable
effort it could be improved at lot.
At least to work with odd filesystem in a satisfying way.
Thanks,
//richard
next prev parent reply other threads:[~2025-04-08 15:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 19:13 [PATCH] hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key Vasiliy Kovalev
2025-03-20 19:30 ` Salvatore Bonaccorso
2025-03-24 16:14 ` Cengiz Can
2025-03-24 16:17 ` Greg KH
2025-03-24 18:43 ` Cengiz Can
2025-03-24 18:53 ` Greg KH
2025-04-06 16:07 ` Cengiz Can
2025-04-06 16:28 ` Greg KH
2025-04-07 10:59 ` Christian Brauner
2025-04-07 17:15 ` Christian Brauner
2025-04-07 17:29 ` Attila Szasz
2025-04-07 19:08 ` Darrick J. Wong
2025-04-08 10:11 ` Richard Weinberger
2025-04-08 14:50 ` Darrick J. Wong
2025-04-08 15:58 ` Richard Weinberger [this message]
2025-04-16 15:10 ` Eric Sandeen
2025-04-08 8:03 ` Greg KH
2025-04-08 12:00 ` Attila Szasz
2025-03-27 19:15 ` Attila Szasz
2025-04-07 17:25 ` Christian Brauner
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=168561308.256760721.1744127900601.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=brauner@kernel.org \
--cc=carnil@debian.org \
--cc=cengiz.can@canonical.com \
--cc=djwong@kernel.org \
--cc=dutyrok@altlinux.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-patches@linuxtesting.org \
--cc=richard.weinberger@gmail.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+5f3a973ed3dfb85a6683@syzkaller.appspotmail.com \
--cc=szasza.contact@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).