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: Thu, 30 Oct 2008 18:43:01 +0100 From: Miklos Szeredi <miklos@...redi.hu> To: stern@...land.harvard.edu CC: miklos@...redi.hu, rjw@...k.pl, linux-kernel@...r.kernel.org, ncunningham@...a.org.au, linux-pm@...ts.linux-foundation.org Subject: Re: [linux-pm] Freezer: Don't count threads waiting for frozen filesystems. On Thu, 30 Oct 2008, Alan Stern wrote: > Okay. Don't forget things like ioctl for sockets -- they often involve > doing I/O directly to the network interface device. Yeah, ioctls should probably just always be protected (at least initially), regardless of what type of file they are done on. > What happens to a task accessing a non-regular file on a fuse > filesystem? :-) The same as on any other filesystem, i.e. the fs is only involved as far as calling init_special_inode(), the rest is taken care of by the VFS. Tejun Heo recently posted patches to fuse which enable emulating a char device from userspace. That is another matter, obviously we'd want to keep the "allow suspend during I/O" property of fuse in that case, even though there's a char device involved (but no hardware, at least not on that level). 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