fs/proc/task_mmu.c: fix buffer overflow in add_page_map()
authoryonghua zheng <younghua.zheng@gmail.com>
Tue, 13 Aug 2013 23:01:03 +0000 (16:01 -0700)
committerBen Hutchings <ben@decadent.org.uk>
Tue, 10 Sep 2013 00:57:23 +0000 (01:57 +0100)
commitbd20948dc24c3a1cf5ea18385943783f11c2c751
treed923ca4e6741961b6c94709517162528d9ce7be8
parent1cf253ee0a4a3102a1dc89a3001abb31a8b60c00
fs/proc/task_mmu.c: fix buffer overflow in add_page_map()

commit 8c8296223f3abb142be8fc31711b18a704c0e7d8 upstream.

Recently we met quite a lot of random kernel panic issues after enabling
CONFIG_PROC_PAGE_MONITOR.  After debuggind we found this has something
to do with following bug in pagemap:

In struct pagemapread:

  struct pagemapread {
      int pos, len;
      pagemap_entry_t *buffer;
      bool v2;
  };

pos is number of PM_ENTRY_BYTES in buffer, but len is the size of
buffer, it is a mistake to compare pos and len in add_page_map() for
checking buffer is full or not, and this can lead to buffer overflow and
random kernel panic issue.

Correct len to be total number of PM_ENTRY_BYTES in buffer.

[akpm@linux-foundation.org: document pagemapread.pos and .len units, fix PM_ENTRY_BYTES definition]
Signed-off-by: Yonghua Zheng <younghua.zheng@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
[bwh: Backported to 3.2:
 - Adjust context
 - There is no pagemap_entry_t definition; keep using u64]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
fs/proc/task_mmu.c