Re: [PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

2013-04-05 Thread Naoya Horiguchi
On Fri, Apr 05, 2013 at 02:32:08PM -0400, KOSAKI Motohiro wrote: > (4/3/13 2:35 PM), Naoya Horiguchi wrote: > > Currently we fail to include any data on hugepages into coredump, > > because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently > > introduced by commit 314e51b98 "mm:

Re: [PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

2013-04-05 Thread KOSAKI Motohiro
(4/3/13 2:35 PM), Naoya Horiguchi wrote: > Currently we fail to include any data on hugepages into coredump, > because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently > introduced by commit 314e51b98 "mm: kill vma flag VM_RESERVED and > mm->reserved_vm counter". This looks to me

Re: [PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

2013-04-05 Thread KOSAKI Motohiro
(4/3/13 2:35 PM), Naoya Horiguchi wrote: Currently we fail to include any data on hugepages into coredump, because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently introduced by commit 314e51b98 mm: kill vma flag VM_RESERVED and mm-reserved_vm counter. This looks to me a

Re: [PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

2013-04-05 Thread Naoya Horiguchi
On Fri, Apr 05, 2013 at 02:32:08PM -0400, KOSAKI Motohiro wrote: (4/3/13 2:35 PM), Naoya Horiguchi wrote: Currently we fail to include any data on hugepages into coredump, because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently introduced by commit 314e51b98 mm: kill vma

Re: [PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

2013-04-03 Thread Rik van Riel
On 04/03/2013 02:35 PM, Naoya Horiguchi wrote: Currently we fail to include any data on hugepages into coredump, because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently introduced by commit 314e51b98 "mm: kill vma flag VM_RESERVED and mm->reserved_vm counter". This looks to me

[PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

2013-04-03 Thread Naoya Horiguchi
Currently we fail to include any data on hugepages into coredump, because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently introduced by commit 314e51b98 "mm: kill vma flag VM_RESERVED and mm->reserved_vm counter". This looks to me a serious regression, so let's fix it. ChangeLog

[PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

2013-04-03 Thread Naoya Horiguchi
Currently we fail to include any data on hugepages into coredump, because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently introduced by commit 314e51b98 mm: kill vma flag VM_RESERVED and mm-reserved_vm counter. This looks to me a serious regression, so let's fix it. ChangeLog

Re: [PATCH v3 1/3] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB)

2013-04-03 Thread Rik van Riel
On 04/03/2013 02:35 PM, Naoya Horiguchi wrote: Currently we fail to include any data on hugepages into coredump, because VM_DONTDUMP is set on hugetlbfs's vma. This behavior was recently introduced by commit 314e51b98 mm: kill vma flag VM_RESERVED and mm-reserved_vm counter. This looks to me a