| 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: Tue, 3 Sep 2013 14:16:24 -0400 From: Milosz Tanski <milosz@...in.com> To: linux-kernel@...r.kernel.org Subject: Question on vma_operations readpages and locking Can anyone help me reason about the readpages() callback in vma_operations? Do the pages that come in the argument list from readahead come locked? The documentation in the kernel says nothing about locking on the way in (Documentation/filesystems/Locking) unlike readpage. It does say that the pages should be unlocked when the operation is done. Should I assume that the readpages implementer needs to take care to lock those pages her / his self? I've been reading through the code for different filesystems to understand what should happen but I'm not a 100% clear on it. Thanks in advance, - Milosz -- 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