| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <E1KpjF2-0007jD-B4@pomaz-ex.szeredi.hu> Date: Tue, 14 Oct 2008 14:43:12 +0200 From: Miklos Szeredi <miklos@...redi.hu> To: szaka@...s-3g.org CC: miklos@...redi.hu, tj@...nel.org, fuse-devel@...ts.sourceforge.net, greg@...ah.com, linux-kernel@...r.kernel.org Subject: Re: [fuse-devel] [PATCHSET] FUSE: extend FUSE to support more operations On Tue, 14 Oct 2008, Szabolcs Szakacsits wrote: > On Tue, 14 Oct 2008, Miklos Szeredi wrote: > > > I still got qualms about this ioctl thing. One is the security > > aspect, but that could be dealt with. The other is that I really > > really don't want people to start implementing new custom ioctls for > > their filesystems, as I think that way lies madness. We could limit > > ioctls to CUSE and that would be fine with me. Or for non-CUSE users > > we could enforce the "standard" format where the type and length is > > encoded in the command number. > > Is this enough to support the most useful/requested file system ioctls, > like FIEMAP? Looking at FIEMAP patches... No, FIEMAP doesn't seem fit in that category. But FIEMAP has a specific handler, so it would not get as far as the generic ioctl handler anyway. If we need FIEMAP support in fuse, that will need to be handled independently of the generic ioctls (just like FIBMAP). Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists