pagewalk: add locking-rule comments

Originally, walk_hugetlb_range() didn't require a caller take any lock.
But commit d33b9f45bd ("mm: hugetlb: fix hugepage memory leak in
walk_page_range") changed its rule.  Because it added find_vma() call in
walk_hugetlb_range().

Any locking-rule change commit should write a doc too.

[akpm@linux-foundation.org: clarify comment]
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Hiroyuki Kamezawa <kamezawa.hiroyuki@gmail.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: Matt Mackall <mpm@selenic.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

path: root/changelog

inotail 0.3

  * Follow files even if they were moved
  * Fix a problem when tailing more than 4096 bytes/chars at once
  * Only print the filename once when the -v option is specified
  * Various small fixes and cleanups

  -- Tobias Klauser <tklauser@distanz.ch> 2007-03-28 12:20

inotail 0.2

  * Support for the -n/-c +<num> options (tail relative to start of file)
  * Copyright and license cleanup
  * Various fixes

  -- Tobias Klauser <tklauser@distanz.ch.ch> 2006-11-30 17:56