What are these changes supposed to do? commit aa29a06fd0c6113560f2c5e3e9630fe67b097ba7 Author: J. R. Okajima <hooano...@yahoo.co.jp> Date: Tue Jun 12 22:08:17 2012 +0900
aufs: for 3.5-rcN, new au_security_file_mmap() 1/2
commit ad02614f68494af290af54325895091917a6b7c7
Author: J. R. Okajima <hooano...@yahoo.co.jp>
Date: Tue Jun 12 22:08:39 2012 +0900
aufs: for 3.5-rcN, call au_security_file_mmap() 2/2
An earlier change for 3.5 added this comment, which was removed by the
second commit above:
/* todo: the locking order between mmap_sem */
/*
* err = security_mmap_file(h_file, au_prot_conv(vma->vm_flags),
* au_flag_conv(vma->vm_flags));
*/
Did lockdep report that an mmap_sem and some other lock (needed by an
LSM) were not taken in the usual order? If so, moving the
security_mmap_file() into another thread (workqueue) won't solve the
possible deadlock, though it may well hide it from lockdep.
Ben.
--
Ben Hutchings
73.46% of all statistics are made up.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
