Re: gfp flags for security_inode_alloc()?
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Wed, Mar 28, 2012 at 01:22:17PM +0900, Tetsuo Handa wrote: > security_inode_alloc() is called from inode_init_always(). > inode_init_always() is called from xfs_inode_alloc(). .... > Therefore, should SMACK use GFP_NOFS like SELinux does? Yes, because you have no idea what the calling context is except for the fact that is from somewhere inside filesystem code and the filesystem could be holding locks. Therefore, GFP_NOFS is really the only really safe way to allocate memory here. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux Ext4 Filesystem] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Photo] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [CEPH Filesystem]