summaryrefslogtreecommitdiffstats
path: root/include/linux/gfp.h
diff options
context:
space:
mode:
authorJoonsoo Kim <js1304@gmail.com>2012-12-12 13:51:53 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2012-12-12 17:38:33 -0800
commit2897b4d29d9fca82a57b09b8a216a5d604966e4b (patch)
tree0b6efa9f80c4115949cc3d26eaddfd3e7031bbae /include/linux/gfp.h
parent44e33e8f95171b93968c3ac3cf8516998b1db65d (diff)
downloadlinux-stable-2897b4d29d9fca82a57b09b8a216a5d604966e4b.tar.gz
linux-stable-2897b4d29d9fca82a57b09b8a216a5d604966e4b.tar.bz2
linux-stable-2897b4d29d9fca82a57b09b8a216a5d604966e4b.zip
mm: WARN_ON_ONCE if f_op->mmap() change vma's start address
During reviewing the source code, I found a comment which mention that after f_op->mmap(), vma's start address can be changed. I didn't verify that it is really possible, because there are so many f_op->mmap() implementation. But if there are some mmap() which change vma's start address, it is possible error situation, because we already prepare prev vma, rb_link and rb_parent and these are related to original address. So add WARN_ON_ONCE for finding that this situtation really happens. Signed-off-by: Joonsoo Kim <js1304@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/gfp.h')
0 files changed, 0 insertions, 0 deletions