Fwd: Question on vma_operations readpages and locking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux