| 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
| ||
|
Date: Wed, 12 Nov 2008 18:30:10 +0900 From: Tejun Heo <tj@...nel.org> To: Christoph Hellwig <hch@...radead.org> CC: Miklos Szeredi <miklos@...redi.hu>, fuse-devel@...ts.sourceforge.net, greg@...ah.com, linux-kernel@...r.kernel.org Subject: Re: [PATCHSET] FUSE: extend FUSE to support more operations Christoph Hellwig wrote: > On Wed, Nov 12, 2008 at 05:41:18PM +0900, Tejun Heo wrote: >>> emulated char devices to be char devices? What I mean is, what would >>> happen if instead of a char device /dev/dsp would be a regular file >>> mounted on /dev/dsp (which implements all the necessary interfaces: >>> ioctls, poll, etc)? >> For most it would work, I suppose, but there are all sorts of wonky >> users out in the wild (and quite a few that we don't have source access >> to) and different configurations, so I think it's better to appear as >> proper character device if it is a character device. It will also help >> udev and other desktop thingies deal with devices implemented in userland. > > Note that mounting a char device on /dev/dsp is exactly the same as > mounting a regular file on /dev/dsp - the only difference is what you > set i_mode to. A difference is how the device is located. With proper character device emulation, any char device node on any filesystem would work. Not sure how relevant that would be tho. Thanks. -- tejun -- 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