linux/mm/madvise.c

3  *	linux/mm/madvise.c
938 			 * operation may not cause madvise() to
1261 /* Does the madvise operation result in discarding of mapped data? */
1279  * We are restricted from madvise()'ing mseal()'d VMAs only in very particular
1283  * only do so via an appropriate madvise() call.
1305 	 * However, in order to avoid issues with potential use of madvise(...,
1329  * Apply an madvise behavior to a region of a vma.  madvise_update_vma
1430 	 * madvise() returns EAGAIN if kernel resources, such as
1630 	 * If VMA read lock is supported, apply madvise to a single VMA
1816  * @start:	Start address of madvise-requested address range.
1817  * @len_in:	Length of madvise-requested address range.
1818  * @behavior:	Requested madvise behavor.
1891  * The madvise(2) system call.
1893  * Applications can use madvise() to advise the kernel how it should
1985 SYSCALL_DEFINE3(madvise, unsigned long, start, size_t, len_in, int, behavior)
1990 /* Perform an madvise operation over a vector of addresses and lengths. */
2020 		 * An madvise operation is attempting to restart the syscall,